Issue /DISPLAY,DB=LOG. If on the primary log file, issue /SWAP and allow the primary log dump job to complete.
(Note: if you prefer to run the log dump jobs outside of CA 7 after shutting down that is also acceptable)
- If you expect CA 7 to be down for an extended time (a maintenance window for example), issue SSCAN and take note of the NEXT SCAN PERIOD START TIME. This may be needed after CA 7 comes back up.
- Issue /SHUTDOWN,Z4 or Z5 (twice). Both Z4 and Z5 perform a DMPQ. Whichever you choose to use is up to you. Details of both are documented in the Commands Reference Guide.
- After shutdown, ensure that you received the following message:
CA-7.937 CA-7 QUEUES SUCCESSFULLY UNLOADED
When ready to start 7 back up
- Update INIT file to turn off SSCAN and STOP the CA 7 queues:
Change INIT statement to RUNOPT=NSTA and add STOPQ=YES to the SCHEDULE statement.
- Start CA7 with the MOVQ - S CA7XXX,TYPE=MOVQ
(Note: if you have any automation that may override the MOVQ start up parameter, you should change the CA 7 proc to reflect the MOVQ instead)
- After the CA 7 restart completes, ensure that you received the following message:
CA-7.936 QUEUES SUCCESSFULLY RELOADED
- When you are ready to start normal processing in CA 7, be sure to set the time you want SSCAN to start from if the noted NEXT SCAN PERIOD START TIME has passed. To do so, issue the following CA7 commands:
(with the Julian date and time provided from the NEXT SCAN PERIOD START TIME on the SSCAN output above prior to shutting down)
Then issue SSCAN,SCAN=SCH to activate schedule scan :
- Start the CA 7 queues by issuing the CA 7 command: START,Q=ALL
(Note: be sure to change the INIT file values back to their normal startup values)
Note: DMPQ/MOVQ commands are no longer valid for CA7 r12.0 and above.