JR31041: RECEIVE SQL1390 ERROR WITH DB2WRITE OPERATOR ON DB2 V9 FP4 WITH Datastage v7.5.1a with patch e75063.

APAR status

• Closed as program error.

Error description

• Receive SQL1390 error with DB2 EE stage (db2write operator) on
  DB2 V9 FP4 with Datastage V7.5.1 and patch 75063 (or
  equivalent).
  
   ecase 75063
  It was a long standing complaint that db2 operators do not run
  on the conductor node against a remote DB2 database. The only
  case when such an enhancement has a practical sense is for the
  read mode.
  Set the following environmental varirable
  APT_DB2READ_RUN_CONDUCTOR and the db2read operator would start N
  player on the conductor node to obtain read data from DB2.
  You will need to specify the following paramters for the
  operator
  -client_instance
  -client_dbname
  -user
  -password
  
  The db2write operator checks if client instance name is
  specified or not. If true, it uses client dbname and client
  instance name for connection parameters.  If false, it uses
  remote dbname and remote instance name for connection
  parameters.
  Since client instance name and client dbname are being
  serialized in ecase 75063, these values are brought down to
  player level, and client dbname and client instance name was
  used instead of remote dbname and remote instance name.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using DB2 Enterprise Stage
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  DB2 Enterprise Stage job using Write Method = Write(db2write)
  fails with -1390 error when connecting to database
  
  
  
  ****************************************************************
  RECOMMENDATION:
  Apply patch for JR31041
  ****************************************************************
  

Problem conclusion

• db2write operator checks if clientname is specified or not. If
  true, it uses client dbname and client instance name for
  connection parameters.
  If false, it uses remote dbname and remte instance name for
  connection parameters.
  When using remote connection, dbname and client instance name
  was used instead of remote dbname and remote instance name.
  
  Fixed to use remote dbname and remote instance name at
  connection time.
  

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

• DB2
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R751 PSN

     UP