Troubleshooting
Problem
We are installing WDI 3.3 for z/OS. The DB2 bind step (Step 14) is returning DSNX200I with SQLCODE204.
Cause
The wrong SQLID was used to create WDI DB2 objects. An example of one of the error messages being issued:
DSNX200I - BIND SQL ERROR
USING owner AUTHORITY
PLAN=EDIENU33
DBRM=EDIELAS
STATEMENT=282
SQLCODE=-204
SQLSTATE=42704
TOKENS=owner.ELOG
CSECT NAME=DSNXOTL
RDS CODE=-500
Resolving The Problem
This error is saying that DB2 cannot find the object (TOKEN), which in this case it is identifying a DB2 synonym. Per page 27 of the WDI 3.3 Install Guide for z/OS this occurs when the SQLID used while creating the objects does not match the table high-level-qualifier. And be sure the OWNER in EDIJBIND job stream matches this SQLID (and high-level-qualifier).
Drop DATABASE EDIDB33E and redefine all WDI DB2 objects. For example, all SQL statements supplied on the WDI 3.3 distribution media create each table, view, index, etc. with 'EDIENU33' as the high-level qualifier. In which case, you would need to define a TSO ID 'EDIENU33' and give it DB2 DBADM authority, then use this id to create all objects. Use this DB2 command to switch to this ID before creating all of the objects:
SET CURRENT SQLID='EDIENU33';
Was this topic helpful?
Document Information
Modified date:
01 August 2018
UID
swg21232427