Configuration for Distributed Program Linking

This section describes any configuration required that is specific to distributed program linking. See the section Common Configuration Tasks for configuration that is required for all types of intersystem communication.

You might need to do some specific configuration for outbound distributed program linking. There are two ways of linking to a program on a remote system:

• Specify the system ID of the remote system in the relevant EXEC CICS command. For example:

  EXEC CICS LINK TRANSID(PPQQ) SYSID(HS01)
  

  links to the transaction program PPQQ which belongs to the remote system HS01.

• Specify the system ID and name of the resource in the resource's local definition. The following table shows the fields that need updating

  Table

  Required Entry

  PPT

  Each remote program to which a local program can link, specifying: Remote SYSID on the PPT Details page of ESMAC The ID of the SysC table entry for the remote system Remote Prog on the PPT Details page of ESMAC The name by which the program is known on the remote system. If you do not specify this field, the program is assumed to have the same name on both systems. Rmt Trans ID on the PPT Details page of ESMAC The name of the transaction (overriding the default mirror transaction ID) under which to run the remote program. This mechanism allows greater flexibility when the remote program accesses DB2 as the DB2 application plan is based upon the active transaction.