In this step you will use existing BMS maps to create two
screen messages for the CICS® example
catalog application (egui).
You will create screen messages for the following two application
screens:
- The Main Menu screen
- The Inquire Catalog screen
Two requirements come into play in this step of the tutorial:
The first requirement is that before you can record a new flow,
you should have a screen description for
each application screen that you are going to visit during the flow
recording (unless you plan to record new application
screens as needed during flow recording).
The second requirement is that if you are working on a project
that creates runtime code for a Link3270 adapter (as in this tutorial)
then each screen description must contain BMS map information
for the application screen being described.
Because of this
requirement, you will use the Import feature
that allows you to generate screen messages directly from BMS maps.
Import the BMS maps
When
you import a BMS map, the importer:
- Reads the BMS information from the map.
- Creates a screen description based on the BMS information.
- Creates a screen message to contain the screen description.
- Stores the screen message in a screen message file.
You can obtain the BMS maps for the CICS example catalog application from the system
administrator for your host system (see
Required environment, materials, and assistance). You will need the following
map files:
- DFH0XS1.BMS -- Contains the maps for the Main Menu screen and
the "Details of your order" screen (the latter screen is not used
in this tutorial).
- DFH0XS2.BMS -- Contains the map for the "Inquire Catalog" screen.
Download these files from the remote z/OS® system and place them in a local directory
of your workstation.
To import the BMS maps:
- In the EST Project Explorer, right-click the CatalogSample.Terminal subproject.
Click . The BMS Import wizard opens.
- On the first page of the Import BMS wizard, titled BMS:
Select the BMS files
DFH0XS1.BMS and
DFH0XS2.BMS:
- Click File System or Workspace.
Depending on your choice, either the system Open window
or the workbench's Browse Workspace wizard
opens.
- Using either the Open window or the Browse
Workspace wizard:
- Navigate to the location where the BMS map files are located.
- Select the files DFH0XS1.BMS and DFH0XS2.BMS.
- Close the Open window or the Browse
Workspace wizard.
The Import BMS wizard displays the selected
files in the BMS files to import list.
In the Project Name list,
select CatalogSample.Terminal.
Click Next.
On the second page of the Import BMS wizard,
titled BMS Import Options:
In the Host code page list, you can
use the default code page or select another.
In the BMS file code page list, you
can use the default code page or select another
In the Screen size list, select the
default screen size: 24x80.
In the
Generate screen recognition criteria group:
- 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.
Click Next.
On the third page of the Import BMS wizard,
titled BMS Overwrite Options:
Click Overwrite existing screens entirely.
In the Match By group, click File name.
Click Finish.
The wizard creates three screen message files:
- Dfh0xs2.Exinqc.sfmxsd
- Dfh0xs1.Exmenu.sfmxsd
- Dfh0xs1.Exordr.sfmxsd (This screen message file is not used in
the tutorial. It is generated automatically by the BMS Import wizard
because the corresponding map was found in the first BMS map file.)
These new screen message files are listed in alphabetical
order in their folder. To see these files, expand .