Previous PageTable Of ContentsNext Page

    Upgrading to SafeSFS Release 1.2.0



This section describes how to upgrade to SafeSFS Release 1.2.0 from previous releases of SafeSFS.

Step 1:
Backup the SAFESFS 192 mdisk using your normal backup procedures.

Step 2:
Log on to the SafeSFS server machine.

Step 3:
Issue the command SAFESERV END to shutdown SafeSFS.

Step 4:
Issue the command SET SERVER OFF to disable the SafeSFS user interface.

Step 5:
Define and format a temporary mdisk (TDISK) large enough to contain 1500 4k blocks.

Step 6:
Use a PC file transfer program to upload the SAFE120.VMA file from the SafeSFS Diskette to the CMS file, SAFE120 VMARC, on the work mdisk. Perform the transfer in "Binary" mode.

Step 7:
Issue the command:
`PIPE < SAFE120 VMARC fm | FBLOCK 80 | > SAFE120 VMARC fm'
Where fm is the filemode of the work mdisk.

Step 8:
Run VMARC to unpack all of the files in the archive to the work disk. Issue the command `VMARC UNPK SAFE120 VMARC fm = = fm' to unpack the SafeSFS product files to the work mdisk accessed as file mode fm.

Note: The command `VMARC LIST SAFE120 VMARC fm' may be used to list the files in the archive.

Step 9:
Copy and replace all files from the work mdisk to the SAFESFS 192 mdisk. The work mdisk may now be discarded, if desired.

Step 10:
Obtain a write link to the PUBLIC mdisk that contains the SafeSFS user component files and access the mdisk.

Step 11:
Copy and replace the following files from the SafeSFS 192 mdisk to the PUBLIC mdisk from the previous step.
SAFESFS EXEC
$SAFESFS XEDIT
SAFESFSP REXX

Step 12:
Copy and replace the following files from the SafeSFS 192 mdisk to the SAFESFS DBA mdisk.
SAFESFS CSLLIB
SAFEESM SAFEEXEC - Rename to SAFEESM EXEC.

Step 13:
If SAFESFS program code from a previous release exists on the SAFESFS 191 mdisk it should be renamed. Any local modifications should be re-applied to a copy of the new version of the SAFESFS program code on the SAFESFS 191 mdisk.

Step 14:
XEDIT the SAFESFS CONTROL file on the SAFESFS DBA mdisk and insert the new SAFEPW that was supplied with your SafeSFS 1.2.0 Product Package.

Step 15:
Restart all SFS filepool servers that are controlled by SafeSFS.

Step 16:
Issue the command SET SERVER ON.

Step 17:
Issue the command SAFESERV INIT to restart SafeSFS.
Note: If you receive messages indicating there is duplicate files on the SAFESFS 191 mdisk it may indicate that there are files from an older release of SafeSFS that should be removed or renamed. See Step 13 above.

Step 18:
Perform the instructions in the section "Install SafeSFS Online HTML Documentation" earlier in this chapter.

To return to the previous release of SafeSFS, restore the SAFESFS 192 mdisk and repeat steps 10 through 17 above. Reverse the renames done in step 13, if any.

Previous PageTable Of ContentsNext Page