Routing DPL requests dynamically
For a program-link request to be eligible for dynamic routing, the remote program must either be defined to the local system as DYNAMIC(YES) or not be defined to the local system.
Note: If the program specified on an EXEC CICS LINK command
without a SYSID is not currently defined, what happens next depends
on whether program autoinstall is active:
- If program autoinstall is inactive, the dynamic routing program is invoked.
- If program autoinstall is active, the autoinstall user program
is invoked. The dynamic routing program is then invoked only if the
autoinstall user program:
- Installs a program definition that specifies DYNAMIC(YES), or
- Does not install a program definition.
See Autoinstall programs started by EXEC CICS LINK commands.
As well as CICS®-to-CICS DPL calls instigated by EXEC CICS
LINK PROGRAM commands, program-link requests received from
outside CICS can also be dynamically routed. For example,
all the following types of program-link request can be dynamically
routed:
- Calls from external CICS interface (EXCI) client programs
- External Call Interface (ECI) calls from any of the CICS Client workstation products
- ONC/RPC calls.
A program-link request received from outside CICS can
be dynamically routed by:
- Defining the program to CICS TS as DYNAMIC(YES)
- Coding your dynamic routing program to route the request.