Safeguard Management Programming Manual (G06.29+, H06.08+, J06.03+)

Safeguard Management Programming Manual—422086-028

3-1

Communicating With the Subsystem

This section describes how an application communicates with the Safeguard

subsystem through the Subsystem Control Point (SCP) or directly with the Safeguard

manager process $ZSMP. The Safeguard subsystem does not receive event

messages, but it does generate them. Section 8, Event Management, discusses event

messages.

For more information about the SCP, see the SPI Common Extensions Manual.

Startup Considerations

$ZSMP is the Safeguard process to which you send commands for managing the

Safeguard software and from which you receive responses. The local super ID starts

$ZSMP with a command interpreter RUN command.

For example, if the Safeguard object files were stored on the $SYSTEM.SYS05

subvolume, the local super ID could start $ZSMP with the following TACL RUN

command:

2>RUN $SYSTEM.SYS05.OSMP /NAME $ZSMP, NOWAIT,CPU 3/4

A backup SMP process must be specified in the RUN command. Otherwise the SMP

runs with no backup.

When $ZSMP is running, it automatically creates these files, if it does not already exist:

$ZSMP also starts the Security Monitor (SMON) processes. It uses the convention

$ZSnn for the SMON process names, where nn is the CPU number. The SMP starts

Note. The SMP process must be named as $ZSMP.

$SYSTEM.SAFE.GUARD Contains object-authorization records for all disk

objects (volumes, subvolumes, and disk files) on

$SYSTEM.

$SYSTEM.SAFE.OTHER Contains object-authorization records for all local

system objects other than disks (devices,

subdevices, processes, subprocesses, and

OBJECTTYPEs).

$SYSTEM.SAFE.CONFIG Contains the attributes that determine the

Safeguard configuration.

$SYSTEM.SAFE.CONFIGP

Contains password configuration information.

$SYSTEM.SAFE.CONFIGA Contains audit configuration information.

Supported only on systems running G06.29 and later G-series RVUs and H06.06 and later H-series RVUs