Although CICS Service Flow Runtime has a prerequisite for CICS Transaction Server for z/OS Version 3 Release 1, there is no such prerequisite for the target CICS application regions (i.e., the CICS region where your user transactions and target applications are running). If CICS Service Flow Runtime is running user transactions via the Link3270 bridge mechanism and if those user transactions are running in CICS Transaction Server for z/OS Version 2 Release 2 environment, CICS Service Flow Runtime and those user transactions are restricted to the CICS Transaction Server for z/OS Version 2 Release 2 Link3270 bridge mechanism supported CICS APIs.
If your user transactions are running in CICS Transaction Server for z/OS Version 2 Release 3, via the Link3270 bridge mechanism and those user transactions are running in a CICS Transaction Server for z/OS Version 2 Release 3 environment, then CICS Service Flow Runtime and those user transactions are restricted to the CICS Transaction Server for z/OS Version 2 Release 3 Link3270 bridge mechanism supported CICS APIs.
See the IBM® provided sample restrictions table, DFHEIDBR, in the CICS provided sample library (hlq.SDFHSAMP) and the CICS External Interfaces Guide for your version(s) and release(s) of CICS Transaction Server for z/OS for further information.
The restrictions table, DFHEIDBR, identifies commands which may not be supported when the generated CICS Service Flow Runtime Link3270 server adapter is run using the Link3270 bridge mechanism. This table can be used with an IBM supplied load module scanner utility, DFHEISUP, to analyze your user transactions/target applications. See the CICS Operations and Utilities Guide for CICS Transaction Server for z/OS Version 2 Release 2 and/or Version 2 Release 3 or higher.
If the scanner shows that these commands are found, then please refer to the section on Bridging to 3270 transactions in the appropriate CICS External Interfaces Guide for CICS Transaction Server for z/OS for further information. There are other restrictions which may limit the generated Link3270 server adapter functionality when using the Link3270 bridge mechanism, therefore this table is a guide rather than a definitive statement.
This command is supported in Passthrough mode only.
The SEND MAP with ACCUM option is supported in passthrough mode only. In CICS Service Flow Runtime passthrough processing, each SEND MAP (with ACCUM), vector data area received is returned to the service requestor as a separate map with its own map header, CIA-MAP-HEADER. There is no attempt to merge these vectors as in BMS processing where the output is to a real terminal.
In both cases, the SEND LENGTH() cannot exceed 132 bytes.
Please note that there is no attempt to merge the SEND TEXT vector data areas based upon screen position or justification (JUSTIFY) as in BMS processing where the output is to a real terminal.
In Link3270 server adapter processing, each SEND TEXT vector data area is accumulated in a text buffer area, each SEND TEXT vector data area is separated by a low-values byte, and returned to the Link3270 server adapter where, if tooled, it can be parsed. (Any HEADER and TRAILER data areas are also stored within the text buffer area.)
(text buffer area)
01 SNA-TEXT-AREA.
05 SNA-TEXT-HEADER PIC X(4096) VALUE LOW-VALUES.
05 SNA-TEXT PIC X(4096) VALUE LOW-VALUES.
05 SNA-TEXT-TRAILER PIC X(4096) VALUE LOW-VALUES.
Link3270 server adapters currently only support 1 outbound vector with a maximum length of 32,000 bytes. The COMMAREA length used to LINK to the Link3270 bridge router program DFHL3270 is 32,000 bytes.
All interactions with target applications are performed via Link3270 bridge session mode. See CICS External Interfaces Guide Version 2 Release 2 or higher.