During the cycle of a CA‑PanAPT Move Request, the Move Request status indicates what events have occurred and what actions are required. Most of the 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 actually contains the 1 to 4 character short name for the level, and l contains the 1 to 2 character abbreviation for the level. The Move Request statuses are:
The request is being created and updated by the request originator. While in this status, the request can be updated, but it cannot be approved. The Move Request remains in this status until it is closed by an authorized user. The originator can enter data about the move and augment or change it over a period of time to avoid last minute rushes.
An authorized user closed the Move Request. If the Move Request includes any moves for levels before the one indicated in the status, those moves have been done. The Move Request includes at least one Library Code that has outstanding approvals to be granted or Verification procedures to be run for the specified level.
While it is in this status, authorized users can grant required approvals or run Verification procedures. The Move Request remains in this status until all approvals are granted and all Verification procedures run successfully. If the Move Request uses only Library Codes that do not require approvals or verifications for this level, then this status is bypassed entirely.
All required approvals have been granted and all required Verification procedures have run successfully for the current move level. This status is set by CA‑PanAPT when the last approval is granted and the last Verification procedure runs successfully. The Move Request remains in this status until CA‑PanAPT batch job APJJ5310 is run and selects the Move Request for movement.
Batch job, APJJ5310, has been run and has confirmed that this Move Request is to be processed. APJJ5310 selects Move Requests that:
The member restrictions that can be checked ensure that a Move Request doesn't get moved if it no longer has assignment of all of its members. It also ensures that the move is not attempted if the members to be moved are missing.
The daily move job has started, but has not completed processing of this Move Request. The daily move job changes the status of this Move Request when the last member has been processed.
The daily move job has started, but has not completed processing this Move Request. The models for at least one Library Code indicate that further processing is required. For example, the model could have built JCL for another job to run after the move, such as a compile and link. These jobs are considered external processing.
The external processing must be completed (in this example the compile and link must be submitted and run) before this Move Request is complete in site‑defined terms. The external processing job must include a step that invokes PROC APJP5391 to change the status of the Move Request to the next status.
The jobs to perform the required moves have been created and those jobs have completed successfully. There are no further move levels for any members because either none of the Library Codes used any subsequent levels or because this was an early stop level for the Move Request. The Move Request remains in this status until:
An authorized user has scheduled the Move Request to be backed out from the current move level's libraries. The Move Request uses at least one Library Code that requires Back Out Approvals at the current move level, and there is at least one outstanding Back Out Approval. While in this status, only authorized users can grant the required approvals. The Move Request remains in the status until all approvals for Back Out have been granted. If the Move Request uses only Library Codes that do not require Back Out Approvals for this move level, then this status is bypassed entirely.
All required Back Out Approvals have been granted, but Back Out processing has not begun. The Move Request is scheduled for Back Out and either the last Back Out Approval was granted, or there are not Back Out approvals required for the current move level. The Move Request remains in this status until CA‑PanAPT batch job APJJ5310 is run to select the Move Request to be processed.
Batch job, APJJ5310, has been run and has selected the Move Request for Back Out processing.
The daily move job, APJJ5320, has started but has not completed processing this Move Request for Back Out processing. The daily move job changes the status of this Move Request when the last member has been processed.
The daily move job has started, but has not completed Back Out processing this Move Request. The models for at least one Library Code indicate that further processing is required. For example, the model could have built JCL for another job to run after the move, such as a compile and link. These jobs are considered external processing.
The external processing must be completed (in this example the compile and link must be submitted and run) before this Move Request Back Out is complete in site‑defined terms. The external processing job must include a step that invokes PROC APJP5391 to change the status of the Move Request to the next status.
The jobs have been created to perform the Back Out and those jobs have completed successfully. The Move Request remains in this status until:
An authorized user has performed the Delete function against this Move Request. (The Delete function does not actually delete a Move Request, but flags the Move Request with a status of Delete.) A Move Request in this status cannot be updated or considered for Move selection processing. An authorized user can reset the status of a Deleted Move Request to Being Created.
|
Copyright © 2004 CA.
All rights reserved.
|
|