FEPI server adapter processing
FEPI server adapters can be part of simple or complex service flows and can therefore be invoked by the navigation manager directly or by a flow navigator. When the FEPI server adapter is invoked during request processing, the 3270 data stream is passed in BTS data-containers to the FEPI server adapter for processing.
The FEPI server adapter uses the information in the BTS data-containers to start a session using the FEPI pool and node as modeled in service flow project tools. The server adapter handles the outbound screen from the FEPI application to the target application, identifying the fields, attributes and data, and the response from the target application. Depending on what is modeled, the adapter can handle multiple screens. It also manages state information about the status of the logical units.
You can model flows running on any 3278 model up to model 5 (27 x 132 screen size). You must set up a FEPI property set with a device type for each 3270 model terminal that you want to use. Use the DATASTREAM option, because CICS Service Flow Runtime uses that to convert from the terminal data to the COBOL representation of the screen. Also specify the MAXFLENGTH in the property set. The MAXFLENGTH must be large enough to contain the largest send or receive 3270 datastream for the transactions you are running in the flow. If the MAXFLENGTH is too small, CICS issues message DFHMA04012E and the flow fails.
FEPI server adapters can use any pool size that has a MAXFLENGTH value of up to and including 25 000 bytes. However, the MAXFLENGTH value helps FEPI use storage more efficiently and you must therefore set this value no larger than is necessary. The property set for the FEPI server adapters should not contain the FEPI sample transactions, as these are not supported in CICS Service Flow Runtime. For example, CZUC, CZUU, CSZX, and CZUX must not be included in the property set.
A FEPI server adapter uses several files to record information about its processing and to pass information to subsequent FEPI server adapters. These are as follows:
- Target interaction file
- The target interaction file is a VSAM data set called DFHMATIF.
It stores the COBOL representation of the last screen that was received
in a FEPI adapter and some additional information in a buffer. The
COBOL representation can be up to 3564 bytes. The additional information
includes the cursor position, last attention key, current screen size,
and the MAXFLENGTH value. Another FEPI server adapter uses this buffer
in the service flow. If the first FEPI server adapter does not sign
out of the terminal, the next FEPI adapter can acquire ownership of
the conversation and uses the buffer to determine the state of that
conversation.
This file is used only in complex service flows. It can contain a buffer of up to 25000 bytes.
- Connection file
- The connection file is a VSAM data set called DFHMACOF that contains
the state of connections and conversations, and the ownership of those
conversations, for a FEPI server adapter. It identifies whether a
terminal (FEPI node) is in use and if that terminal can be used in
subsequent FEPI server adapters.
This file has an associated alternate index. The file is called DFHMAC1F.
You can model a service flow with many FEPI subflows, where each subflow generates a FEPI server adapter. The options that are set in each subflow for logging off the terminal affect the FEPI server adapter processing and how it passes information to the next server adapter:
- If the logoff option is force, hold, or release, the defined target and node that is in use by a FEPI server adapter is deleted when the server adapter has finished its processing. No buffer is written to the target interaction file.
- If the logoff option is pass, the connection and conversation information in the connection file is rewritten to indicate that the existing conversation has no owner. The conversation is available for another FEPI server adapter to use. The last buffer that was sent or received is stored in the target interaction file.
- If the logoff option is leave assigned, the connection and conversation information is left assigned to indicate the owner, which is the user ID that is signed on to CICS and associated with the FEPI server adapter processing. The last buffer that was sent or received is stored in the target interaction file. This option allows the processing of FEPI server adapters in different tasks to run under the same user ID. When this option is specified, the flow navigator adds a unique tag to the alternate connection file DFHMAC1F.