What are the procedures for re-allocating CA 7 files?
As a guideline when CA 7 files are moved, CA 7 can not be up. We suggest that a Z5 shutdown is done unless otherwise specified.
You can use JCLLIB member CA07N010 for sample DD statements (LOG files, queues, etc.) to reallocate the files. Be sure to change the space allocation if you want to make the files larger.
CA 7 Log files should only be moved when CA 7 is not running. Both log files must reside on the same volume.
Use the following procedure for the Log files:
CA 7 Queue and CKPTDS files should only be moved when CA 7 is inactive. The queue files and checkpoint files must reside on the same device type and with DSORG=PSU. Use the following procedure when moving or re-allocating queue files and/or the checkpoint file.
For additional information in regards to moving queue files, see the CA 7 product documentation:
The following files can all be copied using IEBGENER. If the communications data set is going to a different device type it has to be reformatted using the SASSCDSI program (see JCLLIB member CA07N700).
Batch Terminal Interface (BTI) BATCHIN and BATCHOUT Communications file (UCC7CMDS) Browse file (BROWSE) Statistics file (UCC7STAT)
Use the following procedure for the above files.
The database files (SASDS, SASIDS, SASJOB) can be moved with SASSBK00 (change the volume in DBPARMS) or IDCAMS. Please see additional information in the CA 7 documentation if the database files are managed by SMS or for additional SASSBK00 information.
ARF and VRM can be backed-up and restored using IDCAMS or procedures provided by CA 7. There are special considerations on backup and restore of these files (see the CA 7 documentation for special considerations).
Allocation information for each file is documented in the CA 7 product documentation.