Remote Node Connection Record
The remote node connection record contains information you can use to define default values for a generic remote node connection or customize to for a particular new remote node. Following are the remote node connection parameters.
| Parameter | Description | Value |
|---|---|---|
| alternate.comminfo | Provides support for establishing netmap-checked sessions with systems with multiple IP addresses, such as IBM® Connect:Direct®/Plex z/OS. Use this parameter to list all IP addresses or host names that are part of the multiple IP address environment. For IBM Connect:Direct/Plex, this list should include the address of each IBM Connect:Direct/Server with a different IP address from the IBM Connect:Direct/Plex Manager.If the IP address of the initiating node does not match the IP address specified on the comm.info parameter, the alternate.comminfo parameter is checked for other valid IP addresses. For more information on specifying IP addresses and host names, see IP Addresses, Host Names, and Ports. |
host name/IP address or * host name—Host name associated with the IP address, for example: :alternate.comminfo=hops (where hops is a machine on the local domain) :alternate.comminfo=hops.csg.stercomm.com (fully-qualified host name) IP address——the IP address of a machine running IBM Connect:Direct in IPv4 or IPv6 format: nnn.nnn.nnn.nnn (IPv4) or nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn (IPv6) For example: :alternate.comminfo=10.23.107.5 :alternate.comminfo=fe00:0:0:2014::7 Specify multiple addresses/host names by separating them with a comma (,). A space can be added after the comma for readability. For example: 10.23.107.5, fe00:0:0:2014::7, msdallas-dt *—Accepts any IP address. This turns off IP address validation. Note: Partial pattern matches are not supported, such as: *.mydomain.com, myplex??.mydomain.com.
|
| alt.comm.outbound | Alternate communication address (communication path) used for outbound Processes. This parameter provides the alternate addresses for a remote node that has multiple NIC cards. When the local node is the PNODE, the alternate addresses are tried if an initial attempt to the primary address (specified in the comm.info parameter) fails. After a connection has been established, if the connection is subsequently lost, attempts to reestablish the connection through the retry mechanism use the same address as the initial connection. When the local node is the SNODE, the alternate addresses are used in the Netmap check. |
Fully-qualified host name/IP address;nnnn The host name/IP address and port are separated by a semi-colon (;). A comma separates the list of alternate communication paths, and the list is processed from the top down. For example: salmon;9400, 10.20.40.65;9500 For more information on specifying IP addresses and host names, see IP Addresses, Host Names, and Ports. |
| comm.bufsize | The buffer size for transmitting data to and from a remote node on TCP/IP connections. | The value for TCP/IP has no limit (up to 2,147,483,623). For LU6.2, the maximum is 32000. The default is 65536 bytes. |
| comm.info | The information needed to initiate connection requests to remote nodes using TCP/IP or LU6.2. This information refers to the network card that the local IBM Connect:Direct node uses to initiate outbound requests. This value is required.
|
For TCP/IP connections, specify the host name or the IP address and port number. The default port is 1364. For LU6.2 connections, specify a profile name, up to 8 characters. For more information on specifying IP addresses and host names, see IP Addresses, Host Names, and Ports. |
| comm.transport | The transport protocol for the remote node. | tcp | lu62 |blklu62 tcp—TCP/IP connections blklu62—Other LU6.2 connections |
| conn.retry.stwait | Time to wait between retries immediately after a connection failure occurs. The format is hh.mm.ss, where hh specifies hours, mm specifies minutes, and ss specifies seconds. | The maximum value is limited to the highest value in the clock format, 23.59.59. The default is 00.00.30, which is 30 seconds. |
| conn.retry.stattempts | Number of times to attempt connection after a connection failure occurs. | 0–9999 The default is 3. |
| conn.retry.ltwait | Time to wait between long-term retry attempts after all short-term retry attempts are used. The format is hh.mm.ss, where hh specifies hours, mm specifies minutes, and ss specifies seconds. | 0–23.59.59 The default is 00.10.00, or 10 minutes. |
| conn.retry.ltattempts | Number of times to attempt a connection after all short-term retry attempts are used. | 0–9999 The default is 6. |
conn.retry.exhaust.
action |
Action to take after the specified short and long-term retries have been used. | hold | delete hold—Places Processes in the Hold queue in Held in Error status, after all retry attempts are used. This is the default value. delete—Causes the Processes to be deleted from the TCQ. |
| contact.name | The name of the IBM Connect:Direct administrator or operator. | Name |
| contact.phone | The phone number of the IBM Connect:Direct administrator or operator. | Phone number |
| descrip | Comments to include as part of the record. | An unlimited string |
| pacing.send.count | The number of send operations to perform before automatically waiting for a pacing response from the remote node. The value for this parameter has no effect on LU6.2 connections. | No limit exists for the size of this value. The default is 0, which indicates no pacing of this type. |
| pacing.send.delay | The time to wait between send operations to the remote node. The decimal number is the number of milliseconds between the end of one packet and the beginning of the next packet. Time-based pacing does not contribute to network traffic. The value for this parameter has no effect on LU6.2 connections. |
nnn The size of this number has no limit. The default is 0, which indicates no pacing of this type. |
runstep.max.time.to.
wait |
The maximum time to wait for remote run steps to complete. Remote run steps include remote run task, run job, or submit statements. This wait time is different from the wait time specified by the tcp.max.time.to.wait parameter. Using runstep.max.time.to.wait prevents a Process from failing when a remote step takes longer to complete than specified in tcp.max.time.to.wait. The value is in seconds. | 0–10000 The default value is 0. |
| sess.total | The maximum number of concurrent connections between all nodes and the local node. The sum of api.max.connects and sess.total cannot exceed the number of file descriptors available. This value is system dependent. |
0–999 A 1–3 digit number. The default is 255. |
| sess.pnode.max | The maximum concurrent connections, where the local node is the initiator of the session. Number of PNODE sessions cannot exceed the total number of sessions. If sess.pnode.max is larger than sess.total, the value of sess.pnode.max is silently rounded down to the value of sess.total. |
0–999 The default is 255. |
| sess.snode.max | The maximum concurrent connections, where the local node is the secondary node in a session. Number of SNODE sessions cannot exceed the total number of sessions. If sess.snode.max is larger than sess.total, then it is silently changed to the value of sess.total. |
0–999 The default is 255. |
| tcp.crc | Turn on or off the CRC function for TCP/IP Processes on the remote node. | y | n The default is n. |
| tcp.max.time.to.wait | The maximum time the local node waits for a message from the remote node when using TCP/IP. When the time expires, an appropriate communication error is logged. If the time expires during a session start attempt, the process is moved to the Timer queue and Sterling Connect:Direct attempts to re-establish a session with the remote node. When set to 0, wait time is unlimited. | 0–10000 The value is in seconds. The default value is 180. |