Administration Guide

Directory Services Restrictions

This section describes what is not supported.

• Not all database clients may be supported. See your Quick Beginnings manual to determine whether DCE directory services is supported from your DB2 client. Currently, support is only provided for DB2 Client Application Enabler for all UNIX platforms (except HP-UX) and for OS/2.
• A client cannot use DCE Directory Services to connect to a DB2 for OS/2 Version 1 server.
• Only OS/2 clients can use any or all of the TCP/IP, APPC, NetBIOS, and IPX/SPX protocols. All supported UNIX clients (see above) can only use the TCP/IP and APPC protocols.
• LIST DATABASE (or NODE) DIRECTORY COMMANDS only provide entries from the local directories and not entries from the DCE directory. You can use the cdscp show object command in DCE to display the objects.
• When all of the following conditions exist, the owner of the database manager instance must login to DCE before starting the database manager (using the db2start command).
  • The database manager instance is configured to support DCE directory services through the dir_type configuration parameter
  • The cell directory services object can only be read by explicitly logging into DCE
  • The DCE directory must be accessed to support either of the following:
    • A transaction manager database (specified by the tm_database configuration parameter) located on another instance
    • A client that cannot support DCE directory services, or is not configured to use DCE directory services.

  Note:

  When performing the DCE login, you should use a principal that has a long ticket lifetime.

• When using a DDCS Version 2.2 (or earlier) gateway to connect a client that is using DCE directory services to a DRDA server, you must catalog the database alias in the gateway's local directory. This database alias must be the same as the alias on the client and it must represent the same database.

[ DB2 List of Books | Search the DB2 Books ]