The following additions and changes have been made to the functions of
the CICSPlex® SM component of CICS® Transaction Server for OS/390 Release 3.
CICS Transaction Server for OS/390 Release 3 introduces extensions to
the CICSPlex SM dynamic routing program (called the dynamic transaction routing program in previous releases). In addition to dynamic
routing of transactions initiated at a terminal, you can now dynamically route:
- Transactions invoked using the EXEC CICS START commands that are associated with
a terminal
- Transactions invoked using the EXEC CICS START commands that are not associated
with a terminal
- Distributed program links, including:
- The CICS Web support
- The CICS Transaction Gateway
- EXCI calls
- CICS Client ECI calls
- Distributed Computing Environment (DCE) remote procedure calls (RPCs)
- Open Network Computing (ONC) remote procedure calls (RPCs)
- Internet Inter-Object Request Block Protocol (IIOP)
- Any function that issues an EXEC CICS LINK PROGRAM request
- Transactions associated with CICS business transaction services (BTS) activities (see CICS business transaction services)
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 new dynamic functions are supported by:
- A new workload management view, WLMAWAOS, which shows summarized information
about all target regions that are associated with a workload that is within
the CICSplex identified as the context. WLMAWAOS is a summary form of the
WLMAWAOR view.
- A new workload management view, WLMAWTOS, which shows summarized information
about all routing regions that are associated with a workload that is within
the CICSplex identified as the context. WLMAWTOS is a summary form of the
WLMAWTOR view.
- A new field, Dynamic, on the BAS PROGDEF view, which specifies whether
or not an EXEC CICS LINK to the named program may invoke dynamic routing.
- A new field, Routable, on the BAS TRANDEF view, which specifies whether
or not an eligible EXEC CICS START TERMID should be shipped to the terminal-owning
region (TOR) for potential dynamic routing.
An overview of dynamic routing is given in What is workload management?. Full
details are in given in CICSPlex System Manager Managing Workloads.
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.
For full details about BTS, see CICS Business Transaction Services.
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 an activity is attached, WLM routes the
activity to the most appropriate region in the CICSplex. You can separate a BTS workload
based on process-type. Workload management and the CICS
Transaction Affinities Utility understand affinities between BTS processes
and activities.
CICSPlex SM support for BTS is provided by:
- A new BAS resource definition object, PROCDEF, which you use
to define BTS process types. All other BTS resources are created dynamically
when you specify a name in your application.
- New operations views:
- PROCTYP, a general view of all installed process types
- PROCTYPD, a detailed view of a selected process type
- PROCTYPS, a summary view of all installed process types.
- Workload management changes:
- A new view, WLMATAFD, which provides a detailed view of the properties
of a single active BTS affinity. You can use this view to display the contents
of the BTS affinity key in hexadecimal format.
- The TRANDEF and WLMSPEC views have been enhanced to allow you to specify
the BTS BAPPL affinity relation, and the BTS ACTIVITY and PROCESS affinity
lifetimes.
CICS Transaction Server for OS/390 Release 3 introduces Resource Definition
Online (RDO) support for the Temporary Storage Table (TST). For CICSPlex SM, support
for this function is provided by:
- A new BAS resource definition object TSMDEF, which allows you
to specify a temporary storage queue name prefix and associate attributes
with that name.
- New operations views:
- TSMODEL, a general view of all currently available temporary storage queue
models.
- TSMODELD, a detailed view of a temporary storage model.
- TSMODELS, a summary view of temporary storage models.
- TSPOOL, a general view of temporary storage shared pools.
- TSQSHR, a general view of shared temporary storage queues.
- TSQSHRD, a detailed view of a shared temporary storage queue.
- TSQSHRS, a summary view of shared temporary storage queues.
The existing temporary storage operations views, TSQ, TSQS, TSQGBL, and
TSQGBLS, remain unchanged. However, you can now delete temporary storage queues
from the TSQ, TSQSHR and TSQNAME views by entering the command DEL. A new
TSQ Deletion Panel asks you to confirm the deletion.
Users have found it difficult to generate temporary storage queue names
that are unique. Typically, queue names were generated from the transaction
id and the terminal id but unique names could be guaranteed only where the
terminal id was unique and the transaction required one queue only. Many users
like to have the user id as part of the queue name, so that the queue data
is tied to the user rather than the terminal, but then there is no room for
the transaction id which is required if properties, for example, recoverability
and security, are to be associated with the queue via the temporary storage
table (TST).
To provide greater flexibility, the length of temporary storage queue names
has been increased to a maximum of 16 characters. For example, users can generate
queue names of the form:
XXXXaUUUUUUUU
where:
- XXXX
- is the transaction id.
- a
- is a suffix allowing the transaction or user to have more than one queue.
- UUUUUUUU
- is the user id.
The TST or temporary storage model prefix can then be XXXX or XXXXa.
For CICSPlex SM, support for this function is provided by:
- New operations views:
- TSQNAME, a general view of all non-shared temporary storage queues.
- TSQNAMED, a detailed view of a non-shared temporary storage queue.
- TSQNAMES, a summary view of all non-shared temporary storage queues.
CICS Transaction Server for OS/390® Release 3 allows the use of Recoverable
Resources Management Services (RRMS) facilities in an MVS™ image. CICSPlex SM supports
this function through:
- A new value of WAITRRMS for the Wait Cause field of the UOWORKD view.
- A new Protocol field on the UOWLINKD view, that may take values of RRMS
or blank.
- A new RRMS Status field on the CICSRGND view, that may take the values
OPEN, CLOSED, or N/A.
CICS Transaction Server for OS/390 Release 3 extends the CICS application
programming interface to serialize resources across a set of CICS systems. The set
of CICS systems defined as forming the resource set is called the enqueue scope. CICSPlex SM supports this function through:
- A new BAS resource definition ENQMDEF, which defines a global enqueue
model.
- New operations views:
- ENQMDL, a general view of enqueue models.
- ENQMDLD, a detailed view of a selected enqueue model.
- ENQMDLS, a summary view of enqueue models.
- A new field, Enqscope, on the UOWENQ view.
CICSPlex SM supports IIOP inbound to Java™ applications through:
- A new BAS resource definition RQMDEF, which defines a CICS request model
resource.
- New operations views:
- RQMODEL, a general view of request models and their associated transactions.
- RQMODELD, a detailed view of a selected request model.
- RQMODELS, a summary view of all installed request models.
CICS Transaction Server for OS/390 Release 3 introduces support for coupling
facility data tables. Part of this function is the implementation of new attributes
on the FILE resource definition to specify a coupling facility data table
pool to be associated with the file. In support of this function, CICSPlex SM support
of the file inquiry facility is extended by:
- New operations views:
- CFDTPOOL, a general view of coupling facility data table pools associated
with the file.
- CFDTPOOD, a detailed view of a selected coupling facility data table pool.
- CFDTPOOS, a summary view of coupling facility data table pools.
- The existing file operations view, CMDT, and its associated detail view,
CMDTD, and summary view, CMDTS, have been amended to reflect support for coupling
facility data tables.
- Two new detail views for CMDT:
- CMDT2, for detailed information relating to a CICS- or user-maintained
data table, or a coupling facility data table. You can hyperlink to this view
from the Table Info field of the CMDTD view.
- CMDT3, for statistical information relating to a data table file. You
can hyperlink to this view from the Data Set Info field of the CMDT2 view.
- The FILE operations view is amended to reflect support of coupling facility
data tables.
CICS Transaction Server for OS/390 Release 3 introduces various enhancements
to the CICS Web support. Part of this function is the introduction of new
CICS RDO resource definitions, HTMLTEMPLATE and TCPIPSERVICE. CICSPlex SM supports
this function by:
- New BAS views:
- DOCDEF, which defines document templates.
- TCPDEF, which defines TCP/IP services.
- New operations views for document templates:
- DOCTEMP, a general view of document templates.
- DOCTEMPD, a detailed view of a selected document template.
- DOCTEMPS, a summary view of document templates.
- New operations views for TCP/IP services:
- TCPIPS, a general view of TCP/IP services.
- TCPIPSD, a detailed view of a selected TCP/IP service.
- TCPIPSS, a summary view of TCP/IP services.
CICS Transaction Server for OS/390 Release 3 provides the support required
to run a Java transaction under the control of an OS/390 Java Virtual
Machine (JVM). CICSPlex SM supports this function by:
- Two new fields, JVM and JVMClass, on the BAS PROGDEF view.
- Three new fields, Runtime, JVM Class, and JVM Debug, on the operations
PROGRAMD view.
- A new operations view, PROGRAMJ, a detailed view of the JVM Class value
for the current program.
CICS Transaction Server for OS/390 Release 3 introduces an enhancement
to the internal architecture of CICS to enable specified tasks to run under
their own task control block. In support of this function, CICSPlex SM extends
its inquiry function for the following resource types:
- New fields, Force QR and Max open TCBs, added to the CICSRGN2 view.
- A new field, Concurrency, added to the PROGRAMD view.
- Amendments to the PROGRAM view.
- Amendments to the EXITGLUE and EXITTRUE views.
- Amendments to the TASK and TASKD views.
CICS Transaction Server for OS/390 Release 3 introduces changes to the
way in which the CICS/ESA Front End Programming Interface (FEPI) is managed
using CICSPlex SM. The changes are:
- New BAS views:
- FENODDEF, which defines FEPI nodes
- FEPOODEF, which defines FEPI pools
- FEPRODEF, which defines FEPI property sets
- FETRGDEF, which defines FEPI targets.
- FEPI resources are now installed using these new BAS views; they cannot
be installed using the operations views
CICS Transaction Server for OS/390 Release 3 provides support for Tivoli® Global Enterprise Manager (Tivoli GEM). For users of the Tivoli GEM
client, the CICSPlex SM Instrumentation feature enables users to view status information
for the CMAS environment and the MAS environment of the CICSplex.
[[ Contents Previous Page | Next Page Index ]]