In this topic you will prepare for the flow recording.
To prepare for the flow recording follow these steps:
Note: Normally when you plan to record a loop, before you
start recording, you should identify the critical application screens
for the loop and create screen descriptions for these application
screens (see
Preparation for recording a loop).
The critical application screens for the loop in this flow recording
are shown in
Table 1 in
the topic
C. Record the flow information).
Set the options in the Service Flow Projects
preferences window.
On the main menu of the workbench, click . The Preferences
window opens.
In the Preferences window:
- In the left pane, click .
- In the right pane:
- In the group Recording in the Host Editor:
- Clear the check box Automatically capture new screens if
it is not already cleared.
- Select the check box Do
not prompt for name when automatically capturing screens.
- Verify that the input field Time to wait before attempting
screen recognition (milliseconds) is set to 500 milliseconds.
- In the group Recording flow:
- Select the check box Do not prompt for variables when
generating variable mapping.
Note: Selecting
this check box causes the host editor, each time you create
an Extract action or Insert action or record a loop during flow
recording, to automatically create and name a new variable to be used
with the action or loop, instead of prompting you to do so. (This
feature is a great convenience because it allows you to focus on creating
the action or loop without being distracted by windows popping up
to prompt you for information about a variable.)
- The check box Enable screen invoke creating
wizard in flow editor can be selected or cleared. The
default setting is selected.
- In the left pane, click .
- In the right pane:
- Clear the check box Fields checksum descriptor if
it is not already cleared.
- Select the check box Number of fields descriptor.
- Select the check box Number of input fields descriptor.
- If any text-matching descriptors are defined, disable them by
clearing the check box to the left of the text-matching descriptor.
- Click OK. The Preferences
window closes.
- Connect to the remote z/OS® system
and start the CICS® example
catalog application (egui):
Connect to the remote z/OS system:
- In the EST Project Explorer view, expand .
- In the Hosts folder:
- Right-click the host connection file that you created in step
2.1 (for example, system.host) (see Step 2.1: Create a host connection).
- Click Open.
When the session area shows that the session is connected to
the remote z/OS system, follow
these steps:
- Navigate to the CICS logon
screen.
- Log on to CICS if required.
- The CICS command line interface
should now be displayed -- a blank area of 24 lines with the hardware
cursor displayed in row 1, column 1.
In the session area, type the name of the transaction for the CICS example catalog application.
In this tutorial the transaction is egui.
Press Enter. The application should start and display the first
page, with the heading CICS EXAMPLE CATALOG APPLICATION
- Main Menu.
Verify that the host editor correctly recognizes the screen
descriptions that you created in Step 2.2 and modified in Step 2.3:
Note: The
name of the
currently recognized screen description (that is,
the screen description that matches the currently displayed application
screen) is displayed in the information area of the host editor.
- The information area is located immediately above the session
area and to the right of the toolbar.
- You may have to increase the width of the screen message editor
window to see the entire area.
- If the Main Menu application screen is displayed in the host editor
area, then the currently recognized screen description in the information
area should be: Dfh0xs1.Exmenu_Exmenu.
- The format in which the name of the screen description is displayed
in the information area is as follows:
- The name of the screen message file in which the screen description
is stored, without the file extension .sfmxsd.
- An underscore character (_).
- The name of the screen description itself.
- Therefore the text Dfh0xs1.Exmenu_Exmenu indicates that:
- The name of the screen message file in which the recognized screen
description is stored is Dfh0xs1.Exmenu.
- The name of the recognized screen description is Exmenu.
To verify that the host editor correctly recognizes
the screen descriptions that you created in Step 2.2, check the following
application screens:
- To check the Main Menu application screen.
- Navigate to the Main Menu application screen if you have not already
done so. This application screen is the first screen displayed when
you start the application.
- Verify that the currently recognized screen description in the
information area is: Dfh0xs1.Exmenu_Exmenu.
To check the first page of the Inquire Catalog application
screen:
- Navigate to the Inquire Catalog application screen:
- On the Main Menu application screen, in the Action input
field, type 1.
- Press Enter.
- The first page of the Inquire Catalog application screen appears.
- Verify that the recognized screen description is: Dfh0xs2.Exinqc_Exinqc.
To check the END OF DATA page of the Inquire Catalog application
screen:
- Navigate to the END OF DATA page:
- On the first page of the Inquire Catalog application screen, press
F8 to page forward.
- Continue to press F8 until the END OF DATA message
appears on line 23 of the session area.
- For each screen that you display before the END OF
DATA message appears, verify that the recognized screen
description remains Dfh0xs2.Exinqc_Exinqc.
- When the END OF DATA message appears, verify
that the recognized screen description is: Dfh0xs2.Exinqc_EndPage.
Navigate back to the Main Menu application screen.