Process configuration dialog box

Select Process > Configure to open the Process Configuration dialog box to the default Properties tab.

This table shows the availabe configuration items and how to configure:
Option Description
Default Engine Log Configuration Specify the default EO aliases to apply to this process. These default EO aliases apply to all threads in the process. Click List to select from a predefined list.
Xlate Engine Log Configuration Specify the translation thread EO aliases to apply. There is only one translation thread per process. Click List to select from a predefined list.

The process default and xlate EO aliases are evaluated and applied in the order they are listed, from left to right.

Process Bitmap Specify the bitmap file to use for all threads in the selected process. Or, click List to select from a file browser dialog box.

Select Overwrite Thread Bitmap to have the Process Bitmap setting to overwrite the thread Bitmap setting. If this check box is not available, then no process bitmap has been specified.

These settings are saved as process properties, and are reloaded to refresh the IDE when the corresponding process is selected.

The process bitmap is used if Process Bitmap is specified and the Overwrite Thread Bitmap option is selected, or if there is no thread Bitmap specified.

The thread bitmap is used if Process Bitmap is not specified and a thread Bitmap is specified.

If none of the above conditions are met, then the default is the thread bitmap.

By default, Process Bitmap is empty, the Overwrite Thread Bitmap is cleared, and the Thread Bitmap setting on the Thread Properties dialog box is empty.

Error Database Procs The error database TPS gives you a control point before a message is written to the error database. This indicates you have the opportunity to change the error message content and to route the message to another context.
Retries The maximum number of times to attempt message transmission:
  • "0" is the initial transmission only.
  • "1" is the initial transmission plus one retry.
  • "-1" is unlimited retries.
Automatic Log Cycling This automatically cycles message logs when they get to the size that is specified in Threshold in Kilobytes. Cycling a save file causes the current file to close, renames it to old_name.old, and opens a new save file. The save files are located in the subdirectory named %HCISITEDIR%\exec\processes\process.
Threshold in Kilobytes The maximum number of kilobytes the log file can attain before cycling.
Automatic SMAT Cycling This cycles the SMAT files. By default, this option is cleared. See "Automatic SMAT cycling conditions" in SMAT history.
Threshold in Kilobytes The maximum number of kilobytes that the messages size in the SMAT files can attain before cycling.
Disk-Based Queuing This uses disk-based queuing for this process.

Under normal processing, the queues in the threads and process are kept in memory (RAM) and backed by the recovery database, if in use. Disk-based queuing moves the data of the messages, but not the metadata, to disk only. This reduces the RAM required by the process.

Use this option if there is a high volume process, or if the process is working with large messages.

Messages using disk-based messaging save to the recovery database.

Threshold in Megabytes The maximum number of megabytes the log file can attain before cycling.

For example, disk-based queuing is selected and the total RAM that is required for the queues exceeds this threshold. This this case, all subsequent data posted to the queues is saved to the recovery database.

After the RAM requirements fall below this value, the message data is stored in RAM.

Translation Throttling Select this and then configure the Minimum, Maximum, or Percent values. These control how many messages the translation thread processes each time it runs. Under normal circumstances, the translation thread processes all of the messages on its queue. By specifying translation throttling, the number of messages that are processed is limited. This permits other threads in the engine process to run.

Minimum specifies that, if the number of messages on the queue is less than this value, all of the messages are processed. If the queue has more than this many messages, then the percentage is applied.

Maximum specifies the absolute maximum number of messages to process. If the Minimum is exceeded, then the percentage is applied. If the resulting number of messages is greater than this maximum, then only the maximum number of messages is processed.

Percent specifies the percentage of messages to process if the queue has more than the minimum number of messages.

Clear this for the translation thread to process all of the messages in the queue.

Route replies to original source only When this option is selected, the reply messages are routed only to the original source thread.

When cleared, the outbound thread reply is routed back by all reply routes to all inbound threads.

Select this when you have multiple inbound threads and only require the reply to go to the originating thread.

By default, this option is cleared.

Run translation procs in start-mode This runs the translation thread Tcl procedures in startup mode when a protocol thread is started. Unlike other TPS procs (for example, inbound TPS, outbound TPS), pre- and post-xlate TPS procs are not run in startup mode. Use in situations where the startup mode is required to run on pre- and post-xlate procs. For example, initializing global variables before running procs in run mode.
Multi-threaded Translation The translation thread can perform all transformations within a process with a single translation thread per process, or with a multi-threaded translation per process. See Multi-threaded translation.
Reuse parsed message A parse tree created by the grmcreate command in an inbound TPS or another UPoC before translation is cached for use by the translation engine.

By selecting this option, the grm object is cached to the message structure. In this way, the grmcreate Tcl command, TrxID parsing, and xlate parsing cache the grm every time it is parsed. It also cancels any subsequent parse if the message content is unmodified and the message format is the same.

The name in the Tcl command must match the name of the xlt file. If the names do not match, then the parse is not reused.

Note: This option is only supported for the XML message format; parsed data is not saved between contexts.
Enable message tracing (process level) When this is selected, tracing information is saved with the message trace framework to the tracing database.

Message tracing is enabled on the process level or thread level.

If process level tracing is enabled, then there is no requirement to turn on tracing for each individual thread under the process. Conversely, if process level tracing is disabled, then tracing for a thread is enabled with the thread level option.

By default, this option is cleared. When this is selected, all threads under the process automatically have tracing enabled.

Minimum Free Virtual Memory The minimum free virtual memory threshold for the process.