Rational Developer for System z

Mapping routines

A mapping routine is a serial collection of mappings that can be performed at specified point in a flow.

Using the flow editor, you can associate a mapping routine with certain types of items in a flow (see Artifacts from which mapping routines can be referenced).

When a flow is being performed in a runtime environment, and the runtime environment processes an item with which a mapping routine is associated, then the runtime environment performs the mapping routine.

When the runtime environment performs a mapping routine, it performs each mapping in the mapping routine one after another, from top to bottom.

A mapping routine can contain 0, 1, or multiple mappings. If a mapping routine is empty (has 0 mappings) then even if it is associated with one of the items in the preceding list, it has no effect on a flow (no runtime code is generated).

A mapping routine is stored in a mapping file and can be modified in the mapping editor (see Mapping files and Mapping editor).

Mapping routines are used for a somewhat different purpose in terminal flows than in nonterminal flows (see Mapping routines in terminal flows and in nonterminal flows).

When the service flow project tools create a mapping routine automatically, they generate a default name for mapping routine using the following formula:

      <node_name>.<p>_<terminal_name>

Where <node_name> is the name of the node, <p> is a prefix -- either t for an input terminal or r for an output terminal, and <terminal_name> is the name of the input or output terminal. For example:

      MainMenu_01.t_InquireCatalog_01ns_InquireCatalog_01


Feedback