Previous Topic: 8. Select Move Request for Move to ProductNext Topic: Move Processing Cycles


9. Process Selected Move Requests for Product

Batch job APJJ5320 is run. First, APJJ5320 uses the CA‑PanAPT Modeling Facility to create the necessary JCL and control statements to perform the moves. It then executes PROC APJP5391 to initialize the status of each member of each Move Request. The status options are shown below:

M

Move has not completed

E

External Event required

S

External event has started processing (user-defined external processing, not set up as part of CA‑PanAPT)

M, E, or S can be set for a member.

Subsequent steps of APJJ5320 actually perform the moves, or you can schedule and run separate jobs according to your site's requirements. The last step of each PROC in APJJ5320 must execute program APCS5391 to update the status of each member processed for that PROC. In many cases, the PROC performs processing for a single Library Code. When all members in the Move Request have been moved successfully and marked Complete, APCS5391 changes the Move Request status.

If the Move Request is being moved to PROD, APJJ5320 sets the status of the Move Request to:

AMP Awaiting Production Moves

This indicates that Move Request members are processed later in APJJ5320. Some members still have M flags. External processing might be required for some members.

The Move Request status is not changed again until all members to be moved in APJJ5320 have been moved successfully. When all members in the Move Request have had their M flags removed, APCS5391 changes the Move Request status to:

AEP Awaiting Production External Processing.

This indicates that the Move Request is being moved to the Prod level. All member moves done as part of APJJ5320 have completed, but some of the members still require other external processing (indicated by E flags on the members). Some members show S flags, indicating that external processing has started for those members.

When all external processing for the Move Request is completed (all M, E, and S flags have been removed from the members), the Move Request status is set to:

MVP Moved to Production

This indicates that the Move Request has been moved to the Prod level, and processing is complete.

These subsequent APJJ5320 steps control the actual movement of the entities. The steps copy the current Production entities to the Backup library (optional), copy the entities from the QA or Test libraries to the Production Libraries, and then (optionally, depending on how the Library Code is set up) delete the copy from the QA or Test libraries.

At the end of APJJ5320, PROC APJP5395 updates the status of all Special Handling Move Requests to Complete. Note that Special Handling Move Requests have no members to move. APJP5395 lists the status of each Move Request that was originally selected. Report APCS5395‑02 lists the Library Codes for which processing did not complete normally (according to the return codes in the JCL).