For various events, FEPI invokes a transaction, as a CICS® started task, to handle the event. This may be in response to FEPI START, or to handle STSN, begin-session, end-session, or unsolicited-data. The transactions have a start code of ‘SZ’, as can be determined with the EXEC CICS ASSIGN command. FEPI provides start data which describes the event, and the conversation which is to be used to handle it. All of this data must be retrieved by the transaction using EXEC CICS RETRIEVE. The transaction can then gain access to the conversation identified in the data by using FEPI ALLOCATE PASSCONVID.
The structure for start data is shown below; the copy books DFHSZAPA, DFHSZAPO, DFHSZAPC, and DFHSZAPP (according to your programming language) provide declarations for this structure.
DATATYPE | Fullword binary data-area |
EVENTTYPE | CVDA |
EVENTVALUE | CVDA |
EVENTDATA | 8-character data-area |
*spare* | 4-character data-area |
POOL | 8-character data-area |
TARGET | 8-character data-area |
NODE | 8-character data-area |
CONVID | 8-character data-area |
DEVICE | CVDA |
FORMAT | CVDA |
*spare* | 8-character data-area |
FLENGTH | Fullword binary data-area |
USERDATA | 128-character data area. |
Value | Event |
---|---|
BEGINSESSION | Begin-session to be handled |
DATA | Inbound data arrived, following a FEPI START command |
FREE | End-session transaction started to handle end of conversation as a result of a FEPI FREE request |
SESSIONLOST | Active session lost while waiting for inbound data to arrive following a FEPI START command |
STSN | Set and test sequence number (STSN) to be handled |
TIMEOUT | Timed out waiting for inbound data to arrive following a FEPI START command |
UNSOLDATA | Inbound data arrived outside a conversation. |
Values for FREE:
FORCE | A FEPI FREE FORCE command was issued. |
HOLD | A FEPI FREE HOLD command was issued. |
RELEASE | A FEPI FREE RELEASE command was issued. |
SHUTDOWN | CICS is shutting down. |
TASK | Conversation being freed by end-of-task. |