Parameters passed to the dynamic routing program

Figure 47 shows all the parameters passed from the CICS® relay program, to the dynamic routing program by means of a communications area. The communications area is mapped by the copy book DFHDYPDS, which is in the appropriate CICS library for all the supported programming languages.

Figure 47. The communications area passed to a dynamic routing program
              DS      OCL4        Standard header
  DYRFUNC     DS      CL1         Function code
  DYRCOMP     DS      CL2         Component code
  DYRFILL1    DS      CL1         Reserved
  DYRERROR    DS      CL1         Route selection error code
  DYROPTER    DS      CL1         Transaction termination option
  DYRQUEUE    DS      CL1         Queue-the-request indicator
  DYRFILL2    DS      CL1         Reserved
  DYRRETC     DS      F           Return code
  DYRSYSID    DS      CL4         Default/Selected sysid
  DYRVER      DS      H           Version of the interface
  DYRTYPE     DS      CL1         Type of routing request
  DYRFILL3    DS      CL1         Reserved
  DYRTRAN     DS      CL8         Default/Selected remote tranid
  DYRCOUNT    DS      F           Number of invocations count
  DYRBPNTR    DS      F           Address of input buffer
  DYRBLGTH    DS      F           Length of input buffer
  DYRRTPRI    DS      CL1         Pass priority to AOR?
  DYRFILL4    DS      CL1         Reserved
  DYRPRTY     DS      H           Dispatch priority passed to AOR
  DYRNETNM    DS      CL8         Netname matching sysid
  DYRLPROG    DS      CL8         Run this program if routed locally
  DYRDTRXN    DS      CL1         DTRTRAN indicator
  DYRDTRRJ    DS      CL1         DTRTRAN reject?
  DYRFILL5    DS      CL2         Reserved
  DYRSRCTK    DS      XL4         MVS WLM service and reporting class
                                  token
  DYRABNLC    DS      XL4         Abnormal event code
  DYRABCDE    DS      CL4         Transaction abend code
  DYRCABP     DS      CL1         Continue abend processing?
  DYRLEVEL    DS      CL1         Required CICS level of AOR
  DYRFILL6    DS      CL2         Reserved
  DYRACMAA    DS      F           Address of applications's commarea
  DYRACMAL    DS      F           Length of application's commarea
  DYRUAPTR    DS      F           Address of user area
  * THE FOLLOWING 7 FIELDS APPLY ONLY TO BTS TRANSACTIONS
  DYRCBTS     DS      0CL176
  DYRPROCN    DS      CL36        BTS process name
  DYRPROCT    DS      CL8         BTS process-type
  DYRACTN     DS      CL16        BTS activity name
  DYRACTID    DS      CL52        BTS activity ID
  DYRPROCID   DS      CL52        BTS process ID
  DYRACTCMP   DS      CL1         BTS activity completing?
  DYRPROCCMP  DS      CL1         BTS process completing?
  DYRFILL7    DS      CL2         Reserved
  DYRUSERID   DS      CL8         CICS userid
  DYRBRTK     DS      CL8         BRIDGE FACILITY TOKEN, for
                                  Link3270 requests only 
  DYRUSER     DS      CL1024      User area
  Start of changeDYRCHANL    DS      CL16        Channel nameEnd of change
  Start of change* DYRUAREA DSECTEnd of change
  * 
  Start of changeDYRUSERN DS    CL1024           USER AREAEnd of change
Important

The same communications area is passed to both the dynamic routing program and the distributed routing program. Some parameters are meaningful to one routing program but not to the other. Some parameter-values may be passed to one routing program but never to the other. The following list describes in detail only the parameters that are significant to the dynamic routing program; parameter-values that are never passed to the dynamic routing program are not listed. For example, under the DYRFUNC parameter the value X'5' is not listed because it is never passed to the dynamic routing program--it occurs only on a route initiate call to the distributed routing program.

If you use the same program as both a dynamic routing program and a distributed routing program, for descriptions of the parameters and values that are significant on distributed routing calls refer to Parameters passed to the distributed routing program.

DYRABCDE
is the abend code returned when a routed transaction or program-link request abends, or a Link3270 user transaction abends.
DYRABNLC
is an abnormal event code, or null.

This field is significant when the dynamic routing program is invoked for termination of a routed request. Any value other than null indicates that an abnormal event, other than a transaction abend, has occurred in the region to which the request was routed. Your routing program should not route further requests to the same region until the cause of the error has been investigated and rectified.

This field is intended for use by CICSPlex® SM. Start of changeCurrently, it is set only by DB2®. For more information, see the CICS DB2 GuideEnd of change.

DYRACMAA
Start of changeThis field applies to the routing of:

For the routing of these types of request, DYRACMAA contains one of the following:

For the routing of all other types of request, DYRACMAA contains null characters.

For the routing of the three types of eligible request listed above, if the user application employs a COMMAREA:

When your routing program is invoked because the routed transaction has abended (DYRFUNC=4), the information in the communications area, or in the DFHROUTE container, is not meaningful.

Your routing program can alter the data in any application’s communications area, or DFHROUTE container, addressed by DYRACMAA.

End of change
DYRACMAL
Start of changeThis field applies to the routing of:

For the routing of these types of request, DYRACMAL contains one of the following numerical values:

For the routing of all other types of request, DYRACMAL contains zero.

End of change
DYRACTCMP
is not used by the dynamic routing program. On invocation, it is set to nulls.
DYRACTID
is not used by the dynamic routing program. On invocation, it is set to nulls.
DYRACTN
is not used by the dynamic routing program. On invocation, it is set to nulls.
DYRBLGTH
is the length of the copy of the TIOA/LUC buffer.

This field applies only to dynamic transaction routing, or Link3270 requests (not to the routing of program-link requests).

DYRBPNTR
is the 31-bit address of a copy of the TIOA/LUC buffer.

This field applies only to dynamic transaction routing (not to the routing of program-link requests).

When your dynamic routing program is invoked for routing, because of a route-selection error, or for notification (DYRFUNC=0, 1, and 3, respectively), it is given a copy of the input TIOA. Your routing program can alter the terminal input data passed to the routed transaction--see Modifying the initial terminal data.

When your routing program is invoked because a previously-routed transaction has terminated normally (DYRFUNC=2), it is given a copy of the output TIOA. Your routing program can monitor the output TIOA to detect possible problems in the AOR--see Receiving information from a routed transaction.

When your routing program is called for a Link3270 bridge request (DYRTYPE=8), the address of a copy of the TIOA/LUC buffer is not passed in DYRBPNTR.

DYRBRTK
is the 8-byte bridge facility token associated with a Link3270 bridge request. This field is valid only when DYRTYPE=8.
DYRCABP
indicates whether or not you want CICS to continue standard abend processing.
Note:
This field applies only to dynamic transaction routing, not to the routing of program-link or Link3270 requests. (If a linked-to program abends on a remote region, the abend is mirrored in the local region--that is, it is passed to the program that issued the EXEC CICS LINK command.)

The possible values are:

Y
Continue with CICS abend processing.
N
Terminate the transaction, do not continue with CICS abend processing, and give control to the program specified by DYRLPROG.

This option enables you to pass control to a local program that can handle the condition in your own way, and issue appropriate messages to terminal users.

If you enter N, you must ensure that DYRLPROG specifies the name of a valid program on the local system.

There is no default value.

Start of changeDYRCHANLEnd of change
Start of changeis the name of the channel, if any, associated with the program-link or START command. This field applies only to the routing of DPL requests, non-terminal-related START requests, and transactions started by terminal-related START requests. For other types of request, or if there is no channel associated with the command, this field contains blanks.

Note that the routing program is given the name of the channel, not its address, and so is unable to use the contents of this field to inspect or change the contents of the containers. For information about how the routing program can inspect or change the contents of the application’s containers, see Modifying the application’s containers and the description of the DYRACMAA field.

End of change
DYRCOMP
is the CICS component code. For calls to the dynamic routing program, it is always set to 'RT'.
DYRCOUNT
is a count of the times the dynamic routing program has been invoked for this transaction or link request with DYRFUNC set to ‘0’, ‘1’, or ‘3’. This field allows you to limit the number of times your program tries to route a request.
DYRDTRRJ
indicates whether the transaction, which is defined by the common transaction definition specified on the DTRTRAN system initialization parameter, is to be rejected, or accepted for processing.

This field applies only to dynamic transaction routing and Link3270 request routing (not to the routing of program-link requests), and is only relevant when DYRTRXN is set to Y.

The possible values are:

Y
The transaction is rejected. This is the default.
N
The transaction is not rejected.

This indicator is always set to the reject condition when the dynamic routing program is invoked. To dynamically route a transaction defined by the DTRTRAN definition, you must change this to the accept condition.

If you reject the transaction, message DFHAC2001--"Transaction ‘tranid’ is unrecognized"--is sent to the user’s terminal for dynamic transaction routing. For Link3270 requests, the BRIH returned to the client will contain a return code indicating that the transaction was not found, and a compcode indicating that the routing program rejected the transaction specified on the DTRTRAN system initialization parameter.

DYRDTRXN
indicates whether the transaction to be routed is defined by the common transaction definition specified on the DTRTRAN system initialization parameter, or by a specific transaction definition.

This field applies only to dynamic transaction routing and Link3270 requests (not to the routing of program-link requests).

The possible values are:

Y
The transaction is defined by the definition specified by the system initialization parameter DTRTRAN. That is, there is no resource definition for the input transaction identifier (id).

For dynamic transaction routing, the transaction is initiated in the terminal-owning region using the transaction id specified by the system initialization parameter, DTRTRAN.

For dynamic transaction routing, the input transaction id is passed to the dynamic routing program in the DYRTRAN field. For Link3270 requests the common transaction definition is used to determine the routing characteristics of the request. The request still contains the original transaction id, not the common transaction id. If the request is run locally, the request is passed to the driver successfully, but the driver will fail to start the user transaction as it is not defined.

N
The transaction is not defined by the definition specified by the system initialization parameter, DTRTRAN. There is an installed resource definition for the input transaction id.

For dynamic transaction routing, the transaction is initiated in the terminal-owning region using the input transaction id. The transaction id passed to the dynamic routing program in the DYRTRAN field is the remote transaction id from the transaction resource definition (if this is different from the input transaction id).

For Link3270 requests, the transaction id passed to the routing program in the DYRTRAN field is the remote transaction id defined in the TRANSACTION resource definition.

For an explanation of the DTRTRAN system initialization parameter, see the CICS System Definition Guide.

DYRERROR
has a value only when DYRFUNC is set to ‘1’. It indicates the type of error that occurred during the last attempt at route selection. The possible values are:
0
The selected sysid is unknown.
1
The selected system is not in service.
2
The selected system is in service, but no sessions are available.
3
An allocate request has been rejected, and SYSIDERR returned to the application program. This error occurs for one of the following reasons:
  1. An XZIQUE global user exit program requested that the allocate be rejected, or
  2. CICS rejected the allocate request automatically because the QUEUELIMIT value specified on the CONNECTION resource definition has been reached.
4
A queue of allocate requests has been purged, and SYSIDERR returned to all the waiting application programs. This error occurs for one of the following reasons:
  1. An XZIQUE global user exit program requested that the queue be purged, or
  2. CICS purged the queue automatically because the MAXQTIME limit specified on the CONNECTION resource definition has been reached.
5
The selected system does not support this function. This occurs if the routing program tries to:
  1. Route a transaction initiated by an EXEC CICS START command to a pre-CICS TS OS/390®, Version 1 Release 3 region, or to a CICS TS OS/390, Version 1 Release 3 or later region that is not connected by an MRO or APPC parallel-session link.
  2. Route a transaction, or a program-link or Link3270 request, across a LU6.1 connection.
  3. Route a Link3270 request to a pre-CICS TS for z/OS®, Version 2.2 region.

Values 6-B all apply to attempts to route program-link requests. For the meanings of these error conditions, see the CICS Application Programming Reference manual.

6
The EXEC CICS LINK command returned LENGERR.
7
The EXEC CICS LINK command returned PGMIDERR.
8
The EXEC CICS LINK command returned INVREQ.
9
The EXEC CICS LINK command returned NOTAUTH.
A
The EXEC CICS LINK command returned TERMERR.
B
The EXEC CICS LINK command returned ROLLEDBACK.
F
The XPCERES global user exit program on the target region has set a return code of UERCRESU, meaning that a required resource is unavailable on the target region. This error code may be set for program-link, Link3270 bridge, and non-terminal-related START requests.
DYRFUNC
tells you the reason for this invocation of the dynamic routing program. The possible values are:
0
Invoked for route selection.
1
Invoked because an error occurred in route selection.
2
Invoked because a previously routed transaction or program-link request has terminated successfully, or for a request for which the user transaction terminated successfully.
3
Invoked for notification of the destination of a statically-routed request. This applies in the following cases:
ATI requests
A transaction defined as DYNAMIC(YES) has been initiated by a terminal-related automatic transaction initiation (ATI) request--for example, by the expiry of an interval control start request--but the transaction is ineligible for dynamic routing.

For information about which transactions initiated by terminal-related EXEC CICS START commands are eligible for dynamic routing, see the CICS Intercommunication Guide.

Program-link requests
The program is defined as DYNAMIC(YES)--or is not defined--but the caller specified the name of a remote region on the SYSID option of the EXEC CICS LINK command.

In this case, specifying the target region explicitly takes precedence over any SYSID returned by the dynamic routing program.

bridge requests
In session mode, the requested transaction is not the first user transaction and is defined as DYNAMIC(YES).
4
Invoked because the routed transaction or the requested user transaction abended.

The DYRTYPE field tells you the type of routing or notification request.

DYRLEVEL
is the level of CICS required in the target AOR to successfully process the routed request. The possible values are:
X'00'
Any currently-supported version of CICS is able to process the request.
X'01'
CICS TS for z/OS, Version 2.2. This value may be set only for method requests for enterprise beans and CORBA stateless objects Start of change(handled by the distributed routing program)End of change.
X'02'
CICS TS for z/OS, Version 2.3. This value may be set only for method requests for enterprise beans and CORBA stateless objects Start of change(handled by the distributed routing program)End of change.
Start of changeX'03'End of change
Start of changeCICS TS for z/OS Version 3.1. This value is always set for:
  • DPL requests that have a channel associated with them.
  • START requests that have a channel associated with them.
  • Start of changeInbound web services requests.End of change
This value may be set for method requests for enterprise beans and CORBA stateless objects.End of change

Note that values Start of changegreater than X'00'End of change indicate the specific--not the minimum--level of CICS required to process the request successfully.

This parameter is a migration aid, intended to help you perform a "rolling upgrade" of a multi-region logical server, whereby one region at a time is upgraded from one release of CICS to the next, without bringing down the server. Requests that require a specific level of CICS can be routed to an appropriate AOR.

Important

This mixed level of operation, in which different CICS regions in the same logical server are at different levels of CICS, is intended to be used only for rolling upgrades. It should not be used permanently, because it increases the risk of failure in some interoperability scenarios. The normal, recommended, mode of operation is that all the regions in a logical sever should be at the same level of CICS and Java™.

For definitive information about upgrading CICS EJB/CORBA servers, see Java Applications in CICS.

DYRLPROG
is the name of the initial program of the transaction to be routed; or the name of the program specified on the link command to be routed.
Transaction routing
You can use this field to specify the name of an alternative program to be run if the transaction is routed locally. For example, if all remote CICS regions are unavailable, and the transaction cannot be routed, you may want to run a program in the local terminal-owning region to send an appropriate message to the user.
Note:
DYRLPROG must not be set to blanks when you specify DYRCABP=N. If you specify DYRCABP=N, ensure you also specify a valid program name on DYRLPROG.
Program-link requests
When DYRFUNC is ‘0’ or ‘3’, DYRLPROG contains the name of the program to be linked, obtained using the following sequence:
  1. From the REMOTENAME option of the installed program definition
  2. If REMOTENAME is not specified, or there is no program definition, from the PROGRAM option of the EXEC CICS LINK command.

You can use this field to specify that an alternative program, other than that named on the program-link request, is to be linked. You can specify a local or remote program, depending on the region to which the request is to be routed.

Note:
Be aware that, if you change the value of DYRLPROG, and the alternate program you choose is defined as DYNAMIC(YES), the dynamic routing program will be reinvoked for route selection.
bridge requests
When DYRTYPE=8, this field should not be changed; any changes made are ignored by CICS.

You can change DYRLPROG on any call to the dynamic routing program, but it is effective only when DYRFUNC is ‘0’ or ‘1’.

DYRNETNM
is the netname of the CICS region identified in DYRSYSID.

If the DYRNETNM value is changed by the initial invocation of the dynamic routing program, CICS tries to route the request to the CICS region with the new netname.

DYROPTER
specifies whether the dynamic routing program is to be reinvoked when the routed transaction or link request terminates (successfully or unsuccessfully). The possible values are:
N
The dynamic routing program is not to be reinvoked. This is the default.
Y
The dynamic routing program is to be reinvoked.

You can specify this option for transactions, link requests, or bridge requests that are routed to remote CICS regions and also for those that are executed locally.

DYRPROCCMP
is not used by the dynamic routing program. On invocation, it is set to nulls.
DYRPROCID
is not used by the dynamic routing program. On invocation, it is set to nulls.
DYRPROCN
is not used by the dynamic routing program. On invocation, it is set to nulls.
DYRPROCT
is not used by the dynamic routing program. On invocation, it is set to nulls.
DYRPRTY
can be used to set the dispatch priority of the task in the application-owning region, if the connection between the terminal-owning region and application-owning region is MRO, or when processing a bridge request.
Transaction routing
Before invoking the dynamic routing program, CICS sets this value to ‘0’ (zero).
Program-link requests
Before invoking the dynamic routing program, CICS sets this value to the priority of the task that issued the program-link request.
bridge requests
Before invoking the dynamic routing program, CICS set this value to the value defined in the TRANSACTION resource definition of the user transaction in the router region.

On return from the initial invocation of the dynamic routing program, if the DYRRTPRI value is ‘Y’ CICS passes the DYPPRTY value to the application-owning region.

DYRQUEUE
identifies whether or not the request is to be queued if no sessions are immediately available to the remote system identified by DYRSYSID. The possible values are:
Y
The request is to be queued if necessary. This is the default.
N
The request is not to be queued.

For bridge requests, DYRQUEUE is set to Y before the dynamic routing program is invoked. Any change made to this value by the user-replaceable program is ignored by CICS.

DYRRETC
contains a return code that tells CICS how to proceed.
Transaction routing
The possible values are:
0
Continue processing the transaction.
4
Terminate the transaction without message or abend.
8
Terminate the transaction with either a message or an abend.
Whenever the routing program is invoked, DYRRETC is set to ‘0’. When it is invoked for route selection or because an error occurs in route selection, if you want CICS to continue processing the transaction, you must leave it set to ‘0’.

To make CICS terminate the transaction (issuing a message or abend), return a value of ‘8’.

To make CICS terminate the transaction without issuing a message or abend (indicating that DFHDYP has done all the processing that is necessary), return a value of ‘4’.

Notes:
  1. Setting a return code of ‘4’ for APPC transaction routing leads to unpredictable results, and should be avoided.
  2. Setting any non-zero return code other than X'4' is equivalent to setting X'8'.
Program-link requests
The possible values are:
0
Continue processing the link request.
Non-zero
Return an error condition to the program.
Whenever the routing program is invoked, DYRRETC is set to ‘0’. When it is invoked for route selection or because an error occurs in route selection, if you want CICS to continue processing the link request, you must leave it set to ‘0’.

To make CICS reject the link request, return a non-zero value. The program that issued the EXEC CICS LINK command receives a PGMIDERR condition, with a RESP2 value of 27.

bridge requests
The possible values are:
0
Continue processing the request.
4
Terminate processing the request without issuing any error messages.
8
Terminate processing the request with an error message.

Whenever the routing program is invoked, DYRRETC is set to ‘0’. When it is invoked for route selection or because an error occurs in route selection, if you want CICS to continue processing the link request, you must leave it set to ‘0’.

To make CICS terminate the request without issuing a message return a value of 4. The BRIH returned to the client contains a return code informing the client that the dynamic routing program has rejected the request, and a compcode that gives details of the reason the last attempt to route the request failed.

To make CICS terminate the request (issuing a message) return a value of 8. The BRIH returned to the client contains a return code informing the client that the dynamic routing program has rejected the request, and a compcode that gives details of the reason the last attempt to route the request failed.

You do not need to set a return code when the routing program is invoked for notification or at transaction termination. (Any code you set is ignored by CICS.)

DYRRTPRI
indicates whether or not the dispatch priority of the transaction, link request or request should be passed to the application-owning region, if the connection between the terminal-owning region and the application-owning region is MRO. The possible values are:
N
The dispatch priority is not passed. This is the default.
Y
The dispatch priority is passed.
DYRSRCTK
is the MVS™ workload management service and reporting class token for the routed transaction. Your routing program should not alter this value, which is set by CICS and used by CICSPlex SM.
DYRSYSID
is the system identifier (sysid) of a CICS region. The exact meaning of this parameter depends on the values of DYRFUNC and DYRTYPE:
DYRTRAN
contains the remote transaction id.
Transaction routing
When DYRFUNC is set to ‘0’ or ‘3’, DYRTRAN contains the remote transaction id specified on the REMOTENAME option of the installed transaction definition.
bridge requests
When DYRTYPE =8, DYRTRAN contains the transaction id of the target user transaction as it is known in the current region. Note that this is not the same as the current transaction id.
Program-link requests
When DYRFUNC is set to ‘0’ or ‘3’, DYRTRAN contains the transaction id of the remote mirror transaction, obtained using the following sequence:
  1. From the TRANSID option on the LINK command.
    Note:
    A value specified on the TRANSID option of the LINK command cannot be overridden by the routing program.
  2. From the TRANSID option on the program definition.
  3. 'CSMI', the generic mirror transaction. This is the default if neither of the TRANSID options are specified.

Your dynamic routing program can accept this remote transaction id, or supply a different transaction name for forwarding to the remote CICS region. If the supplied name is longer than four characters, it is truncated by CICS.

You can change DYRTRAN on any call to the dynamic routing program, but the change is effective only:

  1. When DYRFUNC is set to ‘0’ or ‘1’.
  2. If the original value was not obtained from the TRANSID option of an EXEC CICS LINK command. A value specified on the TRANSID option of a LINK command cannot be overridden by the routing program.
DYRTYPE
is the type of routing request for which the program is being invoked. For transaction routing, this field is meaningful only when DYRFUNC is set to ‘0’ (route selection) or ‘3’ (notify). The values that can be passed to the dynamic routing program are:
0
A transaction initiated from a terminal.
1
An ATI request that is to be statically routed.
2
A transaction started by a terminal-related EXEC CICS START command, where there is no data Start of changeand no channelEnd of change associated with the START.
3
A transaction started by a terminal-related EXEC CICS START command, where there is data Start of changebut no channelEnd of change associated with the START.
4
A program-link request Start of changewithout a channelEnd of change.
8
A bridge request.
Start of change9End of change
Start of changeA program-link request with a channel.End of change
Start of changeAEnd of change
Start of changeA transaction started by a terminal-related EXEC CICS START command, where there is a channel associated with the START.End of change
DYRUAPTR
Start of changeIf 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 that are earlier than CICS TS for z/OS, Version 2.3:

CICS Transaction Server for OS/390, Version 1 Release 3
PQ75814
CICS Transaction Server for z/OS Version 2 Release 2
PQ75834
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.

End of change
DYRUSER
is a 1024-byte user area.

Start of changeThis field is retained only for compatibility purposes--see the descriptions of the DYRUAPTR and DYRUSERN fields.End of change

DYRUSERID
is the CICS userid associated with the request.

For transaction routing, program-link requests, and bridge requests, DYRUSERID contains the userid under which the current transaction is running.

By examining this field when it is invoked for routing or because of a route-selection error (DYRFUNC=0 or 1, respectively), your routing program can route requests based on the userid associated with the request.

Start of changeDYRUSERNEnd of change
Start of changeis a 1024-byte user area.

CICS initializes this user area to zeroes before invoking the dynamic routing program for a given task. This user area can be modified by the dynamic routing program; the modified area is passed to subsequent invocations of the dynamic routing program for the same request.

End of change
DYRVER
is the version number of the dynamic routing program interface. Start of changeFor CICS Transaction Server for z/OS, Version 3 Release 1, the number is "10".End of change

Related tasks
Routing transactions dynamically
Routing DPL requests dynamically
Routing bridge requests dynamically
Naming your dynamic routing program
Testing your dynamic routing program
Related reference
Dynamic transaction routing sample programs
[[ Contents Previous Page | Next Page Index ]]