Command Reference

CATALOG NAMED PIPE NODE

Adds a named pipe node entry to the node directory. The named pipe is used to access the remote node.

This command is available on Windows NT only.

Authorization

One of the following:

sysadm
sysctrl

Required Connection

None

Command Syntax

>>-CATALOG--+-------+--NPIPE NODE--nodename--REMOTE--computername-->
            '-ADMIN-'
 
>----INSTANCE--instancename----+----------------------+--------->
                               '-SYSTEM--system-name--'
 
>-----+--------------------------------+------------------------>
      '-OSTYPE--operating-system-type--'
 
>-----+-------------------------+------------------------------><
      '-WITH--"comment-string"--'

Command Parameters

ADMIN: Specifies that an NPIPE administration server node is to be cataloged.
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 computername: The computer name of the node on which the target database resides. Maximum length is 15 characters.
INSTANCE instancename: Name of the server instance on which the target database resides. Identical to the name of the remote named pipe, which is used to communicate with the remote node.
SYSTEM system-name: Specifies the DB2 system 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, and SGI.
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 npipe node db2np1 remote nphost instance db2inst1
      with "A remote named pipe 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.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]