Services are usually terminated by the PEND FI (finish) call. If you call PEND FI a dialog message is sent to the terminal, a client program or another program. The end of service is also the end of the processing step.
However, you can use the PEND FC (finish and continue) call to chain another service and continue the processing step within that service.This is useful, for example, if a dialog message is not to be output to the client or if the use of TACs is to be hidden from the user.
Like PEND FI, PEND FC terminates both the transaction and the service and releases service-specific storage areas (LSSBs, KB). Data is transferred to the chained service using an MPUT call; you cannot use service-specific storage areas to do this.
The differences in programming to PEND FI are as follows:
With PEND FC you have to enter the TAC of the chained service in the KCRN field.
MPUT is not necessary before PEND FC. However, if an MPUT call is issued then the follow-up TAC must also be entered in KCRN (as in PEND PA/PR).
If the first transaction of the chained service is rolled back, then openUTM restarts at the synchronization point in PEND FC and restarts the chained service.