A fix is available
APAR status
Closed as program error.
Error description
When setting a constant date value if column value in input file is null, LOAD utility reports message DSNU310I. DSNU310I DSNURCON - RECORD (1) WILL BE DISCARDED DUE TO 'xxx' CONVERSION ERROR FOR aaa.bbb ERROR CODE '05 - INPUT IS TOO LONG FOR A DATE' xxx POSITION(*) DATE EXTERNAL(DATE_E) CONSTANTIF(xxx='') CONSTANT('0001-01-01') . Additional Keywords: DB2OVRLAY/K
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 11 for z/OS users of the LOAD * * utility. * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNU310I, MSGDSNU334I, or ABEND04E * * RC00E20027 during LOAD FORMAT DELIMITED * * with CONSTANTIF(field='') for DATE * * EXTERNAL, TIME EXTERNAL, and TIMESTAMP * * EXTERNAL fields. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** A LOAD FORMAT DELIMITED was run with one input column specifying DATE EXTERNAL CONSTANTIF(field='') CONSTANT('01/01/0001'). Although the input values were valid, the job received DSNU310I with ERROR CODE '05 - INPUT IS TOO LONG FOR A DATE'. A logic error in checking for an empty string for the CONSTANTIF allowed code to execute that should not have, overlaying the value of the specified CONSTANT value. The same problem can occur for data types of TIME EXTERNAL and TIMESTAMP EXTERNAL, and with NULLIF(field='') or DEFAULTIF(field=''), and additional symptoms can be DSNU334I and ABEND04E RC00E20027. Additionally, whether or not DELIMITED was specified, the same problems could occur if the field comparison value for NULLIF, DEFAULTIF, or CONSTANTIF was not an empty string but was shorter than the expected length of the DATE EXTERNAL, TIME EXTERNAL, or TIMESTAMP EXTERNAL field.
Problem conclusion
LOAD has been modified to correct the null checking.
Temporary fix
Comments
APAR Information
APAR number
PI81201
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
2017-05-08
Closed date
2017-06-22
Last modified date
2018-03-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI81247 UI48243
Modules/Macros
DSNURWBG
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RB10 PSY UI48243
UP17/07/08 P F707
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:
14 March 2018