Defining local resources

This section discusses how to define resources, required for intersystem communication, that reside in the local CICS® system.

Defining communication profiles
When a transaction acquires a non-IPIC session to another system, either explicitly with an ALLOCATE command or implicitly because it uses, for example, non-IPIC function shipping, a communication profile is associated with the communication between the transaction and the session.
Architected processes
An architected process is an IBM®-defined method of allowing dissimilar products to exchange intercommunication requests in a way that is understood by both products.
Selecting required resource definitions for installation
The profiles and architected processes, and other transactions and programs that are required for ISC, IPIC, and MRO, are contained in the IBM protected groups DFHSTAND, DFHISC and DFHISCIP.
Defining intrapartition transient data queues
The attributes that apply to queues that cause automatic transaction initiation, or that specify an associated principal facility (such as a terminal or another system), in an intercommunications environment are listed.
Defining local resources for DPL
To support DPL, special resource definitions are sometimes necessary for server programs and mirror transactions.

Parent topic: Defining intercommunication resources