Safeguard Administrator's Manual (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- 2 Controlling User Access
- Introduction
- Using SAFECOM to Establish a Local User Community
- Using SAFECOM to Manage User Access to Your System
- Changing the Owner of a User Authentication Record
- Granting a User Temporary Access to Your System
- Requiring Users to Change Their Passwords
- Granting a Grace Period for Changing an Expired Password
- Forcing Immediate Expiration of a User’s Password
- Freezing a User's Ability to Access the System
- Specifying Auditing for a User ID
- Deleting Users
- Deleting Administrative Groups
- Using SAFECOM to Establish a Network of Users
- Using Safeguard With Nodes With Standard Security
- Identifying Network Users
- Granting a Network User Access to Objects on Your System
- Establishing a Community of Network Users
- Changes to the PAID During a User’s Session
- Additional Considerations for Aliases and Groups
- Additional Considerations for ACCESS with Network Specific Subject IDs
- Establishing Default Protection for a User's Disk Files
- Specifying a Default Command Interpreter for a User
- Establishing Guardian Defaults
- Assigning an Alias to a User
- 3 Managing User Groups
- 4 Securing Volumes and Devices
- 5 OBJECTTYPE Control
- 6 Managing Security Groups
- 7 Securing Terminals
- 8 Warning Mode
- 9 Configuration
- Safeguard Attributes
- Configuring User Authentication
- Configuring Password Control
- Configuring Device Control
- Configuring Process Control
- Configuring Disk-File Control
- Configuring Safeguard Auditing
- Configuring a Default Command Interpreter
- Configuring Communication With $CMON
- Configuring Logon Dialog
- Configuring Exclusive Access at Safeguard Terminals
- Configuring Warning Mode
- Configuring Persistence
- Configuring Attributes for Node Specific Subjects in ACLs
- 10 Installation and Management
- Safeguard Components
- Process Considerations for the SMP and SAFECOM
- Safeguard Subsystem Management Commands
- General Installation Procedure
- Installing the Safeguard Software
- Starting the SMP
- Converting to the Safeguard Subsystem
- Updating the Safeguard Software
- Guidelines for Securing the Safeguard Subsystem
- Monitoring the Safeguard Subsystem
- A SAFECOM Command Syntax
- Index
Installation and Management
Safeguard Administrator’s Manual—523317-013
10-7
Starting the SMP
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
This command is typically part of your CIIN or system startup files.
Note. Because the OSMP object program file contains PRIV code, it can only be run by the
super ID. If other users are to be allowed to start the SMP, the super ID must license the
OSMP and OSMON. For example:
VOLUME $SYSTEM.SYSnn
FUP LICENSE (OSMP, OSMON)