Filter
Top Products
Note that this is the name by which the transaction is known in the routing
region. Unlike the dynamic routing program, the distributed routing program:
1. Is passed the local, not the remote, transaction name
2. Cannot specify an alternative remote transaction name, for forwarding to the
target region.
DYRTYPE
is the type of routing request for which the program is being invoked. The
values that can be passed to the distributed routing program are:
5 A BTS process or activity.
6 A non-terminal-related START request, with or without data but with no
channel.
7 A method request for an enterprise bean or CORBA stateless object, or
an inbound Web services request.
B A non-terminal-related START request, with a channel.
DYRUAPTR
If DYRVER is '7' or greater, this field contains the address of the new user area
(DYRUSERN). The new user area mechanism makes the source of the routing
program independent of the CICS release that created the communications
area. The old user area field DYRUSER is retained only for compatibility
purposes.
The user area can be mapped with the DYRUAREA DSECT.
To ensure that DYRVER is '7' or greater, you must apply the PTFs for the
following APARs to any of your routing or target regions at the specified CICS
release:
CICS Transaction Server for z/OS Version 2 Release 3
PQ81378
In systems where DYRUAPTR is less than '7' the contents of DYRUAPTR are
unpredictable.
DYRUSER
is a 1024-byte user area.
This field is retained only for compatibility purposessee the descriptions
of the DYRUAPTR and DYRUSERN fields.
DYRUSERID
is the CICS userid associated with the request.
v For BTS processes and activities, DYRUSERID contains:
– If the BTS process or activity was activated by a LINK ACQPROCESS or
LINK ACTIVITY command, the userid of the transaction that issued the
LINK, or
– The userid specified on the USERID option of the DEFINE PROCESS or
DEFINE ACTIVITY command, or
– If USERID was not specified on the DEFINE command, the userid under
which the transaction that issued the DEFINE command is running.
For further details of the user IDs associated with BTS processes and
activities, see the CICS Business Transaction Services manual.
v For enterprise beans and CORBA stateless objects, and inbound Web
services requests, DYRUSERID contains the userid associated with the
request stream.
Chapter 18. Writing a distributed routing program 655