A fix is available
APAR status
Closed as program error.
Error description
APAR that would correct ++HOLD actions for UI20718 and UI20719 (code for those PTFs is working properly, just description in ++HOLD is incorrect/confusing, and should be ignored)
Local fix
ignore ++HOLD for UI20718 and UI20719
Problem summary
**************************************************************** * USERS AFFECTED: All users of DSNTXAZP, the DSNTIDxx refresh * * tool, in DB2 10 for z/OS and DB2 11 for z/OS * * who apply a fixing PTF for APAR PI07515: * * - UI20718: DB2 10 for z/OS * * - UI20719: DB2 11 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: One of the ++HOLD actions in the fixing * * PTFs for PI07515 instructs users of * * program DSNTXAZP to bind a package for * * DSNTXAZP with ACTION(ADD). That bind * * request fails with return code 8 and * * these messages: * * DSNT237I -DSN DSNTBCM2 BIND ADD * * ERROR USING auth AUTHORITY * * PACKAGE = location.DSNTXAZP.- * * DSNTXAZP.(version) * * ALREADY EXISTS * * DSNT233I -DSN UNSUCCESSFUL BIND FOR * * PACKAGE = location.DSNTXAZP.- * * DSNTXAZP.(version) * * where 'location' is DB2's location name * * and 'version' is a DSNTXAZP DBRM * * version ID. * **************************************************************** * RECOMMENDATION: Apply the fixing PTF. * **************************************************************** APAR PI07515 provides new options for DB2 subsystem parameter DSN6FAC.DDF_COMPATIBILITY to help users compensate for unexpected behavior of remote client application environments. In order to provide additional space to store the new options, PI07515 changed the format of the DB2 installation CLIST input (DSNTIDxx) member entries for DDF_COMPATIBILITY from this: DDF_COMPATIBILITY LSTR M <a> DDF_COMPATIBILITY1 LSTR M <b> to this: DDF_COMPATIBILITY LLST M <a> DDF_COMPATIBILITY1 LLST M <b> DDF_COMPATIBILITY2 LLST M <c> DDF_COMPATIBILITY3 LLST M <d> DDF_COMPATIBILITY4 LLST M <e> However, PI07515 failed to include a change to DSNTXAZP, the refresh tool for DSNTIDxx members, to make it use the new format. Both fixing PTFs for PI07515 contain a ++HOLD action that instructs users of DSNTXAZP to bind a package for it using ACTION(ADD). Because the intended update of DSNTXAZP was not included in the PTFs for PI07515, its DBRM and module are unchanged when you apply the PTF. If a package is already bound from the existing DSNTXAZP DBRM in prefix.SDSNDBRM, the bind with ACTION(ADD) request fails with the symptoms noted in the problem description section of this APAR.
Problem conclusion
This APAR provides the missing DSNTXAZP changes that were not included in PI07515.
Temporary fix
Comments
APAR Information
APAR number
PI30243
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-24
Closed date
2015-01-30
Last modified date
2015-03-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI24889 UI24890
Modules/Macros
DSN@XAZP DSNTIDXA DSNTXAZP
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
06 May 2020