Changes for CICS Transaction Server for OS/390, Version 1 Release 3

The following additions and changes have been made to the functions of CICS® Transaction Server for OS/390®, Version 1 Release 3.

Dynamic routing

CICS Transaction Server for OS/390, Version 1 Release 3 introduces extensions to the CICSPlex® SM dynamic routing program (called the dynamic transaction routing program in previous releases). You can dynamically route:

These new functions allow you to integrate workload management for requests from all these sources and thereby improve performance and workload throughput.

You specify which transactions and programs may be dynamically routed, and the CICS regions in which they may be run.

The following terms have been introduced to describe the CICS regions involved in dynamic routing:

Requesting region
The CICS region in which the dynamic routing request originates. For transactions initiated at a terminal, and inbound client DPL requests, this is typically a TOR. For terminal-related EXEC CICS START commands, for non-terminal-related EXEC CICS START commands, for peer-to-peer DPLs, and for CICS BTS activities, the requesting region is typically an AOR.
Routing region
The CICS region in which the decision is taken on where the transaction or program should be run. For transactions initiated at a terminal, for EXEC CICS START commands associated with a terminal, and for inbound client DPL requests, this is typically a TOR. For non-terminal-related EXEC CICS START commands, for peer-to-peer DPL requests, and for CICS BTS activities, the routing region is typically an AOR.
Target region
The CICS region in which the transaction or program runs. For all dynamically-routed requests, this is typically an AOR.

Benefits

The new dynamic routing function enables more of the work in a CICSplex to be workload balanced, resulting in more consistent response times. You will be able to:

External control blocks

In support of this function, CICSPlex SM external control blocks have been changed. You should recompile any programs using EYURWTRA, EYURWCOM, EYURCCOM, EYURPCOM, EYURLCOM, and EYU9WRAM. You should also review your dynamic routing exit logic (EYU9WRAM), if you have customized this exit.

For dynamic program link requests, EYU9WRAM can be used to change the transaction id specified on the work request.

BAS implications

Dynamic routing for START commands is controlled by the Dynamic and Routable fields in the transaction definition. DPL is controlled by the Dynamic field of the program definition. For details, see CICSPlex SM Managing Business Applicationsand CICSPlex SM Managing Business Applications.

Operations implications

For routable START requests, the new Routing Status field in the LOCTRAND view indicates whether or not the current transaction may be dynamically routed. For details see CICSPlex SM Operations Views Reference. For dynamic DPL requests, the new Dynam Status field in the PROGRAMD view indicates whether or not the current program may be dynamically routed. For details see CICSPlex SM Operations Views ReferenceThe TASKD, TASK2, and TASK3 views have been amended to include dynamic routing information. New views TASK4, TASK5, TASK6, TASK7, TASK8, and TASK9 have been introduced to show detailed monitoring information. For details, see CICSPlex SM Operations Views Reference.

New views

Two new summary views are provided:

CICS business transaction services

CICS business transaction services (BTS) extends the CICS API and provides support services that make it easier to model complex business transactions. Using BTS, each action that makes up the business transaction is implemented as one or more CICS transactions, in the traditional manner. However, a top-level program is used to control the overall progress of the business transaction. The top-level program manages the inter-relationship, ordering parallel execution, commit scope, recovery, and restart of the actions that make up the business transaction.

BTS processes are CICSplex-enabled, and take full advantage of CICSPlex SM’s workload separation and workload balancing functions. The CICS system group within a CICSplex, across which related BTS processes and activities may run, is known as a BTS-set. When you define a BTS-set, you do not need to define any new communication links, beyond those already defined for use by CICSPlex SM.

For workload management, BTS is supported by

For full details about BTS, see CICS Business Transaction Services.

[[ Contents Previous Page | Next Page Index ]]