VTAM and NCF Node Table Definitions › NCF Node Table Definitions › Node Table Definition Example

Node Table Definition Example

UCC7NODE CSECT
DALLAS   UNCNOD  NODNAME=ADL0101,UCC7ID=01,JESNODE=DAL (local node)
CHICAGO  UNCNOD  NODNAME=ACH0201,UCC7ID=02,JESNODE=CHI
NEWYORK  UNCNOD  NODNAME=ANY0301,UCC7ID=03,JESNODE=NY
SANFRAN  UNCNOD  NODNAME=ASF0401,UCC7ID=04,JESNODE=SF,TYPE=LAST
         END

When a communications link is established between two nodes in a network, this "bind" process automatically includes a verification of the compatibility of the node tables at each of the two sites. Transmission of the node table to the other node with which communications are to be established is handled by the NCF VTAM task automatically.

Once the remote node table has been received, the following verification is performed against the two tables.

• The first entry in the node table must point to the local node. Thus, this implies that the node tables at two different sites are different, since each table has as its first entry its own local node name. You can use the same node table at all sites if you initialize NCF with the NCF(nn) option in the sysfile on the CA71 ADD statement during the CAS9 CAIRIM initialization with nn identifying the UCC7ID of the node where the initialization occurs.
• The first node in each table must be in the other table (in any position other than the first position).
• The node name and identifier byte, as defined with the UNCNOD macro parameters NODNAME and UCC7ID respectively, must be consistent between the two node tables for any node that appears in both tables.

See Messages CA-7.NC502 and CA-7.NC503 for possible errors. If one node can communicate with some nodes with which the other cannot communicate, extra entries may reside in that node table.