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

Installation and Management
Safeguard Administrator’s Manual—523317-029
10-9
Converting to the Safeguard Subsystem
The SMP also starts the SMON processes. It uses this naming convention for the
SMON process names:
$ZS00 - SMON running in CPU 0
$ZS01 - SMON running in CPU 1
$ZS02 - SMON running in CPU 2
$ZS03 - SMON running in CPU 3
.
.
.
$ZSnn - SMON running in CPU nn
The SMP starts all the SMON processes with a priority of 199.
Converting to the Safeguard Subsystem
When the Safeguard software is installed on a system with an existing user community,
it takes over the existing USERID file. The next time each user logs on, his or her
record is expanded to contain security attributes, defined as:
•
OWNER is set to the user ID of the user's group manager. (For example, the
OWNER attribute for a person with a user ID of 4,56 is set to 4,255.) The
Safeguard software does not verify that a group manager exists. The
authentication records for users who belong to a group without a group manager
are owned by a nonexistent user.
•
PASSWORD does not change. (The user keeps the existing logon password.)
•
USER-EXPIRES is set to null. (The user's ability to log on to the system does not
expire.)
•
PASSWORD-MUST-CHANGE EVERY num DAYS is set to null. (The user's
password does not expire.)
•
AUDIT-ACCESS-PASS, AUDIT-ACCESS-FAIL, AUDIT-MANAGE-PASS, and
AUDIT-MANAGE-FAIL are all set to NONE. (No auditing is performed.)
•
REMOTEPASSWORD does not change. (All remote passwords currently defined
for a user are retained.)
•
DEFAULT-PROTECTION is not specified for a user's disk files. (Guardian
protection applies.)
Note.
•
The $SYSTEM.SAFE.SPTGUARD file is created when the SAVED-DISKFILE-PATTERN
protection record is created.
•
The $SYSTEM.SAFE.SPTGUARD file is supported only on systems running J06.10 and
later J-series RVUs and H06.21 and later H-series RVUs
.