If your site uses LU assignment processing for 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 LUs remaining assigned. 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 leavesCICS Service Flow Runtime / BTS process container information available from the failed process for subsequent use. This is true regardless of the LU assignment method processing.
These failed CICS Service Flow Runtime / BTS processes must be addressed by the service requestor, again regardless of the method of LU assignment or regardless of whether FEPI 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 of the CICS Service Flow Runtime / BTS process and process container information.
The unique tag used in the new LU assignment method 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 LU(s) used in the failed process.
The LU(s) are used in the compensating process as indicated in the flow model. The LUs ultimately, however, must be released as part of that compensating process.
The unique tag used in the LU assignment for non-unique UserIDs is included in this container information.
The CICS Service Flow Runtime Target Interaction file should contain the last screen buffer/data sent/received for the assigned LU.
Incorrectly modeled flows that leave LUs assigned in this mode of processing and that complete successfully, may cause those LUs to be rendered useless in normal CICS Service Flow Runtime server run-time processing. There may be no way to locate, use or release these LUs in subsequent CICS Service Flow Runtime processes. 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 cleanup / process LUs left assigned upon successful process execution. If, however, the cleanup/processing of assigned LUs is not successful in this mode and assignment method, it will render those LUs useless in normal CICS Service Flow Runtime server run-time processing. There is no way to locate, use or release these LUs in subsequent CICS Service Flow Runtime processes. It is essential that process execution of the modeled flow attempt to logoff and release LUs assigned using this method.