17
2
Getting Started with the 5250 Component Editor
Getting Started with the 5250
Component Editor Chapter 2
The Sample Transactions
For demonstration purposes, three transactions are used throughout this document
in the samples presented: PART, GORD, and MENU. These transactions represent
typical transactions used by operators. The PART transaction represents a scenario
in which an operator uses a SKU number to drive an inquiry to a database. The
GORD transaction represents a scenario in which an order for an item or several
items is placed. The MENU transaction represents a scenario in which an operator
navigates through a menu-driven application to get to a particular screen. The
PART, GORD, and MENU transactions are used to show you how to build
Composer services that do the same things as the real life scenarios.
Steps Commonly Used to Create a 5250 Component
While there are many ways to go about creating 5250 components, the most
commonly used steps in creating a simple component are as follows:
1 Create XML Templates for transaction.
2 Create a Connection Resource.
3 Create a component.
4 Enter Record mode and navigate through the transaction using terminal
emulation available via the component editor’s Native Environment Pane.
5 Drag and drop input document data into screen.
6 Process the transaction from the keyboard action.
7 Drag and drop screen results into output document.
8 Stop recording.
