A fix is available
APAR status
Closed as program error.
Error description
DSNU049I- DSNUGPRS- INVALID OPERAND 'SYSREC' FOR KEYWORD 'LOAD' Was issued for a LOAD that previously worked. The LOAD statement has top level LOAD keywords after the INTO TABLE clause, which is not supported in the syntax. Example statement that will issue the DSNU49I message: LOAD DATA LOG NO NOCOPYPEND ENFORCE NO INTO TABLE SYSADM.TB1 FORMAT INTERNAL RESUME YES INDDN SYSREC
Local fix
Use the following instead: LOAD DATA INDDN SYSREC LOG NO NOCOPYPEND ENFORCE NO INTO TABLE SYSADM.TB1 FORMAT INTERNAL RESUME YES
Problem summary
**************************************************************** * USERS AFFECTED: * * All Db2 12 for z/OS users of LOAD * **************************************************************** * PROBLEM DESCRIPTION: * * During LOAD, DSNU049I was issued * * for the following working LOAD * * statement: * * * * LOAD DATA LOG NO NOCOPYPEND ENFORCE NO * * INTO TABLE SYSADM.TB1 * * FORMAT INTERNAL RESUME YES * * INDDN SYSREC * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** In the LOAD utility syntax diagram, keywords which apply to the entire statement appear before the INTO TABLE clause; however, Db2 12 for z/OS does not issue a syntax error message when INDDN is specified after the INTO TABLE clause. PH11741 describes a problem in which during LOAD, MSGDSNU049I was issued for a LOAD statement which had INDDN after the INTO TABLE clause. DSNU049I DSNUGPRS INVALID OPERAND 'SYSREC' FOR KEYWORD 'LOAD' Example statement that will issue the DSNU49I message: LOAD DATA LOG NO NOCOPYPEND ENFORCE NO INTO TABLE SYSADM.TB1 FORMAT INTERNAL RESUME YES INDDN SYSREC Note: In the above example, the INDDN keyword applies to the entire LOAD statement, not the INTO TABLE.
Problem conclusion
LOAD was modified to resolve the aforementioned problem.
Temporary fix
Comments
APAR Information
APAR number
PH11741
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-05-03
Closed date
2019-06-04
Last modified date
2019-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI63419
Modules/Macros
DSNUGPRT DSNUGPPF
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI63419
UP19/06/20 P F906 {
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 July 2019