IBM SC34-6814-04 - Manual (Page 12)

Routing transactions dynamically . . . . . . . . . . . . . . . . . . 590
Dynamic transactions . . . . . . . . . . . . . . . . . . . . . 590
When the dynamic routing program is invoked . . . . . . . . . . . . 590
Information passed to the dynamic routing program . . . . . . . . . . 591
Changing the target CICS region . . . . . . . . . . . . . . . . . 592
Changing the program name . . . . . . . . . . . . . . . . . . 593
Telling CICS whether to route or terminate a transaction . . . . . . . . 593
If the system is unavailable or unknown . . . . . . . . . . . . . . 594
Invoking the dynamic routing program at end of routed transactions . . . . 594
Invoking the dynamic routing program on abend . . . . . . . . . . . 594
Modifying the initial terminal data . . . . . . . . . . . . . . . . . 595
Modifying the application’s communications area . . . . . . . . . . . 595
Receiving information from a routed transaction . . . . . . . . . . . 596
Some processing considerations . . . . . . . . . . . . . . . . . 596
Unit of work considerations . . . . . . . . . . . . . . . . . . . 597
Routing DPL requests dynamically . . . . . . . . . . . . . . . . . 597
When the dynamic routing program is invoked . . . . . . . . . . . . 598
Changing the target CICS region . . . . . . . . . . . . . . . . . 599
Changing the program name . . . . . . . . . . . . . . . . . . 599
Changing the transaction ID
. . . . . . . . . . . . . . . . . . 600
Telling CICS whether to route or terminate a DPL request . . . . . . . 600
If an error occurs in route selection . . . . . . . . . . . . . . . . 600
Using the XPCERES exit to check the availability of resources on the target
region . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Invoking the dynamic routing program at end of routed requests . . . . . 602
Modifying the application’s input communications area . . . . . . . . . 602
Monitoring the application’s output communications area . . . . . . . . 602
Some processing considerations . . . . . . . . . . . . . . . . . 602
Unit of work considerations . . . . . . . . . . . . . . . . . . . 603
Routing bridge requests dynamically . . . . . . . . . . . . . . . . 603
Changing bridge request parameters . . . . . . . . . . . . . . . 604
Rejecting a Link3270 bridge request
. . . . . . . . . . . . . . . 605
Handling route selection errors of Link3270 bridge requests . . . . . . . 605
Using the XPCERES exit to check the availability of resources on the target
region . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Re-invoking the dynamic routing program after Link3270 bridge requests 606
Link3270 bridge dynamic routing considerations . . . . . . . . . . . 606
Modifying the application’s containers . . . . . . . . . . . . . . . . 607
Routing by user ID . . . . . . . . . . . . . . . . . . . . . . . 607
Parameters passed to the dynamic routing program . . . . . . . . . . . 607
Naming your dynamic routing program. . . . . . . . . . . . . . . . 621
Testing your dynamic routing program . . . . . . . . . . . . . . . . 621
Dynamic transaction routing sample programs . . . . . . . . . . . . . 622
Chapter 18. Writing a distributed routing program . . . . . . . . . . 623
Differences between the distributed and dynamic routing interfaces . . . . . 624
Routing BTS activities . . . . . . . . . . . . . . . . . . . . . . 625
Which BTS activities can be dynamically routed? . . . . . . . . . . . 625
When the distributed routing program is invoked . . . . . . . . . . . 626
Changing the target CICS region . . . . . . . . . . . . . . . . . 627
Telling CICS whether to route the activity . . . . . . . . . . . . . . 627
If an error occurs in route selection . . . . . . . . . . . . . . . . 628
Invoking the distributed routing program on the target region
. . . . . . 628
Routing method requests for enterprise beans and CORBA stateless objects 629
Where workload balancing occurs . . . . . . . . . . . . . . . . 629
Which requests can be dynamically routed?. . . . . . . . . . . . . 631
x Customization Guide