A fix is available
APAR status
Closed as program error.
Error description
DB2 V11 has been enhanced so that if a tablespace is empty (does not have active tables in it) then Reorg will skip the processing of writing to the sysrec/UNLDDDN dataset during the UNLOAD phase. However if the user have hardcoded DD's for the unload dataset that go to tape, and reorg is run on multiple tablespaces, then when there is an empty tablespace and the write to the tape label is skipped, then the next non-empty tablespace being unloaded on the next label of the same volume will get an abend413 because the specified label/file sequence is incorrect. For example, with the following DD's hardcoded in the REORG job: //DDN00001 DD DSN=S0115.RGH.DB011501.TS011502, // DISP=(MOD,CATLG,CATLG),VOL=(,RETAIN,,99),UNIT=VSMLC,LABEL=1 //DDN00002 DD DSN=S0115.RGH.DB011501.TS011511, // DISP=(MOD,CATLG,CATLG),VOL=(,RETAIN,,99,REF=*.DDN00001), // UNIT=AFF=DDN00001,LABEL=2 //DDN00003 DD DSN=S0115.RGH.DB011501.TS011505, // DISP=(MOD,CATLG,CATLG),VOL=(,RETAIN,,99,REF=*.DDN00002), // UNIT=AFF=DDN00001,LABEL=3 ... with the following Reorg statement: REORG TABLESPACE DB011501.TS011502 UNLDDN DDN00001 ........ REORG TABLESPACE DB011501.TS011511 UNLDDN DDN00002 ........ REORG TABLESPACE DB011501.TS011505 UNLDDN DDN00003 ........ . This job will fail with the following message when the second tablespace is empty: IEC145I 413-08,IFG0194K,J0115014,DSNUPROC,DDN00003,4BF1,, DSNU016I DSNUGBAC - UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X'0413'
Local fix
Use LISTDEF for the UNLDDDN in place of hardcoding the DD's.
Problem summary
**************************************************************** * USERS AFFECTED: * * All DB2 12 for z/OS users of REORG utility * **************************************************************** * PROBLEM DESCRIPTION: * * ABENDA13-10 or ABEND413-34 following MSGDSNU260I on REORG * * utility with unload data sets directed to tape and defined * * by DD cards. * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** User ran multiple REORG TABLESPACE utilities in one job step and defined the unload data sets with DD cards and UNIT specification of TAPE, in which the next UNLOAD DD card is referred back to the previous one. One of the REORG utility issued message DSNU260I -TABLESPACE obj-qual.obj-name IS EMPTY and did not allocate an unload data set for it. When the following REORG tried to open and write to the data set, it failed with ABENDSA13 RC10 or ABENDS413 RC34 because the referred-to data set was never allocated.
Problem conclusion
REORG TABLESPACE code was changed to allocate the unload data set as long as it is provided by DD card or template. REORG will still tolerate an absent unload data set for a table space containing no table.
Temporary fix
Comments
APAR Information
APAR number
PI69843
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-27
Closed date
2017-01-03
Last modified date
2017-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI43685
Modules/Macros
DSNURORG
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI43685
UP17/01/20 P F701
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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 February 2017