This is part of the larger task of customizing your z/OS environment.
WebSphere Business Integration Event Broker for z/OS accesses DB2 tables using ODBC. To connect to DB2 using ODBC, the location name of the DB2 subsystem is used. See the DB2 UDB for OS/390® and z/OS V7 Data Sharing: Planning and Administration manual for more details.
When your DB2 system starts up it displays the message DSNL004I DDF START COMPLETE. The location name is displayed just after this message.
WebSphere Business Integration Event Broker for z/OS customization creates an ODBC initialization file, DSNAOINI. It contains necessary information to establish the ODBC connection. See the DB2 UDB for OS/390 and z/OS V7 ODBC Guide and Reference manual for more details.
Avoid using a data source name that is the same as the subsystem ID or data sharing ID. Using the same name affects the granularity of directives on connection with the database.
The mqsicustomize command generates two separate sections in DSNAOINI for subsystem ID and DSN location. If the section names are equal, keywords from the second instance of the section (such as CURRENTSQLID) are ignored.
If you choose to use the same value for the data source name and subsystem ID, you must edit DSNAOINI in the broker directory so that the Datasource and Subsystem keywords are in one section. Do this after running mqsicustomize, as detailed in mqsicustomize command.
See the DB2 UDB for OS/390 and z/OS V7 ODBC Guide and Reference manual for more information on customizing DSNAOINI.
select * from SYSIBM.SYSPACKLIST where planname ='DSNACLI';Rebind if the location column is blank and not *.
Check that DSNACLI is in the SYSIBM.SYSPLAN table.
You will get significant performance benefits from using the CACHE DYNAMIC SQL facility of DB2, because this eliminates the need to reprocess DB2 statements. See CACHEDYN=YES in the DB2 UDB for OS/390 and z/OS V7 Installation Guide.
If your user database is configured, using the DSNHDECP module, to use a comma as a decimal separator, you will find that there is a restriction. If there is a mismatch between DB2 and the locale settings of the user ID under which the broker runs (specifically LC_NUMERIC), your user database updates can be unpredictable.
To ensure that user database updates work correctly, configure DB2 and set LC_NUMERIC (through the LC_ALL setting in the mqsicompcif file) to use the same character, either a period or a comma, for the decimal point.