Daisy-chaining of DPL requests

Statically-routed DPL requests can be daisy-chained from region to region. For example, imagine that you have three CICS® regions--A, B, and C. In region A, a program P is defined with the attribute REMOTESYSTEM(B). In region B, P is defined with the attribute REMOTESYSTEM(C). An EXEC CICS LINK PROGRAM(P) command issued in region A is shipped to region B for execution, from where it is shipped to region C.

Dynamically-routed DPL requests cannot be daisy-chained from region to region. Imagine two CICS regions, A and B. A program P is defined as DYNAMIC(YES)--or is not defined--in both regions. An EXEC CICS LINK PROGRAM(P) command is issued in region A. The dynamic routing program is invoked in region A and routes the request to region B . In region B, the dynamic routing program is not invoked, even though program P is defined as DYNAMIC(YES); P runs locally, in region B.

Related concepts
Overview of DPL
Intersystem queuing
Examples of DPL
Related tasks
Statically routing DPL requests
Dynamically routing DPL requests
Defining local resources for DPL
Defining remote resources for DPL
Application programming for CICS DPL
Related reference
Limitations of DPL server programs
Appendix A. Intercommunication rules and restrictions checklist
[[ Contents Previous Page | Next Page Index ]]