A fix is available
APAR status
Closed as program error.
Error description
Customer wants to run a LISTDEF statement in DB2 V11 in order to include just the same partition number of all the tablespaces in the same database. An UNLOAD is run with the following control statements: LISTDEF UNLDLIST INCLUDE TABLESPACE TRKSTFM.* PARTLEVEL 05 UNLOAD LIST UNLDLIST UNLDDN UNLDDS PUNCHDDN UNLDPU NOPAD and the customer gets the following : DSNU1039I PROCESSING LIST ITEM: TABLESPACE ... PARTITION 5 DSNU048I INVALID OPERAND FOR KEYWORD 'PART' The problem is happening because the involved tablespace is a PBG and partition 5 is not existing. Though the DSNU048I is reporting a syntax error for the keyword PART, so it is misleading. The more correct message to be externalized in this case should be : DSNU256I .... - INVALID PARTITION SPECIFICATION
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS * * users of UNLOAD utility. * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNU048I was issued during an UNLOAD * * LIST utility run on one part of a * * partition-by-growth (PBG) table space * * that did not exist. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** An UNLOAD utility ran on a list which included PARTLEVEL n for a PBG table space, but this partition did not exist yet. The message DSNU048I - INVALID OPERAND FOR KEYWORD 'PART' was issued to indicate a syntax error, which was not specific for the problem. This problem can also happen for UNLOAD TABLESPACE PART and other types of partitioned table space.
Problem conclusion
UNLOAD code has been modified to issue MSGDSNU256I instead of DSNU048I. DSNU256I - INVALID PARTITION SPECIFICATION.
Temporary fix
Comments
APAR Information
APAR number
PI66323
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
2016-07-22
Closed date
2016-08-24
Last modified date
2016-10-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI40339 UI40340 PI69247
Modules/Macros
DSNUULIA
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 October 2016