Previous Topic: Selecting Special LogonidsNext Topic: Writing Access Rules


Defining User IDs for Emergencies

There are two attributes that can be defined to a logonid for emergency situations, FORCEID and NOAUTOU. The following describes each of these parameters.

What are FORCEIDs?

During implementation, you should also determine which logonids you should define with the FORCEID attribute. These IDs are very important. If CA ACF2 for z/VM ever becomes inoperable, only these FORCEIDs can access VM and make repairs to the system.

When a FORCEID user accesses CA ACF2 for z/VM in NOAUTO mode, CA ACF2 for z/VM does not validate the access other than to match that logonid to an internal list of FORCEID users. Normal CA ACF2 for z/VM password validation is not in effect. It is, therefore, very important to choose people with the FORCEID attribute very carefully. You define FORCEIDs in the FORCEID operand of the VMXAOPTS macros. The NOAUTO OPERAND of the VMXAOPTS macro controls whether the VM directory password is validated when a FORCEID logs on in NOAUTO mode. For more information about how to define FORCEIDs to your system, see the Installation Guide.

What are Noauto Update Users?

In addition to FORCEIDs, CA ACF2 for z/VM also provides a user ID that enables authorized users to log onto CA ACF2 for z/VM while it is inactive and update the databases. These users are called noauto update users. You must identify these user IDs with the NOAUTOU parameter in the VMXAOPTS macros. Only these special users can start up the CA ACF2 for z/VM service machine in NOAUTO mode and issue the appropriate ACF commands to update the CA ACF2 for z/VM databases. For a complete explanation of noauto update users and the ACFSERVE commands used to start the service machine in NOAUTO mode, see the Administrator Guide.