Link3270 State file processing for non-unique IDs — asynchronous mode

If your site uses non-unique UserIDs, and if the process terminates abnormally due to a CICS® Service Flow Runtime system error or an incorrectly modeled flow, this can result in bridge facilities and associated facility state data remaining allocated.

An abnormal termination of a process does not complete/end the CICS Service Flow Runtime / BTS process that was initiated for that modeled flow. This leaves CICS Service Flow Runtime / BTS process container information available from the failed process for subsequent use. This is true regardless of whether you are using non-unique or unique UserIDs.

These failed CICS Service Flow Runtime / BTS processes must be addressed by the service requestor, again regardless of the type of UserID or regardless of whether the Link3270 bridge mechanism is implemented as part of the modeled flow. Since the CICS Service Flow Runtime / BTS process is not complete, BTS resources are still allocated with the state (business request state) of the CICS Service Flow Runtime / BTS process and process container information.

In order to complete the failed CICS Service Flow Runtime / BTS process and release those BTS resources, the service requestor must perform one of the following actions:
If the service requestor initiates a process of a modeled compensating flow, the DPL Stub program will:

The unique tag used in conjunction with the non-unique UserID is included in the container information retrieved from the failed CICS Service Flow Runtime / BTS process and is available to the compensating process.

The unique tag is used to locate all allocated bridge facilities and associated facility state data used in the failed process.

The bridge facilities are used in the compensating process as indicated in the flow model. The facilities ultimately, however, must be deleted as part of that compensating process.

If the service requestor issues a cancel of the failed process, the DPL Stub program will:
Note: If the delete of bridge facilities fails, those bridge facilities will remain until the expiration of bridge facility maximum keeptime, (BRIH-FACILITYKEEPTIME). For information on how to set the Link3270 bridge facility maximum keeptime, see information on MAT_MAX_FAC_KEEPTIME in the Service Flow Modeler help.
Note: Incorrectly modeled flows that leave facilities allocated in this mode of processing and that complete successfully, cause bridge facilities to remain allocated until the expiration of the bridge facility maximum keeptime, (BRIH-FACILITYKEEPTIME).

Cleanup logic in the CICS Service Flow Runtime Navigation Manager program (DFHMAMGR), similar to the logic added to the CICS Service Flow Runtime DPL Stub program (DFHMADPL), attempts to locate and delete facilities left allocated upon successful process execution. If, however, the delete of bridge facilities fails, those bridge facilities will remain until the expiration of bridge facility maximum keeptime, (BRIH-FACILITYKEEPTIME). For information on how to set the Link3270 bridge facility maximum keeptime, see information on MAT_MAX_FAC_KEEPTIME in the Service Flow Modeler help.