DPL server adapter processing

When the DPL server adapter is invoked during request processing, the details of the distributed programming link are passed in BTS data-containers from the adapter navigator or navigation manager to the DPL server adapter.

The adapter performs the link to the CICS application in another CICS region, passing a COMMAREA. When the application returns a response, the server adapter passes the data back to the adapter navigator or navigation manager using BTS data-containers.

The data-containers that are passed to the DPL server adapter store the data that is specified by Service Flow Modeler when the link is modeled. The data for the server adapter is stored in the COMMAND.INPUT data-container. When the server adapter receives a response from the application, it is stored in the COMMAND.OUTPUT data-container and the state information of the DPL adapter is stored in the COMMAND.STATUS data-container.

If you have deployed an adapter service from WebSphere® Developer for System z® version 7, only one DPL server adapter is generated to handle all of the distributed programming links. This server adapter is called DFHMASDP.

DFHMASDP server adapter processing

The DFHMASDP server adapter runs under the CMAS transaction. The data-containers that are passed to DFHMASDP store the data that is specified by Service Flow Modeler when the link is modeled. The data for DFHMASDP is stored in the COMMAND.INPUT data-container. The information regarding the DPL link itself is stored in the DPL.DATA data-container. When the server adapter receives a response from the application, it is stored in the COMMAND.OUTPUT data-container and the state information of the DPL adapter is stored in the COMMAND.STATUS data-container.

If the target application runs in a different region than the CICS® Service Flow Runtime, then the linked-to application program runs under CSMI, the default mirror transaction ID. You can optionally specify a different transaction in Service Flow Modeler. If you do specify a different transaction, ensure that it is defined in CICS to invoke the DFH$MIRS mirror transaction program.

If the target application includes any DB2® calls, then you must configure the transaction under which the target application runs, whether this is CMAS, CSMI, or your own transaction, as follows:

  1. Create the necessary DB2Trans or DB2Entry resources for the transaction
  2. Grant access authority in DB2 and RACF® as appropriate.
Any DPL server adapter that runs a transaction that makes DB2 calls requires a DB2Trans or DB2Entry resource definition for the transaction. The difference is that the DFHMASDP server adapter has the DB2 access occurring in the transaction under which the invoked target application runs, whereas previously the DB2 access occurred in the transaction under which the adapter service runs.