Previous Topic: Generated Moved JobsNext Topic: Online Report Facility

Batch Component › Restart Procedures for Move Jobs › When Status Posting Program (APCS5391) Halts

When Status Posting Program (APCS5391) Halts

CA‑PanAPT executes the Status Posting program (APCS5391) for a Library Code according to condition codes set by the programs that effect the member moves. Typically, if one member fails in a Library Code, the moving program sets a bad condition code. If that happens, APCS5391 does not execute for that Library Code and none of the members for the Library Code are posted. None of the Move Requests that contain these members can be marked complete.

It is possible for a Move Request to be complete, but not have a status of complete. To determine if a Move Request is complete, even though the status does not reflect it, use this procedure along with the Move Processing Summary report (APC55395‑01):

  1. Locate the Move Requests in question.
  2. Determine which members are not marked complete. (Status flags on each member indicates the member is not complete.)
  3. Determine the Library Codes to which they belong.
  4. Determine whether those members did, in fact, get moved. You can see the JCL and output of the move processing Job to see whether any members for that Library Code were moved.
  5. Ensure that processing has completed for all members of the Library Code. You might have to edit the input to some of the processing steps and resubmit the Job.
  6. When you know that all members have been moved, you can change the status using a CA‑PanAPT online activity. Or, you can run the posting program using the original input intended for the PROC that failed with a post type of M.

If the Move Processing Summary report is not available, you can determine the proper status of a Move Request using the CA‑PanAPT ISPF facilities.

  1. Using the Move Request Maintenance BRO function, select the appropriate status codes that allow you to monitor the Move Processing Cycle (SL, AM, AE, SL-B, AM-E, and AE-B for all of your move levels).
  2. Select the Move Requests in question by using the INQ function from the Browse Move Requests List panel.
  3. Determine whether any member in the Move Request has a status flag set.
  4. If all members have completed processing, use the Move Request Maintenance STA function to change the Move Request to whichever status is appropriate: Move to level‑name, Awaiting next‑level‑name App, Approved for next‑level‑name, or level‑name Bkot Complete.