Apply Batch Executive configuration settings

Configuration settings

Enable Restart for RUNNING Batches with Steps in HELD

Default setting = Yes

This specifies whether the Restart button will be available in the Batch List View if there are items in HELD. If this option is set to Yes, the Restart button will be available on the Batch List View, similar to the previous Batch Executive Architecture.

Delete Inactive Runner Directories Older Than

Default setting = 5 days

Sets the length of time the Runner directories are preserved in “\DVData\Batch\Backup\” after the batch has been removed from the Batch List View.

No Equipment Acquired Security Check

Default setting = No

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. For example, creating a batch with deferred units will require security privilege in AREA_A if this option is set to Yes.

4600 Requests always Release Resource

Default setting = No

This feature specifies that a single 4600 request releases a held resource, even if multiple 4500 requests were used to acquire the resource. If set to No, there must be one 4600 request for each 4500 request issued for that resource. If this option is set to yes, only a single 4600 request is required to release all equipment, even if multiple 4500 requests were issued.

Check Failed Control Network Items on Download

Default setting = No

Rescans will be done for the initially unresolved or unassigned equipment 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 next option (Check on Verify Phases), is also 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

Default setting = Yes

Rescans will be done for initially unresolved or unassigned equipment when the Verify Phases button is clicked.

Prompt Operator on Apparent Config Errors

Default setting = Yes

This specifies whether the operator should be prompted to continue or not if there are phase configuration mismatches between the Controller and the Batch Executive. If set to No, batches with mismatches will be put in the HELD state.

Confirm Config Error Prompts

Default setting = No

This setting determines if a confirmer is required for configuration error prompts.

Verify Config Error Prompts

Default setting = No

This setting determines if a verifier is required for configuration error prompts.

Check Phases on Batch Load

Default setting = No

The runner checks to see if BSTATUS is good for all phases in recipe upon load.

Enable Alarm and Events Journaling

Default setting = No

This specifies whether the Batch Executive should create an entry in the Event Chronicle for the following significant Batch Executive events:

• Batch Load (batch created in the Batch List View)

• Batch Remove (batch removed from the Batch List View)

• Procedure Started

• Procedure Finished

• Unit Procedure Started

• Unit Procedure Finished

• Operation Started

• Operation Finished

• Phase Started

• Phase Finished

• Resource Acquired by Recipe

• Resource Released by Recipe

• Mode change for any recipe in a batch

Launching Runner Failed Timeout

Default setting = 90 seconds

Sets the length of time the Batch Manager will wait for a runner to become READY before assuming it never will thereby setting it to LOAD_FAILED.

Enforce Batch Size Check

Default setting = Yes

If set to No, created batches can be scaled to exceed the maximum ‘batch size’ defined in the recipe.

Format Floating Point Strings

Default setting = No

Changes the way floating point strings are formatted when written out (for example, to an EVT file or operator display). When set to 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

Default setting = No

Allows the option of not validating the Active Step Change (ASC) request. The default is No, therefore, validation does occur.

Note

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

Default setting = Yes

Specifies whether, during recipe synchronization, the Batch Runner checks all persisted report parameters to make sure that no types have been changed. In very large batches, this process can take a very long time, therefore the Resync may not be completed and the batch is put in the RECOVER_FAILED state. If this 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, thus resulting in batches that are not recoverable.

Resync - Resolve Formula Values for Top Level Parameters

Default setting = Yes

Specifies how parameters are updated during recipe resynchronization. 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, so 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. Refer to the ‘Parameter Values Resynchronization Chart’ topic in Books On-Line for details.

Allow ASC Rebind of Steps Configured to Retain Unit

Default setting = No

Allows the rebind of an active step when its option ‘Retain unit after completing unit procedure’ is enabled. The default is No; do not allow a rebind on steps with this (retain unit) 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 “<none>” to EVT File if Uploaded Report Parameter is Blank

Default setting = No

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

Default setting = Yes

This setting determines if the Batch Manager will re-launch the Runtime Server if it detects that it is no longer present.

Launch Runtime Server in the Interactive Windows Station

Default setting = Yes

Specifies whether the batch runtime server process would be launched in the Interactive Windows Station rather than a background process. The default behaviour is Yes, which 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 Stations

Default setting = Yes

Specifies whether the batch runner processes should be launched in the Interactive Windows Station rather than in a background process. The default behaviour is Yes, which 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

Default setting = No

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

Default setting = No

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

Default setting = Yes

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

Default setting = No

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.

Note

Procedure-owned resources are always released across a reset unless the contained unit procedure has the Retain unit after completing unit procedure? option selected AND the Release Retained Resources for Reset Batch is set to No.