When the facilities indicated below execute, TP1/Client/J uses a specific TP1/Server as a gateway. This is called a remote procedure call (RPC). For details about RPCs, see the manual OpenTP1 Programming Guide. TP1/Client/J supports four types of RPCs:

• RPCs that use the remote API facility
• RPCs that use the scheduler direct facility
• RPCs that use the name service
• RPCs with a communication destination specified

You use the dchost operand of the TP1/Client/J environment definition to define a TP1/Server as a gateway.

The following figures show the mechanism of TP1/Client/J operation.

Figure 1-4 Mechanism of TP1/Client operation (1/2)

Figure 1-5 Mechanism of TP1/Client operation (2/2)