bulk_batch_size

Indicates how many job and resource details the gateway should load into memory at a time before saving the entities in the Control-M/EM database when performing a download from Control-M. A larger number causes the download to occur faster and more efficiently, at the expense of virtual memory.

Valid values: Any whole number that is equal to or greater than 10.

Default: 100

continue_not_responding

Indicates how the new gateway handles multiple gateway instances for the same Control-M installation if all attempts to stop and kill the original gateway are unsuccessful.

Valid values:

• Y- Both gateway occurrences are allowed to run concurrently. This is not recommended.
• N- The original gateway continues in its "hung" state. The new gateway stops running.

Default: N

dal_rel_cache_size

Valid values:Do not change this parameter unless instructed to do so BMC Software Technical Support.

dal_select_min_bulksize

dal_select_max_bulksize

dal_insert_min_bulksize

dal_insert_max_bulksize

These parameters indicate the bulk size being used by the database access layer during bulk insert and choose SQL operation. Larger numbers cause the insert and choose SQL operations to occur faster and more efficiently, at the expense of virtual memory.

Valid values: Any whole number that is equal to or greater than 10.

Defaults:

• dal_select_min_bulksize: 10
• dal_select_max_bulksize:
• Sybase and Oracle: 50
• MSSQL: 20
• dal_insert_min_bulksize: 10
• dal_insert_max_bulksize:
• Sybase and Oracle: 100
• MSSQL: 10

em_connect_method

Indicates in which mode the gateway opens communication connections.

Valid values:

• 1 - The gateway establishes connections in blocking mode.
• 2 - The gateway establishes connections in non-blocking mode.

gtw_send_ctl_timeout

Timeout period, in seconds, for determining if the original gateway is responsive (up).

Valid values: Any whole number that is equal to or greater than 20.

Default: 45

kill_not_responding

Indicates whether a new gateway stops or kills existing gateway instances for the same Control-M installation.

Valid values:

• Y - The new gateway tries to kill the original gateway and, if successful, continues to run. If the original gateway cannot be killed, the new gateway handles the original gateway according to the continue_not_responding parameter.
• N - The new gateway tries to stop the original gateway (using the ctl utility) and, if successful, continues to run. If the original gateway is not stopped after 3 attempts, the new gateway handles the original gateway according to the continue_not_responding parameter.

Default: N

nonBlockTimeout

If a gateway is in non-block mode and part of a message is not received during the number of seconds specified in this parameter, the gateway assumes communication is down.

Valid values: Do not change this parameter unless instructed to do so by BMC Software Customer Support

Default: 40.

This parameter is relevant only if the useNonBlock parameter is set to Y.

useNonBlock

Indicates whether the gateway operates in blocking mode or non-blocking mode. This mode determines whether the gateway receives entire messages or parts of messages.

Valid values:

• N - The gateway waits and receives for the entire message to arrive in blocking mode, regardless of length of time.
• Y - The gateway receives parts of messages (non-blocking mode). Communication is assumed to be down if part of a message is not received within the time interval specified in the nonBlockTimeout field.

Default: N