CA ACF2 for VM is automatically started (autologged) after VM system initialization has completed and a user other than OPERATOR or AUTOLOG1 tries to log on. Generally, this occurs when the disconnected service machines are being autologged through AUTOLOG1's PROFILE EXEC.
If CA ACF2 for VM is not active, VM is not usable because CA ACF2 for VM CP modules refuse all logons and data accesses. If this ever happens, a special
CA ACF2 for VM feature lets systems programmers log onto the system so that they can correct the problem. Users specified in the FORCEID operand of the VMXAOPTS macro can use this facility. See the Systems Programmer Guide for complete information about the VMXAOPTS macro.
These special users can log on and access data while CA ACF2 for VM is inactive if a system emergency has been declared. At the CA ACF2 for VM system initialization message, reply:
NOAUTO
Consider the example shown below.
ACFpgm000R Enter ACF2 startup options or press enter noauto
This response suppresses automatic startup of the CA ACF2 for VM service machine, letting only FORCEID users log on during the emergency. No one else can access the system. Also, activities that would normally require CA ACF2 for VM validation are automatically allowed for FORCEID users.
If NOAUTO=DIRPASS in the VMXAOPTS macro, FORCEID users must enter a valid directory password when they log on. The default setting of NOAUTO=NOPASS does not require a password. After you take corrective action, IPL the system again to resume normal operation and security controls. When CA ACF2 for VM is up and running, CA ACF2 for VM treats FORCEID users like any other user (access privileges are granted according to the user's logonid record privileges and CA ACF2 for VM access rules).
|
Copyright © 2009 CA Technologies.
All rights reserved.
|
|