For MRO and LUTYPE6.1 links, there is no need to define any remote resources for DTP, provided that the front-end and back-end systems are directly connected. Both the remote system and the remote transaction are identified on the EXEC CICS® commands issued by the front-end transaction. CICS therefore has all the necessary information to connect a session and attach the back-end transaction. (However, if the back-end transaction is to be routed to, it must be defined as a remote resource on the intermediate systems--see A note on "daisy-chaining".)
If you use the EXEC CICS API over APPC links, you can either identify the remote system and transaction explicitly, as for MRO and LUTYPE6.1 links, or by reference to a PARTNER definition. If you choose to do the latter, you need to create the appropriate PARTNER definitions. If you use the CPI Communications API over APPC links, the syntax of the commands requires you to create a PARTNER definition for every remote partner referenced.
Figure 69 shows the general form of the CEDA DEFINE PARTNER command.
DEFINE
PARTNER(sym_dest_name)
[GROUP(groupname)]
[NETWORK(name)]
NETNAME(name)
[PROFILE(name)]
{TPNAME(name)|XTPNAME(value)}
The PARTNER resource has been designed specifically to support Systems Application Architecture® (SAA) conventions. For more guidance about this, see the CICS Resource Definition Guide and the SAA Common Programming Interface Communications Reference manual.
For guidance about designing and developing distributed transaction processing applications, see the CICS Distributed Transaction Programming Guide.