A synchronous-response type RPC transaction terminates when the result of its processing returns to the CUP and synchronous-point-acquisition processing ends.

The following figure shows the relationship between synchronous-response type RPCs and synchronous points.

Figure 2-13 Synchronous-response type RPCs and synchronous points

In a transaction using a no-response type RPC, the CUP waits at a synchronous point until the SPP terminates, and then performs synchronous point processing.

The following figure shows the relationship between no-response type RPCs and synchronous points.

Figure 2-14 No-response type RPCs and synchronous points

A chained RPC is executed with one SPP process. Therefore, the number of transaction branches is 1 regardless of how many times a chained RPC is used.

A transaction using a chained RPC terminates and the SPP process that executed the chained RPC is released when synchronous point processing finishes.

If a non-transactional chained RPC is used during a transaction, normally, the SPP process that executed the chained RPC is released when synchronous point processing finishes. If you want to release the SPP process with a synchronous-response type RPC without releasing it when synchronous point processing finishes, specify 00000002 in the rpc_extend_function operand of the user service definition.

The following figures show the relationship between chained RPCs and synchronous points.

Figure 2-15 Chained RPCs and synchronous points (transactional chained RPC)

Figure 2-16 Chained RPCs and synchronous points (non-transactional chained RPC when no-release is specified)