Server runtime files
Stabilized feature: Service Flow Runtime and Service Flow Modeler capability in IBM Developer for z/OS 14.2.3
are stabilized. Consider exposing and orchestrating applications as API services by using z/OS Connect Enterprise Edition or CICS
web services, or by writing web applications in Java or Node.js. See also Stabilization notices and discontinued functions.
The following table lists the files that CICS Service Flow Runtime uses during request processing.
Every file is a Key Sequenced Data Set (KSDS).
| File name | Summary | Description |
|---|---|---|
| DFHMAASF | Service flow repository | This file contains the definitions for every service flow that is deployed in the CICS region. |
| DFHMACOF | FEPI (SLU) connection | This file is used by FEPI server adapters. It contains the FEPI nodes that are allocated to avoid allocating the same node twice. |
| DFHMAC1F | FEPI (SLU) alternate connection | This file is used to retrieve or establish active FEPI connections and conversations using the signed-on user ID and the FEPI pool name as defined in the FEPI server adapter properties. |
| DFHMAL2F | Link3270 business state | This file is used by Link3270 server adapters. It contains Link3270 facility business (application) state information for the allocated facility. For example; the last BMS ADS sent and the vector header information. |
| DFHMATIF | FEPI target interaction | This file is used by FEPI server adapters. It contains the last screen buffer that was sent or received using the allocated conversation for the target node. |
| DFHMALVA | Vector log | This file is the first of two files that is used by Link3270 server adapters to log Link3270 bridge vector information that is sent and received by the CICS target application. |
| DFHMALVB | Vector log | This file is the second of two files that is used by Link3270 server adapters to log Link3270 bridge vector information that is sent and received by the CICS target application. |