PK13046: OBJECTS NOT MEETING SOME REALLOCATION / EXCEPTION CRITERIA MAY APPEAR IN THE GENERATED JCL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In cases where EXCEPTION profiles are used along with the
  REALLOCATION utility, some objects may incorrectly appear in the
  registration, START(UT), START(RW), or ALTER job steps of the
  generated job but not trigger any other utilities.  If no other
  utilities are included in the job profile or all other utilities
  have an 'Exception Rule' set to 'R' (reject), the ALTER may be
  the only utility for that object in the generated job.
  
  
  Additionally, the registration, START(UT), and START(RW) steps
  may not have contained all qualifying objects.  After this fix,
  if the PROCESS INDEXES flag in the OBJECT profile is set to "Y",
  registration START(UT), and START(RW) will change.  If utilities
  are processed at the tablespace level that can also affect
  indexes, those corresponding indexes will now be included in
  the registration, START(UT), and START(RW) steps.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Automation Tool.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: In cases where EXCEPTION profiles are   *
  *                      used along with the REALLOCATION        *
  *                      utility, some objects may incorrectly   *
  *                      appear in the registration, START(UT),  *
  *                      START(RW), or ALTER job steps of the    *
  *                      generated job but not trigger any       *
  *                      other utilities.  If no other           *
  *                      utilities are included in the job       *
  *                      profile or all other utilities have     *
  *                      an 'Exception Rule' set to 'R'          *
  *                      (reject), the ALTER may be the only     *
  *                      utility for that object in the          *
  *                      generated job. Additionally, the        *
  *                      registration, START(UT), and START(RW)  *
  *                      steps may not have contained all        *
  *                      qualifying objects.  After this fix,    *
  *                      if the PROCESS INDEXES flag in the      *
  *                      OBJECT profile is set to "Y",           *
  *                      registration START(UT), and START(RW)   *
  *                      will change.  If utilities are          *
  *                      processed at the tablespace level that  *
  *                      can also affect indexes, those          *
  *                      corresponding indexes will now be       *
  *                      included in the registration,           *
  *                      START(UT), and START(RW) steps.         *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

Modules/Macros

• HAA$BUTE
  

Fix information

• Fixed component name

  DB2 AUTOMATION

• Fixed component ID

  5697G6300

Applicable component levels

• R220 PSY UK10035

     UP05/12/15 P F512

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.