DB2 10.5 for Linux, UNIX, and Windows

CATALOG NAMED PIPE NODE command

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 only.

Authorization

One of the following authorities:

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.
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: AIX, WIN, HPUX, SUN, OS390, OS400, VM, VSE, SNI, SCO, and LINUX.

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 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 the LIST NODE DIRECTORY command.

If directory caching is enabled (see the configuration parameter dir_cache in the GET DATABASE MANAGER CONFIGURATION command), 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 might not be effective until the application has restarted.

To refresh the CLP's directory cache, use the TERMINATE command. 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.