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.
Tip: Routing by user ID

Optionally, your routing program can route requests based on the CICS user ID (userid) associated with the request. The DYRUSERID field of the communications area contains the user ID. When it is invoked for routing or because of a route-selection error, your routing program can base its routing decision on the contents of this field. For details of how the userid is set for different types of request, see the description of the DYRUSERID field in Parameters passed to the dynamic routing program.