PI54364: AUTOBKO=NO ONLY STOPS PRF FROM RUNNING BACKOUT AT JOB ABEND TIME. BACKOUT IS THEN RUN WHEN THE JOB IS RESTARTED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• AUTOBKO=NO only stops PRF from running backout at job abend
  time. When the job is restarted, backout is run no matter what,
  so long as a .BKO file exists. In addition, if an exclusion
  DDNAME with the "Disable BBO" option is set and AUTOBKO=NO is
  specified, a message is generated telling the user that AUTOBKO
  has been disabled. This is at least misleading.
  

Local fix

• Manually delete the job's .BKO file prior to job restart.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Users of Program Restart Facility V2R2.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: There is no way to put a job under PRF  *
  *                      control and not have PRD control        *
  *                      backout processing. This is             *
  *                      inconvenient for PRF V2.1 customers     *
  *                      who did not also have Batch Backout     *
  *                      Manager installed.                      *
  *                      In addition, when deleting a job        *
  *                      through the ISPF interface, the BBDS    *
  *                      file is not deleted. This can cause an  *
  *                      invalid backout to take place once the  *
  *                      job is restarted.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When PRF V2.2 was coded, it combined the functionality of PRF
  V2.1 and Batch Backout Manager (BBM) V1.2. Batch Backout Manager
  allowed the customer to disable backout by specifying a BCM$EXCL
  DD DUMMY statement. This functionality was removed when BBM was
  folded into PRF V2.2.
  The "active jobs" list functionality of the PRF V2.1 ISPF
  interface was replicated in PRF V2.2. PRF V2.1 did not provide
  backout support, and no logic was added in the PRF V2.2
  interface to provide support to delete a BBDS file when a delete
  request was received for a job in the PRF V2.2 "active jobs"
  list.
  

Problem conclusion

• The Program Restart Facility will check to see if a job step
  contains an AUTOBKO=NO specification. If so, PRF will then
  determine if a DD statement is included that exists in the list
  of user- specified exclusion DD statements that are specified in
  the exclusion DD name table that is maintained by the PRF ISPF
  interface (Option 9). If a DD name exists in the job that
  matches an entry in the exclusion table where "Disable PRF = NO"
  and "Disable BBO = YES", then Batch Backout functionality will
  be disabled. Note that if such a DD name exists in a job that
  contains an AUTOBKO=YES specification, the DD name specification
  will be ignored, and PRF will control backout processing for
  that job.
  
  To support deletion of the BBDS file when deleting a job found
  in the "active jobs" list in the PRF ISPF interface, three new
  panels have been added.
  Panel IRTJOBBD is displayed as a popup panel after you have
  answered 'Y' to the "delete CDTS files" confirmation panel, if
  the PRF ISPF interface determines that a BBDS file exists for
  the job. Panel IRTJOBBD asks for confirmation to delete the BBDS
  file. Specifying 'Y' will cause the ISPF interface to delete
  both the CDTS and the BBDS files. Specifying 'N' will cause the
  ISPF interface to delete the CDTS files but keep the BBDS file.
  Specifying 'C' will cause the ISPF interface to return to the
  "active jobs" list without deleting anything.
  
  Panel IRTJOBBC is displayed as a popup panel after you have
  answered 'Y' to the "delete CDTS files" confirmation panel, if
  the PRF ISPF interface cannot determine if a BBDS file exists
  for the job. This can happen when you specify "CDTSNAM=NOPSB" as
  a PRF Global option, and the ISPF interface cannot read the CDTS
  files to find the information necessary to construct the BBDS
  file name. Specifying 'Y' will cause the ISPF interface to
  continue with the deletion of the CDTS files. Any BBDS file that
  may exist for the job will not be deleted. Specifying 'N' will
  cause the ISPF interface to return to the "active jobs" list
  without deleting anything.
  
  Panel IRTJOBBA is displayed as a popup panel after you have
  answered 'Y' to the "delete BBDS file" confirmation panel, if
  the PRF ISPF interface cannot allocate or delete the BBDS file.
  Specifying 'Y' will cause the ISPF interface to continue with
  the deletion of the CDTS files. The BBDS file will not be
  deleted. Specifying 'N' will cause the ISPF interface to return
  to the "active jobs" list without deleting anything.
  

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:

  UI37589

Modules/Macros

• IRTA04   IRTJOBBA IRTJOBBC IRTJOBBD IRTPPRIM
  IRTRCC00 IRTUPX00 IRTZJOBS
  

Fix information

• Fixed component name

  IMS PGM RESTART

• Fixed component ID

  5655E1400

Applicable component levels

• R220 PSY UI37589

     UP16/05/07 P F605

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.