A fix is available
APAR status
Closed as program error.
Error description
The DB2 Administration Tool for z/OS Change Management ANALYZE MERGE step end RC=12 with a message: Subscriptrange raised due to an internal error Program ADBCCMM detected an Oncode condition 520 in MERGE_TABLES. This may be caused by invalid input or an internal program error Please report this error to IBM . Additional symptoms: oncode520
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of Admin & Object Comparison Tool. * **************************************************************** * PROBLEM DESCRIPTION: When merge encounters a subscript * * range condition, it currently fails * * with the following message: * * * * ************ TOP OF DATA ************* * * Subscriptrange raised due to an * * internal error Program ADBCCMM * * detected an Oncode condition 520 * * in MERGE_TABLES. * * * * This may be caused by invalid input * * or an internal program error Please * * report this error to IBM. * * * * GOCC002E - Severe error. Compare * * terminates * * ******** BOTTOM OF DATA ************** * * * * With the apar fix, the subscript range * * condition has been addressed and to * * allow fast resolution should it occur * * in the future the message is improved * * as below: * * * * ************ TOP OF DATA ************ * * Subscriptrange raised due to an * * internal error Program ADBCCMM * * detected an Oncode condition 520 * * in MERGE_TABLES. * * * * Object details at the time of error: * * Operation : <CREATE,ALTER, * * DROP,...etc> * * Object Type : <Type> * * Object Qualifier: <Qualifier> * * Object Name : <Name> * * * * ADBC012E - Subscript range condition * * detected * * ADBC002E - Severe error. Merge * * terminates * * ********** BOTTOM OF DATA *********** * * * * Due to incorrect usage, the scenario * * for PMR 68584,211,848 should now * * result in the following error: * * * * ************ TOP OF DATA ************* * * TB record expected, but one not found * * ADBC002E - Severe error. Merge * * terminates * * ************ BOTTOM OF DATA ********** * * * * When the unsupported statement i.e * * CREATE TABLE...LIKE clause is found * * a message: * * * * * * ********** TOP OF DATA ************** * * ADBC013E - CREATE TABLE <table> LIKE * * <table> not yet supported * * GOCC002E - Severe error. Compare * * terminates * * *********** BOTTOM OF DATA *********** * * * * will be issued. * **************************************************************** * RECOMMENDATION: Apply The PTF. * **************************************************************** When merge encounters a subscript range condition, it currently fails with the following message: ********************************* TOP OF DATA ****************** Subscriptrange raised due to an internal error Program ADBCCMM dected an Oncode condition 520 in MERGE_TABLES. This may be caused by invalid input or an internal program error Please report this error to IBM. GOCC002E - Severe error. Compare terminates ******************************** BOTTOM OF DATA **************** With the apar fix, the subscript range condition has been addressed and to allow fast resolution should it occur in the future the message is improved as below: ********************************* TOP OF DATA ****************** Subscriptrange raised due to an internal error Program ADBCCMM detected an Oncode condition 520 in MERGE_TABLES. Object details at the time of error: Operation : <CREATE,ALTER,DROP,...etc> Object Type : <Type> Object Qualifier: <Qualifier> Object Name : <Name> ADBC012E - Subscript range condition detected ADBC002E - Severe error. Merge terminates ******************************** BOTTOM OF DATA **************** Due to incorrect usage, the scenario for PMR 68584,211,848 should now result in the following error: ********************************* TOP OF DATA ***************** TB record expected, but one not found ADBC002E - Severe error. Merge terminates ******************************** BOTTOM OF DATA *************** When the unsupported statement i.e CREATE TABLE...LIKE clause is found a message: ********************************* TOP OF DATA ***************** ADBC013E - CREATE TABLE <table> LIKE <table> not yet supported GOCC002E - Severe error. Compare terminates ******************************** BOTTOM OF DATA *************** will be issued.
Problem conclusion
Resolved.
Temporary fix
Comments
APAR Information
APAR number
PK74177
Reported component name
DB2 ADMIN TOOL
Reported component ID
568851500
Reported release
720
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-21
Closed date
2009-03-12
Last modified date
2009-05-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ADBCCMM
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
Applicable component levels
R720 PSY UK44862
UP09/03/18 P F903
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":"720","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
20 May 2009