JR30525: PROBLEM USING DB2/ZOS STAGE TO LOAD DB2 ON ZOS DUE TO JCL 72 CHA RACTER LIMIT

APAR status

• Closed as program error.

Error description

• This is an APAR for a Problem using db2/zOS stage to load db2 on
  zOS, the problem encountered
  is:
  1. Data Stage does not load table with longnamed null columns.
  2. Error "LOAD statement line longer than 72 !!!". As I
  understand Data
  Stage creates data set with too much characters (more than 72)
  and DB2
  can't use it.
  

Local fix

• Use a length under 72
  
  This fix is included in 8.0.1 fix pack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  DB2Z Stage user
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  LOAD failure with DB2Z Stage which LOAD statement is longer than
  72 characters per line
  
  ****************************************************************
  RECOMMENDATION:
  Apply patch for JR30525, or make the column name length smaller
  ****************************************************************
  

Problem conclusion

• JCL is limited to 72 characters per line, and if DB2 table has
  long column names, 72 character limit is being exceeded for
  LOAD statement.
  Fixed LOAD statement generation to put the name of the column on
  a line by iteself with the rest of LOAD syntax for the column on
  a separate line.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• PXDB2Z
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R801 PSN

     UP