A fix is available
APAR status
Closed as program error.
Error description
DB2 OBJECT COMPARISON TOOL FOR Z/OS NEW FUNCTION TO EXTERNALIZE TEMPLATE USAGE IN GENERATED JCL.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Object Comparison * * Tool for z/OS and DB2 Administration * * Tool for z/OS who use User-defined * * TEMPLATEs for DB2 Utilities. * **************************************************************** * PROBLEM DESCRIPTION: The following is delivered: * * * * DB2 Admin allows a new way to specify * * User-defined TEMPLATEs for DB2 * * Utilities usage. This new format * * needs to allow the Change Management * * batch (CM Batch) interface style * * parameter variables and TEMPLATE * * formats. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR will add a new way to specify TEMPLATE information for the USRTEMPL data set, which will be a DD data set that contains TEMPLATE information in either the DB2 format or the XML format that DB2 Admin uses. The USRTEMPL data set will be set up by the user prior to running the APPLY job and will have the following data set naming convention: adbapre.USRTEMPL where adbapre is the 'Prefix for data sets' value given by the user in panels ADB2C11A 'Generate Analyze Job', ADBPALT 'ALTER - Build Analyze and Apply Job', or GOC5 'Generate Compare Jobs'. The USRTEMPL data set is optional. If this data set exists. Object Compare, 'ALT Alter Table' (ALT), and Change Management will use it for TEMPLATE information. If it doesn't exist, TEMPLATE information will be retrieved the way it has been in the past by using the tables specified on panel ADB25TU 'Specify UTILITY TEMPLATE Usage'. Template information from panel ADB25TU tables will be processed first and then the templates from the USRTEMPL will be processed; therefore, USRTEMPL templates will take priority. This enhancement does not affect CM Batch processing that is done with the user's JCL. It already has its own way of allowing user-friendly TEMPLATE information. There can be two types of information in the USRTEMPL data set, template variables and DB2 TEMPLATE data. The DB2 TEMPLATE data has to follow all the TEMPLATE variables. The valid TEMPLATE variables (that are the same as the CM batch variables) are UTIL_TEMPLATE_DISCARDDN_NAME, UTIL_CLONE_TEMPLATE_DISCARDDN_NAME, UTIL_TEMPLATE_DISCARDDNC_NAME, UTIL_CLONE_TEMPLATE_DISCARDDNC_NAME, UTIL_TEMPLATE_UNLOAD_PUNCHDDN_NAME, UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDN_NAME, UTIL_TEMPLATE_UNLOAD_PUNCHDDNC_NAME, UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDNC_NAME, UTIL_TEMPLATE_UNLOAD_UNLDDN_NAME, UTIL_CLONE_TEMPLATE_UNLOAD_UNLDDN_NAME, UTIL_CLONE_TEMPLATE_COPYDDN1_NAME, UTIL_TEMPLATE_COPYDDN2_NAME, UTIL_CLONE_TEMPLATE_COPYDDN2_NAME, UTIL_TEMPLATE_ERRDDN_NAME, UTIL_CLONE_TEMPLATE_ERRDDN_NAME, UTIL_TEMPLATE_FCCOPYDDN_NAME, UTIL_CLONE_TEMPLATE_FCCOPYDDN_NAME, UTIL_TEMPLATE_LOBCOL_NAME, UTIL_CLONE_TEMPLATE_LOBCOL_NAME, UTIL_TEMPLATE_MAPDDN_NAME, UTIL_CLONE_TEMPLATE_MAPDDN_NAME, UTIL_CLONE_TEMPLATE_RECOVERYDDN1_NAME, UTIL_TEMPLATE_RECOVERYDDN2_NAME, UTIL_CLONE_TEMPLATE_RECOVERYDDN2_NAME, UTIL_TEMPLATE_UNLDDN_NAME, UTIL_CLONE_TEMPLATE_UNLDDN_NAME, UTIL_TEMPLATE_WORKDDN1_NAME, UTIL_CLONE_TEMPLATE_WORKDDN1_NAME, UTIL_TEMPLATE_WORKDDN2_NAME, UTIL_CLONE_TEMPLATE_WORKDDN2_NAME, UTIL_TEMPLATE_XMLCOL_NAME, UTIL_CLONE_TEMPLATE_XMLCOL_NAME UTIL_TEMPLATE_DISCARDDN_USE, UTIL_CLONE_TEMPLATE_DISCARDDN_USE, UTIL_TEMPLATE_DISCARDDNC_USE, UTIL_CLONE_TEMPLATE_DISCARDDNC_USE UTIL_TEMPLATE_UNLOAD_PUNCHDDN_USE UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDN_USE UTIL_TEMPLATE_UNLOAD_PUNCHDDNC_USE UTIL_CLONE_TEMPLATE_UNLOAD_PUNCHDDNC_USE, UTIL_TEMPLATE_UNLOAD_UNLDDN_USE UTIL_TEMPLATE_UNLOAD_UNLDDNC_USE, UTIL_CLONE_TEMPLATE_COPYDDN1_USE, UTIL_TEMPLATE_COPYDDN2_USE, UTIL_CLONE_TEMPLATE_COPYDDN2_USE, UTIL_TEMPLATE_ERRDDN_USE, UTIL_CLONE_TEMPLATE_ERRDDN_USE, UTIL_TEMPLATE_FCCOPYDDN_USE, UTIL_CLONE_TEMPLATE_FCCOPYDDN_USE, UTIL_TEMPLATE_LOBCOL_USE, UTIL_CLONE_TEMPLATE_LOBCOL_USE, UTIL_TEMPLATE_MAPDDN_USE, UTIL_CLONE_TEMPLATE_MAPDDN_USE, UTIL_TEMPLATE_PUNCHDDN_USE, UTIL_CLONE_TEMPLATE_PUNCHDDN_USE, UTIL_TEMPLATE_RECOVERYDDN1_USE, UTIL_CLONE_TEMPLATE_RECOVERYDDN1_USE, UTIL_TEMPLATE_RECOVERYDDN2_USE, UTIL_CLONE_TEMPLATE_RECOVERYDDN2_USE, UTIL_TEMPLATE_UNLDDN_USE, UTIL_CLONE_TEMPLATE_UNLDDN_USE, UTIL_TEMPLATE_WORKDDN1_USE, UTIL_CLONE_TEMPLATE_WORKDDN1_USE, UTIL_TEMPLATE_WORKDDN2_USE, UTIL_CLONE_TEMPLATE_WORKDDN2_USE, UTIL_TEMPLATE_XMLCOL_USE, UTIL_CLONE_TEMPLATE_XMLCOL_USE The DB2 TEMPLATE format is as follows: TEMPLATE template_name DSN dsn_definition template_details The XML TEMPLATE format is as follows: NOTE: each line can only have one piece of information like it is shown below. >TEMPLATE< >NAME< template_name ---- example: DISC >/NAME> >DSN< dsn_definition >/DSN< >OTHER< template_details ----- example: DISP(NEW,CATLG,CATLG) >/OTHER< >/TEMPLATE< ---- this line is optional Below is description of the values needed for each XML element: template_name - The name of the template being set dsn_definition - The data set name template_details - All other details needed for the template definition Here is an example of TEMPLATE setting for DISC and ERR: >TEMPLATE< >NAME< DISC >/NAME< >DSN< DIN2.C001ABCD.&DB..&TS..&UNIQ..DISC.T0001 >/DSN< >OTHER< DISP(NEW,CATLG,CATLG) >/OTHER< >TEMPLATE< >NAME< ERR >/NAME< >DSN< DIN2.C001ABCD.C0000286.&DB..&TS..&UNIQ..ERR.T0001 >/DSN< >OTHER< DISP(NEW,CATLG,CATLG) >/OTHER< After resolving the symbol variables, the above XML will be shown as: TEMPLATE DISC DSN DIN2.C001ABCD.&DB..&TS..&UNIQ..DISC.T0001 DISP(NEW,CATLG,CATLG) ; TEMPLATE ERR DSN DIN2.C001ABCD.C0000286.&DB..&TS..&UNIQ..ERR.T0001 DISP(NEW,CATLG,CATLG) NOTE: Please replace all '>' with '<' and all '<' with '>' before using the above examples. Thank you
Problem conclusion
DB2 Admin allows a new way to specify User-defined TEMPLATEs for DB2 Utilities usage. This enhancement is delivered.
Temporary fix
Comments
APAR Information
APAR number
PI30337
Reported component name
DB2 OBJECT COMP
Reported component ID
5697G6400
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-25
Closed date
2015-03-13
Last modified date
2015-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI25946
Modules/Macros
GOCGCMP
Fix information
Fixed component name
DB2 OBJECT COMP
Fixed component ID
5697G6400
Applicable component levels
RB10 PSY UI25946
UP15/03/17 P F503
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1.0"}]
Document Information
Modified date:
12 April 2021