You can use the command line processor CATALOG command on any DB2 Connect system; the "Add Database SmartGuide" of the Client Configuration Assistant on OS/2, Windows 95, or Windows NT; or the Data Sources Setup tool on Windows 3.1 or Windows 3.11 for Workgroups. If you have the DB2 Software Developer Kit (SDK), you can also create an application program to catalog entries. For information about APIs, see the Administrative API Reference and the Command Reference. Note that to catalog a database, you must have sysadm authority.
To update the directories using the command line processor, do the following:
db2 CATALOG APPC NODE nodename REMOTE symbolic_destination_name SECURITY security_type
For example:
db2 CATALOG APPC NODE DB2NODE REMOTE DB2CPIC SECURITY PROGRAM
db2 CATALOG TCPIP NODE nodename REMOTE hostname or IP address SERVER service_name or port_number SECURITY security_type
For example:
db2 CATALOG TCPIP NODE MVSIPNOD REMOTE MVSHOST SERVER DB2INSTC
The default DRDA port number for TCP/IP connections is 446.
db2 CATALOG DCS DATABASE database_name AS target_database_name [AR application_requester] [PARMS "parameter string"]
For example:
db2 CATALOG DCS DATABASE DB2DB AS NEW_YORK3
Or, for OS/2 or Windows NT:
db2 CATALOG DCS DATABASE DB2DB AS NEW_YORK3 PARMS "NOMAP,D"
Or, for AIX:
db2 CATALOG DCS DATABASE DB2DB AS NEW_YORK3 PARMS '"NOMAP,D"'
Note: | See Specifying the Parameter String for information about using the operating system escape character when specifying the LOCALDATE mask in the parameter string. |
db2 CATALOG DATABASE database_name AS alias AT NODE nodename AUTHENTICATION authentication_type
For example:
db2 CATALOG DATABASE DB2DB AS NYC3 AT NODE DB2NODE AUTHENTICATION DCS
If you have remote clients, you must also update directories on each remote client. For more information, see DB2 Connect Enterprise Edition for OS/2 and Windows NT Quick Beginnings.