A fix is available
APAR status
Closed as program error.
Error description
LOB unload using SPANNED YES option abends with error: DSNU038I DSNUGSDA - BLOCK SIZE FOR DCB, DDNAME SYS00001, IS TOO SMALL, MUST BE AT LEAST 28158 BYTES DSNU016I DSNUGBAC - UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X'00E40079 Additional keyword: LOAD SPANNED YES abended with 0C4-00000004 at DSNURILD offset 2CC2
Local fix
specify BLKSIZE=32760
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of UNLOAD utility * * with SPANNED YES or LOAD utility with * * FORMAT SPANNED YES * **************************************************************** * PROBLEM DESCRIPTION: UNLOAD table space with LOB column * * using SPANNED YES option, resulted in * * MSGDSNU038I and ABEND04E RC00E40079. * * * * IDCAMS shows zero rows in SYSREC * * after UNLOAD SPANNED YES. * * * * LOAD with FORMAT SPANNED YES results * * in ABEND0C4 RC00000004 after XMIT of * * the SYSREC data set. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** UNLOAD with SPANNED YES might cause DSNU038I - BLOCK SIZE FOR DCB, DDNAME ddname, IS TOO SMALL, MUST BE AT LEAST nnn BYTES and ABEND04E RC00E40079. This abend can occur if the length of the base row data is longer than the block size of SYSREC. In some cases the block size is determined by the system. IDCAMS shows zero rows in SYSREC after UNLOAD SPANNED YES due to incorrect format of VBS data set record segments. LOAD FORMAT SPANNED YES results in ABENDS0C4 RC00000004 (DSNURWBG OFFSET9A32 after XMIT of SYSREC data set. The SYSREC was generated by UNLOAD SPANNED YES, but the XMIT reformatted the VBS segments so that LOAD did not understand the data.
Problem conclusion
Modified UNLOAD code to be sensitive to the block size when writing the base row and LOB/XML data. Modified LOAD code to be independent of the location of data in the segments of the VBS data set.
Temporary fix
Comments
ž**** PE13/08/05 FIX IN ERROR. SEE APAR PM94155 FOR DESCRIPTION ž**** PE14/04/02 PTF IN ERROR. SEE APAR PI09425 FOR DESCRIPTION
APAR Information
APAR number
PM73034
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-17
Closed date
2013-06-10
Last modified date
2015-09-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK94806
Modules/Macros
DSNURELD DSNURILD DSNUROFL DSNURPLD DSNURPLL DSNURPPD DSNURWBF DSNURWBG DSNURWI DSNURWRF DSNUULIA DSNUULMB
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK94806
UP13/06/26 P F306
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":"10.1","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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
28 September 2015