

Creating, Converting or Extending The Security File › Move the Security File
Move the Security File
Note: If you are sharing the security file between MVS and VM and the security file under MVS has been created with the AESENCRYPT option, the security file can no longer be shared between MVS and VM.
To move the Security File from one system or device to another
- If the Security File is already accessible on z/VM (for example, it is shared with a z/OS system and you want to create a separate Security File on z/VM, or it is a 3380 DASD device and you want to move it to a 3390), skip to Step 3.
- If the Security File exists on a z/OS system, and you want to create a separate Security File on z/VM, with no shared DASD between the systems, use DFDSS or DDR to backup to tape the entire pack containing the Security File. Then, use the same utility to restore the pack on z/VM. Define this pack (a full‑pack minidisk) as 200 in the CA Top Secret server's directory entry.
- If you have a Backup File on z/VM, skip to Step 4. If you do not have a Backup File:
- Create a new Backup File. (Follow the instructions in Creating the New Security File.)
- Enter:
TSS MODIFY(SHUTDOWN)
- Enter the data set name of the new Backup File in the Parameter File on the CA Top Secret server's 100 disk. Re‑(X)AUTOLOG the server to refresh the directory.
- Enter:
TSS MODIFY(BACKUP).
A copy of the Security File is created.
- Enter:
TSS MODIFY(BACKUP(OFF))
The BACKUP function does not interfere with TSSXTEND.
- Follow the instructions in Creating the New Security File, to create a new Security File and copy the contents of the Backup File.
Copyright © 2013 CA.
All rights reserved.
 
|
|