FEPI LUs are assigned and released as modeled. The CICS® Service Flow Runtime server run-time makes no attempts to locate and cleanup the LUs left assigned upon successful or unsuccessful execution of processes.
It is still necessary to compensate or cancel CICS Service Flow Runtime / BTS processes as the result of unsuccessful process execution. However, in this mode it is not necessary that a flow modeled for the purposes of compensation logoff / cleanup assigned LUs as part of its compensation logic.
Since only the UserID is used for LU assignment and that UserID is assumed to be unique, any and all LUs used and left assigned for the specific UserID can be located and used in the execution of subsequent processes by that UserID.
Also if the only requirement, as determined by the service requestor, is to cancel an unsuccessfully executed process, the DPL Stub program (DFHMADPL) issues the BTS CANCEL ACQPROCESS command to end and complete the failed CICS Service Flow Runtime / BTS process.
The DPL Stub program (DFHMADPL) will not terminate LU sessions or remove the assignment on the CICS Service Flow Runtime Connection file record(s) because when only the user UserID is used for LU assignment, the UserID is unique and can be found on any subsequent process execution.
The service requestor may want to cancel the failed CICS Service Flow Runtime BTS process but not logoff and release LUs assigned to that UserID.
Subsequent modeled flows can be initiated as processes to locate, use and / or release any assigned LUs as desired.
For example, as a normal end-of-day processing strategy, the service requestor can invoke a modeled flow as a process to locate, logoff and release any assigned LUs. Failure to incorporate a cleanup strategy for a specific user may leave LUs unavailable to other users over time— unless the customer configuration is such that a significant number of LUs are available for users requiring access via CICS Service Flow Runtime FEPI processing.