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
Configuration
Safeguard Administrator’s Manual—523317-013
9-19
Configuring a Default Command Interpreter
Configuring a Default Command Interpreter
When the Safeguard software controls a terminal, it automatically starts a particular
command interpreter (process) at that terminal each time a user logs on successfully at
the terminal. This command interpreter can also be specified in a user authentication
record and in a terminal definition record. If neither of these records contains a
command interpreter specification, the Safeguard software uses the command
interpreter (and its associated parameters) specified in the configuration record.
These attributes specify the command interpreter to be started at Safeguard terminals:
CI-PROG
Specifies the name of the command interpreter's object file. The file name must be
a local file name. The initial value for CI-PROG file is $SYSTEM.SYSTEM.TACL. A
null entry for CI-PROG sets the value to null. If the value of CI-PROG is null and no
CI-PROG is defined for the user or the terminal, a command interpreter is not
started at the terminal.
CI-LIB
Specifies the file name of the library to be used with the command interpreter. The
file name must be a local file name. The default is no library.
CI-SWAP
Specifies the name of the swap volume or file to be used with the command
interpreter. The volume must be a local volume. The default is same volume that
contains the command interpreter.
CI-CPU
Specifies the number of the processor in which the command interpreter is to run.
The default value is ANY, which means that any processor is used.
CI-PRI
Specifies the priority at which the command interpreter is to run. The initial value
for CI-PRI is 149. A null entry for CI-PRI sets the priority to null, and CI-PROG is
started with a priority the same as that of the Safeguard $ZSMP process.
CI-PARAM-TEXT
Specifies the startup parameter text to be supplied to the command interpreter
when it is started. The default is no parameter text.
To change any of these values, issue the ALTER SAFEGUARD command from
SAFECOM. For example, to specify that the command interpreter is to run in CPU 3
and that $DOOFUS2 is to be used as the swap volume:
=ALTER SAFEGUARD, CI-CPU 3, CI-SWAP $doofus2