Filter
Top Products
introduction
Master terminal operator
The master terminal operator controls system components
using the master terminal transaction, CEMT. With this
transaction, the master terminal operator can dynamically
change the system control parameters.
Although the transaction can be started at any valid IBM
3270 family display device or equivalent terminal, or from the
operating system console, its use is intended to be limited to
a person known as the
master terminal operator
. Starting a
transaction from the operating system console is described in
“The system console as a CICS terminal” on page 5.
The control permitted through CEMT allows you, the master
terminal operator, to improve performance by changing the
system control parameters in the day-to-day operation of the
system. In addition to system control, you have prime
responsibility for administering the terminal facilities of the
system.
By using the routing transaction (CRTE), you can also be a
master terminal operator for multiple connected CICS
systems.
As the master terminal operator, you can access all terminal
and supervisory terminal transactions. In addition, however,
you must be familiar with all the procedures associated
exclusively with the master terminal. You must be aware of
which terminals and operators can access CICS at any given
time, and of the identifiers by which they are known to CICS.
For example, when inquiring about terminals, you can specify
a class of terminals or a list of terminals. A class of terminals
is specified by the CLASS(value) keyword, where ‘value’ is
the 1-or 2-character suffix of the related terminal list table
(DFHTLTxx). A list of terminals is specified by a series of
terminal identifiers following the CEMT SET
TERMINAL(t1,t2,...,) command, where t1, t2, are terminal
identifiers. See “List of resource identifiers” on page 47 for
more information.
For MRO and LUTYPE6.1 connections, you must know the
identifier of each parallel session, and specify this identifier
when operating on the session.
For LUTYPE6.2 (APPC) connections, you must know the
modename of each set of parallel sessions, and specify this
modename when operating on the modegroup.
Your use of the master terminal transaction is restricted by
entries in the signon table and in the installed transaction
definitions. These entries are the responsibility of the system
programmer.
During long periods of continuous operation, you can, at
intervals, read out and reset the statistics counters. The
volume of activity in your system determines how often you
should do this.
When the system has satisfactorily completed its response to
a command, the time and date are printed or displayed at
your terminal, as follows:
TIME=hh.mm.ss DATE=mm.dd.yy
where time is in hours, minutes, and seconds, and date is in
months, days, and years, or in the form specified by the
DATFORM system initialization parameter. For brevity this
final message has been deleted from all examples in the
remainder of the book.
Unless otherwise stated, the information about the master
terminal and its transactions given in this book applies only
to a single CICS system, regardless of whether it is
connected to another CICS system through ISC or MRO.
MRO and ISC support
Multiregion operation (MRO) and intersystem communication
(ISC) allow the sharing of resources between more than one
CICS region. Thus a user at a terminal assigned to one
CICS region can run transactions in connected regions, and
can access resources—files, for example—in other regions.
It is also possible for a transaction running in one region to
communicate with a transaction running in another region,
thus sharing the processing workload.
Except for experiencing longer response times, you should
not be aware that MRO or ISC processes are being used.
BMS partitions
When you use display devices that support BMS partitions,
make sure that you understand:
How to use the SCROLL, PARTITION JUMP, CLEAR,
and CLEAR PARTITION keys
The concept of the active partition
The meanings of the partition-related indicator symbols
that can appear on a display screen.
For information about BMS partitions, see the
CICS
Application Programming Guide
.
CLEAR key
The CLEAR key clears all partitions from the display, and
sets the terminal to ‘base’ state. The next BMS output
request recreates the partitions (but does not restore their
contents), using the application partition set.
The CLEAR and CLEAR PARTITION keys cannot be used
interchangeably when an existing CICS transaction is run in
a single explicit partition.
4 CICS Supplied Transactions