Record the screen operations in the host editor, with the
mode set to screen operations mode.
To record a screen operations file:
- Position the host application at the application screen at which
you want to start recording:
- Open the host editor if it is not already open:
- In the Hosts folder of your project's terminal applications subproject,
double-click the host connection file that you want to use to connect
to the host.
- Wait for the connection to take place.
- Start the host application as you normally do.
- Navigate to the application screen at which you want to start
recording.
- If you plan to use existing screen message files, load the most
recent versions of your screen message files by clicking the Reload
Screen Descriptions icon
(see Currently loaded
screen descriptions).
- Click the go to Screen Operations Mode icon
so that the host editor is in screen operations mode.
- Click the Start Recording Screen Operations icon
to start recording.
- The host editor pops up the Start Recording Screen Operations
window.
- Recording begins.
- Navigate through the host application, visiting the application
screens for which you want to record screen operations. The working
screen operations file is displayed in the Outline view. You can see
the Outline view being updated as information is recorded. The following
items are created or modified:
- Current screen operation: When you navigate
to an application screen, the host editor compares the screen descriptions
in your screen message files with the current application screen until
a matching screen description is found (for example, screen description
scOpIns in screen message file scOpsIns.sfmxsd).
- The host editor then searches in the currently loaded screen
operations file for a screen operation of the same name (scOpIns).
- If a screen operation of the same name is found, then it becomes
the current screen operation (that is, the screen operation to which
information regarding the current application screen will be added).
- If a screen operation of the same name is not found, then the
host editor creates in the working screen operations file a new screen
operation with that name (scOpsIns).
- Screen interactions: When you create a sequence of actions
for the current application screen (by typing input keys, typing an
AID key, adding an insert action, or adding an extract action), the
host editor creates a trial screen interaction containing that sequence
of actions.
- If the current screen operation (scOpIns) already contains a screen
interaction (for example, Interaction 0) having exactly the same sequence
of actions, then the host editor discards the trial screen interaction.
- Otherwise, the host editor adds the trial screen interaction to
the current screen operation as a new screen interaction (Interaction
1).
See Finding screen interactions for the current application screen.
- List of next screens: When you navigate to the next application
screen, the host editor again searches for a matching screen description,
which is again the name of the corresponding screen operation (for
example, scFileInq). The host editor then searches for that name (scFileInq)
in the list of next screens belonging to the immediately previous screen
operation (scOpIns).
- If the name of the screen operation (scFileInq) already exists
in the list of next screen screens belonging to the previous screen
operation's (scOpIns), then the host editor does not add the name
to list of next screens.
- Otherwise, the host editor adds the name (scFileInq) to the list
of next screens belonging to the previous screen operation (scOpIns).
- When you are finished recording, click the Stop Recording
Screen Operations File icon
to stop recording.
- The working screen operations file contains the material that
you just recorded.