To run TSSXTEND, submit the following JCL to copy the contents of the old backup security file into the new security file:
//jobname JOB USER=msca only //EXTEND EXEC PGM=TSSXTEND //MAINTOUT DD SYSOUT=A //SECFOLD DD DSN=name.of.backup.security.file,DISP=SHR //SECFNEW DD DSN=name.of.new.security.file,DISP=SHR //*SECNVSM DD DSN=name.of.vsamfile,DISP=SHR for the output (new) VSAM dataset //*SECOVSM DD DSN=name.of.vsambackupfile,DISP=SHR for the incoming(old)VSAM backup file //MAINTIN DD * COPY SECURITY OLDKEY=???????????????? ENCRYPTION KEY OF OLD FILE NEWKEY=???????????????? ENCRYPTION KEY OF NEW FILE NEWPWBLOCK /*
Note: CA Top Secret r15 provides mixed-case password support by default when you run the TSSMAINT utility to initialize the security file. Therefore, you do not need to use the NEWPWBLOCK keyword when running TSSXTEND with an r15-formatted security file.
The OLDKEY and NEWKEY fields must be a 16‑character hexadecimal number. Comments cannot be added to these fields.
Important! Safeguard your key.
When you submit the JCL, the product executes the utility and indicates that the operation was successful.
Note: If the TSSXTEND utility does not execute successfully, use TSSMAINT to format the new security file again. For information about TSSXTEND abend codes, see the CA Top Secret Message Reference Guide.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|