IBM SC33-1683-02 - Manual (Page 14)

Changing the transaction ID. . . . . . . . . . . . . . . . . . . 560
Telling CICS whether to route or terminate a DPL request. . . . . . . . 560
If an error occurs in route selection . . . . . . . . . . . . . . . . 561
Invoking the dynamic routing program at end of routed requests . . . . . 561
Modifying the application’s input communications area . . . . . . . . . 561
Monitoring the application’s output communications area . . . . . . . . 562
Some processing considerations . . . . . . . . . . . . . . . . . 562
Unit of work considerations . . . . . . . . . . . . . . . . . . . 562
Parameters passed to the dynamic routing program . . . . . . . . . . . 562
Naming your dynamic routing program . . . . . . . . . . . . . . . . 573
Testing your dynamic routing program . . . . . . . . . . . . . . . . 573
Dynamic transaction routing sample programs . . . . . . . . . . . . . 574
Chapter 17. Writing a distributed routing program . . . . . . . . . . 575
Differences from the dynamic routing interface . . . . . . . . . . . . . 576
Distributed routing of BTS activities . . . . . . . . . . . . . . . . . 577
Which BTS activities can be dynamically routed? . . . . . . . . . . . 577
When the distributed routing program is invoked . . . . . . . . . . . 578
Changing the target CICS region . . . . . . . . . . . . . . . . . 579
Telling CICS whether to route the activity . . . . . . . . . . . . . . 579
If an error occurs in route selection . . . . . . . . . . . . . . . . 579
Invoking the distributed routing program on the target region. . . . . . . 580
Some processing considerations . . . . . . . . . . . . . . . . . 580
Routing of non-terminal-related START requests . . . . . . . . . . . . 581
Which requests can be dynamically routed? . . . . . . . . . . . . . 581
When the distributed routing program is invoked . . . . . . . . . . . 582
Changing the target CICS region . . . . . . . . . . . . . . . . . 583
Telling CICS whether to route the request. . . . . . . . . . . . . . 583
If an error occurs in route selection . . . . . . . . . . . . . . . . 584
Invoking the distributed routing program on the target region. . . . . . . 584
Some processing considerations . . . . . . . . . . . . . . . . . 584
Parameters passed to the distributed routing program . . . . . . . . . . 585
Naming your distributed routing program . . . . . . . . . . . . . . . 593
Distributed transaction routing sample programs . . . . . . . . . . . . 593
Chapter 18. Writing a CICS–DBCTL interface status program . . . . . . 595
The sample program and copy book
. . . . . . . . . . . . . . . . 596
Chapter 19. Writing a 3270 bridge exit program . . . . . . . . . . . 599
Chapter 20. Writing a security exit program for IIOP . . . . . . . . . 601
Chapter 21. Writing a program to tailor JVM execution environment
variables. . . . . . . . . . . . . . . . . . . . . . . . . . 603
Environment variables . . . . . . . . . . . . . . . . . . . . . . 603
Part 4. Customizing the XRF overseer program . . . . . . . . . . . . . . . .607
Chapter 22. The extended recovery facility overseer program . . . . . . 609
The sample overseer program . . . . . . . . . . . . . . . . . . . 609
The functions of the sample program . . . . . . . . . . . . . . . 609
How the sample overseer program interfaces with CICS . . . . . . . . 613
How to tell the overseer which actives and alternates to monitor . . . . . 613
The DFHWOSM macros . . . . . . . . . . . . . . . . . . . . . 614
The DFHWOSM tokens . . . . . . . . . . . . . . . . . . . . 615
DFHWOSM FUNC=BUILD macro
. . . . . . . . . . . . . . . . 615
xii CICS TS for OS/390: CICS Customization Guide