Performing 5250 Actions
45
Recording a 5250 Session
The 5250 component, like all UI components, differs from other components
because a major portion of the Action Model is built for you automatically. This
happens by interacting with a live session from the host in the Native Environment
pane and Composer recording your activity as a set of actions in the Action Model.
In other components, you must manually create actions in the Action Model,
which then perform mapping, transformation, and transferring tasks.
When you
create a 5250 component, you essentially record the requests and responses to and
from the AS/400, which generate actions in the Action Model pane specifying the
keystrokes and screen navigation required to build a component. For example,
when you select the Enter button in the 5250 Native Environment pane, the
Action Model records the action as shown in the graphic below. In addition, you
can add actions to the Action Model just the same as other components.
NOTE: You should be familiar with 5250 commands and the application you are
interfacing into your XML integration project in order to successfully build a 5250
component.
¾
¾¾
¾ To record a 5250 session:
1 Create a 5250 component per the instructions in “Before Creating a 5250
Component” on page 27. Once created, the new 5250 component appears in
the 5250 Component Editor window.
