This section lists the most common problem scenarios found when using DB2 UDB DRDA AS.
Make sure the following are set properly at the DB2 UDB end.
Make sure the TP name is configured if necessary.
Also, if security SAME is to be used from the DRDA AR, ensure that it is enabled for the DRDA AR LU.
Make sure that db2start completes without any warning.
If SNA Server for AIX is in use, make sure that the group name for the ~/sqllib/adm/db2sysc executable is in the "Trusted group names" field in the "SNA System Defaults" profile in the SNA configuration.
If the DRDA AR is DB2 for OS/390, make sure that the following fixes have been applied: APAR PQ05771/PTF UQ06843 and APAR PQ07537/PTF UQ09146.
Make sure that the DRDA AR is configured with the database alias for the target DB2 UDB database.
There are special considerations with regard to the AUTHENTICATION setting in the DB2 UDB database manager configuration if the connection from a DRDA AR is over APPC/SNA LU 6.2. If you encounter a security error, please make sure that the database manager configuration AUTHENTICATION setting is set correctly as follows:
With this setting, both security SAME and PROGRAM connections will work.
With this setting, only security PROGRAM connections going to the DB2 UDB DRDA AS on AIX with SNA Server and on OS/2 with CS/2 V4 (with SPM configured) will work.
AUTHENTICATION DCS can now be used with DB2 UDB Version 7 DRDA AS to permit APPC connections from DRDA clients using security SAME (no password required), while at the same time enforcing SERVER authentication (which requires a password) for all other client requests.
With this setting, the following will work:
Security SAME
Security SAME or PROGRAM
These differences exist because some communications subsystems do not expose an incoming password to DB2 UDB.
An SQLCA with SQLCODE -4930 may be returned if a bind option specified by the DRDA AS is not supported. The SQLERRMC field contains information on the bind option causing the error.