A fix is available
APAR status
Closed as program error.
Error description
When using UNLOAD from an image copy for a table that has a clone, the unload utility receives error message DSNU1227I and/or DSNU1408I . Same problem as PM50006.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 11 for z/OS users of UNLOAD FROMCOPY * * utility * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNU1227I RC=8 or MSGDSNU1408I RC=4 * * and no rows unloaded with UNLOAD * * FROMCOPY of an object involved with * * cloning. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** With clone tables, a base and clone table have identical object identifiers except for the high order bit which identifies which data set contains the data for the object. As EXCHANGEs are done the instance numbers change making it look like the data was physically moved. Data set header pages do not change during the EXCHANGE process but they do contain object identifier information. Because the header page information does not change but the object identifiers do change (the object identifier high order bits are toggled) during the EXCHANGE process, it's possible to have the UNLOAD utility fail because of object id mismatches as reported: 1 - MSGDSNU1227I is issued and the job terminates with RC8. Message text: DSNU1227I csect-name - THE CONTENT OF THE IMAGE COPY DATA SET IS INCONSISTENT WITH TABLE SPACE table-space 2 - MSGDSNU1408I is issued and the job terminates with RC4. Message text: DSNU1408I csect-name - SOURCE DATA SET dsname DOES NOT MATCH obj-type obj-qual.obj-name DSNUM n In the cloning cases we will now no longer halt UNLOAD processing if the only difference in the object identifiers is the high order bit. This also means that the DSNU1227I and DSNU1408I messages will no longer be issued in these cases. Caution: it should be noted that the removal of this restriction will now allow clone and/or base table data to be UNLOADed using image copy data sets from the other table in the clone relationship as follows: 1 - UNLOAD from base table using a clone table image copy. 2 - UNLOAD from clone table using a base table image copy.
Problem conclusion
UNLOAD FROMCOPY utility code has been modified so that it will now continue in cases where it would previously fail with the DSNU1408I or DSNU1227I messages when the only difference was in the object identifier high order bits.
Temporary fix
Comments
APAR Information
APAR number
PI28518
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-28
Closed date
2014-11-20
Last modified date
2015-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI23387
Modules/Macros
DSNUULCA DSNUULCB
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RB10 PSY UI23387
UP14/12/16 P F412
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