Local Node Parameters

max.api.connects

The maximum number of concurrent API client connections permitted for the local node by different user IDS. There is no limit to the number of API connections by a single user ID.

A numeric value from 1 to 255. The default is 10.

conn.retry.stwait

The time to wait between retries immediately after a connection failure occurs. The value entered in the Short Term Retry Interval field of the network map remote node object overrides this value.

A 24-hour time value formatted as hh:mm:ss. The maximum value is 23:59:59. The default is 00:00:10, or 10 seconds.

conn.retry.stattempts

The number of times to attempt connection after a connection failure occurs. The value entered in the Short Term Retry Count field of the network map remote node object overrides this value.

A numeric value from 0–9999. The default is 10.

conn.retry.ltwait

The time to wait between long-term retry cycles. This parameter is a long-term connection retry parameter. The value entered in the Long Term Retry Interval field of the network map remote node object overrides this value.

A 24-hour time value formatted as hh:mm:ss. The maximum value is 23:59:59. The default is 00:03:00, or 3 minutes.

conn.retry.ltattempts

The number of times to attempt connection after a connection failure occurs. This parameter is a long-term connection retry parameter. The value entered in the Long Term Retry Count field of the network map remote node object overrides this value.

A numeric value from 0–9999. The default is 10.

contact.name

The name of a contact.

Any name description.

contact.phone

A phone number to use to contact the contact name.

Any valid phone number.

descrip

The description of the local node.

Any valid text string.

name

The name of the local node used when identifying the local server to remote nodes and the server object name for which API programs search when locating active Connect:Direct® servers. You cannot change the value of this parameter. If you want to change the local node name, you must reinstall IBM® Connect:Direct for Microsoft Windows.

A 1- to 16-character alphanumeric string specified during installation.

sess.pnode.max

The maximum concurrent connections for all remote nodes where the local server node is the originator of the Connect:Direct Process.

This field is limited to the lesser of the values defined in the initialization parameters file and the network map definition for a given node.

A numeric value from 1 to 255. The default value is 1 or half of the maximum sessions specified during installation. The workstation version of the product is limited to a maximum of one PNODE session.

sess.snode.max

The maximum concurrent connections for all remote nodes where the local node is the partner node of a Process.

This field is limited to the lesser of the values defined in the initialization parameters file and the network map definition for a given node.

A numeric value from 1 to 255. The default value is 1 or half of the maximum sessions specified during installation. The workstation version of the product is limited to a maximum of two SNODE sessions.

The maximum number of total concurrent connections for all remote nodes.

This field is limited to the lesser of the values defined in the initialization parameters file and the network map definition for a given node.

sess.default

The default session class for starting session managers. A Process executes on the specified class or any higher session class. If the value specified exceeds sess.pnode.max, a warning is issued and the value is reset to the default value. The value entered in the Default Class field of the remote node object overrides this value.

A numeric value from 1 to the value specified for sess.pnode.max.

The default is 1.

netmap.check

The level of network map checking that occurs for each node that you communicate with.

• Y—Checks the network map for all nodes that Connect:Direct will communicate with to validate the node name and the IP address.
• L—Checks the network map only for nodes that the local Connect:Direct will initiate sessions with.
• R—Checks the network map only for remote nodes that will communicate with this node.
• N—Does not validate any session establishment requests in the network map.

Y | L | R | N

The default is Y.

node.check

The level of node checking.

B—Checks both the node address and the node name.

C—Checks the node name only.

B| C

The default is B.

proxy.attempt

Enables the use of a proxy user ID for a remote node. The use of a proxy user ID offers improved security because neither the local system nor the remote system requires a real user ID from the other side.

Y | N

The default is N.

protocol

The communications protocol or protocols to be used by the local node. If more than one, separate entries with commas.

TCP

TCP—Specifies TCP/IP. This is the default.

tcp.api.port

One or more IP addresses (or host name) and optional port numbers used to establish client sessions with this Connect:Direct node.

[IP address | hostname][;port number]

The default port number is 1363.

See IP Addresses.

tcp.host.port

One or more IP addresses (or host name) and port numbers that remote Connect:Direct nodes will connect to for Process execution with this local IBM Connect:Direct for Microsoft Windows node.

One or more IP addresses (or host names) and/or port numbers that remote Connect:Direct nodes will connect to for Process execution with this local IBM Connect:Direct for Microsoft Windows node. You can specify IP address/hostname, IP address/hostname and port, or just a port.

[IP address | hostname][;port number]

The default port number is 1364.

See IP Addresses.

outgoing.address

A virtual IP address for adjacent nodes in a cluster (in a high-availability environment) to use for netmap checking by the remote node.

In a IBM Connect:Direct for Microsoft Windows high-availability cluster, each instance of IBM Connect:Direct for Microsoft Windows has a separate IP address and a virtual IP address assigned to the cluster. After all of the IBM Connect:Direct for Microsoft Windows high-availability nodes are configured to bind to the virtual IP address, remote nodes see the single virtual address during a session. If a node in the cluster fails, another high-availability node takes over. Any remote system that is using netmap checking will still allow communications with the high-availability system.

Be sure remote nodes specify this virtual IP address in their netmap entries for each node in the high-availability cluster.

IP address | hostname

See IP Addresses.

tcp.src.ports

An IP address or multiple addresses and the ports permitted for the address when going through a packet-filtering firewall.

Valid IP address with an optional mask for the upper boundary of the IP address range and the associated outgoing port number or range of port numbers for the specified IP address, for example:

(199.2.4.*, 1024), (fd00:0:0:2015:*::*, 2000-3000), (199.2.4.0/255.255.255.0, 4000-5000),(fd00:0:0:2015::0/48, 6000, 7000)

See IP Addresses.

A wildcard character (*) is supported to define an IP address pattern. If the wildcard character is used, the optional mask is not valid.

udp.src.ports

An IP address or multiple addresses and the ports permitted for the address when going through a packet-filtering firewall.

Valid IP address with an optional mask for the upper boundary of the IP address range and the associated outgoing port number or range of port numbers for the specified IP address, for example:

(199.2.4.*, 1024), (fd00:0:0:2015:*::*, 2000-3000), (199.2.4.0/255.255.255.0, 4000-5000),(fd00:0:0:2015::0/48, 6000, 7000)

See IP Addresses.

A wildcard character (*) is supported to define an IP address pattern. If the wildcard character is used, the optional mask is not valid.

tcp.src.ports.list.iterations

The number of times that Connect:Direct scans the list of available ports defined in tcp.src.ports to attempt a connection before going into a retry state.

This parameter is automatically added to the initialization parameter and is assigned a value of 1. If desired, change this value.

A numeric value from 1–255. The default value is 1.

udp.src.ports.list.iterations

The number of times that Connect:Direct scans the list of available ports defined in udp.src.ports to attempt a connection before going into a retry state.

This parameter is automatically added to the initialization parameter and is assigned a value of 1. If desired, change this value.

A numeric value from 1–255. The default value is 1.

comm.bufsize

The data buffer size for transmitting data to and from a remote node. For TCP/IP, this value will be overridden by the value in the Buffer Size field of the TCP/IP Communications Mode Object.

A numeric value from 256 to 65536.

The default is 65535.

pacing.send.delay

The default time, in milliseconds, to wait between send operations if the value is not in the network map entry. The value entered in the Pacing Send Delay field of the TCP/IP Communication Mode object overrides this value. A value of zero indicates that a data buffer should be sent as soon as possible.

A numeric value from 0–86,400,000 (one day in milliseconds).

The default is 00.00.00.

pacing.send.count

The default number of send operations to perform before automatically waiting for a pacing response from the remote node if the value is not in the network map entry. The value entered in the Pacing Send Count field of the TCP/IP Communication Mode object overrides this value. Specify zero for no pacing.

A numeric value from 0 to 32768.

The default is 0.

tcp.crc

Globally turns on or off the CRC function for TCP/IP processes.

ON | OFF

The default is OFF.

udp.crc

Globally turns on or off the CRC function for UDP processes.

ON | OFF

The default is OFF.

tcp.crc.override

Determines whether node and Process statement overrides for CRC checking are allowed. If this value is set to n, setting overrides for CRC checking will be ignored.

Y | N

The default is N.

udp.crc.override

Determines whether node and Process statement overrides for CRC checking are allowed. If this value is set to n, setting overrides for CRC checking will be ignored.

Y | N

The default is N.

tcp.max.time.to.wait

The maximum time to wait for each pending TCP/IP Read on node to node communications. If the value is 0, Reads will not time out.

A 24-hour time value formatted as hh:mm:ss. The maximum value is 23:59:59. The default is 00:03:00.

udp.max.time.to.wait

The maximum time to wait for each pending UDP Read on node to node communications. If the value is 0, Reads will not time out.

A 24-hour time value formatted as hh:mm:ss. The maximum value is 23:59:59. The default is 00:03:00.

tcp.window.size

The maximum amount of data in bytes that can be sent without receiving an acknowledgement. After a window size of data is sent without acknowledgement, no more data can be sent until an acknowledgement is received. When tcp.window.size=0 (default), the system's default value is used, which may be too low for a high-latency, high-bandwidth connection, causing slow data transfer rates. To improve performance in this situation, the window size configured for IBM Connect:Direct for Microsoft Windows must be large enough to allow a packet to be sent and its acknowledgement received without triggering a wait for an acknowledgement. The optimum window size is the smallest quantity of data that does not trigger waits.

In order for this parameter to take effect, ensure that the following criteria are met:

• RFC1323 support is enabled on the system.
• The system's maximum TCP window size is larger than the configured value.

The formula for determining the optimum window size is as follows:

BDP (bytes) = 125 x <bandwidth (Mb/s)> x <roundtrip delay in ms>

A numeric value from 0 to 2147483646.

The default is 0.

runstep.max.time.to.wait

The maximum time to wait for each pending run task or run job on node-to-node communications on the remote node only. If the value is 0, the run task or run job will not time out. This parameter prevents a task from being terminated when the tcp.max.time.to.wait value is reached. When runstep.max.time.to.wait is set to 0, tasks running on the remote node never terminate. When this variable is set to a value, a task is terminated if the remote task has not finished the job at the time interval defined. When a job is terminated, it is placed in the Hold (HE) queue and no retry effort is attempted. The statistics error reported is “FMH71 was not received.”

A 24-hour time value formatted as hh:mm:ss. The maximum value is 23:59:59. The default is 00:00:00.

active.directory.enabled

Specifies whether IBM Connect:Direct for Microsoft Windows updates its Active Directory entry at startup. This parameter is set automatically at installation. You do not need to update this parameter unless a node is inserted into or removed from the Active Directory after installation.

Y | N

The default is N.

quiesce.resume

Specifies whether testing mode is enabled for IBM Connect:Direct for Microsoft Windows . To enable the testing mode, you must specify Y for this parameter and have a valid NDMPXTBL parameter table in the Server directory where IBM Connect:Direct for Microsoft Windows is installed.

See Use Connect:Direct in Test Mode.

Y | N

The default is N.

tcp.api.inactivity.timeout

The number of seconds of session inactivity to wait before exiting a session. This helps prevent maximum connections (api.max.connects) being reached because of abrupt disconnections that do not free up resources in an orderly manner.

If you are using IBM Control Center to monitor your IBM Connect:Direct for Microsoft Windows server, set this value to at least twice the value of the Monitor Rest Time setting in Control Center.

A numeric value from 0 to 32767.

The default is 0.