Configuration for Function Shipping

This section describes any configuration required that is specific to function shipping. 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 function shipping. There are two ways of ensuring that functions get shipped to a remote system:

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

  EXEC CICS READ FILE(CUSTFILE) SYSID(HS01)
  

  reads the file CUSTFILE which belongs to the remote system HS01.

  EXEC CICS WRITEQ TD QUEUE(QUEUE01) SYSID(HS01)

  writes to the transient-data queue QUEUE01 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
  FCT	The file to be accessed, specifying: Remote SYSID on the FCT Details page of ESMAC The ID of the SysC table entry for the remote system Remote File on the FCT Details page of ESMAC The name by which the file is known on the remote system. If you do not specify this field, the file is assumed to have the same name on both systems
  DCT	The TD queue that can be accessed by local transactions, specifying: SYSID on the DCT Details page of ESMAC The ID of the SysC table entry for the remote system Name on the DCT Details page of ESMAC The name by which the TD queue is known on the remote system. If you do not specify this field, the TD queue is assumed to have the same name on both systems.
  TST	The remote TS queue that can be accessed by local transactions, specifying: SYSID on the TST Details page of ESMAC The ID of the SysC table entry for the remote system Name on the TST Details page of ESMAC The name by which the TS queue is known on the remote system. If you do not specify this field, the TS queue is assumed to have the same name on both systems