PI66859: IRTINCL DOES NOT CREATE AN EXCLUSION DD NAME LIST OR A BBM EXCLUSION ENTRY FOR BCM$EXCL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• PRF V2.1 allows for the creation of module IRT#IGNR to contain a
  list of DD names that can be specified in a job's JCL to bypass
  PRF processing. In addition, BBM V1.2 uses BCM$EXCL as a DD name
  that, when present, will bypass BBM V1.2 processing.
  
  IRTINCL does not look for the IRT#IGNR module, and therefore
  does not create a list of exclusion DD names. Also, the BCM$EXCL
  DD name is not included in the default exclusion list.
  
  IRTINCL should be modified to create an exclusion DD name list
  that contains the entries in the V2.1 IRT#IGNR module, and
  should create a BBM exclusion entry for BCM$EXCL.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Users of the Program Restart Facility    *
  *                 V2.1 -> V2.2 conversion program (IRTINCL).   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Program Restart Facility V2.2 includes  *
  *                      a conversion utility which converts     *
  *                      configuration options from the prior    *
  *                      release (V2.1) into V2.2 format. This   *
  *                      conversion utility only converts        *
  *                      configuration options found in the PRF  *
  *                      V2.1 or Batch Backout Manager V1.2      *
  *                      inclusion options data sets. PRF V2.1   *
  *                      Exclusion DD name specifications are    *
  *                      not kept in the PRF exclusion options   *
  *                      data set, so they are not converted     *
  *                      into V2.2 format. This requires the     *
  *                      customer to manually re-enter the V2.2  *
  *                      Exclusion DD name specifications after  *
  *                      the conversion process completes.       *
  *                                                              *
  *                      In PRF V2.2, the REATTACH parameter is  *
  *                      no longer supported. The conversion     *
  *                      utility ignores this parameter when     *
  *                      converting the V2.1 inclusion options   *
  *                      file to the V2.2 options modules. This  *
  *                      results in jobs running under PRF V2.2  *
  *                      performing logic activated by the       *
  *                      existence of the ABRETRY, RDORETRY, and *
  *                      FSTOP parameters, when these jobs were  *
  *                      prohibited from performing this logic   *
  *                      under PRF V2.1                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Program Restart Facility allows the user to create entries
  in an internal table which represent DD names that, when
  included in the JCL of a job that would normally be run under
  the control of the Program Restart Facility, would disable PRF
  functionality in a BMP/JMP environment, or would disable PRF
  and/or Batch Backout Manager functionality in a batch DL/I
  environment. These entries are called "Exclusion DD" entries.
  
  When converting from PRF V2.1 and/or BBM V1.2, PRF V2.2 provides
  a conversion program that converts PRF V2.2 and BBM V1.2
  configuration options into PRF V2.2 format. This conversion
  program only converts those options found in the PRF and BBM
  inclusion options files. The PRF V2.1 Exclusion DD entries are
  not stored in the inclusion options file, but are instead stored
  in load module format in a member created in the PRF V2.1 User
  Library. This is the IRTUSRL data set (or other data set) where
  you store the IRT#INCL load module you created when you ran the
  IRT#INCL job (found in your V2.1 SIRTSAMP library) while
  configuring PRF V2.1.
  
  Since the PRF V2.2 conversion program only converts
  configuration options found in the PRF/BBM inclusion options
  files, the PRF V2.1 Exclusion DD entries are not converted into
  V2.2 format. Instead, the customer must manually create these
  entries using the PRF V2.2 ISPF panels.
  
  In PRF V2.1, the REATTACH keyword was required to activate
  ABRETRY, RDORETRY, and FSTOP processing. The result was that a
  global or local (on a JOB, PSB, PGM, or IJS statement)
  specification of any of these three keywords did not activate
  this processing unless a global or local specification of the
  REATTACH keyword also applied to the job in question. The
  REATTACH keyword is not used in PRF V2.2, and the conversion
  program ignores the keyword and its effects on the ABRETRY,
  RDORETRY, and FSTOP keywords. The result is that jobs which did
  not execute ABRETRY, RDORETRY, or FSTOP logic only because
  REATTACH=NO applied to these jobs in V2.1, will now execute this
  logic in V2.2. This can result in processing errors on job
  restart if manual intervention is required to restart these jobs
  when they abend.
  

Problem conclusion

• The Program Restart Facility V2.1 -> V2.2 conversion program
  will now read the V2.1 User Library (or other data set you
  specify) to find the IRT#IGNR load module which contains the
  PRF V2.1 Exclusion DD entries. If the conversion program finds
  the load module, it will convert the entries found in that
  load module to V2.2 format so that the customer no longer has
  to manually convert the entries.
  
  The conversion program will now also take into account the
  effect that REATTACH specifications had on a job under PRF V2.1,
  and modify job entries so that jobs which did not execute
  ABRETRY, RDORETRY, or FSTOP logic in V2.1 due to the REATTACH
  specification in effect for the jobs in question, do not execute
  this logic in V2.2
  

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:

  UI41427

Modules/Macros

• IRTINCL
  

Fix information

• Fixed component name

  IMS PGM RESTART

• Fixed component ID

  5655E1400

Applicable component levels

• R220 PSY UI41427

     UP16/10/07 P F610

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.