Command Reference

CATALOG IPX/SPX NODE

Adds an Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) node entry to the node directory. The Novell NetWare IPX/SPX communications protocol is used to access the remote node.

This command is available on OS/2, Windows NT, and Windows 95 only.

Scope

IPX/SPX file server addressing is not supported in a multi-node environment.

Authorization

One of the following:

sysadm
sysctrl

Required Connection

None

Command Syntax

>>-CATALOG--+-------+--IPXSPX NODE--nodename--REMOTE--file-server-->
            '-ADMIN-'
 
>----SERVER--object-name----+---------------------------------+->
                            '-REMOTE_INSTANCE--instance-name--'
 
>-----+----------------------+---------------------------------->
      '-SYSTEM--system-name--'
 
>-----+--------------------------------+------------------------>
      '-OSTYPE--operating-system-type--'
 
>-----+-------------------------+------------------------------><
      '-WITH--"comment-string"--'

Command Parameters

ADMIN

Specifies that an IPX/SPX 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 file-server

Name of the NetWare file server where the internetwork address of the server database manager instance is registered. The internetwork address is stored in the bindery at the NetWare file server, and is accessed using object-name.

Note:

The following characters are not valid: / \ : ; , * ?

SERVER object-name

Name of the database manager instance stored in the bindery of the NetWare file server. Each server database manager instance registered at one NetWare file server must be represented by a unique object-name. It is recommended that each database manager instance on the network be represented by a unique object-name.

Note:

The following characters are not valid: / \ : ; , * ?

When cataloging the IPX/SPX client to use file server addressing, specify the file server and object name as defined above. When cataloging the IPX/SPX client to use direct addressing, specify file-server as *, and specify the server's IPX/SPX internetwork address in the object-name parameter. Use db2ipxad - Get IPX/SPX Internetwork Address to retrieve the server's IPX/SPX internetwork address. For more information about the addressing methods, see one of the Quick Beginnings books.

REMOTE_INSTANCE instance-name

Specifies the name of the server instance to which an attachment is being made.

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 ipxspx node db2ipx1 remote netwsrv server db2inst1
      with "A remote IPX/SPX node"
 
   db2 catalog ipxspx node db2ipx2 remote * server 09212700.400011527745.879E
      with "IPX/SPX node using direct addr"

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 ]