Rational Developer for System z, Version 7.6

When the flow type is Link3270 Bridge -- BMS map information

When the flow type in the generation properties file is Link3270 Bridge, then the Generate Runtime Code wizard can process a screen message in the flow differently, depending on: (a) whether the screen message contains BMS information; and (b) the target runtime set in the generation properties file.
Note: The results described in this topic apply only when the flow type of the flow node in the generation properties file is Link3270 Bridge (see Flow types).

This topic contains the following subtopics:

Type of source code generated when the flow type is Link3270 Bridge

When the flow type of the flow node in the generation properties file is Link3270 Bridge, the Generate Runtime Code wizard processes each screen message individually, depending on whether the screen message contains BMS information and depending on the target runtime set in the generation properties file.

If the screen message contains BMS information, then the wizard generates source code to interact with the terminal application using BMS. This is true whether the target runtime is CICS Service Flow Runtime: Level 1.0 or CICS Service Flow Runtime: Level 2.0 (see CICS® Service Flow Runtime Levels 1.0 and 2.0).

If the screen message does not contain BMS information, then the wizard's action depends on the target runtime:

Handling of String and Field Pattern descriptors when the flow type is Link3270 Bridge

The following table shows how the Generate Runtime Code wizard handles a String descriptor or a Field Pattern descriptor that applies in whole or in part to a field that has a default field name instead of a BMS field name:
Table 1. String descriptor or Field Pattern descriptor applies to a field that does not have a BMS-generated name, and the flow type is Link3270 Bridge
Contents of the screen message: How the Generate Runtime Code wizard responds:
CICS Service Flow Runtime: Level 2.01: CICS Service Flow Runtime: Level 1.01:
The screen message contains BMS map information: The wizard terminates with an error. The wizard terminates with an error.
The screen message contains no BMS map information: The wizard processes the descriptor and then goes to the next item. For this runtime environment a screen message must contain BMS information! Therefore the wizard terminates with an error.
1See CICS Service Flow Runtime Levels 1.0 and 2.0.

As the preceding table shows, when the target runtime environment is CICS Service Flow Runtime: Level 2.0 and the screen message contains no BMS map information, then the wizard processes the descriptor successfully.

Otherwise, the wizard issues the following error message and terminates:
Figure 2. Error message CRRZE7307E
CRRZE7307E COBOL Generator cannot continue. A field that is not BMS named cannot
be used as recognition criteria for screen {screen message name. Change the 
Recognition Description associated with this screen to use only BMS named fields.

Handling of Number of Fields, Number of Input Fields, Fields Checksum, and Cursor Position descriptors when the flow type is Link3270 Bridge

The following table shows how the Generate Runtime Code wizard handles a Fields Checksum descriptor, a Number of Fields descriptor, a Number of Input Fields descriptor, or a Cursor Position descriptor when the flow type of flow node in the generation properties file is Link3270 Bridge:
Table 2. Number of Fields, Number of Input Fields, Fields Checksum, or Cursor Position descriptor when the flow type is Link3270 Bridge
Contents of the screen message: How the Generate Runtime Code wizard handles the descriptor:
CICS Service Flow Runtime: Level 2.01: CICS Service Flow Runtime: Level 1.01:
The screen message contains BMS map information: The wizard issues a warning message but then goes on to process the next item. The wizard issues a warning message but then goes on to process the next item.
The screen message contains no BMS map information: The wizard processes the descriptor and then goes to the next item. For this runtime environment a screen message must contain BMS information! Therefore the wizard terminates with an error.
1See CICS Service Flow Runtime Levels 1.0 and 2.0.
As the preceding table shows, if the screen message contains BMS map information, then the wizard issues the following warning message but then goes on to the next item and continues to process normally. This is true whether the target runtime is CICS Service Flow Runtime: Level 1.0 or CICS Service Flow Runtime: Level 2.0.
Figure 3. Error message when a resource type is not supported
The {resource type} in the Screen Description named {screen description name}
for screen {screen message name} is not supported for Screen Recognition by
this generator and, therefore, is ignored.
where {resource type} is one of the following:
  • Number of Fields descriptor
  • Number of Input Fields descriptor
  • Fields Checksum descriptor
  • Cursor position descriptor
If the screen message contains no BMS map information, then the result depends on the target runtime:
  • If the target runtime is CICS Service Flow Runtime: Level 2.0 then the wizard processes the descriptor and then goes on to the next item.
  • If the target runtime is CICS Service Flow Runtime: Level 1.0 then the wizard terminates with an error, as described in the second subtopic of this topic (see Type of source code generated when the flow type is Link3270 Bridge).


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)