After the security file has become unusable, you can reestablish normal operation by running the product on a backup security file.
Note: To minimize downtime, this task can be performed by data center operations personnel (after obtaining proper authorization) during off-hours.
Follow these steps:
Note: Unless you need to operate by using the backup file for an extended period of time, you should activate only one CA Top Secret security system for recovery purposes in a shared security environment.
VMSERVER name
Note: Use the XAUTOLOG command when running in VM/XA or VM/ESA mode.
If your DOWN option is WAIT or FAIL, and you have difficulty, issue the command and execute the appropriate commands to disable additional terminal logons:
TSS MODIFY(DOWN(VN)) (or VB)
The procedure for restoring the backup file and/or minidisk varies, depending on your backup method. Typically, restoration involves using DDR or the standalone restore utility that is supplied with your DASD utility software. You might also want to include in your procedure the creation of a tape copy of the backup file before bringing up the server, to help prevent incorrect application of changes later.
Presumably, the server has logged itself off because of the failure. If not, use TSS MODIFY(SHUTDOWN) to deactivate security.
You can ask your VM systems programmer how this suboption is set.
XAUTOLOG server_ID
Specifies the VM user ID of the CA Top Secret for z/VM server (typically TSSVM).
The server should now IPL normally, with the addition of the following actions upon recognizing the BACKUP keyword:
Upon successful initialization, a message appears on the VM operator's console to confirm successful backup mode initialization. If necessary, you can now re-enable system logons (if previously disabled) and attain a reasonably normal level of system operation.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|