Command Reference

CATALOG APPC NODE

Adds an APPC node entry to the node directory. The Advanced Program-to-Program Communications protocol is used to access the remote node.

Authorization

One of the following:

• sysadm
• sysctrl

Required Connection

None

Command Syntax

>>-CATALOG--+-------+--APPC NODE--nodename--REMOTE--symbolic-destination-name-->
            '-ADMIN-'
 
>----+-------------------------+-------------------------------->
     |           .-PROGRAM--.  |
     '-SECURITY--+-NONE-----+--'
                 '-SAME-----'
 
>-----+---------------------------------+----------------------->
      '-REMOTE_INSTANCE--instance-name--'
 
>-----+----------------------+---------------------------------->
      '-SYSTEM--system-name--'
 
>-----+--------------------------------+------------------------>
      '-OSTYPE--operating-system-type--'
 
>-----+-------------------------+------------------------------><
      '-WITH--"comment-string"--'
 

Command Parameters

ADMIN

Specifies administration server nodes.

NODE nodename

A local alias for the node to be cataloged. This is an arbitrary name on the user's workstation, used to identify the node. It should be a meaningful name to make it easier to remember. The name must conform to database manager naming conventions (see Appendix B, Naming Conventions).

REMOTE symbolic-destination-name

Specifies the symbolic destination name of the remote partner node. The name corresponds to an entry in the CPI Communications side information table that contains the necessary information for the client to set up an APPC connection to the server (partner LU name, mode name, partner TP name). Maximum length is 8 characters.

SECURITY

Specifies the extent to which security information is to be used in the allocation request sent to the partner LU. Valid values are:

PROGRAM

Specifies that both a user name and a password are to be included in the allocation request sent to the partner LU. This is the default.

NONE

Specifies that no security information is to be included in the allocation request sent to the partner LU.

SAME

Specifies that a user name is to be included in the allocation request sent to the partner LU, together with an indicator that the user name has been "already verified". The partner must be configured to accept "already verified" security.

Note:

For connections using APPC to a DB2 for Windows NT Version 7.1 (or later) server, a user ID longer than 8 bytes is only supported when SECURITY is specified as NONE.

REMOTE_INSTANCE instance-name

Specifies the real name of the instance to which an attachment is being made on the remote server machine.

SYSTEM system-name

Specifies a name that is used to identify the server machine.

OSTYPE operating-system-type

Specifies the operating system type of the server machine. Valid values are: OS2, AIX, WIN95, NT, HPUX, SUN, MVS, OS400, VM, VSE, SNI, SCO, SGI, LINUX and PTX.

WITH "comment-string"

Describes the node entry in the node directory. Any comment that helps to describe the node can be entered. Maximum length is 30 characters. A carriage return or a line feed character is not permitted. The comment text must be enclosed by single or double quotation marks.

Examples

   db2 catalog appc node db2appc1 remote db2inst1 security program
      with "A remote APPC node"

Usage Notes

The database manager creates the node directory when the first node is cataloged (that is, when the first CATALOG...NODE command is issued). On an OS/2 client or a Windows client, it stores and maintains the node directory in the instance subdirectory where the client is installed. On an AIX client, it creates the node directory in the DB2 installation directory.

List the contents of the local node directory using LIST NODE DIRECTORY.

Note:

If directory caching is enabled (see the configuration parameter dir_cache in GET DATABASE MANAGER CONFIGURATION), database, node, and DCS directory files are cached in memory. An application's directory cache is created during its first directory lookup. Since the cache is only refreshed when the application modifies any of the directory files, directory changes made by other applications may not be effective until the application has restarted.

To refresh the CLP's directory cache, use TERMINATE. To refresh DB2's shared cache, stop (db2stop) and then restart (db2start) the database manager. To refresh the directory cache for another application, stop and then restart that application.