Tasks to complete before using the node group commands with DB2 Multisystem

Before using the Create Node Group (CRTNODGRP) command or any of the node group commands, you must ensure that the distributed relational database network you are using has been properly set up.

If this is a new distributed relational database network, see Distributed Database Programming for information about establishing the network.

You need to ensure that one system in the network is defined as the local (*LOCAL) system. Use the Work with RDB (Relational Database) Directory Entries (WRKRDBDIRE) command to display the details about the entries. If a local system is not defined, you can do so by specifying *LOCAL for the remote location name (RMTLOCNAME) parameter of the Add RDB Directory Entries (ADDRDBDIRE) command, for example:

  ADDRDBDIRE  RDB(MP000) RMTLOCNAME(*LOCAL) TEXT ('New York')

The iSeries™ server in New York, named MP000, is defined as the local system in the relational database directory. You can have only one local relational database defined on an iSeries server as the system name or local location name specified for this system in your network configuration. This can help you identify a database name and correlate it to a particular system in your distributed relational database network, especially if your network is complex.

For DB2^® Multisystem to properly distribute files to the iSeries servers within the node groups that you define, you must have the remote database (RDB) names consistent across all the nodes (systems) in the node group.

For example, if you plan to have three systems in your node group, each system must have at least three entries in the RDB directory. On each system, the three names must all be the same. On each of the three systems, an entry exists for the local system, which is identified as *LOCAL. The other two entries contain the appropriate remote location information.