TCP/IP Default Record

The tcp.ip.default record defines default information to use when the remote node is specified by IP address. The tcp.ip.default record parameters are described in the following table:

Parameter	Description	Value
conn.retry.stwait	The 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	The number of times to attempt connection after a connection failure occurs.	0–9999 The default is 6.
conn.retry.ltwait	The 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	The number of times to attempt a connection after all short-term retry attempts are used.	0–9999 The default is 6.
comm.bufsize	The buffer size for transmitting data to and from a remote node.	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.
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.
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–10,000 The value in seconds. The default value is 180. When set to 0, wait time is unlimited unless limited by the operating system.
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.	0–10000 The value in seconds. The default value is 0.
contact.name	The name of the 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
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.	0–999 The default is 255.
sess.snode.max	The maximum concurrent connections, where the local node is the secondary node in a session.	0–999 The default is 255.
sess.default	The default session class for starting session managers. A Process executes on the specified class or any higher session class. The value for this parameter overrides the equivalent value in the local.node record.	1–50 The default is 1.
pacing.send.delay	How long 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.
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.