PM25830: TEMPLATE USAGE - DEFINITIONS FROM ADB25TU3 NOT USED BY OC EVEN THOUGH ADBH5TU SAYS "SPECIFY WHICH TEMPLATE WILL BE USED"

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Object Comparison Tool for z/OS panel GOC5 "Generate
  Compare Jobs" option TU "Specify TEMPLATE usage" gives the
  impression that panel ADB25TU3 "Specify UTILITY TEMPLATE Usage"
  "Template type" UTIL will be used in the WSL generated by the
  DB2 Object Comparison Tool.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool and     *
  *                 DB2 Object Comparison Tool for z/OS who run  *
  *                 DDL via Work Statement Lists (WSL) and who   *
  *                 choose to use utility templates.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the user specifies a particular    *
  *                      template for a utility (e.g. SYSUT1),   *
  *                      the background/inline utility that      *
  *                      ADBTEP2 uses to run a work statement    *
  *                      list will not use the designated        *
  *                      template.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  ADBTEP2 was not informed of the template to use.  This change
  will build statements that will be put into the WSL for use by
  ADBTEP2 to properly specify the correct template to use.
  

Problem conclusion

• This APAR addresses the situation described by APAR PK84264
  which was closed as FIN.
  
  Any subsequent work statement lists should include all
  applicable template specifications. Two new statements are
  now available to ADBTEP2. They are ADMIN xxxxxxxxx TEMPLATE,
  where xxxxxxxxx is SYSUT2 and SYSERR.  ADMIN SYSUT1 TEMPLATE
  is already available, but is currently only used by the REORG
  utility. This change will now use it with background CHECK
  utilities as well.  ADMIN CHECK TEMPLATE statements are now
  deprecated.  Please use the appropriate specific ADMIN
  xxxxxx TEMPLATE statement in its place.
  
  ADMIN CHECK TEMPLATE statements are now deprecated.  You
  can either change the ADMIN CHECK TEMPLATE statement to the
  appropriate equivalent, SYSUT1, SYSUT2 or SYSERR, remove
  the ADMIN CHECK TEMPLATE statement and let it revert to the
  default template, or regenerate your work statement list using
  the apropriate method (i.e. redo the ALT, reANALYZE the change,
  etc.).  If you have an ADMIN CHECK TEMPLATE statement in a work
  statement list and attempt to run it, you will receive a very
  specific error message.
  The ADMIN CHECK TEMPLATE statement is no longer valid.  Please
  change to the appropriate ADMIN xxxxxxx TEMPLATE statement where
  xxxxxxx is SYSUT1, SYSUT2 or SYSERR or rebuild work statement
  list. The ADBTEP2 job will then step whereupon it can be
  restarted after the appropriate corrections have been made.
  
  If an ADMIN CHECK TEMPLATE is found you will receive the
  following error:
  
  ADB5230E ADMIN CHECK TEMPLATE statement no
  longer valid. Please change appropriate ADMIN xxxxxxx
  TEMPLATE statement where xxxxxxx is SYSUT2 or
  SYSERR, rebuild the work statement list.
  ADB5185E The run is ending due to errors.
  
  In the past the sequence of the ADMIN CHECK TEMPLATE
  statement determine which equivalent DD to which the default
  is assigned. The first correlates to SYSUT1, second is SYSUT2
  and the third is SYSERR.  You can either remove the ADMIN
  CHECK TEMPLATE statement or change the word CHECK to the
  appropriate DD (i.e. SYSUT1, SYSUT2 or SYSERR).  For example,
  ADMIN CHECK TEMPLATE can be changed to ADMIN SYSUT2 TEMPLATE
  xxxxxx.
  

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

•    ADBEALT  ADBGAJOB ADBH5TUB ADBTEP2  ADB2WL4
  ADB25T   ADB25TE  ADB25TL3 ADB25TU  ADB25TU3 ADB28M   ADB5000
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK69177

     UP11/06/30 P F106

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.