When a flow uses screen messages that contain BMS map information,
and the flow type in the associated generation properties file is
FEPI, then the Generate Runtime Code wizard ignores any BMS information
in the screen messages.
Note: The results described in this topic apply only when the flow
type of the flow node in the generation properties file is FEPI (see
Flow types).
When the flow type is FEPI, and you have specified CICS Service Flow Runtime: Level 2.0 in
the generation properties file (see CICS® Service Flow Runtime Levels
1.0 and 2.0) then the CICS Service
Flow Runtime can interact with any terminal application using the
3270 Data Stream, whether or not the application uses BMS maps. When
the flow is FEPI, the CICS Service
Flow Runtime ignores any BMS commands and interacts with the application
using the 3270 Data Stream only.
Therefore, when the flow type is FEPI and the
Generate
Runtime Code wizard processes a screen message that contains
BMS map information, the wizard ignores the BMS information and processes
the screen message as if it did not contain any BMS information. Thus:
- The wizard does not generate an error message, whether the flow
contains no screen messages with BMS information, some screen messages
with BMS information, or all screen messages with BMS information.
- The wizard treats the Fields Checksum descriptor, the Number of
Fields descriptor, and the Number of Input Fields descriptor as valid,
even if the screen message contains BMS information.
- The wizard does not generate an error message if a String descriptor
or a Field Pattern descriptor applies to a field that does not have
a BMS name, even if the screen message contains BMS information.