...

The Manager attempts Server reconnection for a limited amount of time, as specified by the following configuration options:

• RECONNECT_RETRY_COUNT (number of retry attempts)
• RECONNECT_RETRY_INTERVAL (frequency of retry attempts)

...

Without Manager Fault Tolerance, the Server enters a disconnected state and waits for the Manager to reconnect. The user process continues running. However, if the user process attempts any I/O on the standard files, it will block. The Server waits for the Manager to reconnect for a period of time defined by the Manager's RECONNECT_RETRY_COUNT and RECONNECT_RETRY_INTERVAL configuration options. When that time has expired, the Server terminates the user process and exits.

With Manager Fault Tolerance, the Server continues executing in a disconnected state. The Server satisfies all user process standard I/O requests. The user process does not block. It continues to execute normally. When the user process ends, the Server waits for a Manager reconnect for a period of time defined by the JOB_RETENTION configuration option.

Universal Command Manager

You can configure Universal Command Manager to request the use of the Network Fault Tolerant protocol via its NETWORK_FAULT_TOLERANT configuration option.

If the Server does not support the protocol or is not configured to accept the protocol, the Manager continues without using the protocol.

...

You can configure Universal Command Server with or without the Network Fault Tolerant protocol via its NETWORK_FAULT_TOLERANT configuration option.

If the Server is configured with the protocol off, the Manager cannot override it. If the Server is configured with the protocol on, the Manager NETWORK_FAULT_TOLERANT configuration option specifies whether or not the protocol is actually used.