The service flow project tools support the CICS® interaction pattern for the back-end
application of a RECEIVE MAP instruction, followed by a SEND
TEXT instruction. This is accomplished by providing the SNA_TEXT_AREA
and SNA_FIELDS system messages.
The SNA_TEXT_AREA and SNA_FIELDS messages are contained in the
IBMCICS.sfmxsd system file, and are available for use in Link3270 Bridge flow
models.
The SNA_TEXT_AREA message includes the following fields:
- SNA_TEXT_HEADER
- SNA_TEXT
- SNA_TEXT_TRAILER
- SNA_HEADER_LENGTH
- SNA_TEXT_LENGTH
- SNA_TRAILER_LENGTH
The SNA_FIELDS message contains the SNA_NEXT_API_CMD field. The
valid values for SNA_NEXT_API_CMD are as follows:
- NO RECEIVE
- RECEIVE
- RECEIVE MAP
- CONVERSE
A typical use would be to compare a SNA_TEXT field to a specific
string literal. If a match is found, then set the SNA_NEXT_API_CMD field to
one of its valid values.
During run time, the text portion of a SEND
TEXT vector is placed in the appropriate SNA_TEXT field in the SNA_TEXT_AREA
message; the associated LENGTH field is also set. If multiple consecutive
SEND TEXT vectors are received, the text will be concatenated in the system
text field. The data within these fields is then available for examination
in a generated navigator.
Setting the SNA_NEXT_API_CMD field causes
the subsequent screen interaction to use the respective CICS API (that
is, RECEIVE, RECEIVE MAP, CONVERSE).
Only the following scenarios are supported:
- A SEND TEXT (no erase) follows a SEND MAP ERASE.
- A SEND TEXT (no erase) results from a PF-Key received
by the application.
- A SEND TEXT ERASE results from a PF-Key received by the
application.
Restriction: No screen recognition can be performed using
the data from the SEND TEXT vector.