In this section: |
You need two CMS minidisks or SFS directories to contain the FOCUS product. We refer to them as the FOCUS maintenance and production CMS locations. If you use minidisks they should be formatted with a blocksize of 4096 bytes. If you use SFS directories, the FOCUS production directory should be a DIRCONTROL directory.
The system programmer must include a Machine XC statement in each user's directory entry if they will be accessing FOCUS from a SFS directory.
The maintenance disk is the CMS minidisk (or SFS directory) onto which you unload the FOCUS distribution cartridge. Initially this disk or directory should be empty and you should not store any other files on it.
You must have different maintenance disks or directories for different FOCUS releases. This is a critical requirement. You may generate a defective copy of FOCUS if you load a maintenance cartridge for one release onto the maintenance disk of another release. When you phase out an older FOCUS release and want to reuse its maintenance disk or directory for the next release, you must erase all the files on it. A simple way to do that is to use the CMS FORMAT command; it erases all the files on the disk and at the same time assigns a CMS label to it. Although you can label this disk any way you like, we suggest a name such as FMnnnn, where nnnn is the FOCUS release signature. For example, FM7603 is a good descriptive name for the maintenance disk for FOCUS 7.6.3.
The maintenance disk or directory should not be accessed by FOCUS users. This makes it possible to do the greater part of FOCUS maintenance and new release testing while end users are still using the current production release.
After installation, the production CMS minidisk or SFS directory contains an executable copy of FOCUS. This is the disk that all FOCUS users must access when they invoke FOCUS. The disk contains all files necessary for execution of the FOCUS version that you have installed. Most of the files on this disk are created by the CMS EXECs that create the installed version of FOCUS, for example FOCUS load modules, and the text of FOCUS error messages. You can add your own locally developed files, such as text of user-written subroutines, or CMS EXECs of interest to all FOCUS users. The set of files created by the FOCUS installation process on the production disk can vary from release to release.
As with the maintenance disk, the CMS label of the production disk is immaterial to FOCUS, but we suggest FOCUS as the label of the production disk of the current version of FOCUS to which all users should be linked by default. If you have more than one version of FOCUS installed, we suggest a descriptive label such as FCnnnn for the FOCUS production disk. Thus FC7603 is a good label for the production disk of FOCUS Version 7.6.3.
| Information Builders |