What need to be considered when moving the CA 7 Checkpoint Dataset to a different Volume or Device?
Release: 12.0 and 12.1 (THIS PROCEDURE IS NOT VALID FOR CA 7 r11.3)
Component: 7, WA CA 7 Edition
When moving the Checkpoint Dataset to a different volume, or Device, CA 7 needs to be down. You should then start CA 7 with a TYPE: CKPT. The CKPT will then be reinitialized and the following will occur:
To avoid resetting the schedule counter, you should perform the the move directly after schedule scan last activated to avoid resetting the counter.
Here are the recommended procedure for moving CA 7 stc files to a different device. The main file of focus is the CHECKPOINT (CKPT).
1. Issue CA 7 command: SSCAN (take a screen shot)
2. Dump the current log and to do this issue the /SWAP command in CA 7. Once the log dump job complete you can go to the next step
3. Stop CA 7
4. Move all files over to new dasd
5. Change the CA 7 init deck set the following to options:
RUNOPT=NSTA (this will disable schedule scan at startup)
STOPQ=YES (this will stop the queues at startup)
6. Start CA 7 and you must do a TYPE=CKPT startup
S ca7,TYPE=CKPT
7. When CA 7 starts all the "checkpoint" values in the checkpoint data set are reset.
8. Issue CA 7 commands to verify and set schedule scan.
- SSCAN should show the following
STATUS: REQQ IS STOPPED
RDYQ IS STOPPED
NEXT SCAN WAKE-UP = 99999 AT 3679
NEXT SCAN PERIOD START TIME = 00000 AT 0000
9. Issue CA 7 command to set the NEXT SCAN PERIOD START TIME to the time from the SSCAN output in step # 1
SSCAN,DATE=20203,PERSTART=1300
10. Issue CA 7 command: SSCAN to verify the NEXT SCAN PERIOD START TIME is correct.
11. If #9 is ok, you can start schedule scan with command:
SSCAN,SCAN=SCH
12. Check the queues to see if all jobs look good. If so, you can start the queues using command:
START,Q=ALL