The Operation Destinations dialog box contains settings that supply the Design
Tool with methods of reaching alternative entities using the selected operation.
Click the Destinations button on the Operation
tab to open this dialog box.
Note: Alternate destination entities in an operation will never be reached
using the Host Emulator as the host.
The following options are available:
- Unassigned entities
Contains the names of all entities in the model that are not assigned to
be navigated to with the selected operation. To enable any of these entities
to be navigated to with the selected operation, move them to the Valid
- Right arrow buttons
- To add an entity to any of the following boxes, select it from the
Unassigned entities box and then click this button.
- Left arrow buttons
- To remove an entity from any of the following boxes, select it and
click this button.
- Valid alternates
- Valid alternates are entities that can be traversed to during navigation
of an operation. If an operation is executed and an entity in this box is
its destination, the operation will be considered successfulit's an
alternative outcome that is still valid.
- Intermediate entities
- Intermediate entities are considered to be a part of the operation but not
a destination of the operation. For example, a Splash screen that is encountered
during the operation, but is not the origin or destination of an operation,
could be a good candidate for an intermediate entity.
- Select an intermediate entity from the Intermediate entities box
and select the Execute operation option to choose an operation to execute
when this entity is encountered. Only operations of the currently selected
intermediate entity will be available.
- Issue these commands
- Select an intermediate entity from the list, and click the Edit button to
define commands that will bypass the intermediate entity in order for the
operation to reach its destination. For example, define a terminal key command,
like rcIBMEnterKey, for the intermediate entity so the host recognizes that
when the Enter key is pressed, it should immediately bypass this screen.
- User-defined error entities
- An error entity
is a location that constitutes an error condition if it's detected during
You can also choose to define a custom error message by creating unique text
or returning attribute data as your error message when an error entity is
encountered. Select one of the following options to customize an error message
to appear when your error entity is reached:
- Return textSelect this option to create any return text that
will be displayed if the error entity is encountered during execution of this
- Return attribute contentsSelect this option to return one or
more attribute values as the contents of your error message. Select the attribute
from the Unused list and click the right arrow button to add it to
the Return list. Attributes are returned in listed order.
- If you are using table procedures, you can choose to add
the error entity to your procedure. To define a custom error message
when using table procedures, use the Procedure
Editor. The error message feature within the Procedure Editor does
not allow you to assign the contents of an attribute to an error message.
- If the starting entity for your operation is also your error entity,
be sure to clear the Wait for host update check box on the Operation
tab. Otherwise, the error entity will not be recognized and you will not
get an error until the operation times out. In this scenario, error
patterns are strongly recommended as an alternative solution.
The following buttons are also available:
CloseClick to close this dialog box.
RevertClick to restore the previously saved values in this dialog
HelpClick to view the online help for this dialog box.