The conditions that make a work request eligible for dynamic routing are
given in the CICS Intercommunication Guide.
Any CICS® system may act as a requesting region, a routing region, or a target region, as long as:
- All of the CICS systems associated with a workload are either part of the same CICSplex, or, for BTS processes
and activities, part of the same BTS-set. They do not need to reside in the
same MVS™ image.
- For dynamic routing of both terminal-related and non-terminal-related
EXEC CICS START commands, requesting, routing, and
target regions must be CICS Transaction Server for OS/390® Version 1
Release 3 or above.
- For dynamic routing of DPLs, routing regions must be CICS Transaction Server
for OS/390 Version 1 Release 3 or above; target regions may be any level of CICS.
- For enterprise beans, the routing and target regions must be part of the
same IIOP server; that is, the same logical EJB server.
- For CICS BTS activities, the routing region (which is also the requesting region) and
the target region must be at CICS Transaction Server for OS/390 Release 3 or later.
They must also be in the same sysplex.
- For dynamic routing of transactions and static routing, the CICS system acting
as the routing region must be running CICS/ESA 3.3 and later. The CICS systems acting
as target regions can be running any version of any CICS platform supported by CICSPlex® SM (CICS/ESA, CICS/MVS, or CICS for OS/2).
- For dynamic routing of enterprise bean-related transactions, the CICS
system acting as the routing region and the target region must be running
CICS Transaction Server Version 2 Release 1 and later.
The routing region must be defined as local to a CMAS involved
in managing the CICSplex..
It must use CICSPlex SM facilities to communicate with that CMAS. For additional
information, see CICS Transaction Server for z/OS Installation Guide.
- For Link3270 bridge requests the target regions must be at CICS Transaction Server for z/OS®, Version 2 Release 2 or
later.
A CICS system can act as a target region in one or more workloads; however, it can act
as a routing region in one and only one workload. Note that a CICS system can act as a routing region and
a target region in the same workload.
When a CICS system acting as a target region is combined with other target regions to form
a CICS system group, each of the target regions should have access to all of the resources
required by any transactions that may be routed to that CICS system group. In the case
of a CICS BTS workload, they must all be in the same sysplex.
Before you can implement dynamic and distributed
routing, you need to specify Yes in the Routing support active field of the
CICS system definition. See CICSPlex System Manager Administration.
[[ Contents Previous Page | Next Page Index ]]