Batch Executive configuration settings

You can access the Batch Executive Configuration Settings dialog by selecting the Advanced button on the Batch Application Manager dialog, and then clicking the Configuration Settings tab.

Most of the configuration settings are toggle switches that can be changed from YES to NO (and from NO to YES) by double-clicking the name of the Configuration Setting. A few options allow the entry of new values on dialogs that open when you click the name in the list. 

Enable Restart for RUNNING Batches with Steps in HELD - allows the user to restart a batch  or a step within a batch (after failures are cleared) when that batch or step is RUNNING but contains steps (at any level underneath) that are in the HELD or HELD_NC state. Note that steps within a batch must be in the appropriate mode (that is, O-AUTO) in order for the Restart button. This option's value is checked with a batch is created. Therefore, currently running batches are not affected by changing this value; only batches created after changing the value are affected. The default value is Yes.

Delete Inactive Runner Directories Older Than - specifies how long to wait before deleting an inactive batch runner's backup directory from ..\dvdata\batch\backup\. The default is five days; the minimum time is five minutes.

No equipment acquired security check - if the option is set to Yes, it specifies that all operator actions on batches with no active equipment will still require the corresponding security privilege in AREA_A. If the option is set to No, then no security check is required for batches with no active equipment. The default setting is No.

4600 Requests always Release Resource - specifies if a single 4600 request releases a held resource, even if multiple 4500 requests were used to acquire the resource. The default is No. There must be one 4600 request for each 4500 request issued for that resource. 

Check Failed Control Network Items on Download - rescans for the initially unresolved or unassigned equipment when only a recipe-related change is present and the Batch Executive download is performed. The default is No (that is no rescanning when only a recipe-related change is present and the Batch Executive download is performed). If an equipment-related change is downloaded, the rescan will occur automatically, regardless of this setting.

If this option is set to No and the following option (Check on Verify Phases) is set to No, the Batch Executive will not attempt to rescan for the initially unresolved or unassigned equipment unless an equipment-related change has been downloaded.

Check Failed Control Network Items when Verify Phases - rescans for initially unresolved or unassigned equipment when the Verify Phases button is clicked. The default is Yes (that is rescanning for initially unresolved or unassigned equipment occurs when the Verify Phases button is clicked).

If this option is set to No and the previous option (Check on Download) is set to No, the Batch Executive will not attempt to rescan for the initially unresolved or unassigned equipment unless an equipment-related change has been downloaded.

Prompt operator on apparent config errors - specifies whether the operator should be prompted with a choice to continue or not if there are phase configuration mismatches between the controller and the Batch Executive. If set to No, such batches will be put in the Held state. The default setting is Yes.

Confirm config error prompts - specifies whether confirmation is required to acknowledge configuration errors. The default setting is No.

Verify config error prompts - specifies that both Confirmation and Verification are required to acknowledge configuration errors. The default setting is No.

Check Phases on Batch Load - determines if batches should verify all phases in the recipe before launching. If a phase references a deferred unit (as with class-based units), that phase's units are not verified, even with this option set to Yes. In other words, verification is not performed on deferred units. Therefore, when the batch goes to run (load) the phase and the selected unit is not downloaded to the controller, the phase will go to Load_Failed. The default setting is No.

Enable Alarm and Events journaling - specifies whether the Batch Executive should create an entry in the Event Chronicle for significant Batch Executive events. The default setting is No.

Launching runner failed timeout - specifies how long the Batch Manager will wait for a runner to come up in the Ready state before it stops trying to launch the runner and sets it to Load_Failed. The default value is 90 seconds; the minimum value is 5 seconds.

Enforce batch size check - specifies whether a check should be made on the size of the batch. (If set to NO, created batches can be scaled to exceed the maximum "batch size" defined in the recipe.) The default setting is Yes. Changing this option requires a reboot of the Batch Executive computer for the change to take affect.

Format Floating Point Strings - changes the way floating point strings are formatted when written out (for example, to an EVT file or an operator display). The default is No. When No, the number 4 is written as 4. When set to Yes, the number 4 is written as 4.0. 

Skip Active Step Change Validation - allows the option of not validating the Active Step Change (ASC) request. The default is No; therefore, validation does occur. Removing validation should be done cautiously and with the knowledge that you can make a step active that is not typically permitted to be active at that point in the recipe.

Resync - Check report parameter types for errors - specifies whether, during a recipe resynchronization, the Batch Runner checks all persisted report parameters to make sure that no types have been changed. The default is Yes. In very large batches, this process can take a very long amount of time, such that the Resync does not complete and the batch is put in the RECOVER_FAILED state. If this case occurs, the report parameter check can be turned off (set to No). However, setting this option to No does not guarantee that the recipe will be successfully resynchronized, resulting in batches that are not recoverable.

Resync - Resolve formula values for top level parameters - specifies how, during a recipe resynchronization, parameters are updated. In a cold Resync, all parameters can be updated. In a warm Resync, only non-persisted parameters can be updated; that is, no set value will ever be overwritten. The default is Yes, the Batch Runner resolves any changes between the two versions of the formula. Setting this option to No allows any new parameters to get their default values which makes the batch appear to have run a non-custom formula but used values not in that formula.

Allow ASC Rebind of Steps Configured to Retain Unit - allows the ability to do a rebind of an active step when that step has this option enabled. The default is No, do not allow a rebind on steps with this option enabled. Allowing ASC rebind of steps that are configured to retain the unit can cause the unit to remain retained until the batch is removed from the batch list. Additionally, allowing this rebind when the recipe uses unit aliases can cause the units to be released (or not released) in an unexpected manner. These concerns are, in part, due to the pairings of the acquire and release requests.

Write "" To EVT File If Uploaded Report Parameter is Blank - write the string <none> in the EVT file when the report parameter is blank. Otherwise, the EVT entry for the report parameter is left blank. The default is No (do not write the string <none> in the EVT file).

Auto launch Runtime Server if it stops execution - specifies whether the Batch Manager should automatically re-launch the Batch Runtime Server if it stops running. The default setting is Yes.

Launch Runtime Server in the Interactive Windows Station - specifies whether the Batch Runtime Server process is launched in the Interactive Windows Station rather than a background process. The default behavior is Yes, and should be suitable for almost all machines and configurations. Before toggling this setting, Emerson support should be contacted so that an investigation as to why it is needed can be done.

Launch Runners in the Interactive Windows Station - specifies whether the Batch Runner processes are launched in the Interactive Windows Station rather than a background process. The default behavior is Yes, and should be suitable for almost all machines and configurations. Before toggling this setting, Emerson support should be contacted so that an investigation as to why it is needed can be done.

Hold any running batches on switchover - determines if the active (running or restarting) batches are Held (the Hold logic for the phase is executed) when a switchover of the Batch Executive occurs. This setting is used only when Redundant Batch is enabled, however it is always visible. The default is No. Changing this option does not require a download and immediately affects the running batches.

Use current parameter value in operator prompt - specifies what the value is in a parameter prompt, every time that prompt is issued to the operator (for example, when the recipe has a loop and the prompt is reissued on subsequent passes). When No, the configured default value is used. When Yes, the current value from the process is displayed. The default is No. Changing this option does not require a download. Changing this option only affects new batches and not currently running batches.

Allow Implicit Mode Change - allows the operator to select the ASC (Active Step Change) button even when the batch/step is in AUTO mode. When the ASC button is pressed the batch runner places the recipe (the parent of the recipe level currently selected) in MANUAL mode before entering the ASC_Pending state. A prompt is sent to the operator to confirm the mode change and the mode change is recorded in the EVT log. The parent step is then placed in the ASC_Pending state to allow operators to perform the active step change on the contained steps. There is no implicit mode change when the ASC is complete; therefore, the operator must change the parent step back to AUTO mode using the command bar buttons. The default is Yes. Changing this option only affects new batches and not currently running batches.

Release Retained Resources for Reset Batch - specifies if the resources owned by either a unit procedure or operation are released when a batch is reset. The default is No. Changing this option does not require a download and affects new batches.