Safeguard Administrator's Manual (G06.29+, H06.08+, J06.03+)

Installation and Management
Safeguard Administrator’s Manual—523317-029
10-7
Including the Safeguard Software in the OSIMAGE
File (D-Series RVUs)
Including the Safeguard Software in the OSIMAGE File (D-Series
RVUs)
To configure the Safeguard software in your CONFTEXT file, you must add the
Safeguard files OSMP and OSMON to the SYSTEM_PROCESS_CODE_FILES entry
of the ALLPROCESSORS paragraph. The entry should contain these definitions:
SYSTEM_PROCESS_CODE_FILES $dsv-vol.ZSAFEGRD.OSMON,
$dsv-vol.ZSAFEGRD.OSMP,
TANDEM^PROCESS^CODE^FILES;
where $dsv-vol is the name of the volume containing the ZSAFEGRD DSV.
If the Safeguard subsystem is included in the OSIMAGE file, it is started automatically
when the system is loaded, and it cannot be stopped without stopping the system.
If you include the Safeguard software in the OSIMAGE file or start the Safeguard
software as part of the CIIN file, you should keep another OSIMAGE file in a backup
SYSnn subvolume on $SYSTEM. This OSIMAGE file should not include either the
Safeguard software or a CIIN file. If necessary, you can use this backup SYSnn
subvolume to recover from an inadvertent security lockout without performing a tape
load.
If the Safeguard software is included in the OSIMAGE file, take these precautions to
prevent auditing from being suspended during a system load:
1. Before shutting down the system, ensure that the current audit pool resides on a
disk that is connected to the same processor as the $SYSTEM disk.
2. When the system load is complete, you can select a new audit pool on another
disk volume if necessary.
Starting the SMP
The Safeguard subsystem must be started manually if it is not included in your
OSIMAGE file. The local super ID starts the SMP by executing the OSMP file with a
command interpreter RUN command. The SMP process must be named $ZSMP.
Furthermore, $ZSMP should be in the same processor as $SYSTEM, and a backup
processor should be specified. The SMP is always started with a priority of 198,
regardless of any priority specified in the RUN command.
For example, if the Safeguard object files were stored in the current SYSnn subvolume
on $SYSTEM, which is configured between processors 3 and 4, the local super ID
starts the SMP with this TACL command:
2> OSMP/NAME $ZSMP, CPU 3, NOWAIT/4