Rational Developer for System z

How actions are implemented in mappings: AID key, Input, Extract, and Insert

This topic describes how mappings are used to describe how Input actions, AID key actions, Insert actions, and Extract actions are to be performed.

Recall that during flow recording the host editor creates for each new action that is created one or more mappings that describe how the operation that is specified in the action is to be performed (see Overview of creating an action).

The mapping or mappings that are generated for each of the four actions are described below. You can see and edit these mappings if you open the primary mapping file for a terminal flow and view the appropriate mapping routine.

"Fields" data structure: A mapping for an Input action, an Extract action, or an Insert action uses a message element that contains subelements corresponding to all the fields in the particular application screen for which the action was created. There is a subelement for every field in the application screen (whether the field is used in the mapping or not) and each subelement has the name (the custom name if any, otherwise the default name) of the field that the subelement corresponds to: Field2, Field 136, Field162, and so on.

a) AID key action:

b) Input action:

c) Extract action:

d) Insert action:


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)