APJJ5320 reads the cataloged file of moves passed from APJJ5310, sorts it, and uses the CA-PanAPT Modeling Facility to create the necessary JCL and control statements to perform the moves. APJJ5320 then executes PROC APJP5391 to initialize the status of each member of each Move Request. A status of E means that a model indicates that the member requires external processing (external to APJJ5320). A status of M means that the member is to be moved as part of APJJ5320. Either or both E and M can be set for a member. APJJ5320 then executes proc APJP5391 again to post the completion of any null moves you might have. Finally, APJJ5320 executes proc APJP5905 to submit the generated move job.
As the generated move job runs, APJP5391 posting steps are executed to update the status of the selected Move Requests. The statuses your selected Move Requests are in during or upon completion of the generate move job follow. These statuses contain the move level to which they pertain. This is indicated by the word level for the full status name and by the letter l for the short status code; level contains the 1 to 4 character short name for the level, and l contains the 1 to 2 character abbreviation for the level.
Awaiting level Moves. The Move Request is being moved. External processing might be required for some members.
Awaiting level Bkot. The Move Request is being backed out. 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.
If external processing is required, the Move Request status is set to:
Awaiting level EP. All moves are complete for the Move Request, but some of the members require external processing that is not complete. Some members have E flags (external processing is required) or S flags (external processing has started), but all M flags have been removed.
Awaiting level Bkot EP. All back out moves are complete for the Move Request, but some of the members require external processing that is not complete. Some members have E flags (external processing is required) or S flags (external processing has started), but all M flags have been removed.
When all processing for the Move Request is complete (all M, E, and S flags have been removed from the members), the Move Request status is set to:
Awaiting level App. The Move Request has been moved, and any external processing is complete. Some of the members required approvals or verifications for the next move level. The final move date has been propagated to the next move date field and should be reviewed.
Approved for level. The Move Request has been moved, and any external processing is complete. None of the members require approvals or verifications for the next move level, so the Move Request is eligible to be moved again on its new move date. The final move date has been propagated to the next move date field and should be reviewed.
Moved to level. The Move Request has been moved and there are no subsequent levels to be moved to. Processing is complete for this Move Request. The members of this Move Request are (or are at the end of the move job if still running) released or reassigned to other Move Requests. If they were reassigned, their assigned‑to users might change, depending on the value of the Reassign/Transfer flag in the Control File. For more information, see "Reassign/Release Processing" in the "Move Requests" chapter.
level Bkot Complete. The Move Request has been backed out. Processing is complete for this Move Request.
If processing for a Library Code did not complete normally, none of the members for that Library Code are posted as complete. You must review the execution of the steps for that Library Code in the listing of the move job.
At the end of APJJ5320, the generated move job proc APJP5395 produces several summary reports and updates the status of all Special Handling Move Requests to MVl (Moved to level). Note that Special Handling Move Requests have no members to move, so they are not updated by any of the member processing steps. The reports are:
Lists the status of each Move Request that was originally selected.
Lists the Library Codes for processing that did not complete normally (according to the return codes in the JCL).
|
Copyright © 2004 CA.
All rights reserved.
|
|