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-10
Updating a Previous RVU With the Safeguard
Software Running
with previous product versions of the Safeguard software. Read this section carefully
before attempting to update your system from a previous Safeguard RVU.
Updating a Previous RVU With the Safeguard Software Running
If the Safeguard software must always be running, the following steps are suggested to
update your system from a previous RVU:
1. Bring all applications to an orderly shutdown, just as you would for a system load.
2. Rename the current Safeguard program files, and then load the new program files
from tape. If necessary, use the old program files to establish Safeguard security
for the new program files.
3. Perform all the steps normally taken to shut down a system.
4. Reset all processors, and perform a system load.
5. Start the Safeguard software normally. As the Safeguard software starts, it
determines that the audit trail file names do not exist, and creates these files, with
the correct size and structure. This is the key step in any changeover.
6. If Safeguard DDL files are used to build a DDL dictionary or to create precompiled
Enform queries, then build a new DDL dictionary and recompile those Enform
queries.
Updating a Previous RVU With the Safeguard Software Stopped
The main points to remember in replacing a previous RVU with the Safeguard software
stopped:
1. Stop the Safeguard software.
2. Restore the new program files.
3. Start the Safeguard software.
4. Make a new DDL dictionary if you use one.
Returning to a Previous RVU
To return to a previous RVU, follow the steps used to change over to this RVU, but use
the previous RVU's programs. Make a new DDL dictionary if you use one.
Note. Consult the softdoc for migration and fallback issues.