Troubleshooting Guide

Troubleshooting Tips for Host Connections to DB2 Universal Database

See the Quick Beginnings for your server for detailed instructions on how to set up connections so that host clients can access DB2 Universal Database databases.

Use the following checklist as a starting-point for diagnosing problems with these connections:

[  ]

Are the application server and host correctly configured? (For MVS hosts, ensure that SPUFI is configured as well.)

[  ]

Are the appropriate authentication types being used?

The following authentication settings can be used in the database manager configuration at the DB2 Universal Database server:

• When using Communications Server/2 on OS/2 or SNA Server/6000 on AIX, SERVER or CLIENT
• In all other cases, CLIENT or DCS

[  ]

Is the communications layer set up properly on the machine where DB2 Universal Database resides?

For example:

• On OS/2, Communications Manager or Communications Server must be set up.
• On AIX when using SNA, the TP name used by the host client must match the TP name on the AIX machine.

[  ]

Is two-phase commit properly set up if it is being used?

[  ]

Are the same bind options used on the host and on DB2 Universal Database?

You must select bind options that are supported by DB2 Universal Database and override defaults on the host (date and time options, for example). On MVS, you may want to bind SPUFI against the DB2 Universal Database database.