Rational Developer for System z

Support for screen descriptors in the runtime environments

This topic describes the support for screen descriptors in the different runtime environments.

For a description of the runtime environments see Supported runtime environments for each project type.

This topic contains the following subtopics:

Host Access Transformation Services (HATS): Support for screen descriptors

Table 1 shows which screen descriptors are supported for the Host Access Transformation Services (HATS) runtime environment:
Table 1. Support for HATS runtime
Type of descriptor: Supported in the Host Access Transformation Services (HATS) runtime environment:
String Yes
Field Pattern Yes
Number of Fields Yes
Number of Input Fields Yes
Fields Checksum Yes
Color Yes
Rectangle Yes
Cursor Position Yes

CICS Service Flow Runtime and FEPI: Support for screen descriptors

Table 2 shows the support for screen descriptors when the flow type of the flow node in the generation properties file is FEPI (see Flow types).
Note: For all runtime environments, if the flow type is FEPI, but the screen message contains BMS information, then the Generate Runtime Code wizard ignores the BMS information and processes the screen message as an ordinary captured screen.
Table 2. When the flow type of the flow node in the generation properties file is FEPI
Type of descriptor: Supported in the CICS® Service Flow Runtime:
Level 2.0:1 Level 1.0:1
String Yes Yes
Field Pattern Yes Yes
Number of Fields Yes No
Number of Input Fields Yes No
Fields Checksum Yes No
Color No No
Rectangle No No
Cursor Position Yes No
1See CICS Service Flow Runtime Levels 1.0 and 2.0.

CICS Service Flow Runtime and Link3270 Bridge: Support for screen descriptors

Table 3 shows the support for screen descriptors when the flow type of the flow node in the generation properties file is Link3270 Bridge (see Flow types).
Table 3. When the flow type of the flow node in the generation properties file is Link3270 Bridge
Type of descriptor: Supported in the CICS Service Flow Runtime: Level 2.0:3 Supported in the CICS Service Flow Runtime: Level 1.0:3
  If the screen message does not contain BMS information: If the screen message does contain BMS information: If the screen message does not contain BMS information: If the screen message does contain BMS information:
String Yes Yes1 Error2 Yes1
Field Pattern Yes Yes1 Error2 Yes1
Number of Fields Yes No Error2 No
Number of Input Fields Yes No Error2 No
Fields Checksum Yes No Error2 No
Color No No Error2 No
Rectangle No No Error2 No
Cursor Position Yes No Error2 No

1 The String descriptor and Field Pattern descriptor must apply only to fields having BMS names, not to fields having default field names (see Handling of String and Field Pattern descriptors when the flow type is Link3270 Bridge).

2 For CICS Service Flow Runtime: Level 1.0 every screen message in the flow must contain BMS information, otherwise the Generate Runtime Code wizard terminates with an error and displays an error message.

3See CICS Service Flow Runtime Levels 1.0 and 2.0.

Considerations for using screen descriptors in different runtime environments

This is a summary of points to keep in mind:

  1. Determine which screen descriptors are supported in your target runtime environment and flow type.

  2. Modify the default screen description so that it includes only screen descriptors that are supported in your target runtime environment and flow type (see Default screen description, Setting the contents of the default screen description, and When the flow type is Link3270 Bridge -- BMS map information).

  3. Verify that your screen messages do not contain unsupported screen descriptors.

  4. If you generate screen messages that contain unsupported screen descriptors, modify the screen descriptions in the screen messages to replace the unsupported screen descriptors with supported ones.

  5. When the Generate Runtime Code wizard closes, look in the Runtime Code Generation Complete window that the wizard displays. This window indicates whether the operation was a success or a failure, displays status messages, and displays warning messages if there are any (see Step B9. Check the results from running the Generate Runtime Code wizard).


Terms of use | Feedback

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