Recall that a terminal flow is a flow that interacts directly with the application screens of a terminal application running on a remote z/OS® system (see Terminal flow).
However, you cannot use mappings to manage the input parameters and the output parameters for an invocation, because a terminal flow cannot invoke other entities.
Also, a terminal flow contains mappings that the host editor creates during flow recording for each application screen, to implement the actions (AID key actions, Input actions, Extract actions, or Insert actions) that you specify for the application screen during flow recording (see Overview of creating an action and How actions are implemented in mappings: AID key, Input, Extract, and Insert).
The mappings created for AID key actions, Input actions, and Insert actions are stored into the mapping routine associated with the input terminal of the Invoke screen operation node corresponding to the application screen for which you created the actions.
The mappings created for Extract actions for the same application screen are stored into the mapping routine associated with the immediately preceding Invoke screen operation node or Assign node (see Implementation of Extract actions and Insert actions).