Database is not on the default port

For clients at version 7.0 and later that are not using the default port, a port number must be specified in the Connect Options field. However, for clients at version 2003.06.12 and earlier it is not possible to specify connect options. Therefore, to enable Rational® ClearQuest® version 2003.06.12 and earlier clients, and version 7.0 and later clients, to access the same DB2® database, either the DB2 database must run on the default port (50000), or all databases must run on the same nondefault port.

If the DB2 database is running on the default port, no special action is required.

If all databases are using the same port number, you can change the connection information as follows:
  1. Not specify the port number on the database properties pages of the schema repository and user databases.
  2. Use the installutil registerconnectoptions command to update the port number on every 7.0 and later Windows client.
  3. Update the port number in the CQ_OVERRIDE_DB2_CONNECT_OPTIONS environment variable on every Linux and UNIX system client.

If you make any changes to the connection information for the schema repositories and user databases, then you must propagate a new connection profile to the Rational ClearQuest clients. For more information about propagating a new connection profile to the Rational ClearQuest clients, see Propagating connection information to clients.

If all databases are not running on the same port, you can switch the DB2 database to the default port (50000) on the database server. In this case, you do not need to specify the port on the database properties pages of the schema repositories or user databases. You also do not need to update the connection profiles on any of the clients. Check with your database administrator; some organizations do not put databases on the default port for security reasons.

If none of these options are acceptable, you must upgrade all clients to version 7.0.1 at the same time.

Figure 1 shows the process.

Figure 1. Cross-version compatibility for DB2
A flowchart with the related configuration required to allow Rational ClearQuest clients using DB2 in different releases to interoperate.

Feedback