Scheduling the Production turnover for batch systems might be different than for online systems. The job, APJJ5320, that actually performs the Production moves is typically run daily. APJJ5320 should also run during a time when a System Administrator can immediately review the output from the moves.
This review of move output is frequently done during prime shift hours. For batch systems, this prime shift move of new programs for each application might be appropriate timing. For online systems, however, the timing might not be appropriate. The online systems might stay up late or run continuously.
Changes for the online transactions might not be appropriate until the next day. If new programs are moved into Production Libraries while the online systems are up, they might take effect immediately, or at least might take effect after an online restart. Therefore, we recommend that the PROD set of CA‑PanAPT libraries (primarily the load libraries) for online systems be next‑day libraries or that a special Move Type be used for online Move Processing Cycles.
CA‑PanAPT moves to the next‑day libraries during prime shift. An additional job is scheduled daily to copy from the next‑day libraries to the Production online libraries after the online terminates for that day's processing. Job APJJNEXT is supplied as a sample job to perform the next‑day Prod moves to online libraries.
You can include this processing in the online JCL as part of start‑up or shutdown. Alternatively, you can submit JCL similar to APJJNEXT from a model as external processing. Schedule the external processing job for a time appropriate to the target library.
This, or a similar technique, is suggested for any library type that has unique scheduling considerations.
|
Copyright © 2004 CA.
All rights reserved.
|
|