Appendix B: Omnicomm configuration settings

MAX_USER_DATA

8,000 bytes

The maximum size of the user data in a command request. Protocols use this setting to hold protocol-specific data.

If command requests exceed this size, the system generates the following error message:

User Data size %d exceeds max allowed %d

MIN_SLEEP_MS 

40 milliseconds

The minimum time in milliseconds (multiplied by four) to lock a queue while Omnicomm purges data.

This setting affects the command request, as well as all internal queues.

DFT_OMNI_CRIT_SECONDS

180 seconds

The time interval at which Omnicomm checks in to ProcessMonitor when performing a critical task.

CHECKIN_INTVL_SECONDS

10 seconds

The time interval at which Omnicomm checks in to ProcessMonitor when not performing a critical task.

MAX_CHECK_CMDS_DELAY

2,000 milliseconds

The time to wait in milliseconds before checking all connections for data.

MAX_REMOTE_CONN

304

The maximum number of remotes on one connection.

If the system detects a configuration with more remotes on one connection than this value, it generates the following error message:

Too many remotes on connection (%d max)

Note: This value must be a multiple of eight.

MAX_TX_RETRY

2

The maximum number of times to retry transmitting a query on a network.

POST_HOT_OWN_DELAY_SECONDS 

30 seconds

The number of seconds for Omnicomm to wait before processing connections.

The valid range is 0 to 300.

MODEM_ESC_PAUSE_MS

1,500 milliseconds

The time value in milliseconds for a modem escape sequence pause.

MODEM_MIN_DELAY_MS

50 milliseconds

The minimum delay period in milliseconds between modem commands.

MODEM_CNT_DELAYS1_MS

2,000 milliseconds

The modem on-hook or off-hook command timeout in milliseconds.

MODEM_CNT_DELAYS2_MS

1,000 milliseconds

The Modem Echo command timeout in milliseconds.

MODEM_CNT_DELAYS3_MS

1,500 milliseconds

The modem control "&" commands timeout in milliseconds.

MODEM_CNT_DELAYS4_MS

30,000 milliseconds

The modem dial command timeout in milliseconds.

MODEM_DCT_DELAYS1_MS

8,000 milliseconds

The modem hang-up timeout in milliseconds.

MODEM_CHK_DELAYS1_MS

8,000 milliseconds

The modem on-line state timeout in milliseconds.

OMNICOMM_BUILD_DELAY

0 milliseconds

The delay period in milliseconds for the Omnicomm rebuild (SCH_RBUILD) command from the command queue.

When the delay is zero or not set, Omnicomm immediately executes a rebuild of its internal hash tables once it receives the SCH_RBUILD command from the command queue. When the delay is greater than zero, Omnicomm starts a timer once it receives the first rebuild command from the command queue. If another rebuild command comes in at any time while the timer is running, the timer restarts from zero. When the timer expires, Omnicomm executes the rebuild of its internal hash tables.

Note: Omnicomm always executes a rebuild anytime it detects a change, regardless of the timer. For example, when you modify or create a connection, remote, or remconnjoin record.

RBUILD_BLOCK_COMMAND_ALL_REMOTE

false (default)

When false:

• An RBUILD command against a specific remote will not cause Omnicomm to abort the execution of commands that have already been read off the command queue for other remotes. The commands will still execute.

• Omnicomm aborts broadcast commands to a connection if an RBUILD command is executing on one of the remotes associated with that connection.

  Note: Data loading can trigger multiple instances of the RBUILD process. As a result, some of the commands may time out depending on the remote configurations, as well as the available resources and processing power on the servers.

true

When true:

• An RBUILD command aborts the execution of commands for all remotes, not just the remotes involved in the RBUILD.

• The system allows you to execute broadcast commands to any connection, regardless of whether or not an RBUILD command is in progress.