All processing in the single connector pattern is the same whether it is run "persistent" or "nonpersistent" with the exception of the BTS DEFINE PROCESS command in the CICS® Service Flow Runtime DPL stub program (DFHMADPL).
See Properties file record descriptor (DFHMARPF) to view the structure of the properties file.
See Request properties for request property value settings and descriptions.
The CICS Service Flow Runtime DPL stub program calls a user-defined program to parse the XML application request tag data and return in a COBOL fixed format structure. The application program name is determined by the request properties file field, MP-XML-PARSE-PROGRAMID. See Request properties for further information.
See XML request and response processing and XML message formats for non-passthrough for further information regarding XML message processing.
EXEC CICS DEFINE PROCESS (processname)
PROCESSTYPE (processtype)
TRANSID (transid)
PROGRAM (program)
NOCHECK
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
EXEC CICS DEFINE PROCESS (processname)
PROCESSTYPE (processtype)
TRANSID (transid)
PROGRAM (program)
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
The NOCHECK processing option indicates that no record is to be written to the BTS repository data set to reserve the name of the process. Using the BTS NOCHECK option improves BTS performance by removing the write to the repository and its associated logging. See CICS Business Transaction Services manual for further information on the DEFINE PROCESS command and options.
State information includes the request name (DFHMAH-REQUESTNAME) as specified in the message header (DFHMAH) and the program name and transaction that will process the application request data as defined by request properties, MP-INITIAL-PROGRAMID and MP-INITIAL-TRANSID fields, respectively.
For Adapter services of the single connector type, the program and transaction defined and run will not be an Adapter Navigator but rather will be a DPL, FEPI or Link3270 server adapter.
EXEC CICS RUN ACQPROCESS
SYNCHRONOUS
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
EXEC CICS RUN ACQPROCESS
ASYNCHRONOUS
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
EXEC CICS DEFINE ACTIVITY (ADC-NAV-ACTIVITY)
EVENT (<completionevent>)
TRANSID (ADC-NAV-TRANSACTION)
PROGRAM (ADC-NAV-PROGRAM-ID)
ACTIVITYID (ADC-NAV-ACTIVITYID)
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
Additional state information includes the ACTIVITYID, CICS applid where the Navigation Manager (DFHMAMGR) is running, EIBTASKN of the running Navigation Manager, etc.
For Adapter services of the single connector type, the program and transaction invoked will not be an Adapter Navigator but rather will be a DPL, FEPI or Link3270 server adapter. Only one server adapter type will be invoked for this processing pattern as defined by the Adapter service.
EXEC CICS RUN ACTIVITY (ADC-NAV-ACTIVITY)
SYNCHRONOUS
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC.
EXEC CICS RUN ACTIVITY (ADC-NAV-ACTIVITY)
ASYNCHRONOUS
RESP (CICS-RESP)
RESP2 (CICS-RESP2)
END-EXEC
As a result of the Navigation Manager (DFHMAMGR) running the Adapter service activity, the DPL, FEPI or Link3270 server adapter performs business request processing (as modelled in Service Flow Modeler) in order to complete the request made by the service requestor.
Each business request issued by the service requestor results in a different BTS process instance to fulfill the appropriate Adapter service as defined by the business request name.
Each process instance consists of a Navigation Manager (DFHMAMGR) activity and the one server adapter activity that is needed to support that Adapter service.