You must have uCosminexus TP1 Connector or Cosminexus TP1 Connector to use the XA resource service facility. Operations with TP1/Client/J alone are not guaranteed.

This section describes the facilities that are made available to TP1/Client/J when the XA resource service facility is used.

The following table shows the communication method supported by TP1/Client/J.

Table 2-5 Communication method supported by TP1/Client/J

TP1/Client/J communication method	Use of the remote API facility	Use of the scheduler direct facility	Use of the name service
Supported	Y	N	N

Legend:

Y: Supported

N: Not supported

The following table shows the connection modes supported by TP1/Client/J.

Table 2-6 Connection modes supported by TP1/Client/J

Connection mode	Supported
Non-auto connect mode	N
Auto connect mode	Y

Legend:

Y: Supported

N: Not supported

The following table shows the RPC call modes supported by TP1/Client/J.

Table 2-7 RPC call modes supported by TP1/Client/J

RPC call mode	Supported
Synchronous-response RPC	Y
Asynchronous-response RPC	Y
Chained RPC	Y

Legend:

Y: Supported

Note that you can specify in the dchost operand of the TP1/Client/J environment definition only one TP1/Server as a gateway. If you specify more than one, operations cannot be guaranteed.