The service flow repository file

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 service flow repository file, DFHMAASF, contains a record for every service flow that is deployed in the runtime environment. The record contains the request name and the properties of the service flow and definitions for each server adapter.

When you deploy a new service flow, the service flow repository file is updated to include all of the information necessary to perform request processing for that service flow. Each service flow record begins with the name of the flow, followed by definitions for the server adapters, programs, and transactions. It can also include additional information:

  • The persistence of the request processing
  • The processing mode, either synchronous or asynchronous
  • The connector type of the service flow, simple or complex

The only server adapters that are not required in this file are the Web services and Program link server adapters.

The service flow repository file is read by the CICS SFR interface program, DFHMADPL, which then creates BTS data-containers for the Navigation manager and server adapters to access during request processing.

You can view the contents of the service flow repository file by using the flow management transaction, CMAN. You cannot share the repository file between CICS regions.