You can dynamically route requests to CICS® programs
from applications that use the EXCI using CICSPlex SM.
Procedure
- Specify the following system initialization parameters
in the CICS region:
- DSRTPGM=EYU9XLOP
- DTRPGM=EYU9XLOP
- Update your RDO group as follows:
- Add an RDO entry for the EXCI server program, DFHMIRS. You can use another transaction instead of EXCI if required,
but it must point to program DFHMIRS and have a profile of DFHCICSA.
Model it after the EXCI transaction in group DFH$EXCI. This transaction
will point to DFHMIRS program.
Note: The user transaction when defined
as remote will only work within an APPC configuration. Within an EXCI
or MRO configuration the mirror transaction must run in the local CICS region,
by specifying DYNAMIC(NO) and no REMOTE attributes. Routing the mirror
transaction to another CICS region can impact performance
and make problem determination more difficult.
- Add the RDO group to the terminal-owning region (TOR)
LIST.
Ensure that the TOR region has program autoinstall disabled.
- Log into CICSPlex SM and define the transaction for the
routing region into these CPSM groups: TXNGRP, WLMDEF, WLMGRP WLMSPEC.
- For each application-owning region (AOR), create the RDO
group in the same way as the sample definition DFH$EXCI. This
group must contain only the connections, sessions, and application
programs, or equivalent transactions. If you used a different transaction
instead of EXCI, you must specify it in this group.
Results
When an application issues a distributed program link, CICSPlex
SM checks if the incoming transaction is under its control. When it
finds that EXCI or its equivalent is valid in its transaction group,
CICSPlex SM routes the transaction to one of the candidate AORs for
processing.
An alternative to this approach is to define an RDO
definition for the program or transaction with DYNAMIC=Yes. CICSPlex
SM routes the request to the selected region.