A fix is available
APAR status
Closed as program error.
Error description
The DB2 Administration Tool for z/OS produces REBIND PACKAGE syntax without the TRIGGER keyword when attempting to REBIND a TRIGGER PACKAGE: DSNT264I #ssid- DSNTBRB2 REBIND ERROR USING schema AUTHORITY PACKAGE ssid.schema.trigger.() IS A TRIGGER PACKAGE DSNT233I #ssid- UNSUCCESSFUL REBIND FOR PACKAGE = ssid.schema.trigger.()
Local fix
Add the TRIGGER keyword to the REBIND statement: REBIND TRIGGER PACKAGE(schema.trigger) or Use the RB line command to REBIND the Trigger package.
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Administration Tool for * * z/OS who use the REBIND primary command and * * the 'BC' (BIND COPY) line command for * * TRIGGER packages. * **************************************************************** * PROBLEM DESCRIPTION: The DB2 Administration Tool for z/OS * * produces a REBIND PACKAGE statement * * without the keyword TRIGGER when * * attempting to REBIND a TRIGGER * * PACKAGE, and displays the following * * messages after executing the rebind * * statement: * * * * DSNT264I #ssid-DSNTBRB2 REBIND * * ERROR USING schema * * AUTHORITY PACKAGE * * ssid.schema.trigger.() * * IS A TRIGGER PACKAGE * * * * DSNT233I #ssid- UNSUCCESSFUL * * REBIND FOR PACKAGE= * * ssid.schema.trigger.() * * * * The DB2 Administration Tool for z/OS * * wrongly enables the 'BC' (BIND COPY) * * line command for TRIGGER packages. * **************************************************************** * RECOMMENDATION: * **************************************************************** The DB2 Administration Tool for z/OS produces a REBIND PACKAGE statement without the keyword TRIGGER when attempting to REBIND a TRIGGER PACKAGE, and displays the following messages after executing the rebind statement: DSNT264I #ssid- DSNTBRB2 REBIND ERROR USING schema AUTHORITY PACKAGE ssid.schema.trigger.() IS A TRIGGER PACKAGE DSNT233I #ssid- UNSUCCESSFUL REBIND FOR PACKAGE= ssid.schema.trigger.() The DB2 Administration Tool for z/OS wrongly enables the 'BC' (BIND COPY) line command for TRIGGER packages.
Problem conclusion
The keyword TRIGGER is generated when using the REBIND primary command to rebind TRIGGER packages. The 'BC' (BIND COPY) line command has been disabled for TRIGGER packages.
Temporary fix
Comments
APAR Information
APAR number
PM44630
Reported component name
DB2 ADMIN TOOL
Reported component ID
568851500
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-28
Closed date
2011-11-23
Last modified date
2011-12-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK74152 UK74153
Modules/Macros
ADB21K ADB21KRX
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
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":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 December 2011