Creating, Converting or Extending The Security File › TSSXTEND JCL

TSSXTEND JCL

Use the following JCL to copy the contents of the old Backup File into the new Security File. Use the Backup File, and not the current Security File, as input to TSSXTEND. Otherwise, changes made to the current Security File during the execution of TSSXTEND could corrupt the new Security File. If you do need to copy the current Security File, replace COPY BACKUP in the sample below, with COPY SECURITY.

//TSSJOB ACID=mscaacid,PASSWORD=mscapass
//EXEC  PGM=TSSXTEND
COPY BACKUP
OLDKEY=xxxxxxxxxxxxxxx
NEWKEY=xxxxxxxxxxxxxxx
NEWDSN=new.file.data set.name
NEWPWBLOCK**OPTIONAL**

Notes:

• 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.
• This job can only be submitted using the MSCA’s ACID.
• NEWKEY card is always required. If you are not changing the Security File encryption key, then the NEWKEY and OLDKEY fields must be identical.
• The OLDKEY and NEWKEY fields must be 16‑character hexadecimal values. The first 8 characters of an encryption key cannot be identical to the last 8 characters. There can be no embedded commas or spaces, and comments cannot be placed on these fields.
• Use the optional NEWPWBLOCK keyword to add mixed case password support to the security file. If the security file will be shared with a previous release of CA Top Secret, do not use the NEWPWBLOCK keyword until you verify that the previous release supports NEWPWBLOCK. For information, contact CA Support.

Important! Safeguard your key.