Design considerations for Function Shipping

User application programs can run in a CICS® intercommunication environment and use the intercommunication facilities without being aware of the location of the file or other resource that is being accessed. The location of the resource is specified in the resource definition.

Guidance on identifying and defining remote resources is given in Defining remote resources.

The resource definition can also specify the name of the resource as it is known on the remote system, if it is different from the name by which it is known locally. When the resource is requested by its local name, CICS substitutes the remote name before it sends the request. Substituting the remote name is useful when a particular resource exists with the same name on more than one system but contains data specific to the system on which it is located.

This technique might limit program independence. Application programs can also name remote systems explicitly on commands that can be function-shipped, by using the SYSID option. If you specify this option, the request is routed directly to the named system, and the resource definition tables on the local system are not used. You can specify the local system in the SYSID option so that the decision whether to access a local resource or a remote one can be taken at execution time.

For design considerations that relate to initiating transactions in other CICS systems, or other systems that are not CICS but implement SNA LU Type 6 protocols, by shipping interval control START requests, see Asynchronous processing.



dfht1k9.html | Timestamp icon Last updated: Sunday, 4 June 2017