PH62472: BATCH BUILD SYSOUT: THE NBR OF ACCEPTED/REJECTED OBJECT COUNTS DISPLAYED CAN BE INCORRECT WHEN DEFINE NO INDEXES ARE INCLUDED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When performing a batch job build, the SYSOUT output currently
  includes COPY NO INDEXES in the total number of
  accepted/rejected object counts. These objects are not included
  in the generated JCL - thus, they will now be bypassed (not
  counted) when calculating the number of accepted/rejected
  objects for the aforementioned SYSOUT report.
  
  Additionally, the SYSOUT report heading was modified (see below)
  
  
  to clarify how objects at the ALL
  Level is counted:
  
  "Following are the objects included in generated JCL based on
  the utility profile or the exception profile
  exception rule. If there is no exception profile in the job, all
  
  
  objects in the job are ACCEPTED objects. Partition-level
  statistics are displayed for all objects. Objects at the ALL
  level are expanded to their individual parts but are only
  counted as one (1) object."
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Users                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When performing a batch job build,      *
  *                      the SYSOUT output currently includes    *
  *                      COPY NO INDEXES in the total number of  *
  *                      accepted/rejected object counts. These  *
  *                      objects are not included in the         *
  *                      generated JCL - thus, they will now be  *
  *                      bypassed (not counted) when             *
  *                      calculating the number of               *
  *                      accepted/rejected objects for the       *
  *                      aforementioned SYSOUT report.           *
  *                                                              *
  *                      Additionally, the SYSOUT report         *
  *                      heading was modified (see below) to     *
  *                      clarify how objects at the ALL          *
  *                                                              *
  *                      "Following are the objects included in  *
  *                      generated JCL based on the utility      *
  *                      profile or the exception profile        *
  *                      exception rule. If there is no          *
  *                      exception profile in the job, all       *
  *                      objects in the job are ACCEPTED         *
  *                      objects. Partition-level statistics     *
  *                      are displayed for all objects.          *
  *                      Objects at the ALL level are expanded   *
  *                      to their individual parts, but are only *
  *                      counted as one (1) object."             *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF                                *
  ****************************************************************
  .
  

Problem conclusion

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:

  UI98473

Modules/Macros

• HAA@POBJ
  

Fix information

• Fixed component name

  DB2 AUTOMATION

• Fixed component ID

  5697G6300

Applicable component levels

• R430 PSY UI98473

     UP24/09/20 P F409

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.