PI61194: UNEXPECTED END OF JOB MAY CAUSE RESTART TO USE EARLIER CTA / CTBFILE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If a job ends unexpectedly due to operator cancel or OS issues,
  there is a timing crack that can occur so that the time values
  in the latest CTA/CTB file match the time values in the earlier
  file. This causes restart to use the earlier file when it should
  be using the later file.
  

Local fix

• At job backout, verify that DFSBBO00 backs out to the last
  checkpoint reported by IMS in the last DFS681I message the job
  generates. If DFSBBO00 reports a different checkpoint, manually
  edit the CTA/CTB file that contains the latest checkpoint, and
  delete the last record whose first byte is x'A0', and all
  subsequent records. Create a job override specifying
  AUTOXRST=FORCE, then restart the job.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Users of Program Restart Facility V2R2.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: If a PRF-controlled job abends in the   *
  *                      middle of processing a checkpoint, it   *
  *                      is possible for PRF to choose the prior *
  *                      checkpoint taken as the checkpoint from *
  *                      which to restart the job.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  PRF keeps information for the last two checkpoints taken by a
  program. To deal with the problem that can be caused by an abend
  in the midst of checkpoint processing, PRF first catalogs the
  checkpoint prior to sending it off to IMS for processing. At
  this point, PRF sets a bit in the CTDS file containing the
  checkpoint information that indicates this checkpoint has not
  finished processing yet, and is therefore "indoubt". PRF then
  sends the checkpoint off to IMS for processing. When IMS
  returns, PRF then sets a bit in the CTDS file containing the
  checkpoint information that indicates the checkpoint has been
  processed by IMS and is now available to be used for restart. If
  the job abends between the time IMS processes the checkpoint and
  the time PRF sets the bit indicating the checkpoint can be used
  for restart, PRF will choose the prior checkpoint for restart
  purposes. What PRF should do in this situation is to treat the
  current checkpoint as indoubt.
  
  NOTE: This situation can occur if you OS-cancel a batch DL/I or
  DBB job, or if you use the /STO REGION xxxx ABDUMP command to
  stop a BMP. If you think you may need to abnormally terminate a
  PRF-controlled job, you should specify FSTOP=YES in your global
  options, the job options entry for the job, or the job's
  IRT$CNTL file. You should then terminate the job using the OS
  MODIFY <jobname>,STOP command. This will help avoid indoubt
  restart situations.
  

Problem conclusion

• The Program Restart Facility restart logic has been modified to
  correctly recognize this situation as indoubt.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI38281

Modules/Macros

• IRTFXSR0 IRTIXT09 IRTIXT10 IRTIXT11 IRTIXT12
  IRTIXT13 IRTIXT14 IRTPRE00 IRTPRE10 IRTXRI09 IRTXRI10 IRTXRI11
  IRTXRI12 IRTXRI13 IRTXRI14 IRTXSC09 IRTXSC10 IRTXSC11 IRTXSC12
  IRTXSC13 IRTXSC14
  

Fix information

• Fixed component name

  IMS PGM RESTART

• Fixed component ID

  5655E1400

Applicable component levels

• R220 PSY UI38281

     UP16/06/03 P F606

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.