NETMAP.CHECK = NO | (ALL | TCP, ALL | BOTH | NODENAME, FAIL | WARN | PASS)
This parameter defines the communication types that perform NETMAP checking, the verification to perform, and the action to take if the node does not exist. This parameter is ignored for CTCA connections.
|NO||This value indicates that the IBM® Connect:Direct® node attempting to establish a session with this IBM Connect:Direct node need not be defined in the network map at this node. This feature is convenient when another IBM Connect:Direct node initiates contact the majority of the time.|
|ALL | TCP||ALL enables NETMAP checking for all communication
types except for TCP/IP.
TCP enables NETMAP checking for TCP/IP communication.
Note: If you code NETMAP.CHECK = TCP, you must provide a network map entry for each TCP/IP node. The adjacent node entry must specify the logical node name, port number, TCP/IP address, and a session type of TCP. For example:
ADJACENT.NODE=((UNIX.DALLAS,5555,188.8.131.52,TCP) ENVIRONMENT = UNIX)
|ALL | BOTH | NODENAME||ALL or BOTH (for SNA) enables verification on
both the logical node name and APPLID/LUNAME.
ALL or BOTH (for TCP) enables verification on both the logical node name and IP address.
NODENAME enables verification on the logical node name or TCP Alias names.
|FAIL | WARN | PASS||FAIL indicates that access to the system is denied.
WARN indicates that access is allowed, but a warning message is issued.
PASS indicates that access is allowed without any warning message being issued.
You must define all three parameters to require that the IBM Connect:Direct node establishing a session with this IBM Connect:Direct node be defined in the network map of this node under certain conditions.
To enable NETMAP checking for all communication types, you must code the NETMAP.CHECK parameter for each. Following is an example.
- The first entry for NETMAP.CHECK causes IBM Connect:Direct to check all communication types, except for TCP, for both NODENAME and APPLID/LUNAME.
- The second NETMAP.CHECK entry checks TCP nodes for NODENAME only. If the node does not exist, IBM Connect:Direct issues a warning message but permits access.
Modifiable through MODIFY INITPARMS command: NO