CICS Supplied Transaction

CICS Transaction Server for OS/390 IBM
CICS Supplied Transactions

Release 3
SC33-1686-02
CICS Transaction Server for OS/390 IBM
CICS Supplied Transactions
Release 3
SC33-1686-02
Note!
Before using this information and the product it supports, be sure to read the general information under “Notices” on page vii.
Third edition (March 1999)
This edition applies to Release 3 of CICS Transaction Server for OS/390, program number 5655-147, and to all subsequent versions, releases,
and modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the product.
This edition replaces and makes obsolete the previous edition, SC33-1686-01. The technical changes for this edition are summarized under
"Summary of changes" and are indicated by a vertical bar to the left of a change.
Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address
given below.
At the back of this publication is a page entitled “Sending your comments to IBM”. If you want to make comments, but the methods described
are not available to you, please address them to:
IBM United Kingdom Laboratories, Information Development,

Mail Point 095, Hursley Park, Winchester, Hampshire, England, SO21 2JN.
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate
without incurring any obligation to you.
 Copyright International Business Machines Corporation 1982, 1999. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
What this book is about . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Who should read this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
What you need to know to understand this book . . . . . . . . . . . . . . . . . . . . ix
How to use this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
CICS Transaction Server for OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
CICS books for CICS Transaction Server for OS/390 . . . . . . . . . . . . . . . . . xi
CICSPlex SM books for CICS Transaction Server for OS/390 . . . . . . . . . . . . xii
Other CICS books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Books from related libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Determining if a publication is current . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
| Changes for this edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Changes for the CICS Transaction Server for OS/390 release 2 edition . . . . . . . . xv
Changes for the CICS Transaction Server for OS/390 release 1 edition . . . . . . . . xvi
Changes for the CICS/ESA 4.1 edition . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Chapter 1. Transactions supplied by CICS . . . . . . . . . . . . . . . . . . . . . . . 1

Upgrading CICS transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
How to start or stop a transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Syntax notation and conventions used in this book . . . . . . . . . . . . . . . . . . . . 2
Terminal operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
MRO and ISC support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
BMS partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
The system console as a CICS terminal . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Time sharing option (TSO) consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
| Chapter 2. CBAM—BTS browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 3. CDBC—database control menu . . . . . . . . . . . . . . . . . . . . . . 11

Connecting CICS to DBCTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Disconnecting CICS from DBCTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
The HELP panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 4. CDBI—database control inquiry . . . . . . . . . . . . . . . . . . . . . 13

The HELP panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 5. CDBM—database control interface . . . . . . . . . . . . . . . . . . . . 15

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
| DFHDBFK - The CDBM GROUP command file . . . . . . . . . . . . . . . . . . . . . 16
| The MAINTENANCE panel for DFHDBFK . . . . . . . . . . . . . . . . . . . . . . . . 16
The CICS-DBCTL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
The HELP panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 6. CEBR—temporary storage browse . . . . . . . . . . . . . . . . . . . . 19

The HELP panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 7. CEBT—master terminal (alternate CICS) . . . . . . . . . . . . . . . . . 21

Minimum abbreviation of keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
CEBT INQUIRE and SET commands . . . . . . . . . . . . . . . . . . . . . . . . . . 21
 Copyright IBM Corp. 1982, 1999 iii

CEBT PERFORM commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
The HELP panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 8. CECI—command-level interpreter . . . . . . . . . . . . . . . . . . . . 31

The HELP panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Command-level syntax-checking transaction (CECS) . . . . . . . . . . . . . . . . . . 32
Chapter 9. CEDA—resource definition online . . . . . . . . . . . . . . . . . . . . 33

Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
CSD compatibility panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Security checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
CEDA HELP panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
CEDB and CEDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Chapter 10. CEDF & CEDX — the execution diagnostic facility . . . . . . . . . . 41

CEDF transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
CEDX transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 11. CEMT—master terminal . . . . . . . . . . . . . . . . . . . . . . . . . 45

Starting the CEMT transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
CEMT DISCARD commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
CEMT INQUIRE commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
CEMT PERFORM commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
CEMT SET commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Chapter 12. CEOT—terminal status . . . . . . . . . . . . . . . . . . . . . . . . . . 213

CEOT in inquiry mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
CEOT in set mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Chapter 13. CESF—sign off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Chapter 14. CESN—sign on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

IBM 3270 family display devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Non-3270 family terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Signing off with CESN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Chapter 15. CEST—supervisory terminal . . . . . . . . . . . . . . . . . . . . . . . 219
Chapter 16. CETR—trace control . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Component trace options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Transaction and terminal-related trace options . . . . . . . . . . . . . . . . . . . . . . 222
HELP panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Chapter 17. CIND—in-doubt testing tool . . . . . . . . . . . . . . . . . . . . . . . 227

Running the CIND in-doubt tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Resource definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Chapter 18. CMAC—messages and codes display . . . . . . . . . . . . . . . . . 229
Chapter 19. CMSG—message switching . . . . . . . . . . . . . . . . . . . . . . . 231

Sending a message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Subsystems and terminal systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
CMSG command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Message-switching responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Examples of complete message-switching transactions . . . . . . . . . . . . . . . . . 245
Chapter 20. CRTE—remote transactions . . . . . . . . . . . . . . . . . . . . . . . 247
iv CICS Supplied Transactions

Chapter 21. CSFE—terminal and system test . . . . . . . . . . . . . . . . . . . . 249
Terminal test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
System spooling interface trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Terminal builder trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Debug functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Global trap/trace program exit and global kernel exit . . . . . . . . . . . . . . . . . . 251
Chapter 22. CSPG—page retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Retrieve a page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Display information about logical messages . . . . . . . . . . . . . . . . . . . . . . . 255
Message chaining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Message termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Copying pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Status of hardcopy terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Routed pages displayed at terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Chapter 23. CWTO—write to console operator . . . . . . . . . . . . . . . . . . . 259
Chapter 24. DSNC—CICS DB2 transaction DSNC . . . . . . . . . . . . . . . . . . 261
Appendix. List of CICS transactions . . . . . . . . . . . . . . . . . . . . . . . . . 263
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Sending your comments to IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Contents v
vi CICS Supplied Transactions
Notices
This information was developed for products and services offered in the U.S.A. IBM may not
offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently
available in your area. Any reference to an IBM product, program, or service is not intended
to state or imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any IBM intellectual
property right may be used instead. However, it is the user's responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in
this document. The furnishing of this document does not give you any license to these
patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual
Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation

Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply in the United Kingdom or any other country
where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore this statement may not apply to you.
This publication could include technical inaccuracies or typographical errors. Changes are
periodically made to the information herein; these changes will be incorporated in new
editions of the publication. IBM may make improvements and/or changes in the product(s)
and/or the program(s) described in this publication at any time without notice.
Licensees of this program who wish to have information about it for the purpose of enabling:
(i) the exchange of information between independently created programs and other programs
(including this one) and (ii) the mutual use of the information which has been exchanged,
should contact IBM United Kingdom Laboratories, MP151, Hursley Park, Winchester,
Hampshire, England, SO21 2JN. Such information may be available, subject to appropriate
terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are
provided by IBM under terms of the IBM Customer Agreement, IBM International
Programming License Agreement, or any equivalent agreement between us.
 Copyright IBM Corp. 1982, 1999 vii

Trademarks
The following terms are trademarks of International Business Machines Corporation in the
United States, or other countries, or both:
ACF/VTAM IBM
BookManager IBMLink
CICS IMS
CICS/ESA IMS/ESA
CICS/VM Language Environment
CICSPlex MQ
DB2 MVS/DFP
DFSMS OS/390
DFSMS/MVS RACF
DFSMSdss VTAM
DFSMShsm
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in
the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks of others.
viii CICS Supplied Transactions

Preface
What this book is about

This book tells you how to start the transactions supplied with CICS. It tells you how to
control the CICS system, how to send messages, how to collect statistics, and how to get
terminal error information. It is also useful if you are responsible for preparing procedures for
people who operate such terminals.
The book also describes how you can use the operating system console as a CICS terminal.
Who should read this book

This book is intended for CICS terminal operators and persons responsible for preparing
terminal operating procedures. It is also useful for both system and application programmers.
What you need to know to understand this book

A general knowledge of the concepts and terminology is required.
How to use this book

This book is mainly for reference. After a short introduction, the rest of the book is arranged
in alphabetic order of the transaction identifier. An index is provided to pinpoint individual
transactions and keywords.
Some CICS transactions are described in greater detail in other CICS books. These include:
Transaction CICS book

CBAM CICS Business Transaction Services
CDBC CICS IMS Database Control Guide
CDBI CICS IMS Database Control Guide
CEBR CICS Application Programming Guide
CECI CICS Application Programming Guide
CECS CICS Application Programming Guide
CEDA CICS Resource Definition Guide
CEDF CICS Application Programming Guide
CETR CICS Problem Determination Guide
CRTE CICS RACF Security Guide
CSFE CICS Problem Determination Guide
DSNC CICS DB2 Guide
In these cases, this book contains a brief description of the transaction and indicates where
further information is to be found.
Front end programming interface

Information about the Front End Programming Interface feature (FEPI) is not given in this
book. See the CICS Front End Programming Interface User's Guide for relevant information.
 Copyright IBM Corp. 1982, 1999 ix

Notes on terminology
CICS refers to IBM CICS Transaction Server for OS/390 Release 3
VTAM refers to IBM ACF/VTAM
IMS refers to IBM IMS/ESA
TCAM refers to the DCB interface of ACF/TCAM.
x CICS Supplied Transactions

Bibliography
CICS Transaction Server for OS/390

CICS Transaction Server for OS/390: Planning for Installation GC33-1789
CICS Transaction Server for OS/390 Release Guide GC34-5352
CICS Transaction Server for OS/390 Migration Guide GC34-5353
CICS Transaction Server for OS/390 Installation Guide GC33-1681
CICS Transaction Server for OS/390 Program Directory GI10-2506
CICS Transaction Server for OS/390 Licensed Program Specification GC33-1707
CICS books for CICS Transaction Server for OS/390

General
CICS Master Index SC33-1704
CICS User's Handbook SX33-6104
CICS Transaction Server for OS/390 Glossary (softcopy only) GC33-1705
Administration
CICS System Definition Guide SC33-1682
CICS Customization Guide SC33-1683
CICS Resource Definition Guide SC33-1684
CICS Operations and Utilities Guide SC33-1685
CICS Supplied Transactions SC33-1686
Programming
CICS Application Programming Guide SC33-1687
CICS Application Programming Reference SC33-1688
CICS System Programming Reference SC33-1689
CICS Front End Programming Interface User's Guide SC33-1692
CICS C++ OO Class Libraries SC34-5455
CICS Distributed Transaction Programming Guide SC33-1691
CICS Business Transaction Services SC34-5268
Diagnosis
CICS Problem Determination Guide GC33-1693
CICS Messages and Codes GC33-1694
CICS Diagnosis Reference LY33-6088
CICS Data Areas LY33-6089
CICS Trace Entries SC34-5446
CICS Supplementary Data Areas LY33-6090
Communication
CICS Intercommunication Guide SC33-1695
CICS Family: Interproduct Communication SC33-0824
CICS Family: Communicating from CICS on System/390 SC33-1697
CICS External Interfaces Guide SC33-1944
CICS Internet Guide SC34-5445
Special topics
CICS Recovery and Restart Guide SC33-1698
CICS Performance Guide SC33-1699
CICS IMS Database Control Guide SC33-1700
CICS RACF Security Guide SC33-1701
CICS Shared Data Tables Guide SC33-1702
CICS Transaction Affinities Utility Guide SC33-1777
CICS DB2 Guide SC33-1939
 Copyright IBM Corp. 1982, 1999 xi

CICSPlex SM books for CICS Transaction Server for OS/390
General
CICSPlex SM Master Index SC33-1812
CICSPlex SM Concepts and Planning GC33-0786
CICSPlex SM User Interface Guide SC33-0788
CICSPlex SM View Commands Reference Summary SX33-6099
Administration and Management
CICSPlex SM Administration SC34-5401
CICSPlex SM Operations Views Reference SC33-0789
CICSPlex SM Monitor Views Reference SC34-5402
CICSPlex SM Managing Workloads SC33-1807
CICSPlex SM Managing Resource Usage SC33-1808
CICSPlex SM Managing Business Applications SC33-1809
Programming
CICSPlex SM Application Programming Guide SC34-5457
CICSPlex SM Application Programming Reference SC34-5458
Diagnosis
CICSPlex SM Resource Tables Reference SC33-1220
CICSPlex SM Messages and Codes GC33-0790
CICSPlex SM Problem Determination GC33-0791
Other CICS books

CICS Application Programming Primer (VS COBOL II) SC33-0674
CICS Application Migration Aid Guide SC33-0768
CICS Family: API Structure SC33-1007
CICS Family: Client/Server Programming SC33-1435
CICS Family: General Information GC33-0155
CICS 4.1 Sample Applications Guide SC33-1173
CICS/ESA 3.3 XRF Guide SC33-0661
If you have any questions about the CICS Transaction Server for OS/390 library, see CICS
Transaction Server for OS/390: Planning for Installation which discusses both hardcopy and
softcopy books and the ways that the books can be ordered.
Books from related libraries

The reader of this book may also want to refer to the following IBM publications:
OS/390 MVS System Commands, GC28-1781
Resource Access Control Facility (RACF): Security Administrator’s Guide, SC28-1340
IMS Utilities Reference manual, SC26-4284
IMS Messages and Codes manual, SC26-4290
IMS System Administration Guide, SC26-4278
IMS Operations Guide, SC26-4287
An Introduction to the IBM 3270 Information Display System, GA27-2739
Systems Network Architecture—LU6.2 Reference: Peer Protocols, SC31-6808
MVS/DFP 3.2 System Programming Reference manual, SC26-4567
OS/390 MVS Diagnosis: Tools and Service Aids, SY28-1085
Determining if a publication is current

IBM regularly updates its publications with new and changed information. When first
published, both hardcopy and BookManager softcopy versions of a publication are usually in
step. However, due to the time required to print and distribute hardcopy books, the
BookManager version is more likely to have had last-minute changes made to it before
publication.
xii CICS Supplied Transactions

Subsequent updates will probably be available in softcopy before they are available in
hardcopy. This means that at any time from the availability of a release, softcopy versions
should be regarded as the most up-to-date.
For CICS Transaction Server books, these softcopy updates appear regularly on the
Transaction Processing and Data Collection Kit CD-ROM, SK2T-0730-xx. Each reissue of
the collection kit is indicated by an updated order number suffix (the -xx part). For example,
collection kit SK2T-0730-06 is more up-to-date than SK2T-0730-05. The collection kit is also
clearly dated on the cover.
Updates to the softcopy are clearly marked by revision codes (usually a “#” character) to the
left of the changes.
Bibliography xiii
xiv CICS Supplied Transactions
Summary of changes
This edition is based on the CICS Transaction Server for OS/390 Release 2 edition,
SC33-1686-01. Changes for this edition are marked by vertical bars to the left of the text.
| Changes for this edition

| Changes include:
| The CEMT transaction is extended to support the new resource types:
| – DOCTEMPLATE
| – ENQMODEL
| – PROCESSTYPE
| – REQUESTMODEL
| – TCPIPSERVICE
| – TSMODEL
| also added to CEMT are the following:
| – INQUIRE CFDTPOOL
| – INQUIRE ENQ
| – INQUIRE RRMS
| – INQUIRE TCPIP and SET TCPIP
| – INQUIRE TSPOOL
| – INQUIRE TSQNAME and SET TSQNAME
| – INQUIRE TSQUEUE and SET TSQUEUE
| – INQUIRE WEB and SET WEB
| and there are changes to
| – CEMT INQUIRE FILE and SET FILE in support of coupling facility data tables
| – CEMT INQUIRE PROGRAM and CEMT SET PROGRAM to support running JAVA
| applications under the control of a Java Virtual Machine (JVM).
| The new CBAM transaction (described in Chapter 2, “CBAM—BTS browser” on
| page 9).
| The CDBM transaction is extended to support storing of commands for reuse, and
| issuing of stored commands.
Changes for the CICS Transaction Server for OS/390 release 2 edition
Changes included:
The CDEX transaction
Addition of BRIDGE and IDENTIFIER to CEMT INQUIRE TASK.
Addition of BREXIT and FACILITYLIKE to CEMT INQUIRE TRANSACTION.
The CICS DB2 attachment facility is enhanced to provide resource definition online
(RDO) support for DB2 resources as an alternative to resource control table (RCT)
definitions. The following CEMT INQUIRE, and SET, commands are added:
– CEMT INQUIRE|SET DB2CONN
– CEMT INQUIRE|SET DB2ENTRY
– CEMT INQUIRE|SET DB2TRAN
The CEMT DISCARD command is extended to allow the resource definitions
DB2CONN. DB2ENTRY, and DB2TRAN to be discarded.
The CEDA check function is enhanced to perform consistency checks on the new DB2
objects.
 Copyright IBM Corp. 1982, 1999 xv

Changes for the CICS Transaction Server for OS/390 release 1 edition
This edition is based on the CICS/ESA 4.1 CICS-Supplied Transactions manual
(SC33-0710-00).
For CICS Transaction Server for OS/390, the following changes have been made:
Removal of local DL/I and CEMT INQUIRE and SET PITRACE
Addition of CEMT DISCARD JMODEL, CEMT DISCARD JOURNALNAME, CEMT
DISCARD TDQUEUE, CEMT INQUIRE EXCI (replacing CEMT INQUIRE IRBATCH),
CEMT INQUIRE JMODEL, CEMT INQUIRE JOURNALNAME, CEMT INQUIRE
STREAMNAME, CEMT INQUIRE UOW, CEMT INQUIRE UOWDSNFAIL, CEMT
INQUIRE UOWENQ, CEMT INQUIRE UOWLINK, CEMT PERFORM ENDAFFINITY,
CEMT SET JOURNALNAME, CEMT SET UOW, and CEMT SET UOWLINK commands
New options on the CEMT INQUIRE CONNECTION, CEMT INQUIRE DSNAME, CEMT
INQUIRE FILE, CEMT INQUIRE NETNAME, CEMT INQUIRE TASK, CEMT INQUIRE
TDQUEUE, CEMT INQUIRE TERMINAL, CEMT PERFORM SHUTDOWN, CEMT
PERFORM STATISTICS RECORD, CEMT SET CONNECTION, CEMT SET DSNAME,
and CEMT SET TDQUEUE commands.
Changes for the CICS/ESA 4.1 edition

This edition is based on the CICS/ESA 3.3 CICS-Supplied Transactions manual
(SC33-0669-02).
For CICS/ESA 4.1, the following changes have been made:

CEMT INQUIRE CONNECTION has been enhanced to display more information.
CEMT INQUIRE|SET DSAS has been added.
CEMT INQUIRE|PERFORM|SET DELETSHIPPED has been added.
RELATED and LOCAL options have been added to the CEMT INQUIRE
SYDUMPCODE and TRDUMPCODE commands and to the CEMT SET SYDUMPCODE
and TRDUMPCODE commands.
CEMT, CEDA, and CETR now show the SYSID alongside the APPLID.
CEDA now shows the resource type and resource name in all the View, Alter, and
Define panels.
In CEMT INQ|SET SYSTEM, the CSCS, ECSCS, ERSCS, EUSCS, and USCS
operands have been removed, and the DSALIMIT, EDSALIMIT, ESDASIZE, RDSASIZE,
SDSASIZE, and TRANISOLATE operands have been added. In addition, the definitions
have been changed for the CDSASIZE, ECDSASIZE, ERDSASIZE, and EUDSASIZE
operands. The DTRTRANSID, PROGAUTOCTLG, PROGAUTOEXIT, and
PROGAUTOINST operands have also been added. FEPI and PROGAUTO options are
added to the CEMT PERFORM STATISTICS command.
In addition, many editorial changes have been made to clarify the information in this manual.
xvi CICS Supplied Transactions

introduction
Chapter 1. Transactions supplied by CICS

CICS provides operations, usually initiated from terminals,
called transactions, each of which involves the use of CICS
Upgrading CICS transactions
tables, programs, and internal services. This book deals with
You may wish to apply a CICS-supplied upgrade, but are
those transactions that are supplied by CICS and which, in
using modified versions of one or more CICS-supplied
addition, have an operator interface.
transactions or of the CICS-supplied calling programs that
CICS transactions have identification codes that start with “C” handle CICS-supplied transactions. After you have first
and are 4 characters long; for example, CEMT. copied them to differently named groups, you must replace
these private versions from the upgraded CICS-supplied
The following table shows the transactions that are described version and modify them afresh to ensure that the necessary
in this book. For a more complete list of CICS transactions, upgrade changes are carried out. Failure to do this can lead
including those that do not have an operator interface, see to unpredictable results.
the Appendix, “List of CICS transactions” on page 263.
Function Name Page How to start or stop a transaction

| CICS business transaction CBAM 9
| services (BTS) browser You start a CICS transaction by pressing the CLEAR key to
Command-level interpreter CECI, 31 clear the screen, and entering the transaction identifier, either
CECS by itself or followed by data, on the command line of the
Database control inquiry CDBI 13 screen. The command line is a single line, usually at the top
Database control interface CDBM 15
of the screen.
Database control menu CDBC 11
Execution diagnostic facility CEDF 41
You can type the transaction identifier by itself and follow the
CEDX 41
In-doubt testing tool CIND 227 prompts until a complete transaction command is built up, or
Master terminal CEMT 45 you can type the complete transaction command on the
Master terminal (alternate CICS) CEBT 21 command line. If you do not enter enough information, or if
Messages and codes display CMAC 229 the information you enter is wrong, you are prompted to
Message switching CMSG 231 complete or correct your input.
Page retrieval CSPG 253
Remote transactions CRTE 247 For example, in the following transaction, CEMT is the
Resource definition online CEDA, 33 transaction identifier and the additional data is INQUIRE
(RDO) CEDB,
PROGRAM(PROG1).
CEDC
Sign off CESF 215 CEMT INQUIRE PROGRAM(PROG1)
Sign on CESN 217
When the transaction starts, it processes the additional data.
Supervisory terminal CEST 219
Temporary-storage browse CEBR 19 At the completion of this transaction, you get the following
Terminal status CEOT 213 message:
Trace control CETR 221 STATUS: SESSION ENDED
Terminal and system test CSFE 249
Write to console operator CWTO 259 After a transaction has completed, press the CLEAR key to
clear the screen in readiness for the next transaction. You
In general, you start a CICS transaction by entering its can cancel any request by typing CANCEL on the command
transaction identifier (for example, CEMT). The transaction line.
identifier is used by CICS to identify the programs that
handle the specified transactions, and to establish a task to
process them.
If you use an IBM 3270 system display or similar display

device that has the appropriate features installed, you can
also start a transaction by a program function (PF) key or
program attention (PA) key, by an operator identification card
reader, by a magnetic slot reader, or by a light pen. For other
types of terminals or subsystems, see the appropriate
CICS/OS/VS subsystem guide.
 Copyright IBM Corp. 1982, 1999 1

introduction
Syntax notation and conventions used in Uppercase input to transactions

this book In general, most CICS-supplied transactions accept only
uppercase input. If UCTRAN=YES has been specified in the
Each command has a syntax box to show you what options terminal definition, all lowercase characters, even those
there are. enclosed within single quotation marks, are translated to
uppercase.
You interpret the syntax by following the arrows from left to
right. The conventions are: If you have to specify UCTRAN=NO for your terminal, you
have to ensure that the group specified for your terminal
Symbol Action refers to a profile that will carry out uppercase translation.
55──┬─A─┬─────5% A set of alternatives—one of which you
├─B─┤ must code. CICS provides a PROFILE definition, DFHCICSP, in the
└─C─┘ DFHSTAND group in the CICS system definition (CSD) file.
A set of alternatives—one of which you This profile is identical to DFHCICST except that it specifies
┌──
─────┐
55───6┬─A─┬┴───5% must code. You may code more than UCTRAN(YES) instead of UCTRAN(NO).
├─B─┤ one of them, in any sequence.
└─C─┘ The new profile is used by the CICS-supplied page retrieval
55──┬───┬─────5% A set of alternatives—one of which you transaction, CSPG. The new profile, together with changes in
├─A─┤ may code. the task-attach routine and the page retrieval program,
├─B─┤ enables CICS to perform uppercase translation at the
└─C─┘
transaction level for BMS paging.
┌──
─────┐ A set of alternatives — any number
55───6┬───┬┴───5% (including none) of which you may code This allows users of terminals that are defined with
├─A─┤ once, in any sequence. uppercase translation switched off to use the page retrieval
├─B─┤
└─C─┘ function without having to enter paging commands in upper
case. Assigning a new profile for CSPG means that all data
┌─A─┐ Alternatives where A is the default.
entered on the retrieval command (defined by the PGRET
55──┼───┼─────5%
└─B─┘ system initialization parameter) and the purge command
(defined by the PGPURGE system initialization parameter) is
55──┤ Name ├──5% Use with the named section in place of its
name.
translated to uppercase.
Name:
├──A─┬───┬─────┤ If a user’s terminal is defined with UCTRAN(YES), the new
└─B─┘ profile has no effect because all terminal input is translated
Punctuation and Code exactly as shown. to uppercase anyway.
uppercase
characters
Lowercase Code your own text, as appropriate (for Terminal operators
characters example, name).
A CICS system makes provision for the following classes of
operators:
Minimum abbreviation of keywords A terminal operator who can use a terminal to perform
In general, the CICS transactions accept as few characters routine transactions that cause application programs to
of a keyword as needed to identify it within the request. For be processed. You can use a small selection of CICS
example, in a CEMT INQUIRE TASK command, you could transactions. For example, you can inquire about, or
use TASK, TAS, or TA to uniquely identify TASK. T alone, change, the status of your own terminal.
however, could be confused with TCLASS, TERMINAL, A supervisory terminal operator who can perform all the
TRACE, or TRANSACTION. duties of a terminal operator, in addition to supervising
other operators within a functional group. Your operator
In the syntax displays on your screen (unless your terminal is security code gives you access to the supervisory
uppercase only), and in most cases in this book, the terminal transaction, CEST, with which you can monitor
minimum permitted abbreviation is given in uppercase and control some of the system resources used by your
characters, the remainder in lowercase. group.
A master terminal operator who can monitor and control
resources in a CICS system. Your operator security
code gives you access to the master terminal
transaction, CEMT, with which you monitor and control
the system resources. Internal security checking may
limit the range of resources under your control.
2 CICS Supplied Transactions

introduction
| $ (the dollar symbol) Your responsibilities can be thought of as a subset of those

of the master terminal operator, and you should be aware of
| In the character sets given in this book, the dollar symbol ($) those functions that are not available to the terminals under
| is used as a national currency symbol and is assumed to be your supervision. You also should be aware of, and
| assigned the EBCDIC code point X'5B'. In some countries a understand, the procedure for changing the status of each
| different currency symbol, for example the pound symbol (£), terminal.
| or the yen symbol (¥), is assigned the same EBCDIC code
| point. In these countries, the appropriate currency symbol You should know the identifiers of all terminals and operators
| should be used instead of the dollar symbol. under your supervision. The terminal identifiers are defined in
one or more CICS terminal list tables (TLTs). Individual TLTs
can be identified by a 1-or 2-character suffix you enter as the
Operator security SUPRID and CLASS(value) keywords of the CEST
transaction.
The transactions you can initiate are defined by your profile
in the external security manager (ESM) database, which is When you use the CEST command for all terminals defined
normally provided when you sign on using the CESN in a TLT, you have to specify the SUPRID keyword followed
transaction. by the 2-character identifier of that TLT.
Generally, the master terminal operator has access to all A subset of those terminals can be grouped together as a
CICS-supplied transactions, the supervisory terminal operator class, and can be defined as such in a different TLT. (For
has access to a subset, and the terminal operator has information about defining the TLT itself, see the CICS
access to very few transactions. Resource Definition Guide.) You can specify that class by
means of the CLASS(value) keyword of the CEST SET
The system programmer is responsible for allocating operator TERMINAL command, where ‘value’ is the suffix that
security codes to restrict the use of particular transactions. identifies the TLT in which the class of terminals has been
For more information, see the relevant system administration defined.
guide for the ESM you are using. For example, if you are
using RACF, see the Resource Access Control Facility Alternatively, you can name one or more terminals in the
(RACF): Security Administrator’s Guide. CEST SET TERMINAL(value) command itself.
If you frequently want to restrict a CEST command to a

Terminal operator subset of your terminals, and have defined another TLT
identifying that subset, you then have to use the CEST SET
To operate the system, you normally first sign on to the
TERMINAL SUPRID(value) keyword to refer to the “main”
system and, as a minimum, enter your user ID and your
TLT, followed by the CLASS(value) keyword to refer to the
password.
specific TLT containing the subset.
During signon, the information you enter is used by CICS to
So, for example, if you have defined terminals S202, S203,
establish priorities and your ESM profile for the transactions
S204, and S205 in DFHTLTAB and you want to issue a
that you may want to use later. When you have signed on,
CEST command that sets all those terminals out of service,
you have access to those transactions defined in your ESM
you issue the following command:
profile.
CEST SET TERMINAL SUPRID(AB) OUTSERVICE
After you have signed on, you can enter only specific
If, on the other hand, you want to restrict your command(s)
transaction identifiers. Be aware of error messages that
to terminals S202 and S204, for example, you could define
might be generated by the transactions you start, and the
these two terminals in another TLT—DFHTLTCD, say—and
corrective action that you must take. In addition to error
issue the following command:
messages, be aware of other messages that CICS might
transmit to your terminal. CEST SET TERMINAL SUPRID(AB) CLASS(CD) OUTSERVICE
Alternatively, of course, you could issue the following
You need to know the terminal identifiers of other terminals command:
with which you want to communicate.
CEST SET TERMINAL(S2ð2,S2ð4) SUPRID(AB) OUTSERVICE
Supervisory terminal operator Unless otherwise stated, the information in this book about
the supervisory terminal and the CEST transaction applies
A supervisory terminal operator is the supervisor of any part only to a single CICS system, regardless of whether it is
of the system for which group control is desired. You are connected to another CICS system through ISC or MRO.
responsible for supervising, and keeping operational, groups
of terminals defined in one or more terminal list tables
(TLTs). You do this using the supervisory terminal
transaction, CEST.
Chapter 1. Transactions supplied by CICS 3

introduction
Master terminal operator When the system has satisfactorily completed its response to
a command, the time and date are printed or displayed at
The master terminal operator controls system components your terminal, as follows:
using the master terminal transaction, CEMT. With this TIME=hh.mm.ss DATE=mm.dd.yy
transaction, the master terminal operator can dynamically
change the system control parameters. where time is in hours, minutes, and seconds, and date is in
months, days, and years, or in the form specified by the
Although the transaction can be started at any valid IBM DATFORM system initialization parameter. For brevity this
3270 family display device or equivalent terminal, or from the final message has been deleted from all examples in the
operating system console, its use is intended to be limited to remainder of the book.
a person known as the master terminal operator. Starting a
transaction from the operating system console is described in Unless otherwise stated, the information about the master
“The system console as a CICS terminal” on page 5. terminal and its transactions given in this book applies only
to a single CICS system, regardless of whether it is
The control permitted through CEMT allows you, the master connected to another CICS system through ISC or MRO.
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 MRO and ISC support
responsibility for administering the terminal facilities of the
system. Multiregion operation (MRO) and intersystem communication
(ISC) allow the sharing of resources between more than one
By using the routing transaction (CRTE), you can also be a CICS region. Thus a user at a terminal assigned to one
master terminal operator for multiple connected CICS CICS region can run transactions in connected regions, and
systems. can access resources—files, for example—in other regions.
As the master terminal operator, you can access all terminal It is also possible for a transaction running in one region to
and supervisory terminal transactions. In addition, however, communicate with a transaction running in another region,
you must be familiar with all the procedures associated thus sharing the processing workload.
exclusively with the master terminal. You must be aware of
which terminals and operators can access CICS at any given Except for experiencing longer response times, you should
time, and of the identifiers by which they are known to CICS. not be aware that MRO or ISC processes are being used.
For example, when inquiring about terminals, you can specify

a class of terminals or a list of terminals. A class of terminals BMS partitions
is specified by the CLASS(value) keyword, where ‘value’ is
the 1-or 2-character suffix of the related terminal list table When you use display devices that support BMS partitions,
(DFHTLTxx). A list of terminals is specified by a series of make sure that you understand:
terminal identifiers following the CEMT SET
How to use the SCROLL, PARTITION JUMP, CLEAR,
TERMINAL(t1,t2,...,) command, where t1, t2, are terminal
and CLEAR PARTITION keys
identifiers. See “List of resource identifiers” on page 47 for
more information. The concept of the active partition
The meanings of the partition-related indicator symbols
For MRO and LUTYPE6.1 connections, you must know the
that can appear on a display screen.
identifier of each parallel session, and specify this identifier
when operating on the session. For information about BMS partitions, see the CICS
Application Programming Guide.
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. CLEAR key
Your use of the master terminal transaction is restricted by The CLEAR key clears all partitions from the display, and
entries in the signon table and in the installed transaction sets the terminal to ‘base’ state. The next BMS output
definitions. These entries are the responsibility of the system request recreates the partitions (but does not restore their
programmer. contents), using the application partition set.
During long periods of continuous operation, you can, at The CLEAR and CLEAR PARTITION keys cannot be used
intervals, read out and reset the statistics counters. The interchangeably when an existing CICS transaction is run in
volume of activity in your system determines how often you a single explicit partition.
should do this.

introduction
Partitions and the execution diagnostic is redisplayed in each partition in the following
circumstances:
facility
For the initial display when the BMS paging program is
The execution diagnostic facility (EDF), invoked by CEDF, is first invoked
not available in single-screen mode on a terminal in
Following erasure of the terminal partition set caused by
partitioned state. EDF must be used in dual-screen mode for
pressing the CLEAR key
debugging application programs that use partitions.
Following page retrieval for a different page-chaining
level
Partitions and the command interpreter
Following page purge for a different page-chaining level.
The CICS command interpreter, invoked by CECI or CECS,
cannot be used to process commands that refer to partitions.
This is because the command interpreter display cannot be
Copying pages
restored after the screen has been partitioned. BMS page copy operates on a partition basis (not a screen
or partition set basis). BMS page copy copies a page from a
PA1 print key partition to any terminal in ‘base’ state. You cannot copy a
page from a partition to another partition on the same or
The PA1 print key is not supported from a terminal in another terminal.
partitioned state.
Message termination
Routing and multiple partitions
When you terminate a message, the entire logical message
Routed messages can be directed to a terminal, including the (that is, all pages in all partitions) is purged, irrespective of
transaction terminal, which supports partitions. However, the partition in which you entered the purge command.
such messages reset the terminal to ‘base’ state.
The response to a page query request is displayed on a
cleared, unpartitioned screen.
Terminal paging
When a BMS logical message is saved in CICS temporary Error messages
storage, CICS also saves the application partition set. This
partition set is loaded onto the target terminal before any Most error messages relating to invalid paging commands
pages are delivered. CICS builds a separate page for each are displayed with an erase or write in the partition in which
partition, and overflow occurs on a partition basis. you entered the command. Other error messages unrelated
to any particular partition (such as those relating to invalid
message identifiers) are displayed on a cleared unpartitioned
Page retrieval screen.
Terminal-operator page-retrieval commands operate on a

partition basis. When a page-retrieval or page-copy
command is entered in a partition, it implicitly refers to pages
The system console as a CICS terminal
in that partition. If single-keystroke retrieval is used, the
Console support makes it possible for a terminal to be both
retrieval command applies to the partition containing the
an operating system console and a CICS master terminal.
cursor when the PF key is pressed. The first page for a
partition is displayed initially in the viewport. If multiple console support (MCS) is in use, you can define
each console to CICS as a separate terminal, and all
Message chaining consoles can communicate with CICS simultaneously.
CICS retains a current partition for each level of page You can use any operating system console as a CICS
chaining. This is initially the default partition for that partition terminal if it has been specified as such on the CONSOLE
set. Page-retrieval commands entered on a cleared screen, keyword of the CEDA DEFINE TERMINAL command. If this
or page-retrieval commands for a chaining level other than has not been done, you get the following message when you
the one being displayed, refer to the current partition for the try to use the console:
target chaining level. The current partition is reset to the DFHAC2ð15 This console has not been defined to CICS.
partition in which the last terminal-operator command was and your input is ignored.
entered.
All consoles that have been defined as CICS terminals can
CICS retains the current page for each partition in the use automatic transaction initiation (ATI), and can receive
partition set. This is initially the first page. The current page

introduction
messages from other terminals and consoles, as well as from MODIFY command
CICS transactions.
You start a CICS transaction from a console by using the
In a system that has consoles and VTAM terminals, a MODIFY command, as follows:
console can remain active when CICS and VTAM are
MODIFY ident,datastring
disconnected from each other. You can use the console to
make or break the CICS-VTAM connection without CICS You can abbreviate the MODIFY command to F.
being terminated.
ident can be any of the following:
Use the MODIFY and REPLY commands to start the
CICS-supplied transactions from an operating system The name of the job used to start CICS, when it is
console. started by a job stream.
The name of the procedure used to start CICS, when it
In addition to the MODIFY and REPLY commands, the is started by an MVS START command, for example:
system programmer should consider use of the CONTROL,
DISPLAY, START, and VARY commands when preparing START procedure_name
console operator procedures. For information on these where “procedure_name” is the ident value.
commands and other system details, see the OS/390 MVS
The task identifier that was used to qualify the procedure
System Commands manual.
name, for example:
START procedure_name.taskid
Rules for console entry
where “taskid” is the ident value. This is likely to be used
Commands typed at a console are translated to uppercase, where the same procedure is started more than once.
except for characters enclosed within single quotation marks
(' '), which remain unchanged. The occurrence of a literal datastring is a string of data, starting with a CICS
single quotation mark must be indicated by a pair of single transaction identifier.
quotation marks (''), for example:
For example, to start transaction CEBT on the CICSA system
'Please phone Mr O''Neill'. from the console, type:
MODIFY CICSA,CEBT PERFORM TAKEOVER
If UCTRAN=YES has been specified in the terminal
definition, all lowercase characters, even those enclosed You can type more than one MODIFY command at a
within single quotation marks, are translated to uppercase. console; each is processed in order of entry.
A CICS transaction can issue terminal control READ,

WRITE, or CONVERSE commands to communicate with a
console operator. WRITE and CONVERSE transmit
application program messages, but READ simply produces a
prompt, incorporating message ‘DFH4200A’, as follows:
@nn DFH42ððA jjjjjjjj tttt
where:
nn is the number (generated by the operating
system) that you must use in your reply to the
prompt. Messages from a transaction that uses
CONVERSE commands also contain this
number.
jjjjjjjj is the jobname of CICS in the operating system.
tttt is the transaction identifier of the CICS
transaction that has issued the READ command.
REPLY command
You (the console operator) must respond to each prompt by
using the REPLY command, which you can type at either the
prompted console or the master console:
R[EPLY] nn,datastring

introduction
where nn is the number of the prompt to which you are

replying, and datastring is your reply. Time sharing option (TSO) consoles
If a transaction is purged while it is awaiting a reply from the A TSO session can be used to input CICS commands. This
operator, the reply is canceled. has several advantages:
It removes the MVS limitation of 99 consoles.
You should note that messages to the console can become
interspersed with messages from the operating system and It supports additional device types, such as the IBM
from other regions, making them difficult to read. In extreme 3290.
cases, parts of lengthy messages can ‘scroll off’ the console It supports remote operation.
screen before they have been read.
The console ID is 4 bytes, only one of which is used for
locally connected consoles. TSO and JES3 consoles use all
Example of a conversation using 4 bytes. In addition, each console in a sysplex has an 8-byte
CONVERSE name.
modify jobðð2,serv .1/
@17 FAULT TYPE? .2/
r 17,elec .3/
MESSAGE HAS BEEN SENT
.1/ MODIFY command specifying that transaction “serv” is to

be started; this transaction sends messages to service
groups supporting the installation.
.2/ The transaction response produced by a CONVERSE

command and relayed by the operating system.
.3/ Your reply that the fault is an electrical one.
Example of a conversation using

WRITE/READ
modify jobðð2,usid .1/
USER SIGNON ID=? .2/
@25 DFH42ððA JOBðð2 USID .3/
r 25,accts1 .4/
USER'S NAME: J. SMITH .5/

USER'S TEL. NO.: 88999 .6/
.1/ MODIFY command specifying that transaction “usid” is to

be started. This transaction provides information about the
user identified by “usid”.
.2/ Application-program message produced by a WRITE

command.
.3/ System message produced by a READ command.
.4/ Your reply.
.5/ Transaction message, produced by a WRITE command,

giving the requested information. No reply is needed.
.6/ Another transaction message, produced by a WRITE

command, giving more requested information. Again, no
reply is needed.

introduction

CBAM—BTS browser
| Chapter 2. CBAM—BTS browser

| Use CBAM to browse the CICS business transaction
| services (BTS) objects (process-types, processes, activities,
| containers, events and timers) known to this region. CBAM is
| described in the CICS Business Transaction Services
| manual.

CBAM—BTS browser

CDBC—database control menu
Chapter 3. CDBC—database control menu

Use CDBC to connect CICS to DBCTL, or to disconnect You should get the following message:
CICS from DBCTL. CDBC is applicable only to CICS DFHDB82ð7D DBCTL Connection requested. Press PF5
systems using the IMS/ESA Database Control (DBCTL) to confirm.
interface. For detailed guidance on using the CDBC
transaction with databases controlled by DBCTL, see the If you want to proceed with the CICS-DBCTL connection,
CICS IMS Database Control Guide. press PF5 as requested on the display. The “status” line of
the display is then updated. (You can find out the current
You can start CDBC from any terminal, from a card status of the connection at any time by pressing PF2, which
| reader/line printer (CRLP) or DASD sequential terminal, or refreshes the display.)
| from the operating system console.
This display also shows you the application identifier of the
There are two ways of commencing this transaction: CICS system (in this case, DBDCCICS), and the identifier of
Type the identifier, CDBC, on the command line of your the DBCTL system to which CICS is connected. The DBCTL
display, followed by the required keyword, which can be identifier is available only when the connection has been
either: made. You can also see the suffix of the startup table for this
connection.
CDBC CONnect [SUFfix(startup)]
where startup is a two-digit startup table suffix, or: The following display shows you the effect of asking for
CDBC DISconnect [IMMediate] option 1:
Type the identifier, CDBC, on the command line of your

display, and press the ENTER key. You get the following
display:
à CDBC CICS-DBCTL CONNECTION/DISCONNECTION 93.259
ð
13:33:59
Select one of the following:
1 Connection
ð 2 ORDERLY disconnection
3 IMMEDIATE disconnection
13:33:2ð
Select one of the following: Option Selection ==> 1

Startup Table Suffix ==> ðð
1 Connection DBCTL ID Override ==>
2 ORDERLY disconnection
3 IMMEDIATE disconnection DFHDB82ð7D Connection to DBCTL requested. Press PF5 to confirm.
Status of the Interface: DFHDB829ðI DBCTL not connected to CICS.

Option Selection ==> CICS APPLID: IYAHZCD2
Startup Table Suffix ==> ðð DBCTL ID:
DBCTL ID Override ==> Startup Table Suffix:
PF1 = Help 2 = Refresh 3 = End

Status of the Interface: DFHDB829ðI DBCTL not connected to CICS.
CICS APPLID: IYAHZCD2
DBCTL ID:
á ñ
Startup Table Suffix:
Figure 2. CDBC transaction: option 1 screen

á ñ
Figure 1. CDBC transaction: initial screen Disconnecting CICS from DBCTL
As you can see from this display, you can select a To disconnect CICS from DBCTL, you can:
CICS-DBCTL connection, an orderly disconnection, or
an immediate disconnection. 1. Type
CDBC DISConnect [IMMediate]
or
Connecting CICS to DBCTL
2. Choose either option 2 or option 3 of the CDBC panel.
You can connect CICS to DBCTL by:
Option 2 gives you an orderly disconnection. An orderly
1. Typing CDBC CONnect [SUFFIX(xx)], or disconnection allows all existing CICS-DBCTL tasks to be
2. Typing ‘1’ in the Option Selection field indicated by ==>. completed before CICS is disconnected from DBCTL.
You can also specify a startup table suffix in the Startup
Table Suffix field. If you leave this field blank you get the
existing suffix, if one exists.

CDBC—database control menu
The following display shows you the effect of asking for

option 2:

ð
13:39:2ð
Select one of the following:
1 Connection
2 ORDERLY disconnection
3 IMMEDIATE disconnection
Option Selection ==> 2

Startup Table Suffix ==> ðð
DBCTL ID Override ==>
DFHDB82ð9D DBCTL orderly disconnection requested. Press PF5 to confirm.
Status of the Interface: DFHDB8293I DBCTL connected and ready.

CICS APPLID: IYAHZCD2
DBCTL ID: SYS2
Startup Table Suffix: ðð
á ñ
Figure 3. CDBC transaction: option 2 screen
Option 3 gives you an immediate disconnection. This allows

only current DL/I requests to DBCTL from this CICS system
to be completed before CICS is disconnected from DBCTL.
Specifying a DBCTL system identifier

(DBCTLID)
A field on the CDBC panel enables you to use the CDBC
transaction to specify a DBCTLID to override the one in the
DRA startup table. The syntax for connection to DBCTL via
CDBC is:
CDBC CONNECT [SUFFIX(xx)] [DBCTLID(yyyy)]
For more details on using CDBC, see the CICS IMS

Database Control Guide.
The HELP panel

If you press the help key (PF1), the following panel is
displayed:
à HELP : CICS-DBCTL CONNECTION/DISCONNECTION

ð
To CONNECT to DBCTL, select option 1. You can also specify a startup
table suffix, or accept the existing suffix. The id of the DBCTL system is
obtained from the startup table, but can be optionally overridden.
To DISCONNECT from DBCTL, select option 2 or option 3.
Select option 2 for ORDERLY disconnection: this allows all CICS-DBCTL

transactions from this CICS to complete before disconnecting from DBCTL.
Select option 3 for IMMEDIATE disconnection: this allows all CICS-DBCTL

requests from this CICS to complete before disconnecting from DBCTL.
------------------------------------------------------------------------------
Displayed information (press PF2 to refresh the information):
STATUS OF THE INTERFACE The current status of the connection to DBCTL.
CICS APPLID The application identifier for this CICS system.
Displayed when available:

DBCTL ID Identifier of the DBCTL system with which this
CICS system is communicating.
STARTUP TABLE SUFFIX Suffix used when CICS was connected to DBCTL.
PRESS ENTER TO RETURN TO SELECTION SCREEN
á ñ
Figure 4. CDBC transaction: the HELP panel

CDBI–database control inquiry
Chapter 4. CDBI—database control inquiry

Use CDBI to inquire about the status of the interface
between CICS and DBCTL. You can start CDBI from 3270
The HELP panel
(and 3270-like) terminals or from the operating system
If you press the help key (PF1), you get the following display:
console.
For detailed information about the CICS-DBCTL interface

and guidance on using the CDBI transaction with databases à HELP : CICS-DBCTL INTERFACE INQUIRY
ð
controlled by DBCTL, see the CICS IMS Database Control The CICS-DBCTL interface inquiry screen shows:
Guide. STATUS OF THE INTERFACE The status can be:
DFHDB829ðI DBCTL not connected to CICS.

DFHDB8291I DBCTL connect phase 1 in progress.
Start the transaction by typing the identifier, CDBI, on the DFHDB8292I DBCTL connect phase 2 in progress.
DFHDB8293I DBCTL connected and ready.
command line of your display, and press the ENTER key. DFHDB8294I DBCTL orderly disconnect in progress.
DFHDB8295I DBCTL immediate disconnect in progress.
You get the following display: DFHDB8296I DBCTL cannot be connected to CICS.
CICS APPLID The application identifier of this CICS system.
Displayed when available:
DBCTL ID The identifier of the DBCTL system with which this CICS
is communicating
à CDBI CICS-DBCTL INTERFACE INQUIRY 91.184

ð You can press PF2 to update (refresh) the information shown on screen.
11:23:5ð PRESS ENTER TO RETURN TO INQUIRY SCREEN
á ñ
Status : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
CICS APPLID: DBDCCICS Figure 6. CDBI transaction: the HELP panel
DBCTL ID : SYS1
á ñ
Figure 5. CDBI transaction: initial screen
This display tells you the current status of the CICS-DBCTL

connection, which can be one of the following:
DFHDB829ðI DBCTL not connected to CICS.
DFHDB8293I DBCTL connected and ready.
DFHDB8294I DBCTL orderly disconnect in progress.
DFHDB8295I DBCTL immediate disconnect in progress.
DFHDB8296I DBCTL cannot be connected to CICS.
The display also shows you the application identifier of the

CICS system (in this case, DBDCCICS), and the identifier of
the DBCTL system to which CICS is connected.

CDBI–database control inquiry

CDBM–database control interface
Chapter 5. CDBM—database control interface

Use the CDBM transaction to issue DBCTL operator
commands from a CICS terminal. CDBM is applicable only to à CDBM CICS-DBCTL Operator Transaction 98.135
ð
13:24:2ð
CICS systems using the IMS/ESA Database Control
Type IMS command.
(DBCTL) interface. ____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
| CDBM also provides a means of maintaining a command file
| which stores commands. You may store commands for any For /DBDUMP or /DBRECOVER commands
| reason, but repeated re-use is likely to be a frequent Choose one. 1 1. Do not force end of volume
2. Force end of volume
| purpose. These stored commands may include more
| databases than the operator transaction panel has space for. Press enter to display responses.
CICS APPLID DBDCCICS

To use CDBM you must: DBCTL ID SYS3
1. Have a DBCTL system running IMS/ESA 5.1 or later | F1=Help F2=Maintenance F3=Exit F5=Refresh F12=Cancel
| 2. DBCTL must have the AOIS parameter set to a value á ñ

| other than N. If values A, C or R are used, appropriate
| security controls must be used to allow the CICS-DBCTL Figure 7. CICS-DBCTL operator transaction
| interface to operate.
| On this panel you can enter a DBCTL command, for
3. Generate and add to the DBCTL system, a PSB named
| example:
DFHDBMP.
| /DISPLAY DB ALL
| or a group command, for example:
Syntax | /GROUP SAMPLE STA
The syntax of the CDBM transaction is:
| An example of the use of a /GROUP command from the
CDBM /DBCTL operator command | CICS-DBCTL Operator Transaction screen is shown in
where / is the default command recognition character | Figure 8.
(CRC) for DBCTL. Note that, in this case, the default
CRC is the one that must be used.
Note: IMS requires that each command be prefixed à CDBM CICS-DBCTL Operator Transaction 98.135
ð
13:24:2ð
with the default CRC. The CRC is present only
Type IMS command.
for syntax checking reasons; it does not /GROUP SAMPLE STA___________________________________________
____________________________________________________________
determine the DBCTL to which the command is ____________________________________________________________
____________________________________________________________
sent. You cannot use a CRC value to route a
command to a particular DBCTL system through For /DBDUMP or /DBRECOVER commands
CDBM - it can only be sent to the one currently Choose one. 1 1. Do not force end of volume
connected to CICS. This DBCTL may have its
Press enter to display responses.
own CRC value which is different from the
default one of /. This does not matter to CDBM CICS APPLID DBDCCICS
DBCTL ID SYS3
however, because the / character is used only for
syntax checking, and the command is presented F1=Help F2=Maintenance F3=Exit F5=Refresh F12=Cancel
to the connected DBCTL without a CRC, using á ñ

the AIB interface.
Figure 8. CICS-DBCTL operator transaction panel showing a
| You can enter a DBCTL command, for example: GROUP command
| CDBM /DISPLAY DB DEPT\
| Note: The group command SAMPLE STA referred to in this
| or a group command, for example:
| panel can be found in the “DFHDBFK - The CDBM
| CDBM /GROUP SAMPLE STO | GROUP command file” on page 16.
| in this way.
| Responses to commands issued using CDBM are returned in
You can also start the transaction by typing the identifier, a screen like the one shown in Figure 9 on page 16, which
CDBM, on the command line of your display, as follows: shows the first of a number of screens issued in response to
CDBM a /DISPLAY DB ALL command.
Press the ENTER key. You get the panel shown in
Figure 7.

| field length content description

à CDBM CICS-DBCTL IMS Responses Screen 1
ð
Responses 1 to 18
More: +
| 1 12 Group a 12-character field containing
DATABASE TYPE TOTAL UNUSED TOTAL UNUSED ACC CONDITIONS | your chosen name for this group.
ACCUNTDB UP STOPPED, NOTOPEN, NOTINIT
ADMIDX1 UP STOPPED, NOTOPEN, NOTINIT | The acceptable characters are
ADMOBJ1 UP STOPPED, NOTOPEN, NOTINIT
ADMOBJ2 UP STOPPED, NOTOPEN, NOTINIT | A-Z 0-9 $ @ and #. Leading or
ADMOBJ3 UP STOPPED, NOTOPEN, NOTINIT
ADMSYSDF UP STOPPED, NOTOPEN, NOTINIT | embedded blanks are not
BE1CHKPT DL/I UP NOTOPEN
BE1PARTA UP STOPPED, NOTOPEN, NOTINIT | allowed, but trailing blanks are
BE1PARTB
BE1PARTC
UP
UP
STOPPED, NOTOPEN,
STOPPED, NOTOPEN,
NOTINIT
NOTINIT | acceptable.
BE1PARTS UP STOPPED, NOTOPEN, NOTINIT
BE2ORDER
BE2ORDRX
DL/I
DL/I
UP
UP
NOTOPEN
NOTOPEN
| 2 10 IMS a 10-character field containing
BE2PARTS
BE2PCUST
DL/I
DL/I
UP
UP
NOTOPEN
NOTOPEN
| Command any of the IMS command verbs
BE3ORDER DL/I UP NOTOPEN | that are valid for CDBM (see the
BE3ORDRX DL/I UP NOTOPEN
More... | CICS IMS Database Control
F1=Help F3=Exit F4=Top F6=Bottom F7=Bkwd F8=Fwd F9=Retrieve F12=Cancel | Guide for details). Leading or
á ñ | embedded blanks are not
| allowed, but trailing blanks are
Figure 9. CICS-DBCTL IMS responses | acceptable.
| Note: The validity of the IMS
| command verb is not
| checked by CDBM.
| DFHDBFK - The CDBM GROUP command | Invalid values will be
| file | reported by IMS when
| the command is
| Before you can use the /GROUP command CDBM requires a | attempted.
| file in which all your predefined commands can be stored. | 3 1406 IMS Up to 1406 characters of
| This file, DFHDBFK, is the CDBM GROUP command file. It | Command parameters appropriate to the
| is a VSAM KSDS. | parameters chosen IMS command verb.
| (This will often consist of lists of
| The DFHDBFK file is not required until you first attempt to | databases.)
| use the /GROUP command. | Note: Wildcard characters may
| not be used in the
| Sample JCL to enable you to define this file and optionally to | parameters stored in the
| place some of your group definitions within it is provided in | CDBM Group command
| the CICS System Definition Guide. The example given there | file. This is unlike the
| also shows you how to batch load this file if you want to do | other functions of the
| so. | CDBM transaction which
| permit the use of
| You may load many definitions in this way, or load none. You | wildcard characters to
| may use whatever means you prefer to define this file and | describe multiple similarly
| and to maintain its content. One method of maintainting the | named databases.
| content once the file is defined is provided by CDBM which
| offers a Maintenance function for the DFHDBFK file.
| The MAINTENANCE panel for DFHDBFK
| To use the the /GROUP command functions of the CDBM
| transaction, add the data set name of the group command | If you press the Maintenance key (PF2) on the main CDBM
| file to the definition of the DFHDBFK file within the | panel, you get the panel shown in Figure 10 on page 17.
| DFHDBCTL group. For information about how to do this, see
| the CICS Resource Definition Guide manual.
| Record layout in the CDBM GROUP

| command file
| Each record in the DFHDBFK file may be up to 1428
| characters long, as follows:

| D Delete
|
| à CDBM CICS/DBCTL COMMAND GROUP MAINTENANCE
ð | Delete a record from the DFHDBFK file. A Delete must
| _ ACTION A add B browse D delete R read U update
| ____________ GROUP __________ IMS COMMAND
| be immediately preceded by a Read to lock the required
| > <
| > <
| record.
| > <
| > <
| > <
| > < | R Read
| > <
| > <
| > < | Read displays a specific record. Unlike Browse it does
| > <
| > < | not operate on partial, or absent keys, and does not
| > <
| > < | present the next record when you press ENTER.
| > <
| > <
| > < | Read is required before those actions (Delete and
| > <
| > <
| Update) which change an existing record. It locks that
| > <
| F1=Help F3=Exit F12=Cancel | record against the possibility of being changed by

| á ñ | another operator. This action also serves to help you
| confirm that the correct record has been selected.
| Figure 10. CICS-DBCTL Group Maintenance panel | A lock is released by exiting the CDBM maintenance
| panel, or by your next CDBM Maintenance action
| Input fields | (whether that is the Update or Delete you had
| contemplated, or something different entirely).
| The input fields are:
| U Update
| Action
| Update a record in the DFHDBFK file. An Update must
| Group | be immediately preceded by a Read to lock the required
| IMS Command | record.
| IMS Command parameters | You cannot update the key fields (GROUP and IMS
| (between the > < marks). | COMMAND).
| Note: Use Add to create a new key.
| Group, IMS Command and IMS Command parameters are
| described in the section “Record layout in the CDBM | Note: In the descriptions above, Key refers to the 22
| GROUP command file” on page 16 | characters at the beginning of each record in the
| DFHDBFK file (namely the GROUP and IMS
| The Action field will accept one of the following:
| COMMAND).
| A Add
| Add a new record to the DFHDBFK file. If the key
| already exists, the Add fails. The CICS-DBCTL interface
| Note: To Add a record that is very similar to an existing For detailed information about the CICS-DBCTL interface
| record, but which has a different key, you may and guidance on using the CDBM transaction with databases
| find it helpful to Read the existing record, modify controlled using DBCTL, see the CICS IMS Database Control
| the displayed fields, and then Add this new Guide.
| record.
| B Browse
The HELP panels
| Displays the contents of the command file, record by
| record. Specify any key (or none) to indicate where you | If you press the help key (PF1) from the CICS-DBCTL
| want the browse to start. Each time you press ENTER, | Operator Transaction panel, you get the panel shown in
| Browse moves on to the next record. At the end of the Figure 11 on page 18.
| file you will be prompted to wrap around to the start of
| the file. You can accept this or not as you prefer.
| Incomplete keys, and unknown keys are also acceptable
| as start points. If no key is provided, the browse starts at
| the first record in the file.
| If you have used Browse to locate a specific record for
| deletion or for update, remember to use Read before
| either Delete or Update.
Chapter 5. Database control interface CDBM 17

à CDBM Help: CICS-DBCTL Operator Transaction

ð
CDBM Use the transaction to send an IMS command to a DBCTL system.
Command Type the command recognition character / followed by an IMS

command and press enter to display responses.
Responses Use the PF keys to page IMS responses.
Wildcards \ or + can be used within one database name.
End of volume For /DBDUMP or /DBRECOVER commands only

Choose one.
1. Do not force end of volume
CICS APPLID
DBCTL ID These are shown for information.
Maintenance Enter the group command maintenance screen.
Example /DIS DB DEPT\ displays the status of several databases.
F3=Exit F12=Cancel
á ñ
Figure 11. CICS-DBCTL operator transaction help panel
| If you press the help key (PF1) from the CICS-DBCTL

| Maintenance panel, you get the panel shown in Figure 12.
|
| à CDBM Help: CICS-DBCTL Operator Transaction
ð
| Maintenance Store commands for issuing from the CDBM screen.
| GROUP Enter the group you want to store a command in.
| IMS COMMAND Enter a valid IMS command to execute with the supplied data.
| ACTION A - Add a command to the command file.

| B - Browse the contents of the command file.
| D - Delete a command, only after it has been read.
| R - Read a command from the file.
| U - Update a command, only after it has been read.
| Issue commands from the main screen in the format

| /GROUP group command.
| Example /GROUP SAMPLE DIS shows information for the databases in SAMPLE.
| F3=Exit F12=Cancel
| á ñ
| Figure 12. CICS-DBCTL Maintenance help panel

CEBR—temporary storage browse
Chapter 6. CEBR—temporary storage browse

Use the CEBR transaction to browse temporary storage invoking CEBR without a queue name or from an EDF
queues and to delete them. session at terminal S21A is shown in Figure 14.
You can also use CEBR to transfer a transient data queue to

temporary storage in order to look at its contents, and to
recreate the transient data queue when you have finished.
The CEBR commands that perform these transfers allow you
to create and delete transient data queues as well.
| Remember that:
| browsing of Temporary Storage queues retrieves the
| next record, following whichever record has most
| recently been retrieved by ANY active task.
| This is can lead to confusion if for example an EXEC
| CICS READQ NEXT and a CEBR transaction attempt to
| work with the same Temporary Storage queue at the
| same time.
| transient data queue reads are destructive. If you read a
| transient data queue that is being used on an active
| system by applications, this is likely to cause problems.
You start the CEBR transaction by entering the transaction

identifier CEBR, followed by the name of the queue you want
to browse. For example, to display the temporary storage
queue named CEBRS209, you enter:
CEBR CEBRS2ð9
CICS responds with a display of the queue, a sample of

which is shown in Figure 13:
à ð
CEBR TSQ AXBYQUEUENAME1 SYSID CIJP REC 1 OF 3 COL 1 OF 5
ENTER COMMAND ===>
\\\\\\\\\\\\\\\\\\\\\\\\\\ TOP OF QUEUE \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
ðððð1 HELLO
ðððð2 HELLO
ðððð3 HELLO
\\\\\\\\\\\\\\\\\\\\\\\\\ BOTTOM OF QUEUE \\\\\\\\\\\\\\\\\\\\\\\\\\\\\
PF1 : HELP PF2 : SWITCH HEX/CHAR PF3 : TERMINATE BROWSE

PF4 : VIEW TOP PF5 : VIEW BOTTOM PF6 : REPEAT LAST FIND
PF7 : SCROLL BACK HALF PF8 : SCROLL FORWARD HALF PF9 : UNDEFINED
PF1ð: SCROLL BACK FULL PF11: SCROLL FORWARD FULL PF12: UNDEFINED
á ñ
Figure 13. Typical CEBR screen displaying temporary storage
queue contents
Alternatively, you can start the CEBR transaction from CEDF.

You do this by pressing PF5 from the initial CEDF screen
(see Figure 35 on page 41) which takes you to the
working-storage screen, and then you press PF2 from that
screen to browse temporary storage (that is, you invoke
CEBR). CEBR responds by displaying the temporary storage
queue whose name consists of the four letters ‘CEBR’
followed by the four letters of your terminal identifier. (CICS
uses this same default queue name if you invoke CEBR
directly and do not supply a queue name.) The result of

CEBR—temporary storage browse
If you enter CEBR from CEDF, you will return to the EDF
panel when you press PF3 from the CEBR screen.
à CEBR TSQ AXBYQUEUEAME1 SYSID CIJP REC 1 OF ð COL 1 OF .1/ð

ð
ENTER COMMAND ===> .2/
\\\\\\\\\\\\\\\\\\\\\\\\\\ TOP OF QUEUE \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
\\\\\\\\\\\\\\\\\\\\\\\\\ BOTTOM OF QUEUE \\\\\\\\\\\\\\\\\\\\\\\\\\\\\
.3/
TSQUEUE AXBYQUEUEAME1 DOES NOT EXIST .4/

PF1 : HELP PF2 : SWITCH HEX/CHAR PF3 : TERMINATE BROWSE.5/
PF4 : VIEW TOP PF5 : VIEW BOTTOM PF6 : REPEAT LAST FIND
PF7 : SCROLL BACK HALF PF8 : SCROLL FORWARD HALF PF9 : UNDEFINED
PF1ð: SCROLL BACK FULL PF11: SCROLL FORWARD FULL PF12: UNDEFINED
á ñ
Note: .1/Header .2/Command line .3/Body .4/Message line
.5/Menu of options
Figure 14. Typical CEBR display of default temporary storage queue
For information about the CEBR temporary storage browse

transaction and guidance on using it, see the CICS
Application Programming Guide.
The HELP panel

displayed:
à These commands are available to you (abbreviations in UPPER CASE):

ð
Find /string/ - Keyword optional. Final delimiter optional if
string has no blanks. Any other delimiter is OK.
Line line-number
Column column-number
Top
Bottom
TERMinal terminal-id - Browse temp. storage queue for another terminal.
Queue temp-stg-queue - Browse a named temp. storage queue
(name may be in hex - e.g., X'C134')
Sysid shared/remote sysid - Browse shared or remote temp. storage queue
Put transient-data-queue - Copy current queue into a transient data queue.
Get transient-data-queue - Fetch a transient data queue for browsing.
PURGE - Destroy the current queue.
á ñ

CEBT INQUIRE AUXTRACE
Chapter 7. CEBT—master terminal (alternate CICS)

Use CEBT to control an alternate CICS system in an CEBT INQUIRE AUXTRACE
extended recovery facility (XRF) environment. For information
about XRF, see the CICS/ESA 3.3 XRF Guide. Function: Return information about the status of auxiliary
trace.
You can start this transaction only at the operating system
console. Starting a transaction at the system console is Description: Auxiliary trace entries are made to a pair of
described in “The system console as a CICS terminal” on CICS-controlled BSAM data sets, ‘A’ and ‘B’.
page 5.
CEBT INQUIRE AUXTRACE tells you:
Whether the auxiliary trace data set is open or closed
Minimum abbreviation of keywords
Which of the auxiliary trace data sets is active, Cur(A) or
The CEBT command accepts as few characters of a keyword Cur(B)
as needed to uniquely identify it within the request. An Whether an auxiliary trace is in progress (started) or not
exception to this rule is the SHUTDOWN keyword, for which (stopped).
the minimum abbreviation is SHUT.
For background information about auxiliary tracing, see the
In the syntax displays on your screen and in this book, the CICS Problem Determination Guide.
minimum permitted abbreviation is given in uppercase
characters, and the rest of the keyword in lowercase Input: Press the Clear key and type CEBT INQUIRE
characters. AUXTRACE (the minimum abbreviation is CEBT I AUX).
To change various attributes, use the CEBT SET

CEBT INQUIRE and SET commands AUXTRACE command.
The CEBT INQUIRE and SET commands allow you to query

55──CEBT Inquire Auxtrace──5%
or set:
Auxiliary trace (CEBT INQUIRE|SET AUXTRACE)
The dump data set (CEBT INQUIRE|SET DUMP)
Displayed fields
GTF tracing (CEBT INQUIRE|SET GTFTRACE) All

Automatic switching occurs as necessary until the end of
Internal tracing (CEBT INQUIRE|SET INTTRACE) this CICS session without the need for operator
Surveillance or ‘tracking’ of the active CICS system by intervention.
the alternate CICS system (CEBT INQUIRE|SET
Auxiliary
SURVEILLANCE)
identifies this panel as relating to auxiliary trace.
Takeover from the active CICS system by the alternate
CICS system (CEBT INQUIRE|SET TAKEOVER). Current(A|B)
displays a 1-character identifier of the current auxiliary
Descriptions follow of the CEBT INQUIRE and SET data set, which can be ‘A’ or ‘B’. This value is blank if
commands in alphabetic order of the name of the resource. there is no auxiliary trace data set.
Next
Automatic switching occurs when the current trace data
set is full, but not subsequently.
Noswitch
Switching does not occur without operator intervention.
Pause
Auxiliary tracing has stopped, but the trace data set has
been left open. A subsequent START request causes
trace entries to be written immediately following those
that were written before the PAUSE request.
Start
Auxiliary tracing is in progress.

CEBT INQUIRE DUMP
Stop CEBT INQUIRE DUMP

Auxiliary tracing has stopped.
Switch Function: Retrieve information about the CICS dump data

displays the information that an immediate switch is sets.
being made from the current auxiliary trace data set to
Description: CEBT INQUIRE DUMP tells you which dump
the alternate trace data set.
data set (A or B) is currently open.
For general information about dumps, see the CICS Problem

Determination Guide.
Input: Press the Clear key and type CEBT INQUIRE DUMP
(the minimum abbreviation is CEBT I DU).
To change various attributes, use the CEBT SET DUMP

command.
55──CEBT Inquire Dump──5%
Displayed fields
Autoswitch
The switch occurs only when the active dump data set
is full, but not subsequently.
Closed
The active CICS dump data set is closed.
Currentdds(value)
displays a 1-character indicator as to which of the two
dump data sets is active. This can be A or B.
Dump
indicates that this panel relates to a dump data set
inquiry.
Noautoswitch
When the active dump data set is full, there is not to be
an automatic switch to the inactive dump data set.
Note: Because this is a ‘negative’ attribute, the field
appears blank.
Open
The active CICS dump data set is open.
Switch
The currently active dump data set is to become
inactive, and the currently inactive data set is to become
active.

CEBT INQUIRE GTFTRACE CEBT INQUIRE INTTRACE
CEBT INQUIRE GTFTRACE CEBT INQUIRE INTTRACE

Function: Show the GTF status. Function: Show the status of CICS internal tracing.
Description: CEBT INQUIRE GTFTRACE tells you Description: CEBT INQUIRE INTTRACE tells you
whether CICS tracing to the MVS Generalized Tracing whether CICS internal tracing is in progress.
Facility (GTF) is started or stopped.
This command is intended for use at terminals that do not
This command is intended for use at terminals that do not support the full-screen tracing transaction CETR.
support the CETR full-screen tracing transaction.
Input: Press the Clear key and type CEBT INQUIRE
For information about GTF tracing, see the CICS Problem INTTRACE (the minimum abbreviation is CEBT I IN).
Determination Guide and the CICS Performance Guide.
To change various attributes, use the CEBT SET INTTRACE
Input: Press the Clear key and type CEBT INQUIRE command.
GTFTRACE (the minimum abbreviation is CEBT I G).
To change various attributes, use the CEBT SET 55──CEBT Inquire Inttrace──5%
GTFTRACE command.
Displayed fields
55──CEBT Inquire Gtftrace──5%
Inttrace
indicates that this panel relates to an INTTRACE inquiry.
Displayed fields Start
Gtftrace CICS internal tracing is in progress.
indicates that this panel relates to a GTFTRACE inquiry.
Stopped
Start CICS internal tracing is not in progress.
CICS tracing to the MVS Generalized Tracing Facility
(GTF) is in progress.
Stopped
(GTF) is not in progress.
Chapter 7. Master terminal (alternate CICS) CEBT 23

CEBT INQUIRE SURVEILLANCE CEBT INQUIRE TAKEOVER
CEBT INQUIRE SURVEILLANCE CEBT INQUIRE TAKEOVER

Function: Display whether surveillance (or tracking) of the Function: Display whether any takeover from the active
active CICS system by the alternate CICS system is ON or CICS system by the alternate CICS system is to be
OFF. automatic, manual, or command-driven.
Input: Press the Clear key and type CEBT INQUIRE Input: Press the Clear key and type CEBT INQUIRE
SURVEILLANCE (the minimum abbreviation is CEBT I SU). TAKEOVER (the minimum abbreviation is CEBT I T).
To change various attributes, use the CEBT SET To change various attributes, use the CEBT SET
SURVEILLANCE command. TAKEOVER command.
55──CEBT Inquire Surveillance──5%
For more information about surveillance, see the CICS/ESA

3.3 XRF Guide.

CEBT PERFORM commands CEBT PERFORM SHUTDOWN
CEBT PERFORM commands CEBT PERFORM SHUTDOWN
The CEBT PERFORM commands allow you to: Function: Shut down the alternate CICS system in an
XRF complex.
Shut down the alternate CICS system (CEBT PERFORM
SHUTDOWN) Description: If you enter CEBT PERFORM SHUTDOWN,
Request a dump of the alternate CICS and continue all active system tasks are allowed to finish, and the
processing (CEBT PERFORM SNAP) alternate CICS system signs off normally from the CICS
availability manager (CAVM) data set.
Cause the alternate CICS to take over from the active
CICS (CEBT PERFORM TAKEOVER).
55──CEBT Perform SHutdown──Dump──Immediate──5%
Descriptions follow of the CEBT PERFORM commands in
alphabetic order.
Options
Dump
causes a dynamic storage dump to be produced when
the shutdown is complete.
Immediate
causes the alternate CICS system to be shut down
immediately, terminating all active tasks. The alternate
CICS signs off abnormally from the CAVM data set. This
can cause the primary (active) CICS system to abend if
tasks are still running.

CEBT PERFORM SNAP CEBT PERFORM TAKEOVER
CEBT PERFORM SNAP CEBT PERFORM TAKEOVER

Function: Cause a “snapshot” dump of the alternate CICS Function: The CEBT PERFORM TAKEOVER command
system to be taken while CICS continues to run. initiates a takeover by the alternate CICS system, causing
the active CICS system to sign off abnormally.
All CEBT PERFORM SNAP requests result in an SDUMP on
an MVS SYS1.DUMPnn data set. Syntax
The use of CEBT PERFORM SNAP prevents all other tasks
from running on the alternate system, and could delay 55──CEBT Perform Takeover──Dump──5%
takeover or recovery after takeover.
Syntax Options
Dump
55──CEBT Perform SNap──5% sends a message to the active CICS system requesting
it to take a system dump from the CAVM data set. This
request is not honored if the active CICS fails before the
dump can be taken.

CEBT SET AUXTRACE
CEBT SET AUXTRACE STArt

CICS is to start auxiliary tracing and open the auxiliary
Function: Change auxiliary tracing options. trace data set if it is currently closed.
STOp
Description: You can start, stop, or pause tracing, and
CICS is to stop auxiliary tracing and close the auxiliary
specify that automatic switching of the auxiliary data set is to
trace data set. A subsequent START request causes
occur when needed. You can use the switch option to
new trace entries to be written at the start of the data
change the data set.
set, thereby overwriting the trace entries that were
Instead of using the SET command, you can overtype your written before the STOP request.
changes on the INQUIRE screen after tabbing to the SWitch
appropriate field (see “Overtyping a display” on page 47). specifies that an immediate switch from the current
auxiliary trace data set is to be made to the alternate
For information about using traces, see the CICS Problem
trace data set.
Syntax: Press the Clear key to clear the screen. There are
two ways of commencing this transaction:
Type CEBT SET AUXTRACE (the minimum abbreviation is
CEBT S AUX). You get a display that lists the current
status, similar to that obtained by CEBT INQUIRE
AUXTRACE. You can then tab to the highlighted or
blank fields and overtype them with the required values.
Type CEBT SET AUXTRACE (CEBT S AUX) followed by one
or more attribute settings that you wish to change. For
example, CEBT S AUX STO will stop auxiliary tracing if it is
already running.
55──CEBT Set Auxtrace──┬───────┬───────────────5

├─STArt─┤
├─Pause─┤
└─STOp──┘
5──┬──────────┬──SWitch──5%
├─NOswitch─┤
├─NExt─────┤
└─All──────┘
Options
All
Specifies that automatic switching between the two
auxiliary trace data sets is to occur as necessary until
the end of this CICS session, without the need for
operator intervention.
NExt
Automatic switching of the auxiliary trace data set is to
occur when the current trace data set is full, but not
subsequently.
NOswitch
Switching between the auxiliary trace data sets is not to
occur without operator intervention.
Pause
Auxiliary tracing is to stop, but the data set is to remain
open. A subsequent START request causes trace
entries to be written immediately following those that
were written before the PAUSE request.

CEBT SET DUMP CEBT SET GTFTRACE
CEBT SET DUMP CEBT SET GTFTRACE

Function: Change the attributes of a CICS dump data set. Function: Change the status of GTF tracing
Description: Using CEBT SET DUMP, you can open or Description: CEBT SET GTFTRACE allows you to switch
close the active CICS dump data set, and specify whether or CICS tracing to the MVS Generalized Tracing Facility (GTF)
not the automatic switch to the inactive dump data set is to on and off.
occur when the active dump data set is full. Instead of using
the SET command, you can overtype your changes on the This command is intended for use at terminals that do not
INQUIRE screen after tabbing to the appropriate field (see support the CETR full-screen tracing transaction.
“Overtyping a display” on page 47).
For information about using GTF tracing, see the CICS
For information about using dumps, see the CICS Problem Problem Determination Guide.
Syntax: Press the Clear key to clear the screen. There are two ways of commencing this transaction:
two ways of commencing this transaction: Type CEBT SET GTFTRACE (the minimum abbreviation is
Type CEBT SET DUMP (the minimum abbreviation is CEBT CEBT S G). You get a display that lists the current status,
S DU). You get a display that lists the current status, similar to that obtained by CEBT INQUIRE GTFTRACE.
similar to that obtained by CEBT INQUIRE DUMP. You You can then tab to the highlighted or blank fields and
can then tab to the highlighted or blank fields and overtype them with the required values.
overtype them with the required values. Type CEBT SET GTFTRACE (CEBT S G) followed by one or
Type CEBT SET DUMP (CEBT S DU) followed by one or more attribute settings that you wish to change. For
more attribute settings that you wish to change. For example, CEBT S G STO will stop GTF tracing if it is
example, CEBT S DU A will cause an automatic switch to already running.
the inactive dump data set if ‘noautoswitch’ was
previously specified.
55──CEBT Set Gtftrace──┬───────┬──5%
├─STArt─┤
└─STOp──┘
55──CEBT Set Dump──┬────────┬──────────────────5
├─Open───┤
├─CLosed─┤
└─Switch─┘ Options
5──┬──────────────┬──5% STArt
├─Autoswitch───┤
└─Noautoswitch─┘ CICS tracing to the MVS Generalized Tracing Facility
(GTF) is started.
STOp
Options CICS tracing to the MVS Generalized Tracing Facility
Autoswitch (GTF) is stopped.
is full, but not subsequently.
CLosed
The active CICS dump data set is closed.
Noautoswitch
When the active dump data set is full, there is not to be
an automatic switch to the inactive dump data set.
Open
The active CICS dump data set is opened.
Switch
active.

CEBT SET INTTRACE CEBT SET SURVEILLANCE
CEBT SET INTTRACE CEBT SET SURVEILLANCE

Function: Switch CICS internal tracing on or off. Function: Set surveillance (or tracking) of the active CICS
by the alternate CICS on or off.
Description: This command is intended for use at
terminals that do not support the full-screen tracing Syntax
transaction CETR.
Syntax: Press the Clear key to clear the screen. There are 55──CEBT Set Surveillance──┬─────┬──5%
two ways of commencing this transaction: ├─OFf─┤
└─ON──┘
Type CEBT SET INTTRACE (the minimum abbreviation is
CEBT S IN). You get a display that lists the current
status, similar to that obtained by CEBT INQUIRE Options
INTTRACE. You can then tab to the highlighted or blank
OFf
fields and overtype them with the required values.
Surveillance of the active CICS system by the alternate
Type CEBT SET INTTRACE (CEBT S IN) followed by one or CICS is to be stopped.
more attribute settings that you wish to change. For
example, CEBT S IN STO will stop internal tracing if it is ON
already running. Surveillance of the active CICS system by the alternate
CICS is to be started.
55──CEbt Set Inttrace──┬───────┬──5% For more information about surveillance, see the
├─STArt─┤ CICS/ESA 3.3 XRF Guide.
└─STOp──┘
Options
STArt
CICS internal tracing is started.
STOp
CICS internal tracing is stopped.

CEBT SET TAKEOVER
CEBT SET TAKEOVER The HELP panel

Function: Set takeover from the active CICS system by If you press the help key (PF1), the following panel is
the alternate CICS system to be automatic, manual, or displayed:
command-driven.
two ways of commencing this transaction: à GENERAL HELP INFORMATION
ð
Enter command on the first line and press ENTER (after returning from HELP).
Type CEBT SET TAKEOVER (the minimum abbreviation is Options can be abbreviated to the minimum to make them unique.
? before command gives COMMAND SYNTAX CHECK and prevents execution.
CEBT S T). You get a display that lists the current status, To modify results, position cursor using TAB key, overtype and press ENTER.
? at start of results line gives SYNTAX OF SET COMMAND.
similar to that obtained by CEBT INQUIRE TAKEOVER. PF KEY HELP INFORMATION
You can then tab to the highlighted or blank fields and PFð1 HELP HELP INFORMATION
overtype them with the required values. PFð2
PFð3 END
UNDEFINED
END SESSION
PFð4 UNDEFINED
Type CEBT SET TAKEOVER (CEBT S T) followed by one or PFð5
PFð6
UNDEFINED
UNDEFINED
PFð7 SBH SCROLL BACK HALF
more attribute settings that you wish to change. For PFð8 SFH SCROLL FORWARD HALF
PFð9 MSG MESSAGES
example, CEBT S T M changes takeover to a manual PF1ð SB SCROLL BACK
PF11 SF SCROLL FORWARD
operation if it was previously specified to be automatic. PF12 UNDEFINED
55──CEBT Set Takeover──┬───────────┬──5%

├─Automatic─┤
├─Command───┤ USE ENTER TO RETURN
└─Manual────┘ á ñ
Figure 15. CEBT transaction: the HELP panel
Options
Automatic
Takeover is to occur automatically.
Command
Takeover is to be by command.
Manual
Takeover is to be manual.
The CICS/ESA 3.3 XRF Guide tells you more about these
command options.

CECI/CECS—command-level interpreter
Chapter 8. CECI—command-level interpreter

Use CECI, which invokes the CICS command-level
interpreter, to enter an EXEC CICS command, check its à RETR
ð
STATUS: ABOUT TO EXECUTE COMMAND NAME=
syntax, and modify it if necessary. In most cases, you can EXEC CICS RETRieve
< Set() | Into() >
also process the command. < Length() >
< RTRansid() >
< RTErmid() >
< Queue() >
For programming information on each EXEC CICS < Wait >
command, see the CICS Application Programming Reference

manual or the CICS System Programming Reference
manual.
For details of how to use the CECI transaction, see the CICS
Application Programming Guide, which includes an example
of a complete session with CECI. PF 1 HELP 2 HEX 3 END 4 EIB 5 VAR 6 USER 7 SBH 8 SFH 9 MSG 1ð SB 11 SF
Start the transaction by entering CECI on the command line

á ñ
of the screen, as follows: Figure 17. CECI transaction: RETRieve command screen
CECI
Alternatively, you can enter CECI together with the name of
Press ENTER. You get a list of all EXEC CICS commands.
the command in which you are interested, and bypass the
full list of commands; for example:
CECI asktime
à STATUS: ENTER ONE OF THE FOLLOWING
ð
ABend
ACquire
DISAble
DISCard
ISsue
Journal
RELease
RESEtbr
SUspend
SYncpoint
In both cases, you can generally go on to check the syntax
ADdress
ALlocate
DUmp
ENAble
LInk
LOad
RESYnc
RETRieve
Trace
Unlock
of the command, change it if necessary, and then process
ASKtime
ASSign
ENDbr
ENQ
Monitor
PErform
RETUrn
REWrite
Verify
WAIT
the command.
BIf ENTer POInt ROute WAITCics
BUild EXtract POP SENd WRITE
CAncel
CHange
FEpi
FOrmattime
POSt
PURge
SET
SIGNOFf
WRITEQ
Xctl
Many CICS system programming commands use CVDA
COLlect
CONNect
FREE
FREEMain
PUSh
Query
SIGNON
SPOOLClose
values, and CECI shows numeric equivalents for these. See
CONVerse
DELAy
GDs
GEtmain
READ
READNext
SPOOLOpen
SPOOLRead the CICS System Programming Reference manual for
DELETE Handle READPrev SPOOLWrite
DELETEQ IGnore READQ START programming information, including a “translation” of these
DEQ INquire RECeive STARTBr
numeric values to their alphabetic values.
PF 1 HELP 2 HEX 3 END 4 EIB 5 VAR 6 USER 9 MSG
á ñ
The HELP panel
Figure 16. CECI transaction: initial screen
Note: RECEIVE and SEND cannot be used on displayed:
TCAM-attached terminals. If you then enter the
command or its abbreviation on the top line and
press ENTER, you get a complete display of the à GENERAL HELP INFORMATION
ð
syntax for that command. For example, Figure 17 Enter command on the first line and press ENTER (after returning from HELP).
shows the screen displayed for the EXEC CICS Options can be abbreviated to the minimum to make them unique.
? before command gives COMMAND SYNTAX CHECK and prevents execution.
RETRIEVE command. To expand a value or variable to full screen,
position cursor using TAB key and press ENTER.
PF KEY HELP INFORMATION
PFð1 HELP HELP INFORMATION

PFð2 HEX SWITCH HEX/CHAR
PFð3 END END SESSION
PFð4 EIB EXEC INTERFACE BLOCK
PFð5 VAR VARIABLES
PFð6 USER USER DISPLAY
PFð7 SBH SCROLL BACK HALF
PFð8 SFH SCROLL FORWARD HALF
PFð9 MSG MESSAGES
PF1ð SB SCROLL BACK
PF11 SF SCROLL FORWARD
PF12 UNDEFINED
USE ENTER TO RETURN
á ñ
Figure 18. CECI transaction: general HELP panel

CECI/CECS—command-level interpreter
Command-level syntax-checking
transaction (CECS)
Use the CECS transaction, which also invokes the
command-level interpreter, to check the syntax of an EXEC
CICS command, but not to process it.
Start the transaction by entering CECS on the command line

of the screen, as follows:
CECS
Press ENTER. You get a list of all the EXEC CICS
commands. This is similar to the CECI screen shown in
Figure 16 on page 31. Enter the command or its
abbreviation at the top of the screen (next to the ?) and
press ENTER and you get a complete display of the syntax
for that command.
Alternatively, you can enter CECS together with the name of

the command in which you are interested, and bypass the
full list of commands:
CECS command
For information how to use the CECI and CECS transactions,

see the CICS Application Programming Guide.

CEDA—resource definition online
Chapter 9. CEDA—resource definition online

Use CEDA to define resources to your CICS system while REName Renames a resource definition.
the system is running. With CEDA, you can update both the
UNlock Removes a lock on a group or list which was
CICS system definition (CSD) file and the running CICS
previously put there by a CEDA LOCK
system.
command.
Start the transaction by entering CEDA on the command line USerdefine Instead of using CICS-supplied default values
of the screen. Press ENTER. You get the following screen with the DEFINE command, you can set your
(Figure 19), which shows the options available within CEDA. own defaults and use the USERDEFINE
command to create a new resource definition on
the CSD file.
à ENTER ONE OF THE FOLLOWING
ð View Lets you look at the resource definition
ADd attributes.
ALter
APpend
CHeck
COpy This section briefly describes each of these functions and
DEFine
DELete their syntax. For guidance on how to use CEDA, see the
DIsplay
Expand CICS Resource Definition Guide.
Install
Lock
Move
REMove If you enter DEF on the command line and press ENTER,
REName
UNlock you get the screen shown in Figure 20 which lists the
USerdefine
View resources:
SYSID=CI41 APPLID=IYAHZCCV
PF 1 HELP 3 END 6 CRSR 9 MSG 12 CNCL
á ñ à ð
DEF
ENTER ONE OF THE FOLLOWING
Figure 19. CEDA transaction: initial screen | Connection TCpipservice
DB2Conn TDqueue
DB2Entry TErminal
CEDA provides the following functions: |
DB2Tran
DOctemplate
TRANClass
TRANSaction
| Enqmodel TSmodel
ADd Adds a group name to a list, and creates a new File
Journalmodel
TYpeterm
list if the list did not already exist. Lsrpool

Mapset
PARTItionset
ALter Changes some of the attributes of an existing |
PARTNer
PROCesstype
PROFile
resource definition. PROGram
| Requestmodel
Sessions
APpend Copies a list to another list.
SYSID=JOHN APPLID=I
CHeck Checks that the resource definitions within a PF 1 HELP 3 END 6 CRSR 9 MSG 1
group or list are consistent with one another.
á ñ
COpy Copies one or more resource definitions.
DEFine Creates a new resource definition on the CSD Figure 20. CEDA transaction: DEFINE screen
file.
DELete Erases one or more resource definitions from the
CSD file.
DIsplay Displays one or more lists or groups on a
full-screen panel.
Expand Shows the resource definitions in one or more
groups on a full-screen panel.
Install Dynamically makes one or more resource
definitions available to an active CICS system.
Lock Assures exclusive access to a group or list by
restricting update and delete access to a single
operator identifier.
Move Moves one or more resource definitions from
one named group to another.
REMove Removes a group name from a list.

If you enter INST on the command line and press ENTER,

you get the screen shown in Figure 21 which lists the
resources:
à CEDA INST
ð
OVERTYPE TO MODIFY
CEDA Install
All
Connection ==>
DB2Conn ==>
DB2Entry ==>
DB2Tran ==>
| DOctemplate ==>
| Enqmodel ==>
File ==>
Journalmodel ==>
LSrpool ==>
Mapset ==>
PARTItionset ==>
PARTNer ==>
| PROCesstype ==>
PROFile ==>
PROGram ==>
| Requestmodel ==>
Sessions ==>
| TCpipservice ==>
TDqueue ==>
TErminal ==>
+ TRANClass ==>
+ TRANSaction ==>
| TSmodel ==>
TYpterm ==>
Group ==>
LIst ==>
S GROUP or LIST must be specified.
SYSID=JOHN APPLID=I
PF 1 HELP 3 END 6 CRSR 7 SBH 8 SFH 9 MSG 1ð SB 11 SF 1
á ñ
Figure 21. CEDA transaction: INSTALL screen
Command syntax

55──CEDA────────────────────────────────────────────────────────────────────5
5──┬─ADD──GROUP(groupname1)──LIST(name)──┬────────────────────┬─────┬──5%
│ ├─AFTER(groupname2)──┤ │
│ └─BEFORE(groupname3)─┘ │
(1) ────────┤
├─ALTER──┤ Resource ├──GROUP(name)──┤ attribute list ├───
├─APPEND──LIST(list1)──TO(list2)─────────────────────────────────┤
├─CHECK──┬─GROUP(name)─────────────┬──┬─────────────────────┬────┤
│ └─LIST(list1, ..., listn)─┘ └─REMOTESYSTEM(sysid)─┘ │
│ ┌─ALL──────────┐ │
├─COPY──┼──────────────┼──┬───────────┬──┬─────────┬─────────────┤
│ └─┤ Resource ├─┘ └─┤ Route ├─┘ ├─REPLACE─┤ │
│ └─MERGE───┘ │
├─DEFINE──┤ Resource ├──GROUP(name)──┤ attribute list ├───(1) ───────┤
├─DELETE──┬─ALL──────────┬──GROUP(name)──┬────────┬──────────────┤
│ └─┤ Resource ├─┘ └─REMOVE─┘ │
├─DISPLAY──┬─LIST(name)──┬─────────────┬───────────────┬─────────┤
│ │ └─GROUP(name)─┘ │ │
│ └─GROUP(name)──┬──────────────┬──┬────────┬─┘ │
│ ├─ALL──────────┤ └─RENAME─┘ │
│ └─┤ Resource ├─┘ │
├─EXPAND──┬─LIST(name)──┬─────────────┬───────────────┬──────────┤
│ │ └─GROUP(name)─┘ │ │
│ └─GROUP(name)──┬──────────────┬──┬────────┬─┘ │
│ ├─ALL──────────┤ └─RENAME─┘ │
├─INSTALL──┬──────────────┬──┬─GROUP(name)─┬─────────────────────┤
│ ├─ALL──────────┤ └─LIST(name)──┘ │
├─LOCK──┬─GROUP(name)─┬──────────────────────────────────────────┤
│ └─LIST(name)──┘ │
│ ┌─ALL──────────┐ │
├─MOVE──┼──────────────┼──┬───────────┬──┬─────────┬──┬────────┬─┤
│ └─┤ Resource ├─┘ └─┤ Route ├─┘ ├─REPLACE─┤ └─REMOVE─┘ │
│ └─MERGE───┘ │
├─REMOVE──GROUP(name)──LIST(name)────────────────────────────────┤
├─RENAME──┬──────────────┬──┬───────────┬──┬────────┬────────────┤
│ ├─ALL──────────┤ └─┤ Route ├─┘ └─REMOVE─┘ │
├─UNLOCK──┬─GROUP(name)─┬────────────────────────────────────────┤
│ └─LIST(name)──┘ │
├─USERDEFINE──┤ Resource ├──GROUP(name)──┤ attribute list ├─── (1) ───┤
└─VIEW──GROUP(name)──┬──────────────┬────────────────────────────┘
├─ALL──────────┤
└─┤ Resource ├─┘
Note:
1 Consult the CICS Resource Definition Guide for information about the attributes
applicable to each resource type.
Chapter 9. Resource definition online CEDA 35

Resource:
├──┬─CONNECTION(name)───┬──┤
├─DB2CONN(name)──────┤
├─DB2ENTRY(name)─────┤
├─DB2TRAN(name)──────┤
| ├─DOCTEMPLATE(name)──┤
| ├─ENQMODEL(name)─────┤
├─FILE(name)─────────┤
├─JOURNALMODEL(name)─┤
├─LSRPOOL(name)──────┤
├─MAPSET(name)───────┤
├─PARTITIONSET(name)─┤
├─PARTNER(name)──────┤
| ├─PROCESSTYPE(name)──┤
├─PROFILE(name)──────┤
├─PROGRAM(name)──────┤
| ├─REQUESTMODEL(name)─┤
├─SESSIONS(name)─────┤
| ├─TCPIPSERVICE(name)─┤
├─TDQUEUE(name)──────┤
├─TERMINAL(name)─────┤
├─TRANCLASS(name)────┤
├─TRANSACTION(name)──┤
| ├─TSMODEL(name)──────┤
└─TYPETERM(name)─────┘
Route (Copy and Move):
├──GROUP(from-name)──┬─AS(newname)──────────────┬──┤
├─TO(to-name)──────────────┤
└─AS(newname)──TO(to-name)─┘
Route (Rename):
├──┬──────────────────┬──┬─────────────┬──┬─────────────┬──┤
└─GROUP(from-name)─┘ └─AS(newname)─┘ └─TO(to-name)─┘
attribute list:
├──for details consult the Resource Definition Guide──┤
DB2CONN
Defines the CICS DB2 connection.
You can go directly to the working screen to make your
changes by typing: DB2ENTRY
Defines resources to be used by a transaction or group
CEDA function resource_type
of transactions when accessing DB2.
For example:
DB2TRAN
CEDA DEF CONN Associates a transaction ID with a DB2ENTRY.
| DOCTEMPLATE
| Defines a document templates to CICS. Document
The CEDA keywords are as follows: | templates allow you to perform variable substitution on
AFTER | documents in a manner similar to that done by BMS for
Controls the placing of a group name in a list. | 3270 screens.
ALL | ENQMODEL
All resources are to be copied, deleted, displayed, | Use of ENQMODEL definitions provides an enqueue
installed, moved, or renamed. | mechanism that serializes access to a named resource
| across a specified set of CICS regions operating with a
AS The new name specified for a definition. | sysplex.
BEFORE FILE
Controls the placing of a group name in a list. The FILE definition describes to CICS file control the
physical and operational characteristics of a file.
CONNECTION
The remote system that your CICS system
communicates with, using ISC or MRO.

GROUP | TCpipservice
Every resource definition must have a GROUP name. | Use this resource definition to define which TCP/IP
The resource definition becomes a member of the group | services are to use CICS internal sockets support. The
and is installed in the CICS system when the group is | internal CICS services that can be defined are IIOP and
installed. The GROUP name can be up to 8 characters | the CICS Web Interface.
in length.
TDQUEUE
JOURNALMODEL The definition of each transient data queue used in your
The name of a journal model containing specifications of CICS system. Queue types can be intrapartition,
journal names. An MVS log stream name is associated extrapartition, or indirect. Remote queues cannot be
with each journal model entry. specified explicitly; see the CICS Resource Definition
Guide for more information about defining transient data
LIST
queues to be remote.
The name of the list for which a specified group is to be
added, appended, checked, displayed, expanded, TERMINAL
installed, locked, removed, or unlocked. The definition of each terminal used in your CICS
system. A terminal can be any device linked to your
LSRPOOL
system, for example, visual display units, printers,
The local shared resources (LSR) pool is a reserve of
facsimile machines. To simplify matters, it is possible to
data buffers, strings, and hiperspace buffers that VSAM
group resources that have common features by using
uses when processing access requests for certain files.
TYPETERM and through AUTOINSTALL.
MAPSET
TO The new group to which a definition is to be copied.
A series of different BMS maps.
TRANCLASS
PARTITIONSET
The name of a user-defined class of transactions.
A table that describes to CICS how a display screen is
to be partitioned. TRANSACTION
The name of the transaction. Within the transaction
PARTNER
definition, you can specify options such as transaction
The PARTNER definition enables CICS application
priority and length of the transaction work area. You also
programs to communicate via APPC protocols to a
add to the transaction name the names of related
partner application program running on a remote logical
resources: PROGRAM, PROFILE, and PARTITIONSET.
unit. PARTNER is one of the four resources (the other
three are PROFILE, CONNECTION, and SESSION) that | TSMODEL
you must specify to allow the System Application | The TSMODEL resource allows you to specify a TS
Architecture (SAA) communications interface to be used. | queue name prefix, and associate attributes with that
| name. You can also map names directly to a shared TS
| PROCESSTYPE
| pool (without the need for a shared sysid).
| Use the CICS business transaction services (BTS) API
| to define and execute complex business applications TYPETERM
| called processes. Some of the common attributes of your terminals. This
has to be defined as part of the terminal definition.
PROFILE
A group of programs that control a number of
transactions or partners.
CSD compatibility panel
PROGRAM
The name of the program that is to control a given Figure 22 on page 38 shows a normal ALTER panel with
transaction. one attribute (PRIMedsize) that is obsolete in CICS/ESA
3.3, protected as indicated by the colon symbol (:).
| REQUESTMODEL
| A REQUESTMODEL resource definition provides the Use the PF2 key to change to the compatibility mode panel
| connection between an Internet Inter-ORB Protocol shown in Figure 25 on page 38. PRIMedsize is now shown
| (IIOP). with the ==> symbols indicating that it can be modified. Use
the PF2 key again to return to the normal panel.
SESSIONS
The logical link of two systems that communicate using See the CICS Resource Definition Guide for background
ISC or MRO. information about the CSD compatibility panel.

à ALTER TRANS
ð Security checking
OVERTYPE TO MODIFY CICS RELEASE = ð41ð
CEDA ALter TRANSaction( )
TRANSaction ==> The scope of a particular CEDA command can be limited by
Group ==>
DEscription ==> a combination of several levels of security checking. The
PROGram ==>
TWasize ==> ð-32767 normal transaction-attach security is described in the CICS
PROFile ==>
PArtitionset ==>
STAtus ==> Enabled | Disabled
RACF Security Guide. CEDA calls the exec interface
PRIMedsize ==>
TASKDATALoc ==>
ð-6552ð
Below | Any
programs to process the user’s commands, in much the
TASKDATAKey ==>
STOrageclear ==>
User | Cics
No | Yes same way as CECI or a user’s command-level program
RUnaway ==> System | ð-27ððððð
SHutdown ==> Disabled | Enabled would. The resource security and the command security
ISolate ==> Yes | No
REMOTE ATTRIBUTES used by the command-level programming interface are thus
+ DYnamic ==> No | Yes
applicable to the master terminal user.
Figure 22. CEDA transaction: normal panel For programming information about command security
checking, see the CICS System Programming Reference
manual.
à REMOTESystem ==>
ð
REMOTEName ==>
TRProf ==>
Localq ==> No | Yes
SCHEDULING
PRIOrity ==> ð-255
CEDA HELP panels
TClass : No | 1-1ð
TRANClass ==>
ALIASES
Alias ==>
If you press the help key (PF1), the following panels are
TASKReq
XTRanid
==>
==>
displayed:
TPName ==>
==>
XTPname ==>
==>
==>
RECOVERY
DTimout ==> No | 1-68ðð
à CEDA Help Selection
ð
+ INdoubt ==> Backout | Commit | Wait
This panel allows you to see a brief description of the CEDA transaction.
For a complete description see Resource Definition (Online) (SC33-ð666).
Figure 23. CEDA transaction: normal panel (continued) Select one of the following topics:
1 Command Summary
2 Resources, Groups and Lists
3 Using the commands
4 Expand and Display
5 Messages
à RESTart ==> No | Yes
ð 6
7
Defaults and Userdefine
PF keys
SPurge ==> No | Yes
TPUrge ==> No | Yes Selection ==>
DUmp ==> Yes | No
TRACe ==> Yes | No
SECURITY
RESSec ==> No | Yes
Cmdsec ==> No | Yes
Extsec :
TRANSec : 1-64
RSl : ð-24 | Public Press Enter or any PF key to return
á ñ
Figure 24. CEDA transaction: normal panel (end)
Figure 26. CEDA transaction: initial HELP panel
à ð
OVERTYPE TO MODIFY
CEDA ALter
TRansaction ==>
COMPATIBILITY MODE
à Command Summary
ð
Group ==> Resource management commands:
DEscription ==> DEFINE creates a resource definition (see Topic 6 for USERDEFINE)
PROGram ==> ALTER,VIEW modify and display the attributes of a resource (or resources)
TWasize ==> ð-32767 COPY creates new resources from existing definitions
PROFile ==> DELETE destroys resource definitions
PArtitionset ==> MOVE,RENAME change the names and/or groupings of resources
STatus ==> Enabled | Disabled
PRIMedsize ==> ð-6552ð List management commands:
TASKDATALoc ==> Below | Any ADD creates or extends a list
TASKDATAKey ==> User | Cics REMOVE reduces or destroys a list
REMOTE ATTRIBUTES APPEND copies a list or combines lists
DYnamic ==> No | Yes
REMOTESystem ==> General purpose commands:
REMOTEName ==> CHECK cross-checks definitions in a group or list
TRProf ==> DISPLAY shows the names of groups or lists on the CSD file
+ Localq ==> No | Yes EXPAND shows the contents of groups or lists
INSTALL dynamically adds resources to the running CICS system
LOCK,UNLOCK control access to a group or list
Figure 25. CEDA transaction: compatibility mode panel CEDB does not have INSTALL. CEDC has DISPLAY, EXPAND and VIEW only.
Press Enter or any PF key to return to Help Selection Panel
á ñ
Figure 27. CEDA transaction: HELP Panel 1

à Resources, Groups and Lists

ð à Messages
ð
You use CEDA to create and modify resource definitions. Using the DEFINE Single messages appear near the bottom of panels. If there is more than one
command, you specify a resource's type, name and attributes, which are message a summary appears instead. PF9 shows the details of such a summary.
then stored on the CICS System Definition (CSD) file.
Messages are preceded by a single letter indicating the severity:
You can see what types of resource there are by using DEFINE on its own I-Informatory W-Warning E-Error S-Severe
as a command. Similarly you can see what attributes any resource may have
by adding just the type of resource, as in, for example, DEFINE PROGRAM. Commands with only I or W-level messages are executed. E-level messages
are given for errors that CEDA attempts to correct. Such commands can
Each resource must belong to a GROUP, which is a collection of resources, be executed by pressing ENTER without making any changes. S-level
usually related in some way. A group of resources can be installed on messages require you to correct the command.
your running CICS system.
A LIST is a collection of group names, and can be used to specify large For a command executed on an EXPAND or DISPLAY panel you can see the
numbers of resources during a cold start. messages by using ? in the command field or by means of the cursor and PF9.
Commands with errors that have apparently been fixed (E-level messages)
Note that program P, say, may be defined in more than one group. Such must still be corrected by you.
definitions are separate resources and may have different attributes. You can correct a command on the message panel or on the original panel.
By contrast the same group names in different lists refer to the same group.
The DELETE command destroys a resource, but REMOVE does not destroy a group.
A group has no attributes and need not even exist to be used in a list.
Press Enter or any PF key to return to Help Selection Panel Press Enter or any PF key to return to Help Selection Panel
á ñ á ñ
Figure 28. CEDA transaction: HELP Panel 2 Figure 31. CEDA transaction: HELP Panel 5
à Using the commands

ð à Defaults and Userdefine
ð
You type CEDA commands on the first line of the screen and press ENTER. When you DEFINE a resource any attributes you do not specify are
You will then see a panel that shows your command in detail, and the defaulted. You cannot change the defaults that DEFINE uses.
results of its execution. You can then either modify the panel to You can however DEFINE "default resources" with whatever values you
execute a similar command with new values or type a different command like and then create new resources using USERDEFINE.
on the top line.
You DEFINE resources called USER in a group called USERDEF, giving
You can see the syntax of a command, without executing it, by typing ? each one the values you would like to have as defaults. These are
in front of the command. now your default resources.
You can shorten command keywords as much as you like provided the result USERDEFINE will then behave just like DEFINE except that it will get
remains unique. Thus ALT and AL both mean ALTER but A is invalid default values from the appropriate default resource. If a default
because of ADD. The minimum number of letters you can use is shown resource does not exist then USERDEFINE fails.
in upper case.
This facility is restricted to initial values only. Default values
You can specify generic names in some commands, by using \ and +. are also given by CEDA to attributes you remove from a resource, by
\ means any number of characters, + means any single character. overtyping with blanks for instance. These defaults are the same as
Thus PROGRAM(P\) refers to all programs whose names begin with P. those used for the DEFINE command and you cannot change them.
Current values for GROUP and LIST are kept and are used when either
keyword is omitted from commands other than DISPLAY and EXPAND LIST.
á ñ á ñ
Figure 29. CEDA transaction: HELP Panel 3 Figure 32. CEDA transaction: HELP Panel 6
à Expand and Display

ð à PF keys
ð
The commands you can use on each kind of panel are as follows: The PF keys do the following:
EXPAND GROUP panel - Alter, Copy, Delete, Install, Move, Rename, View 1 HELP Gives the initial help panel
EXPAND LIST panel - Add, Remove 2 COM Selects and deselects compatibility mode
DISPLAY GROUP panel - Check, Expand, Install , Lock, Unlock 3 END Terminates the CEDA transaction if no data has been entered
DISPLAY LIST panel - Append, Check, Expand, Lock, Unlock 4 Does nothing
5 Does nothing
All these commands operate on the thing beside which you enter them. 6 CRSR Moves the cursor to the command line or first input field
ALTER means ALTER PROGRAM(P) GROUP(G), if these are the object and 7 SBH Scrolls back half a screen
group values on the line. In this case, since no attributes are changed, 8 SFH Scrolls forward half a screen
you will see a display of the object which you can then overtype. 9 MSG Displays the current set of messages
The EXPAND command on a DISPLAY panel also results in a new panel. 1ð SB Scrolls back a full screen
11 SF Scrolls forward a full screen
You can enter as many commands as you like at one time and you can 12 CNCL Cancels changes not yet executed and returns to previous panel
use = to mean the same command as the last one.
When you press ENTER without having entered any data you will normally
The RENAME option of EXPAND GROUP gives a panel on which you can change the be returned to the previous panel.
names of objects directly, by overtyping the name fields displayed.
When you change a name field a RENAME command is put in the corresponding Positioning the cursor at a PF key and pressing ENTER will have the same
command field, and causes anything entered there to be ignored. effect as pressing the key. PF13 to PF24 have the same effects as PF1 to PF12.
á ñ á ñ
Figure 30. CEDA transaction: HELP Panel 4 Figure 33. CEDA transaction: HELP panel 7

CEDB and CEDC CEDC

The CEDC transaction allows you only to look at data on the
Two further resource definition transactions, CEDB and
CICS system definition (CSD) file. You cannot update either
CEDC, allow you to use some, but not all, of the functions of
the CSD file or the running CICS system. The only options
CEDA.
that are available are DISPLAY, EXPAND, and VIEW.
CEDB For background information about the CEDA, CEDB, and

CEDC transactions, see the CICS Resource Definition Guide.
When you use the CEDB transaction, the INSTALL
command is not available to you. This means that you can
update the CSD, but not the running CICS system.
à ENTER ONE OF THE FOLLOWING

ð
ADd
ALter
APpend
CHeck
COpy
DEFine
DELete
DIsplay
Expand
Lock
Move
REMove
REName
UNlock
USerdefine
View
SYSID=CI41 APPLID=IYAHZCCV
PF 1 HELP 3 END 6 CRSR 9 MSG 12 CNCL
á ñ
Figure 34. CEDB transaction: initial screen

CEDF—execution diagnostic facility
Chapter 10. CEDF & CEDX — the execution diagnostic facility

The CICS execution diagnostic facility (EDF) provides two ON
transactions that you can use for testing application specifies whether the EDF screen is to be switched ON.
programs. These transactions—CEDF and CEDX—enable The default is ON. If you specify ON you must enter
you to test application programs interactively without having the preceding comma, as shown in the following
to supply special program testing procedures. examples:
CEDF CEDF T33A

Use CEDF to invoke EDF for testing application CEDF ,ON
programs that are associated with user transactions sessionid
initiated from a terminal. specifies the session identifier used to test a transaction
CEDX attached across an MRO, APPC, or LU6.1 session. All
Use CEDX to invoke EDF for testing application CICS commands processed by the attached transaction
programs that are associated with non-terminal are monitored.
transactions. sysid
specifies the system identifier used to test a transaction
across an MRO or APPC session.
CEDF transaction
termid
CEDF allows you to intercept your application programs at specifies the identifier of the terminal on which the
the program’s initiation, at each CICS command, and at the transaction to be tested is being run. If you do not
program termination. CEDF helps you to isolate and focus on provide an identifier, the terminal at which you enter the
problems in your application programs. CEDF transaction is assumed.
For information on how to use the CEDF transaction, see the

CICS Application Programming Guide.
Beginning an EDF session (single-screen
mode)
You must ensure that the EDF resource definitions are
installed. These resource definitions are provided in the To start an EDF session with a single terminal, clear the
IBM-supplied group, DFHEDF. For information about screen and enter the transaction identifier, CEDF. The EDF
installing the resource definitions, see the CICS Resource inputs and outputs are interleaved with those of the
Definition Guide. transaction. This is known as single-screen mode.
CEDF
You must also ensure that the terminal from which you run
EDF is in transceive (ATI/TTI) status. When you press ENTER, the response is:
THIS TERMINAL: EDF MODE ON
Command syntax Now clear the screen and enter the name of your
transaction. Figure 35 shows the initial screen for a typical
transaction using EDF.
┌─,ON──┐
55──CEDF──┬───────────┬──┼──────┼──5%
├─termid────┤ └─,OFF─┘
├─sysid─────┤ à TRANSACTION: ACCT PROGRAM: ACCTðð TASK: ððððð54 APPLID: ðððð1349 DISPLAY: ðð
ð
└─sessionid─┘ STATUS: PROGRAM INITIATION
EIBTIME = 11ð343
EIBDATE = 89174
EIBTRNID = 'ACCT'
EIBTASKN = 54
EIBTRMID = 'ð25L'
Command options EIBCPOSN = 4
EIBCALEN = ð
OFF EIBAID
EIBFN
=
=
X'7D'
X'ðððð'
AT X'ðð543F1E'
AT X'ðð543F1F'
specifies whether the EDF screen is to be switched EIBRCODE
EIBDS
=
=
X'ðððððððððððð'
'........'
AT X'ðð543F21'
+ EIBREQID = '........'
OFF. If you specify OFF you must enter the preceding
ENTER: CONTINUE
comma, as shown in the following examples: PF1 : UNDEFINED PF2 : SWITCH HEX/CHAR PF3 : END EDF SESSION
PF4 : SUPPRESS DISPLAYS PF5 : WORKING STORAGE PF6 : USER DISPLAY
PF7 : SCROLL BACK PF8 : SCROLL FORWARD PF9 : STOP CONDITIONS
CEDF T33A PF1ð: PREVIOUS DISPLAY PF11: UNDEFINED PF12: UNDEFINED
CEDF T33A ,OFF á ñ
CEDF ,OFF
Figure 35. CEDF transaction: initial screen

Beginning an EDF session (dual-screen security checking of transactions running under

CEDF.
mode)
You can also use EDF in what is known as dual-screen
mode; that is, using one terminal to monitor a transaction à TRANSACTION: DLID PROGRAM: DLID TASK: ððððð49 APPLID: IYAHZCIB
ð
ADDRESS: ðððððððð
running at a second terminal.
This mode is started by adding the terminal identifier (termid)

of the second terminal to the CEDF command at the first
terminal:
CEDF tttt
The message that CEDF gives in response to this depends
on whether there is already a transaction running on the WORKING STORAGE IS NOT AVAILABLE
ENTER: CURRENT DISPLAY
second terminal. If the second terminal is not busy, the PF1 : UNDEFINED
PF4 : EIB DISPLAY
PF2 : BROWSE
PF5 : INVOKE
TEMP STORAGE
CECI
PF3 :
PF6 :
UNDEFINED
USER DISPLAY
message displayed at the first terminal is: PF7 : SCROLL BACK HALF
PF1ð: SCROLL BACK FULL
PF8 : SCROLL
PF11: SCROLL
FORWARD HALF
FORWARD FULL
PF9 :
PF12:
UNDEFINED
REMEMBER DISPLAY
TERMINAL tttt: EDF MODE ON á ñ

and nothing further will happen until a transaction is started Figure 36. Typical EDF display from which CEBR or CECI can be
on the second terminal, when the PROGRAM INITIATION invoked
display will appear.
To invoke the CEBR transaction from the CEDF screen,
If a transaction is already running on the second terminal, the press PF2. You can then use CEBR commands to browse
message displayed at the first terminal is: temporary storage queues and to delete them. (CEBR
TERMINAL tttt: TRANSACTION RUNNING: EDF MODE ON commands are described briefly in Chapter 6,
“CEBR—temporary storage browse” on page 19; for detailed
CEDF then picks up control at the next command processed
guidance on using them, see the CICS Application
and presents the appropriate display. At the first terminal,
Programming Guide.)
you can then follow the sequence of commands in the
transaction running at the second terminal. To invoke the CECI transaction from the CEDF screen, press
PF5. You can then use CECI commands to display or alter
Monitoring remote transactions resource status. (CECI commands are described briefly in
Chapter 8, “CECI—command-level interpreter” on page 31;
In a multiregion operation (MRO) or an intersystem for detailed guidance on using them, see the CICS
communication (ISC) environment (APPC only), you can use Application Programming Guide.)
CEDF (in single screen mode only) for transactions that are
defined in the terminal owning region (TOR) as remote.
CICS automatically notifies the application owning region CEDX transaction
(AOR) that the transaction is to be run in EDF mode.
Use CEDX to monitor and debug non-terminal transactions.
When the remote application ends, if your reply is YES, the The transaction you specify for debugging can be:
terminal remains in EDF mode as usual. However, CICS
Initiated without an associated terminal; for example, by
deletes all the associated temporary storage queues, and
an EXEC CICS START command, or by a transient data
none of the previous EDF screens or options is saved: you
queue trigger-level.
must type these again for the next transaction. Responding
NO at the termination screen ends the EDF session in all Initiated at a terminal, which can be either the EDF
participating regions. terminal or a different terminal.
Note: CICS supports EDF for remote transactions only CICS intercepts the transaction specified on the CEDX tranid
when all the communicating regions are using command, and displays the EDF diagnostic panels at the
CICS/ESA. terminal at which the EDF command is issued.
CEDX provides the same function and diagnostic display

Invoking CEBR and CECI from CEDF
panels as CEDF, and the same basic rules for CEDF also
See Figure 36 for an example of the screen from which apply to CEDX.
CEBR and CECI can be invoked.
Note: If you are not authorized to use the CEBR or CECI Command syntax
transaction by the external security manager, a
warning message will appear on the EDF panel. See
the CICS RACF Security Guide for information about

The transaction you specify on the CEDX command

┌─,ON──┐ must run in the local CICS region.
55──CEDX──tranid──┼──────┼──5%
└─,OFF─┘ CEDX cannot interrupt transactions that are already
running when you issue the CEDX command. It affects
only a transaction that starts after you issue the
command.
Command options
OFF The following diagram illustrates the use of CEDX to invoke
specifies that the EDF screen is to be switched OFF. If EDF for a transaction initiated by an EXEC CICS START
you specify OFF you must enter the preceding comma, command:
as shown in the following example: ┌────────────┐ ┌────────────┐
│ CICS │ │ CICS user │
CEDX TRNA,OFF │ terminal │ ┌──────┐ │ terminal │
│ used ├─────────5│ BBBB │ │ │
ON
│ for EDF │ └──────┘ │Transaction │
specifies that the EDF screen is to be switched ON. The │ │ Transaction │AAAA starts│
default is ON. If you specify ON you must enter the │ CEDX BBBB │ BBBB started │ BBBB │
preceding comma, as shown in the following example: └────────────┘ └────────────┘
The CEDX command is AAAA issues
CEDX TRNB,ON issued at this terminal, EXEC CICS START
before BBBB is command to start
tranid
started, to invoke EDF BBBB, without
specifies the identifier of a transaction that you want to services to intercept and a terminal.
test using the execution diagnostic facility. The debug the specified
diagnostic panels are displayed on the terminal at which transaction.
you issue the CEDX tranid command.
Chapter 10. Execution diagnostic facility CEDF & CEDX 43


CEMT—master terminal
Chapter 11. CEMT—master terminal

Use CEMT to invoke all the master terminal functions. Press the ENTER key. You get the following response:
The master terminal program provides dynamic user control

of the CICS system. By using this function, an operator can
inquire about and change the values of parameters used by
à STATUS: ENTER ONE OF THE FOLLOWING
ð
Discard
CICS, alter the status of the system resources, terminate Inquire
Perform
tasks, and shut down the CICS system. Set
The following transactions are subsets of CEMT (that is, they

contain some but not all of the functions of CEMT):
CEBT for alternate CICS systems (see page 21) Figure 37. CEMT transaction: initial screen
CEOT (see page 213)
CEST (see page 219). This display prompts you to enter one of the keywords
shown.
The CECI transaction (see page 31 ) ) also uses the same
command interpreter as CEMT. If you then type:
D
You can start CEMT from IBM 3270 family display devices or
equivalent terminals or from the system console. Starting and press ENTER, you get the following screen:
CEMT from the operating system console is described in
“The system console as a CICS terminal” on page 5. The
description of CEMT throughout this section assumes, unless à D
ð
stated otherwise, that you are using a 3270 family display STATUS: ENTER ONE OF THE FOLLOWING
device or equivalent terminal. |

Autinstmodel
Connection
PROGram
Requestmodel
DB2Conn TCLass
| DB2Entry TCPipservice
To start CEMT, you can either enter the identifier CEMT on |
DB2Tran
DOctemplate
TDqueue
TErminal
the command line by itself, or you can add options on the | Enqmodel TRansaction
| FENode TSmodel
same line, separated by commas or blanks, to form a FEPOol
FEPRopset
FETarget
complete request. FIle
JModel
JOurnalname
If you start the transaction by entering CEMT by itself and |
PArtner
PROCesstype
pressing ENTER, you get a display that prompts you for PROFile
S At least 4 characters of DISCARD must be specified.
SYSID=JOHN APPLID=I
more information, as described in “CEMT INQUIRE
PF 1 HELP 3 END 5 VAR 9 MSG
SYSTEM” on page 116.
Figure 38. CEMT transaction: DISCARD screen

Starting the CEMT transaction
If you type:
You can construct a CEMT request in stages, or you can
I
enter a complete request in one go. The CEMT transaction
checks the syntax of requests and diagnoses errors. If your and press ENTER, you get the following screen:
request is syntactically correct, it is processed immediately. If
your request cannot be processed because of severe syntax
errors, the full syntax of your request is displayed. à I
ð
STATUS: ENTER ONE OF THE FOLLOWING OR HIT ENTER FOR DEFAULT
If you put a question mark (?) in front of your request, the

| AUTInstmodel FENode PROGram TSQueue
syntax of your request is displayed but it is not processed. | AUTOinstall FEPOol REquestmodel UOW
| AUXtrace FEPRopset RRms UOWDsnfail
| CFdtpool FETarget STAtistics UOWLink
| COnnection FIle STReamname Vtam
After you have initiated the CEMT transaction, you need not | DB2Conn Gtftrace SYDumpcode Web
DB2Entry INttrace SYStem
reenter CEMT on subsequent requests, because the DB2Tran IRc TAsk
| DEletshipped JModel TCLass
identifier is implied at the beginning of any further request. | DOctemplate JOurnalname TCPIP
| DSAs Line TCPIPService
However, if you are using the system console, you must DSName
DUmpds
MODename
MONitor
TDqueue
TErminal
always start each master terminal request with CEMT. | ENQ Netname TRAnsaction
| ENQModel PArtner TRDumpcode
| EXci PROCesstype TSModel
| FEConnection PROFile TSPool
Enter CEMT on the command line of the screen, as follows:
CEMT Figure 39. CEMT transaction: INQUIRE screen

If you type: PF2 switches the display of character values to

P hexadecimal format on an expanded panel (see
“Expanded panels” on page 48).
and press ENTER, you get the following screen:
PF3 ends this master terminal session by terminating the
CEMT transaction. If, however, you use this key when
you are modifying your display, say by keying in a new
à P
ð command, or by overtyping an old command, this key
STATUS: ENTER ONE OF THE FOLLOWING
DEletshipped
does not end your session; it is ignored.
DUmp
ENDaffinity
RESet
PF5 gives a variables display. You can use this to create
SEcurity
SHUTdown values for use in a command.
SNap
STatistics
PF7 scrolls backward half a screen.
PF8 scrolls forward half a screen.
PF9 expands messages. If more than one message has
Figure 40. CEMT transaction: PERFORM screen been generated in response to your request, a
message telling you how many messages have been
If you type: generated appears near the bottom of the screen. PF9
S lets you display all the messages on a separate
display. Press ENTER to go back to your original
and press ENTER, you get the following screen: display.
PF10 scrolls backward a full screen.
à S
ð PF11 scrolls forward a full screen.
STATUS: ENTER ONE OF THE FOLLOWING OR HIT ENTER FOR DEFAULT
| AUToinstall Gtftrace TCPIPService

AUXtrace
Connection
INttrace
IRc
TDqueue
TErminal Minimum abbreviation of keywords
DB2Conn Journalname TRAnsaction
DB2Entry Line TRDumpcode
| DB2Tran MODename TSqueue CEMT accepts as few characters of a keyword as needed to
DEletshipped MONitor UOW
| DOctemplate Netname UOWLink
uniquely identify it within the request. This means that you
| DSAs PROCesstype Vtam
| DSName PROGram Web
can enter the keyword TASK as TA or TAS, but you cannot
| DUmpds Requestmodel
| Enqmodel STatistics
use T, because it can be confused with TCLASS,
FEConnection SYDumpcode
FENode SYStem
FEPool TAsk TDQUEUE, TERMINAL, TRANSACTION, or TRDUMPCODE.
FETarget TCLass
| FIle TCPIP You are prompted if the abbreviation you use is not unique.
SYSID=JOHN APPLID=I
PF 1 HELP 3 END 5 VAR 9 MSG

An exception to this rule is SHUTDOWN, for which you must
specify at least SHUT.
Figure 41. CEMT transaction: SET screen In the syntax displays on your screen and in the railroad
diagrams and syntax descriptions in this book, the minimum
permitted abbreviation is given in uppercase characters, with
System parameters the remainder in lowercase characters.
If you press ENTER without selecting one of the CEMT
keywords, INQUIRE SYSTEM is assumed and you get a ALL option
display of the system parameters. Full details are given in
“CEMT INQUIRE SYSTEM” on page 116. Many of the request formats contain the ALL option. For
INQUIRE, this is the default. For example, if you inquire
about terminals, you receive information about all terminals
Program function (PF) keys unless you specify a terminal identifier, a terminal class
When you start CEMT, the lower part of your display identifier, or a system identifier.
contains a list of PF keys. If your terminal does not have
ALL is not the default on a SET command, however. If you
such keys, you can get the same effect by placing the cursor
specify the ALL option on a SET command, any changes you
under a name in the list, and pressing ENTER.
request are made to all resources of the specified type that
Here is what the PF keys do: you are authorized to access.
PF1 is a general HELP key. It also gives you a list of all the If there are no resources of the type specified on the SET
PF keys and what they do. command, a response of NOT FOUND is given.

CLASS option Subdefining resource groups

When operating on terminals, transactions, and programs, When you make an inquiry, you can subdefine a resource
the CLASS option can be used to identify the suffix of a TLT, group by specifying one or more attributes of the group. For
XLT, or PLT. This limits the scope of the INQUIRE or SET example:
commands to those resources defined in the specified table. CEMT INQUIRE TERMINAL ALL INSERVICE
Any resources whose definitions have not been installed are
displayed as NOT FOUND. For information about the TLT, displays the status of all terminals that are in service.
the XLT, and the PLT, see the CICS Resource Definition
If the subdefined resource group has no members, CEMT
Guide.
returns a NOT FOUND response. For example, if all the files
in the system are closed, the command:
Family of resources (using * and + CEMT INQUIRE FILE ALL OPEN
symbols) gives the NOT FOUND response.
You can use the symbols * and + as part of an identifier to
You cannot subdefine a resource group on the SET
specify a family of resources. * represents any number of
command in the same way. For example:
characters (including none), and + represents a single
character, for example: CEMT SET TERMINAL ALL INSERVICE PAGE
puts all terminals both in service and into page status.
A* all identifiers beginning with A
*DATA* all identifiers containing the characters DATA
However, you can manage such groups of resources by
TERM00+ all 7-character identifiers starting with TERM00.
issuing an INQUIRE request, and overtyping the display
Use of * and + is restricted to selecting existing resources produced.
and cannot be used either to create a new set of resources
or to discard resources. Overtyping a display
| Note: The INQUIRE command and the SET command may
| use the generic name in a different way. The When you issue an INQUIRE request, you usually get a
| following two examples illustrate the difference: display that consists of status information for each resource
in the specified group. The status information is displayed as
| CEMT INQUIRE FI(\) DSN(ABCD\) a list of abbreviated keywords. You can move the cursor to
| lists all the files with data sets with a name some fields and change their contents by overtyping. When
| beginning with ABCD. you press the ENTER key again, CICS reads the contents of
| CEMT SET FI(\) DSN(ABCD\) CLO all fields that have been changed, and processes any valid
operations implied by the changes. If you make an invalid
| associates all your files with data set ABCD* and change, you get an error message, and the field is not
| closes them all. changed.
| Thus the generic name has the expected effect only When a field is overtyped, CEMT will accept and identify only
| for the resource itself. as few characters as are necessary to uniquely identify the
keyword within the valid options for that position. This is
List of resource identifiers: You can specify a list of usually only one character.
resource identifiers, rather than a single one, separating the
items in the list by commas or blanks. Any errors of syntax On many of the status displays, the current status is
are reported. displayed in certain positional fields at the right-hand side of
| CEMT SET TERMINAL(TO1,TO2,TO3,TO4) INSERVICE the display. For some fields, the positional display appears
only when the status of a particular resource is ‘on’. You can
You cannot use * or + when the identifier is in a list of overtype the current status (when it is either displayed or
identifiers. blank) to change it.
| Note: If you use the comma (,) in the name of a resource
So, for example, if you type ‘CEMT INQUIRE SYD’, you get
| identifier, you will not be able to use any commands
a display of the current settings of the entries in the system
| that permit the use of lists of resources, because the
dump table. The various attributes of those entries are
| comma will be treated as a list separator, and not as
displayed in fields across the screen. If CICS is to be shut
| a part of a name.
down after the occurrence of an error for this dump code,
‘Shu’ appears in the third field of attributes for that dump
code. If CICS is not to be shut down, however, the ‘Shu’
space is left blank. If you want CICS to be shut down for
this dump code, you can tab to that field and type ‘shu’ in
that blank space in that field only.
Chapter 11. Master terminal CEMT 47

The sequence of the positional fields is given in the Expanded panels

descriptions of the various CEMT INQUIRE commands.
You can select one resource item from a list, then check and
Whenever you overtype a display, not only is that particular change its options if required. Type the required CEMT
action taken but all the status information is refreshed. You INQUIRE or SET command name, then move the cursor to
can avoid the overhead of a large number of table searches the relevant line on the display panel and press ENTER. This
either by using the SET command, or by limiting your inquiry will result in an expanded display showing the attributes of
to a specific number of resources (either by using a ‘wild the selected resource item. In the process, an INQUIRE
card’ in the search argument or by naming a range of command is executed for the associated resource.
resource identifiers).
For example, if you enter CEMT INQUIRE TERM, this gives
the screen in Figure 43.
Tab key
The fields you can change are different in each display. You
can detect them, however, by pressing the tab key à in task
ð
repeatedly. This causes the cursor to jump from one field to STATUS: RESULTS - OVERTYPE TO MODIFY
\\\ Sample screen required \\\

the next.
Figure 43. Sample of screen showing a list of terminals
Scrolling symbol (+ sign)
Move the cursor to the left of the first entry and press
A plus (+) sign on the first or last line of a display tells you ENTER. This selects the first terminal, and displays the
that there is more data above or below your current display. relevant information for that terminal (see Figure 44).
Scrolling backward reveals data above, and scrolling forward
reveals data below.
à in term
ð
RESULT - OVERTYPE TO MODIFY
Blank fields in a display Terminal(bell)
Transaction()
Priority( ððð )
Pagestatus( Pageable )
Some displays contain blank fields that allow you to specify Servstatus( Inservice )
Atistatus( Noati )
options, such as NEWCOPY, on the CEMT SET PROGRAM Ttistatus( Tti )
Nature(Local)
command, which are not part of the status of a resource. A Purgetype(
Netname()
)
status, such as NOREAD, which begins NO, is also Termstatus(

Createsess(
)
)
Task(ððððð)
represented by a blank field. You can detect these fields by Remotesystem()
Rname()
using the tab key. Rnetname()
Cid()
Using the ? key Figure 44. Terminal settings for a selected terminal
If you precede the command with ?, the syntax for that Overtype the displayed settings if you want to make
command appears on the screen. For example ?INQUIRE changes. Press ENTER to restore the original panel.
TERMINAL gives the list of options that you can specify with
the inquiry command with the default highlighted. See You can view a number of expanded panels in succession by
Figure 42. entering ‘?’ or ‘s’ in the space at the beginning of the line for
each resource you wish to query. After the first expanded
panel, pressing ENTER takes you to the next panel.
à ?INQ TERM
ð
STATUS: COMMAND SYNTAX CHECK
CEMT Inquire TErminal()
< CLass() | ALl > Hexadecimal values
< TRansaction() >
< PRiority() >
< PAgeable | AUtopageable >
< Inservice | Outservice >
Some values such as TSQUEUE and NETUOWID may
< ATi | NOAti >
< TTi | NOTti > contain nondisplayable characters, which are shown as
< NEtname() >
< ACquired | RELeased > periods. You can use PF2 on the expanded panel to see the
< CReate | NOCreate >
< REMotesystem() > hexadecimal values of these characters. To switch back to
character format, press PF2 again.
Figure 42. Sample of screen showing the syntax of a INQUIRE

command

CEMT DISCARD
Variables CEMT DISCARD commands

PF5 gives a display of variables, similar to that for the CECI
The DISCARD command allows you to remove an installed
command. Here are some examples of its use.
resource definition and its corresponding catalog entry from
From a FILE display, you may wish to inquire of a particular an active CICS system.
DSNAME, which is typically 26 characters and can be up to
DISCARD does not affect the CICS system definition (CSD)
44 characters in length. Go to the expanded panel, position
file, and you can therefore reinstate the resource using
the cursor on the DSNAME line, and press PF5. You now
CEDA INSTALL(resourcename). DISCARD commands
have a variable &DSN with the required value. Type I
require ALTER access to the resource to provide similar
DSN(&DSN) on the command line, and press ENTER.
security to that for SET commands (which use UPDATE
You may wish to find all the TSQUEUE names beginning access). You cannot discard resources that are currently in
with a nondisplayable character—for example, X'FF'. Press use or are CICS owned resources (beginning with “DFH” or
PF5 for the variables display. Enter X and 2 to make a “C”).
variable &X of length 2. Press PF2 to switch to hexadecimal,
You can discard the following resource types:
and overtype ‘4040’ with ‘FF5C’ (‘%c’ is hexadecimal for the
asterisk (*) symbol). Type I TS(&X) on the command line and Autinstmodel
press ENTER. Connection
DB2Conn
For more information on the variables display, see the CICS DB2Entry
Application Programming Guide. DB2Tran
| Doctemplate
| Enqmodel
Invoking CEMT from an application FEPI node
program FEPI pool
FEPI property set
Many of the CEMT INQUIRE and SET operations are
FEPI target
available through the EXEC CICS INQUIRE and EXEC CICS
File
SET commands; for programming information, see the CICS
JModel
System Programming Reference manual.1
Journalname
Partner
Security checking | Processtype
Profile
The scope of a particular DISCARD, INQUIRE, SET, or Program
PERFORM command can be limited by a combination of | Requestmodel
several levels of security checking. The normal TClass
transaction-attach security is described in the CICS RACF | TCPIPservice
Security Guide. CEMT calls the exec interface programs to TDqueue
process the user’s commands, in much the same way as Terminal
CECI or a user’s command-level program would. The Transaction.
resource security and the command security used by the | TSmodel
command-level programming interface are thus applicable to
the master terminal user. (Programming information about FEPI commands is in the
CICS Front End Programming Interface User's Guide.)
For programming information about command security
checking, see the CICS System Programming Reference There are two ways to discard a resource:
manual. 1. If you know the name of the resource that you want to
discard, type:
CEMT DISCARD resourcetype(resourcename)

2. If you do not know the name of the resource, type:
CEMT INQUIRE resourcetype
1 Users of earlier releases of CICS may be familiar with the old programmable interface to the master terminal program (DFHEMTA). Its use
is still supported, though the documentation is available only in the CICS libraries for releases prior to CICS Transaction Server for OS/390
Release 3.

CEMT DISCARD
and a screen similar to Figure 45 on page 50 appears. CEMT DISCARD

Use the carriage return key to move the cursor to the
beginning of the line for the resource or resources you Syntax
want to discard, and type “D” as shown and then press
ENTER.
┌──
───────────────────────┐
55──CEMT Discard───6┬─────────────────────┬┴──5%
├─Autinstmodel(value)─┤
à IN PROG
ð ├─Connection(value)───┤
STATUS: RESULTS - OVERTYPE TO MODIFY ├─DB2Conn─────────────┤
D Prog(ABCDTASK) Len(ððð2936) Ass Pro Ena Pri Ced
Res(ððð) Use(ðððððð)
Prog(DFHACP ) Len(ððð8232) Ass Pro Ena Pri
├─DB2Entry(value)─────┤
Res(ðð1) Use(ððððð2) Any Cex Ful ├─DB2TRAN(value)──────┤
Prog(DFHAKP ) Len(ððð5672) Ass Pro Ena Pri
Res(ððð) Use(ððððð1) Bel Cex Ful | ├─Doctemplate(value)──┤
Prog(DFHAMP ) Len(ð1ð8432) Ass Pro Ena
Res(ððð) Use(ððððð9) Any Cex Ful
Pri | ├─Enqmodel(value)─────┤
Prog(DFHAPATT) Len(ðððð632) Ass Pro Ena
Res(ðð5) Use(ðððð18) Any Cex Ful
Sha ├─FENode(value)───────┤
Prog(DFHBRCP ) Len(ððððððð) Ass Pro Ena Pri ├─FEPool(value)───────┤
Res(ððð) Use(ðððððð) Bel Cex Ful
Prog(DFHCCNV ) Len(ððððððð) Ass Pro Ena Pri ├─FEPropset(value)────┤
Res(ððð) Use(ðððððð) Any Cex Ful
D Prog(ERRTASK ) Len(ðððð448) Ass Pro Ena Pri
├─FETarget(value)─────┤
Res(ððð) Use(ðððððð) ├─FIle(value)─────────┤
├─JModel(value)───────┤
├─JOurnalname(value)──┤
Figure 45. Example of screen showing the discarding of resources ├─PArtner(value)──────┤
| ├─PROCesstype(value)──┤
Notes: ├─PROFile(value)──────┤
├─PROGram(value)──────┤
1. A CEMT INQUIRE display can be used to discard more | ├─Requestmodel(value)─┤
than one entry at a time. If you overtype another value ├─TClass(value)───────┤
as well as typing ‘D’, the ‘D’ is ignored. | ├─TCPIPservice(value)─┤
├─TDqueue(value)──────┤
2. When discarding a resource, the use of * or + in the ├─TErminal(value)─────┤
resource name is not allowed. ├─TRansaction(value)──┤
| └─TSmodel(name)───────┘

CEMT DISCARD
Options | Enqmodel(value)
| specifies the 8-character identifier of the resource to be
AUTInstmodel(value) | discarded.
specifies the name of the autoinstall model that is to be
removed. The name can be up to 8 characters long. The FENode
DISCARD AUTINSTMODEL command removes the This is described in the CICS Front End Programming
installed name of an autoinstall model from the Interface User's Guide.
autoinstall terminal model (AITM) table and the CICS
FEPool
catalog.
This is described in the CICS Front End Programming
Connection(value) Interface User's Guide.
specifies the 4-character identifier of the CONNECTION
FEPropset
definition to be discarded. When a connection is
This is described in the CICS Front End Programming
removed, all its associated sessions are also removed.
Interface User's Guide.
For deletion to be successful:
FETarget
A non-remote connection must be out of service. This is described in the CICS Front End Programming
A remote connection must have no active sessions. Interface User's Guide.
For MRO connections, the interregion FIle(value)

communications facility (IRC) must be closed. (You specifies the name of the file that is to be removed. The
can use CEMT SET IRC CLOSED to close it.) name can be up to 8 characters long. The DISCARD
FILE command removes the installed name of a file from
If the local system is a member of a VTAM generic
the CICS file control table and the CICS catalog.
resource group, APPC synclevel 2 connections must
not have any outstanding recovery information. JModel(value)
Other types of connection can be discarded, even if specifies the name of the installed journal model that
there is recovery work outstanding for them. you want to remove. The name can be up to 8
However, it is recommended that you do not discard characters long. The DISCARD JMODEL command
them if there is. You can use the INQUIRE removes the journal model name from the installed
CONNECTION RECOVSTATUS command to journal model table and the CICS catalog. It does not
check. affect any existing journals that have been defined using
the journal model name. These continue to use their
In some unusual circumstances, it is possible for existing definitions unless they are discarded using the
deletion of an LU61 connection to fail, even though the DISCARD JOURNALNAME command.
connection is out of service, because its sessions are
still in-service. If this happens, set the connection JOurnalname(value)
INSERVICE, then OUTSERVICE, then reissue the specifies the journal name that you want to remove. The
DISCARD command. name can be up to 8 characters long. The DISCARD
JOURNALNAME command removes the journal name
DB2Conn(value) from the journal table and the CICS catalog. It does not
Specifies that the currently installed DB2CONN is to be affect the VSAM data sets currently using the journal as
removed. You can only discard a DB2CONN when the a forward recovery log or autojournal; they continue to
CICS DB2 interface is not active. Note that discarding a use the existing definition until the data sets are closed.
DB2CONN also discards all currently installed
To discard journals defined with a numeric identifier for
DB2ENTRYs and DB2TRANs.
auto-journaling or forward recovery logs, specify the
DB2Entry(value) journal name as DFHJnn, where nn is the journal
Specifies the name of an installed DB2ENTRY to be number in the range 1–99.
removed. A DB2ENTRY can only be discarded when it Note: Specifying DFHJ01 on this command refers to a
is in a disabled state. user journal, DFHJ01.
DB2Tran(value) Any future reference to the journal name will cause it to
Specifies the name of the DB2TRAN to be removed. be reinstalled using the journal model resource in effect
Transaction IDs referenced by this DB2TRAN will be at that time.
routed to the pool after the DB2TRAN is removed.
PArtner(value)
| DOctemplate(value) specifies the name of the partner that is to be removed.
| Specifies the name of the document template to be The name can be up to 8 characters long. The
| removed. DISCARD PARTNER command removes the installed
name of a partner from the CICS side information table
and the CICS catalog.

CEMT DISCARD
| PROCesstype(value) TDqueue(value)
| Specifies the 8–character name of the Processtype to be specifies the name of the transient data queue that is to
| removed. Only disabled processtypes can be discarded. be removed from a running CICS system. The name can
| If you are using BTS in a sysplex, it is strongly be up to 4 characters long.
| recommended that you use CPSM to remove them.
Note: When you discard a transient data queue, an
PROFile(value) implicit DELETEQ command is issued to free the
specifies the name of the profile that is to be removed. control intervals used by the queue if the queue
The name can be up to 8 characters long. The is an intrapartition queue. If the queue is a
DISCARD PROFILE command removes the installed logically recoverable intrapartition queue, a
name of a profile from the CICS profile table (PFT) and syncpoint is taken after the DELETEQ request,
the CICS catalog. but before the queue definition is discarded. This
ensures that the associated control intervals
PROGram(value) have been freed before the definition is
specifies the name of the program, map set, or partition discarded.
set that is to be removed. The name can be up to 8
characters long. The DISCARD PROGRAM command TErminal(value)
removes the installed name of a program, map set, or specifies the name of the terminal to be removed. The
partition set from the CICS processing program table name can be up to 4 characters long. The DISCARD
(PPT) and the CICS catalog. TERMINAL command removes the installed name of a
terminal from the terminal control table (TCT) and the
| Requestmodel(value) CICS catalog.
| Specifies the name of the Requestmodel resource
Only terminals that use VTAM as an access method or
| definition to be removed.
consoles are eligible for deletion. Terminals that
TCLass(value) represent sessions cannot be deleted with DISCARD
specifies the name of the transaction class that is to be TERMINAL; use the DISCARD CONNECTION command
removed. The name can be up to 8 characters long. The instead.
DISCARD TCLASS command removes the installed
TRansaction(value)
name of a transaction class from the CICS program
specifies the name of the transaction that is to be
control table (PCT) and the CICS catalog.
removed. The name can be up to 8 characters long. The
Note: ‘TRANCLASS’ is also accepted as a synonym for DISCARD TRANSACTION command removes the
TCLASS. installed name of a transaction from the CICS program
control table (PCT) and the CICS catalog.
| TCPipservice(value)
| Specifies the name of the TCPIP service to be removed. | TSmodel(value)
| specifies the name of the TS model that is to be
| removed. The name can be up to 8 characters long. You
| cannot discard a TSmodel that is in use, or one which
| has a name begining with DFH.

CEMT INQUIRE COMMANDS CEMT INQUIRE AUTINSTMODEL
CEMT INQUIRE commands CEMT INQUIRE AUTINSTMODEL
Most CEMT requests either inquire about (INQUIRE), or Function: Find out whether a named autoinstall model is
change (SET) the status of one or more named instances of present.
a resource (such as a terminal), a particular subgroup of
resources (such as a class of terminals), or all resources of a
Description: The INQUIRE AUTINSTMODEL command
returns the names of all the autoinstall models installed in
particular type (such as all terminals).
your system. There is no CEMT SET AUTINSTMODEL
The INQUIRE command causes the status of the specified function, but the INQUIRE AUTINSTMODEL screens allow
resources to be displayed. The SET command makes the you to use the DISCARD function.
changes that you specify, and displays the new status of the
For information about autoinstall models, see the CICS
resources. No changes are made if there are syntax errors in
Resource Definition Guide.
the SET command.
If, for example, you want to inquire about a resource, enter Input: Press the Clear key and type CEMT INQUIRE
INQUIRE (or a suitable abbreviation) on the command line. AUTINSTMODEL (the minimum abbreviation is CEMT I AUTI).
The keywords you can use with CEMT INQUIRE are
You will get a display screen, a sample of which is shown
described in the rest of this section.
below.
If you want to perform those functions that are not concerned
If you do not type the name of a specific autoinstall model
with resource status, enter PERFORM (or a suitable
(the name can be up to 8 characters long—for example, cemt
abbreviation) on the command line. The keywords you can
i auti(dfhluðe2)), the names of all the autoinstall models
use with PERFORM are described in “CEMT PERFORM
will be displayed.
commands” on page 155.
And finally, if you want to change the attributes of a Sample screen

resource, enter SET (or a suitable abbreviation) on the
command line. The keywords you can use with SET are
described in “CEMT SET commands” on page 160. à IN AUTIN
ð
STATUS: RESULTS
Auti(DFHLUðE2)
If you enter INQUIRE, you get the following display: Auti(DFHLUðM2)
Auti(DFHLUðM3)
Auti(DFHLUðM4)
Auti(DFHLUðM5)
Auti(DFHLU2 )
Auti(DFHLU2E2)
Auti(DFHLU2E3)
à INQ %─Command Line
ð Auti(DFHLU2E4)
Auti(DFHLU2M2)
STATUS: ENTER ONE OF THE FOLLOWING OR HIT ENTER FOR DEFAULT %─Status Line Auti(DFHLU2M3)
Auti(DFHLU2M4)
AUTInstmodel FENode PROGram TSQueue %─┐Resources Auti(DFHLU2M5)
| AUTOinstall FEPOol REquestmodel UOW Auti(DFHLU3 )
| AUXtrace FEPRopset RRms UOWDsnfail Auti(DFHLU62T)
| CFdtpool FETarget STAtistics UOWLink Auti(DFHSCSP )
COnnection FIle STReamname Vtam Auti(DFH327ð )
| DB2Conn Gtftrace SYDumpcode Web + Auti(DFH327ðP)
DB2Entry INttrace SYStem
DB2Tran IRc TAsk
DEletshipped JModel TCLass
| DOctemplate JOurnalname TCPIP
| DSAs Line TCPIPService Figure 47. CEMT INQUIRE AUTINSTMODEL screen
DSName MODename TDqueue
DUmpds MONitor TErminal
| ENQ Netname TRAnsaction
| ENQModel PArtner TRDumpcode Note: The ‘+’ symbol in the left margin by the last item on
| EXci PROCesstype TSModel
| FEConnection PROFile TSPool the screen indicates that further model names are
SYSID=CICS APPLID=CICSHTC1 displayed when the PF8 key is pressed.
PF 1 HELP 3 END 5 VAR 9 MSG %─PF keys
á ñ
55──CEMT Inquire AUTInstmodel───┬─────┬───5%
Figure 46. Sample of the screen following either the INQUIRE or the └─All─┘
SET command
You can inquire about any of the displayed options by typing

Displayed fields
its keyword after INQUIRE on the command line. For
example, All Automatic switching occurs as necessary until the end of
INQUIRE PROGRAM this CICS session without the need for operator
intervention.
gives you the status of all programs, and for each program
gives its attributes. Full details are given in “CEMT INQUIRE
PROGRAM” on page 105.

CEMT INQUIRE AUTOINSTALL
CEMT INQUIRE AUTOINSTALL | Progauto

| Autoinstall for consoles is active, with the support
Function: Retrieve information about autoinstall values. | of the autoinstall control program (specified on the
| AIEXIT system initialization parameter). The
Description: The INQUIRE AUTOINSTALL command | autoinstall control program is required to provide
| displays information and parameters that control the | the terminal ID and, optionally, a delete-delay
| automatic installation (autoinstall) of VTAM terminals, APPC | period.
| connections, and MVS consoles. | Noauto
| Autoinstall for consoles is not active.
For background information about autoinstall, see the CICS
| Note: You can change this attribute by overtyping it
| with a different value.
Input: Press the Clear key and type CEMT INQUIRE
AUTOINSTALL (the minimum abbreviation is CEMT I AUTO). | Enablesatus(value)
| displays the overall status of the terminal autoinstall
You will see a display screen, a sample of which is shown | facility, indicating whether CICS is enabled to install
below. If you want to change any of the values shown, you | VTAM terminals and MVS consoles. The values
can tab to the highlighted fields and overtype them as | displayed are:
required.
| Enabled
Sample screen | CICS can currently install consoles, or terminals,
| or both. To determine which of these the facility is
| enabled for, check the values returned on the
à INQ AUTOINSTALL
ð | MAXREQS and CONSOLES options. Enabled is
STATUS: RESULTS - OVERTYPE TO MODIFY | returned for the following conditions:
Auto Max( 1ðð ) Pro( DFHZATDX ) Cur(ððð) Pro Ena
| Terminals
| MAXREQS not equal 0 and autoinstall
Figure 48. CEMT INQUIRE AUTOINSTALL screen | control program is enabled.
| Consoles
If you place the cursor against the result and press ENTER, | 1. CONSOLES displays FULLAUTO.
CICS displays an expanded format as shown in Figure 49. | 2. CONSOLES displays PROGAUTO and
| the autoinstall control program is
| enabled.
à IN AUTOIN
ð | Disabled
Autoinstall
Maxreqs( 1ðð ) | Neither consoles nor terminals can be
Program( DFHZATDX )
Curreqs( ððð ) | autoinstalled in CICS. DISABLED is returned for
| Consoles( Fullauto )
| the following conditions:
| Enablestatus( Enabled )
| Terminals
Figure 49. The expanded display of an individual entry | MAXREQS equal 0, or autoinstall control
| program is disabled.
| Consoles
55──CEMT Inquire AUTOinstall──5% | 1. CONSOLES displays NOAUTO.
| 2. CONSOLES displays PROGAUTO but
| the autoinstall control program is
Displayed fields | disabled.
AUTOinstall Curreqs(value)
identifies this panel as relating to terminal autoinstall. displays the number of autoinstall requests that are
| COnsoles(value) currently being processed. (This is not the number of
| displays the status of autoinstall for MVS consoles in the terminals currently installed using autoinstall.)
| CICS region. The values are: Maximum(value)
| Fullauto displays the largest number of autoinstall requests that
| Autoinstall for consoles is active without any are allowed to queue at any one time. (This is not the
| support from the autoinstall control program. CICS largest number of terminals that can be installed using
| generates the required terminal ID automatically autoinstall.)
| without calling the control program, and sets the Note: You can reset this value by overtyping it with a
| default delete-delay period (60 minutes) for the different value.
| console entry.

CEMT INQUIRE AUXTRACE
Program(value) CEMT INQUIRE AUXTRACE

displays the name of the program that controls the
autoinstall process. This is either the CICS-supplied Function: Retrieve information about the status of
default autoinstall program, DFHZATDX, or a auxiliary trace.
user-written program.
Note: You can reset this value by overtyping it with a Description: Auxiliary trace entries are made to a pair of
different value. CICS-controlled BSAM data sets, ‘A’ and ‘B’.
INQUIRE AUXTRACE tells you:

Whether the auxiliary trace data set is open or closed
Which of the auxiliary trace data sets is active, Cur(A) or
Cur(B)
Whether an auxiliary trace is in progress (started) or not
(stopped).
You can start, stop, or pause tracing, and specify that

automatic switching of the auxiliary data set is to occur when
needed. You can use the SWITCH option to change the data
set.
Instead of using the SET command, you can overtype your

changes on the INQUIRE screen after tabbing to the
appropriate field (see “Overtyping a display” on page 47).
For information on using auxiliary tracing, see the CICS

Problem Determination Guide. See also the description of the
CETR transaction, Chapter 16, “CETR—trace control” on
page 221.

AUXTRACE (the minimum abbreviation is CEMT I AUX).

below. If you want to change any of the values shown, you
can then tab to the highlighted or blank fields and overtype
them as required.
Sample screen
à I AUX
ð
STATUS: RESULTS - OVERTYPE TO MODIFY
Aux Cur(A) Sto
Figure 50. CEMT INQUIRE AUXTRACE screen
Note: There are blank fields on the screen where a value

does not apply or is ‘negative’; that is, the value
begins with ‘No’. To modify these fields, locate them
by tabbing (they appear in the same sequence as in
the expanded format), and overtype with input valid
for that field. You may find it more convenient to use
the expanded format when setting one of these
values, (negating is easier because you are
overtyping a displayed field with its negative causing
the result to become non-displayed).
If you place the cursor against the result and press ENTER,
CICS displays an expanded format as shown in Figure 51 on
page 56.

CEMT INQUIRE AUXTRACE
immediately following those that were written

à I AUX
ð before the PAUSE request.
Auxtrace
Curauxds(A) Stop Auxiliary tracing has stopped, and the trace data
Status( Stop )
Switchstatus( Noswitch ) set is closed.
Switchaction( )
Note: You can reset this value by overtyping it with a

Figure 51. The expanded display of an individual entry different value.
SWITCHAction(value) (input only field)

55──CEMT Inquire AUXtrace──5% specifies that the trace data set is to be switched. The
value is:
SWITCH
Displayed fields
Makes an immediate switch from the current
Auxiliary auxiliary trace data set to the alternate trace data
identifies this panel as relating to auxiliary trace. set.
Curauxds(value) SWITCHStatus(value)
displays a 1-character identifier of the current auxiliary displays whether automatic data set switching is to occur
data set, which can be ‘A’ or ‘B’. This value is blank if when the current auxiliary trace data set becomes full.
there is no auxiliary trace data set. The values are:
STatus(value) Noswitch
displays the status of auxiliary tracing in your CICS Switching does not occur without operator
system. The values are: intervention.
Start Auxiliary tracing is in progress (the auxiliary trace NExt Automatic switching occurs when the current trace
data set is open). data set is full, but not subsequently.
Pause ALl Automatic switching occurs as necessary until the

Auxiliary tracing has stopped, but the trace data end of this CICS session without the need for
set has been left open. A subsequent START operator intervention.
request causes trace entries to be written
different value.

CEMT INQUIRE CFDTPOOL
| CEMT INQUIRE CFDTPOOL | Displayed fields
| ALL
| Function: Retrieves information about coupling facility
| This is the default. CICS displays the names of all
| data table pools.
| installed CFDT pools.
| Description: INQUIRE CFDTPOOL returns information | CFdtpool(value)
| about any currently installed CFDT pool names. CICS installs | displays information about a named CFDT pool.
| these automatically whenever it installs a file resource
| CICS creates a resource entry for a CFDT pool when a
| definition that refers to a CFDT.
| file resource definition that refers to a coupling facility
| Input: Press the Clear key to clear the screen, and type | data table is first installed. The resource entry is
| CEMT INQUIRE CFDTPOOL (the minimum abbreviation is CEMT I | cataloged, and reinstalled from the catalog on a warm or
| CF). You get a display that lists the names and status of any | emergency restart.
| coupling facility data table pools to which CICS is connected | Note: You cannot discard CFDT pool entries other than
| through a CFDT server. Note that you cannot change any of | by a cold or initial start of the CICS region.
| the displayed information.
| Connstatus
| Sample screen | displays the connection status for the named CFDT pool.
| The values are:
| Connected
|
| à inquire cfdt
ð | The server for the coupling facility data table pool
| STATUS: RESULTS
| is available in this MVS image, and CICS is
| Cfd(DTPOOL1 ) Con
| currently connected to it.

| Unconnected
| SYSID=HA61 APPLID=CICSHA61 | The server for the coupling facility data table pool
| RESPONSE: NORMAL TIME: 15.54.22 DATE: ð9.ð3.98
| PF 1 HELP 3 END 5 VAR 7 SBH 8 SFH 9 MSG 1ð SB 11 SF | is available in this MVS image, but CICS is not
| currently connected to it.
| Figure 52. CEMT INQUIRE CFDTPOOL screen
| Unavailable
| | The server for the coupling facility data table pool
| 55──CEMT Inquire DOctemplate──┬─────────┬──────5 | is currently unavailable in the MVS image.
| ├─TSq─────┤
| ├─TDq─────┤
| ├─File────┤
| ├─EXitpgm─┤
| └─Member──┘
| 5──┬────────────┬──┬──────────┬──┬────────┬────5
| └─Name(name)─┘ ├─Append───┤ ├─Ebcdic─┤
| └─Noappend─┘ └─Binary─┘
| 5──┬────────────────────┬──────────────────────5
| └─Templatename(name)─┘
| 5──┬──────────────────────────┬──┬────────┬──5%
| └─Templatename──(──name──)─┘ ├─DDname─┤
| └─DSname─┘

CEMT INQUIRE CONNECTION

55──CEMT Inquire Connection──┬─(value)─┬───────5
└─ALl─────┘
Function: Retrieve information about system connections.
5──┬────────────────┬──┬────────────┬──────────5
Description: CEMT INQUIRE CONNECTION returns └─NEtname(value)─┘ ├─NOTPending─┤
└─PEnding────┘
information about the status of connections to a remote
system or to another CICS region. 5──┬────────────┬──┬───────────┬───────────────5
├─INService──┤ ├─ACquired──┤
└─OUtservice─┘ ├─RELeased──┤
You can reset the options either by typing the SET command
├─OBtaining─┤
or by overtyping at the appropriate place on the INQUIRE ├─FReeing───┤
screen. └─AVailable─┘
5──┬──────────────┬──┬─────────────┬───────────5
If you want to install a new connection definition when one is | ├─NOTSupported─┤ ├─Vtam────────┤
already installed, and: | ├─Unattempted──┤ ├─IRc─────────┤
| ├─COMPlete─────┤ ├─XM──────────┤
You are using APPC, | └─Failed───────┘ ├─INDirect────┤
You are using MRO, ├─XCf─────────┤
└─RConnection─┘
You are using remote,
5──┬──────┬──┬──────────┬──┬─────────────┬─────5
You are using LU6.1, you must set the connection ├─EXci─┤ ├─XOk──────┤ ├─RECovdata───┤
OUTSERVICE and, if it is VTAM-connected, release it ├─APpc─┤ └─XNotdone─┘ ├─NORecovdata─┤
└─Lu61─┘ └─NRs─────────┘
before using the CEDA INSTALL commands for your
new definition. 5──┬───────────────┬──┬───────────────────┬────5
└─Grname(value)─┘ └─Membername(value)─┘
See the CICS Resource Definition Guide for further
5──┬─────────────────────┬─────────────────────5
information about connections. └─REMotesystem(value)─┘
Input: Press the Clear key to clear the screen. There are 5──┬──────────────┬──┬─────────────────┬──5%
└─RNAme(value)─┘ └─RNEtname(value)─┘
Type CEMT INQUIRE CONNECTION (the minimum
abbreviation is CEMT I C). You get a display that lists the (value)
current status. specifies one or more names (1–4 characters) defined
for an interregion communication (IRC) or an intersystem
Type CEMT INQUIRE CONNECTION (CEMT I C) followed by
communication (ISC) connection.
as many of the other attributes as are necessary to limit
the range of information that you require. So, for ALl
example, if you enter cemt i c ins acq, the resulting is the default.
display will show you the details of only those
connections that are in service and acquired. Sample screen
You can then tab to the highlighted or blank fields and
overtype them with the required values.
à IN CONN
ð
Con(G1GA) Ins Irc Exci
Con(ISC1) Net(AUHZCIC1) Ins Acq Vta Appc Xok Unk
Con(MRO2) Net(CICSHAA1) Ins Acq Irc Unk
Con(MRO6) Net(CICSHAB1) Ins Acq Xcf
Figure 53. CEMT INQUIRE CONNECTION screen


If you place the cursor against a specific entry in the list and access method is defined as IRC or XM in the
press ENTER, CICS displays an expanded format as shown connection definition.
in Figure 54 on page 59.
RConnection
The connection is remote—that is, it is owned by
another CICS system.
à IN CONN
ð
RESULT - OVERTYPE TO MODIFY Affinity (input only field)
Connection(MRO5)
Netname(CICSHAA3) specifies, where CICS is a member of a VTAM generic
Pendstatus( Notpending )
Servstatus( Inservice )
Connstatus( Acquired )
resource group, that VTAM is to end an affinity owned
Accessmethod(Irc)
Purgetype( )
by CICS. This option is valid only for APPC and LU61
Protocol()
Xlnstatus()
connections. The connection must be out of service and
Recovstatus( Norecovdata )
Uowaction( ) in NORECOVDATA state. The value is:
| Cqp( Notsupported )
Grname()
Membername() Endaffinity
Affinity( )
Remotesystem()
Rname()
VTAM is to end an affinity owned by CICS.
Rnetname()
Connection(value)
identifies this panel as relating to system connections,
Figure 54. The expanded display of an individual entry and displays the 4-character name by which the
connection is known.
Displayed fields
Connstatus
Accessmethod
displays the state of the connection between CICS and a
displays the access method in use for this connection.
remote system. The remote system can be an APPC or
The values are:
an MRO partner identified by (value) on the CEMT
Vtam INQUIRE CONNECTION command. The ACQUIRED
The connection is used for intersystem and RELEASED values are common to both APPC and
communication (ISC). MRO; the others are unique to APPC. The values are:
IRc The connection is used for multiregion operation ACquired (APPC and MRO)
(MRO), and has been defined to use the The CONNECTION is acquired. The criteria for
interregion communication (IRC) program for ACQUIRED for VTAM links are:
communication. If the CONNECTION is
The partner LU has been contacted.
ACQUIRED, the MRO partner is running on the
same MVS image. If the CONNECTION is Initial CNOS exchange has been done.
RELEASED, the MRO partner may not be on the The criteria for ACQUIRED for MRO links are:
same MVS image; if it is not, the XCF access
method will be used when the connection Both sides of the link are in service.
becomes ACQUIRED. Both sides of the link are successfully logged
XM The connection is used for multiregion operation on to the CICS interregion communication
(MRO) and has been defined to use MVS program (DFHIRP).
cross-memory (XM) services for communication. If A connection request by each side has been
the CONNECTION is ACQUIRED, the MRO successful for at least one session, and
partner is running on the same MVS image. If the therefore each side can send and receive
CONNECTION is RELEASED, the MRO partner data.
may not be on the same MVS image; if it is not,
RELeased (APPC and MRO)
the XCF access method will be used when the
The connection is released. Although the
connection becomes ACQUIRED.
connection might be in service, it is not usable.
INDirect
In the case of an MRO link, the released status
Communication between the local CICS system
can be caused by any one of a number of
and the system defined by this connection is
conditions. For example, it could be because the
through the system named in the INDSYS
CICS region on the other side has not yet
operand of the connection definition.
initialized, or not yet signed on to the CICS
XCf The connection is used for multiregion operation interregion communication program (DFHIRP); or
(MRO), and communication uses the cross-system it could be because CICS interregion
coupling facility (XCF) of MVS. XCF is used for communication may have been closed on the
MRO links between CICS regions on different other side, or the connection on the other side
MVS images within an MVS sysplex. It is selected may have been set out of service.
dynamically by CICS for such links when the

OBtaining (APPC only) Pendstatus (appc and mro only)

The connection is being acquired. The connection displays whether there are any pending units of work for
remains in the OBTAINING state until all the this connection. The values are:
criteria for ACQUIRED have been met.
NOTPending
FReeing (APPC only) There has been no mismatch of lognames with the
The connection is being released. partner.
AVailable (APPC only) Note: MRO connections to pre-CICS Transaction
The connection is acquired but there are currently Server for OS/390 systems do not use
no bound sessions because they were unbound lognames. Therefore, for these
for limited resource reasons. connections, PENDSTATUS is always
NOTPENDING.
Connstatus can be reset with Acquired or Released.
PEnding
| Cqp(value) There is resynchronization work outstanding for
| displays the status of the connection quiesce protocol for the connection but the partner system has
| the connection. The values are: performed an initial start, preventing completion of
the resynchronization process. (If the partner is a
| NOTSupported
pre-CICS Transaction Server for OS/390 system,
| The connection quiesce protocol is not supported
its performing a cold start has the same effect.)
| for this connection.
The units of work associated with the connection
| Unattempted may need to be individually investigated and
| CICS has not attempted to use the connection forced to commit or backout. Alternatively, the
| quiesce protocol (because the connection has not units of work can be unilaterally committed or
| been released). backed out, according to their associated
transaction definitions, by using the SET
| COMPlete
CONNECTION NOTPENDING command.
| The connection quiesce protocol completed
| succesfully when the connection was release. The If this is an APPC connection, no new syncpoint
| status reverts to UNATTEMPTED when the work (that is, work involving synclevel 2 protocols)
| connection is re-acquired. can be transmitted across it until a SET
CONNECTION NOTPENDING command has
| FAiled
been issued. This restriction does not apply to
| The connection quiesce protocol failed (for
MRO connections.
| instance, becasue a session failed while the
| protocol was executing). The status reverts to If you are not concerned by the loss of
| UNATTEMPTED when the connection is synchronization caused by the initial (or cold) start
| re-acquired. of the partner, you can cause the SET
CONNECTION NOTPENDING command to be
Grname(value) (appc only)
issued automatically by specifying
displays (for an APPC connection to a generic resource
XLNACTION(FORCE) on the CONNECTION
when this system is also a generic resource) the
definition.
8-character generic resource name of the connected
system. Otherwise this field is blank. CICS assumes that
Pendstatus can be reset with Notpending.
the partner is a generic resource if the two NETNAMEs
sent with a BIND are different. Thus, information may For further information about pending units of work, see
be displayed for a partner that is not a generic resource the CICS Intercommunication Guide.
but which uses XRF.
Protocol
Membername(value) displays the protocol in use if this is a VTAM or external
displays (for an APPC connection to a generic resource CICS interface connection. The values are:
when this system is also a generic resource) the
APpc
8-character member name (applid) of the connected LU.
The connection uses the VTAM LUTYPE6.2
Otherwise this field is blank. CICS assumes that the
protocol for intersystem communication, or is
partner is a generic resource if the two NETNAMEs sent
remote.
with a BIND are different. Thus, information may be
displayed for a partner that is not a generic resource but EXci The connection uses the external CICS interface
which uses XRF. for communication between CICS and a non-CICS
client program.
NEtname(value)
displays the 8-character name by which the remote
system is known to the network.

Lu61 An ‘AIDS CANCELED’ message appears on the

The connection uses the VTAM LUTYPE6.1 CEMT panel whenever AIDs are deleted using the
protocol for CICS-to-CICS or CICS-to-IMS CANCEL option of the CEMT SET CONNECTION
intersystem communication. command.
Purgetype (input only field) FCancel

specifies how associated transactions are to be purged. All AIDs, including system AIDs, queuing for the
The values are: specified connection are to be canceled. See
Table 1 for a list of those system AIDS that
PUrge (vtam only and irc only) require FCANCEL to remove them. This can lead
Transactions running on the connected system are to unpredictable results and should be used only
abnormally terminated. Transactions are in exceptional circumstances.
terminated only if system and data integrity can be
Note: FCANCEL does not remove transient data
maintained. A transaction is not purged if its
AIDs with an associated triggered task.
definition specifies SPURGE=NO.
These aids may be removed by purging
FORCEPurge (vtam only) the associated task.
All transactions running on sessions on the
An ‘AIDS CANCELED’ message appears on the
connected system are immediately terminated
CEMT panel whenever AIDs are deleted using the
abnormally. This can lead to unpredictable results
FCANCEL option of the CEMT SET
and should be used only in exceptional
CONNECTION command.
circumstances.
In some extreme cases (for example, if an error Recovstatus (appc and mro only)
occurs during backout processing), CICS might displays whether there is resynchronization work
terminate abnormally. outstanding for this connection. The connection may
never have been connected, or may have been quiesced
CAncel
and all resynchronization work completed, or disrupted
Automatic initiate descriptors (AIDs) queuing for
without quiesce—in which case resynchronization may
the specified connection are to be canceled.
be necessary. The values are:
AIDs representing scheduled and allocated
NORecovdata
requests waiting in the local CICS system for the
Neither side has recovery information outstanding.
specified connection are canceled. However, TD
AIDs with an associated triggered task already NRs CICS does not have recovery outstanding for the
started will not be canceled. In addition, the connection, but the partner may have.
following CICS system AIDs are not purged unless
RECovdata
FCANCEL is specified.
There are in-doubt units of work associated with
the connection, or there are outstanding resyncs
Table 1. System AIDs requiring FCANCEL to remove them awaiting FORGET on the connection.
Description Tranid Resynchronization takes place when the
Remote delete AIDs connection next becomes active, or when the
UOW is unshunted.
Remote scheduler AIDs CRSR
LU6.2 service manager 1 AIDs CLS1 If there is recovery outstanding, on completion of
LU6.2 service manager 3 AIDs CLS3 exchange of lognames either resynchronization takes
place or, in the case of a cold exchange, the PENDING
Remote scheduler PURGE AIDs CRSQ
condition is created.
Resource manager resync AIDs CRSY
Recovstatus can be reset with Norecovdata.
Autoinstalled terminal delete AIDs CATD
REMotesystem(value)
Autoinstalled terminal restart AIDs CATR
displays the 4-character name of a connection, if the
subject of the inquiry is a remote or an indirect
When a canceled SCHEDULE request is found to connection. In either case, the named connection can be
have a precursor in a remote CICS system, that either a connection entry that links towards the TOR, or
is, the AID was originally scheduled in a remote an indirect connection that provides the netname of the
system, the remote AID is canceled TOR.
asynchronously.
If the subject of the inquiry is an indirect connection, the
Message DFHTF0100 is written to CSMT to value of REMOTESYSTEM is taken from the INDSYS
indicate how many AIDs have been deleted for the option of the CONNECTION definition.
connection and how many remain.
Otherwise this field is blank.

RNAme(value) FORCEUow
displays the 4-character name by which this connection All UOWs shunted due to the failure of this
is known in a remote system, if the subject of the inquiry connection are to be forced to BACKOUT or
is a remote connection. COMMIT, as specified on the INDOUBT option of
the TRANSACTION definition.
RNEtname(value)
displays the 8-character netname of the owning TOR, if Resync
the subject of this inquiry is a remote connection. If it is Any UOWs shunted due to the failure of this
blank, but the connection is remote, the system named connection are to be retried (that is, exchange
in the REMOTESYSTEM field has not been installed, lognames resynchronization for this connection is
and no value was specified for the REMOTESYSNET to be attempted). This process should normally be
option when the connection was defined. started automatically when a connection is
acquired or when a UOW is unshunted.
Servstatus
displays whether the system can receive and send data. Xlnstatus
The values are: displays the status of the exchange lognames (XLN)
process. The values are:
INService
The system is in service; that is, it is available for XOk (appc only)
use. The exchange log names (XLN) process for the
APPC connection has completed successfully.
OUtservice
The system is out of service; that is, it is not XNotdone (APPC only)
available for use. The exchange log names (XLN) flow for the APPC
connection has not completed successfully. The
Note: You can reset this value by overtyping it with a CSMT log can contain information relating to this
different value. state. Synchronization level 2 conversations are
not allowed on the connection, but synchronization
Uowaction (input-only field) levels 0 and 1 are still allowed.
specifies that the normal resynchronization process is to
be partially overridden. The value specifies the type of No status is displayed if exchange log names is not
decision to be taken for any units of work that become applicable. This can be because the link:
in-doubt due to a failure of the connection; the decisions
are recorded and any data inconsistencies are reported Is released
when the connection is next acquired. The values are: Is MRO, LU6.1, or single-session APPC
Backout Does not support synchronization level 2
All UOWs shunted due to the failure of this conversations.
connection are to be backed out.
For information about the APPC exchange log names
COMMit process, see the CICS Intercommunication Guide.
All UOWs shunted due to the failure of this
connection are to be committed.

CEMT INQUIRE DB2CONN
CEMT INQUIRE DB2CONN may be an accounting record produced for each

UOW.
Function: Retrieves information about the CICS DB2 Txid The CICS DB2 attachment facility causes an
connection. accounting record to be produced when the
transid using the thread changes.
Description: INQUIRE DB2CONN returns information
about the attributes of the currently installed DB2CONN, Because pool threads are typically used by a
which defines the connection to DB2. number of different transaction IDs, there is an
increased chance that a transaction containing
Note that because there can be only one DB2CONN installed multiple UOWs will use a different thread for each
at a time, the name of the DB2CONN is not required on UOW (assuming the thread is released at
input. syncpoint. In this case, an accounting record may
be produced for each UOW.
Input: Press the Clear key to clear the screen, and type None
CEMT INQUIRE DB2CONN. You get a display that lists the No accounting records are required for
current status. You can then tab to the highlighted or blank transactions using pool threads.
DB2 does, however, produce at least one
Sample screen accounting record for each thread when the thread
is terminated. Additionally, authorization changes
cause accounting records to be produced.
à inquire db2conn
ð Authid
Accountrec( None ) Priority( High ) returns an id to be used for security checking when
Authid( ) Purgecyclem( ðð )
Authtype( Userid ) Purgecycles( 3ð ) using pool threads. If an AUTHId is returned, AUTHType
Comauthid( ) Signid( CICSHTC1 )
Comauthtype( Cuserid )
Comthreadlim( ððð1 )
Security( )
Standbymode( Reconnect )
is not applicable.
Comthreads(ðððð) Statsqueue( CDB2 )
Connecterror( Sqlcode ) Tcblimit( ðð12 )
Connectst( Notconnected ) Tcbs(ðððð) Authtype
Db2id( DB2A ) Threaderror(N9ð6d)
Db2release() Threadlimit( ððð3 ) returns the type of id to be used for security checking
Drollback(Rollback) Threads(ðððð)
Msgqueue1( CDB2 ) Threadwait( Twait ) when using pool threads. If an AUTHType is returned,
Msgqueue2( )
Msgqueue3( ) AUTHid is blank. The values are:
Nontermrel( Release )
Plan( )
Planexitname( DSNCUEXT ) Group
The 8-character USERID and the connected group
Figure 55. CEMT INQUIRE DB2CONN screen name are used as the authorization ID. The
following table shows how these two values are
interpreted by DB2.
55──CEMT Inquire DB2Conn──5%
IDs passed to DB2 How DB2 interprets values
CICS sign-on user ID Represents the primary DB2
Displayed fields (USERID) authorization ID.
Accountrec RACF connected If the RACF list of group options

group name is not active, DB2 uses the
returns the minimum amount of DB2 accounting required
connected group name supplied
for transactions using pool threads. The specified
by the CICS attachment facility
minimum may be exceeded, as described in the as the secondary DB2
following options. The values are: authorization ID. If the RACF list
of group options is active, DB2
UOW ignores the connected group
The CICS DB2 attachment facility causes an name supplied by the CICS
accounting record to be produced for each UOW, attachment facility, but the value
assuming that the thread is released at the end of appears in the DB2 list of
the UOW. secondary DB2 authorization
IDs.
Task
The CICS DB2 attachment facility causes a
If no RACF group ID is available for this USERID,
minimum of one accounting record to be produced
an 8-character field of blanks is passed to DB2 as
for each CICS task.
the group ID.
A transaction containing multiple UOWs may use
a different thread for each of its UOWs (assuming Sign The SIGNID parameter of the DB2CONN is used
the thread is released at syncpoint). The result as the resource authorization ID.

Tern The terminal identification (four characters padded If no RACF group ID is available for this USERID,
to eight) is used as an authorization ID. An an 8-character field of blanks is passed to DB2 as
authorization ID cannot be obtained in this manner the group ID.
if a terminal is not connected with the transaction.
Csign
If a transaction is started (using a CICS command) The SIGNID parameter of the DB2CONN is used
and has no terminal associated with it, as the resource authorization ID.
AUTHTYPE(TERM) should not be used.
Cterm
Tx The transaction identification (four characters The terminal identification (four characters padded
padded to eight) is used as the authorization ID. to eight) is used as an authorization ID. An
authorization ID cannot be obtained in this manner
Opid
The user operator identification associated with
the userid, associated with the CICS transaction, If a transaction is started (using a CICS command)
is used as the authorization ID (three characters and has no terminal associated with it,
padded to eight). COMAUTHTYPE(CTERM) should not be used.
Userid Ctx The transaction identification (four characters
The 8-character USERID associated with the padded to eight) is used as the authorization ID.
CICS transaction is used as the authorization ID.
Copid
When the DB2 sample sign-on exit DSN3@SGN The operator identification associated with the
is used with AUTHTYPE(USERID), the exit sends userid that is associated with the CICS transaction
the USERID to DB2 as the primary authorization is used as the authorization ID (three characters
ID and the RACF group ID to DB2 as the padded to eight).
secondary ID. When the sample sign-on exit is
Cuserid
used, there is no difference between
The 8-character USERID associated with the
AUTHTYPE(USERID) and AUTHTYPE(GROUP).
Comauthid When the DB2 sample sign-on exit DSN3@SGN
returns an ID to be used for security checking when is used with COMAUTHTYPE(CUSERID), the exit
using command threads. If COMAUTHType is returned, sends the USERID to DB2 as the primary
COMAUTHid is not applicable. authorization ID and the RACF group ID to DB2
as the secondary ID. When the sample sign-on
Comauthtype
exit is used, there is no difference between
returns the type of ID to be used for security checking
COMAUTHTYPE(CUSERID) and
when using command threads. If COMAUTHType is
COMAUTHTYPE(CGROUP).
returned, COMAUTHid is blank. The values are:
Comthreads
Cgroup returns the current number of active command threads.
The 8-character USERID and the connected group
name are used as the authorization ID. The Comthreadlim
following table shows how these two values are returns the current maximum number of command
interpreted by DB2. threads the CICS DB2 attachment allows active before
requests overflow to the pool.
Connecterror
returns a value when CICS is not connected to DB2
(USERID) authorization ID.
because the adapter is in 'standby mode'. The value
RACF connected If the RACF list of group options shows how this information is to be passed back to an
group name is not active, DB2 uses the application that has issued a SQL request. The values
connected group name supplied
are:
by the CICS attachment facility
as the secondary DB2 Abend
authorization ID. If the RACF list
The application is abended with abend AEY9.
ignores the connected group Sqlcode
name supplied by the CICS The application receives a -923 SQLCODE.
attachment facility, but the value
appears in the DB2 list of
secondary DB2 authorization
IDs.

Connectst Norelease
returns the status of the CICS DB2 connection. The non-terminal transactions do not release threads
values are: for reuse at intermediate syncpoints.
Connected Plan
CICS is connected to DB2. returns the name of the plan used for the pool. If a plan
name is returned, PLANEXITNAME is blank,
Notconnected
CICS is not connected to DB2. Planexitname
Connecting returns the name of the dynamic plan exit used for pool
CICS is currently attempting to connect to DB2. threads. If a PLANEXITNAME is returned, PLAN is
blank,
Disconning
CICS is currently disconnecting from DB2. Priority
returns the priority of the pool thread subtasks relative to
DB2id
the CICS main task (QR TCB). CVDA values are:
returns the name of the DB2 subsystem that the CICS
DB2 attachment is connected to or is to connect to. High subtasks attain a higher priority than the CICS
main task from which the subtask was generated.
DB2release
returns a four-character value indicating the version and Equal
release level of the DB2 susbsytem CICS is connected subtasks have equal priority with the CICS main
to. When CICS is not connected to DB2, blanks are task.
returned. Low subtasks have a lower priority than the CICS main
task.
Drollback
returns a value showing whether the CICS DB2 Purgecyclem
attachment is to initiate a SYNCPOINT ROLLBACK if a returns in minutes the length of the protected thread
transaction is selected as victim of a deadlock resolution. purge cycle. The range for PURGECYCLEM is 0-59.
The values are:
A protected thread is not terminated immediately when it
Rollback is released. It is terminated only after two completed
the attachment facility issues a sync point rollback purge cycles, if it has not been reused in the meantime.
before returning control to the application. An SQL Hence if the purge cycle is set to 30 seconds after it is
return code of -911 is returned to the program. released, a protected thread will be purged 30 - 60
seconds after it is released. An unprotected thread is
Norollback
terminated when it is released (at syncpoint or end of
the attachment facility does not initiate a rollback
task) if there are no other transactions waiting for a
for a transaction. An SQL return code of -913 is
thread on that DB2ENTRY.
returned to the application.
Purgecycles
Msgqueue1
returns in seconds the length of the protected thread
returns the name of the first transient data destination to
purge cycle. The range for PUrgecycles is 30-59.
which unsolicited messages from the CICS DB2
attachment are sent. A protected thread is not terminated immediately when it
is released. It is terminated only after two completed
Msgqueue2
purge cycles, if it has not been reused in the meantime.
returns the name of the second transient data
Hence if the purge cycle is set to 30 seconds after it is
destination to which unsolicited messages from the CICS
released, a protected thread will be purged 30 - 60
DB2 attachment are sent.
seconds after it is released. An unprotected thread is
Msgqueue3 terminated when it is released (at syncpoint or end of
returns the name of the third transient data destination to task) if there are no other transactions waiting for a
which unsolicited messages from the CICS DB2 thread on that DB2ENTRY.
attachment are sent.
Signid
Nontermrel returns the authorization ID to be used by the CICS DB2
returns a value showing whether non-terminal attachment when signing on to DB2 for pool and DB2
transactions are to release threads for reuse at entry threads specifying AUTHTYPE(SIGNID) and
intermediate syncpoints. CVDA values are: command threads specifying COMAUTHTYPE(CSIGN).
Release Security
non-terminal transactions release threads for has no meaning for INQUIRE. It is supplied to allow
reuse at intermediate syncpoints. overtyping with the REBUILD option, to initiate a CEMT

SET DB2CONN. See SECURITY(REBUILD) on occurred. The transaction must be terminated and
page170. reinitialized before it is allowed to issue another
SQL request.
Standbymode
returns the action to be taken by the CICS DB2 N906D
attachment if DB2 is not active when an attempt is made A transaction dump is taken and the DSNCSQL
to start the connection from CICS to DB2. The values RMI associated with the transaction is not to be
are: disabled. The transaction receives a -906
SQLCODE if another SQL is issued, unless the
Noconnect transaction issues SYNCPOINT ROLLBACK.
The CICS DB2 attachment terminates. SYNCPOINT without the ROLLBACK option
Connect results in an ASP3 or ASP7 abend. The
The CICS DB2 attachment goes into 'standby transaction dump records an abend of AD2S,
mode' to wait for DB2. AD2T or AD2U.
Reconnect N906
The CICS DB2 attachment goes into 'standby The DSNCSQL RMI associated with the
mode' and waits for DB2. Having connected to transaction is not to be disabled. The transaction
DB2, if DB2 subsequently fails the CICS DB2 receives a -906 SQLCODE if another SQL request
attachment reverts again to standby mode and is issued, unless the transaction issues a
subsequently reconnects to DB2 when it comes up SYNCPOINT ROLLBACK. SYNCPOINT without
again. the ROLLBACK option results in an ASP3 or
ASP7 abend.
Statsqueue
returns the transient data destination for CICS DB2 Threadlimit
attachment statistics produced when the CICS DB2 returns the current maximum number of pool threads the
attachment is shutdown. CICS DB2 attachment allows active before requests are
made to wait or are rejected (see THREADWait).
Tcbs
returns the current number of subtask TCBs attached to Threads
service command, pool, and DB2ENTRY threads. returns the current number of active pool threads.
Tcblimit Threadwait
returns the current maximum number of subtasks that returns a value showing whether transactions should
can be identified to DB2. wait for a pool thread or be abended if the number of
active pool threads reaches the threadlimit number. The
Threaderror values are:
returns the processing that is to occur following a create
thread error. The values are: Twait
If all threads are busy, a transaction waits until
Abend one becomes available.
Notwait
| For a second or subsequent SQL error the If all threads are busy, a transaction is terminated
transaction abends with abend code AD2S, AD2T with an abend code AD3T.
or AD2U, dependent on the type of error that

CEMT INQUIRE DB2ENTRY
CEMT INQUIRE DB2ENTRY 55──CEMT Inquire DB2Entry(data-area)──┬───────────────┬──────5

└─AT(data-area)─┘
Function: Returns the attributes of the DB2ENTRY that 5──┬───────┬──┬──────────────────┬──┬───────────────────┬────5
├─START─┤ ├─ACCOUNTREC(cvda)─┤ └─AUTHID(data-area)─┘
defines resources to be used by a specific transaction or by ├─END───┤ ├─UOW──────────────┤
a group of transactions when accessing DB2. └─NEXT──┘ ├─TASK─────────────┤
├─TXID─────────────┤
└─NONE─────────────┘
Description: The entry is identified by the name with
which it was defined in CEDA. 5──┬────────────────┬──┬───────────────────┬─────────────────5
├─AUTHTYPE(cvda)─┤ ├─DISABLEDACT(cvda)─┤
├─GROUP──────────┤ ├─ABEND─────────────┤
Input: For RCTs migrated to the CSD, the name is the ├─SIGN───────────┤ ├─SQLCODE───────────┤
name of the first transaction on the DSNCRCT ├─TERM───────────┤ └─POOL──────────────┘
├─TX─────────────┤
TYPE=ENTRY statement unless the RDONAME parameter ├─OPID───────────┤
has been specified. └─USERID─────────┘
5──┬─────────────────┬──┬────────────────────┬───────────────5
Sample screen ├─DROLLBACK(cvda)─┤ ├─ENABLESTATUS(cvda)─┤
├─ROLLBACK────────┤ ├─ENABLED────────────┤
└─NOROLLBACK──────┘ ├─DISABLED───────────┤
└─DISABLING──────────┘
à inquire db2entry
ð 5──┬─────────────────┬──┬─────────────────────────┬──────────5
STATUS: RESULTS - OVERTYPE TO MODIFY └─PLAN(data-area)─┘ └─PLANEXITNAME(data-area)─┘
Db2e(DB2ENT1 ) Use Ena Poo Hig Pro( ðððð ) Pth(ðððð)
Threadl( ðððð ) Threads(ðððð) Tpo Plane( DSNCUEXT 5──┬────────────────┬──┬───────────────────────┬─────────────5
Db2e(DB2ENT2 ) Use Ena Poo Hig Pro( ðððð ) Pth(ðððð)
Threadl( ðððð ) Threads(ðððð) Tpo Plane( DSNCUEXT ├─PRIORITY(cvda)─┤ └─PROTECTNUM(data-area)─┘
├─HIGH───────────┤
├─EQUAL──────────┤
└─LOW────────────┘
Figure 56. CEMT INQUIRE DB2ENTRY screen
5──┬─────────────────────┬──┬────────────────────────┬───────5
If you place the cursor against the result and press ENTER, └─PTHREADS(data-area)─┘ └─THREADLIMIT(data-area)─┘
an expanded format is displayed as shown in Figure 57. 5──┬────────────────────┬──┬──────────────────┬─────────────5%
└─THREADS(data-area)─┘ ├─THREADWAIT(cvda)─┤
├─TWAIT────────────┤
├─NOTWAIT──────────┤
└─TPOOL────────────┘
à inquire db2entry
ð
Db2entry(DB2ENT1)
Accountrec( None )
Authtype( Userid )
Enablestatus( Enabled )
Displayed fields
Disabledact( Pool )
Priority( High )
Protectnum( ðððð ) ACcountrec
Pthreads(ðððð)
Threadlimit( ðððð ) returns the minimum amount of DB2 accounting record
Threads(ðððð)
Threadwait( Tpool ) required for transactions using this DB2ENTRY. The
Plan( )
Planexitname( DSNCUEXT ) specified minimum may be exceeded, as described in
Authid( )
Drollback(Rollback) the following options. The values are:
UOW
Figure 57. The expanded display of an individual entry The CICS DB2 attachment facility causes an
accounting record to be produced for each UOW,
assuming that the thread is released at the end of
the UOW.
TAsk
minimum of one accounting record for each CICS
task to be produced.
a different thread for each of its UOWs (assuming
the thread is released at syncpoint). The result
may be an accounting record produced for each
UOW.
TXid The CICS DB2 attachment facility causes an
accounting record to be produced when the
transid using the thread changes.
This option applies to DB2ENTRYs that are used
by more than one transaction ID. As threads are
typically released at syncpoint, a transaction

containing multiple UOWs may use a different OPid

thread for each UOW. The result may be that an The operator identification associated with the
accounting record is produced for each UOW. userid that is associated with the CICS transaction
is used as the authorization ID (three characters
NOne
padded to eight).
No accounting records are required for
transactions using threads from this DB2ENTRY. USerid
accounting record for each thread when the thread
is terminated. Additionally, authorization changes When the DB2 sample sign-on exit DSN3@SGN
cause accounting records to be produced. is used with AUTHTYPE(USERID), the exit sends
the USERID to DB2 as the primary authorization
AUTHId
ID and the RACF group ID to DB2 as the
returns an ID to be used for security checking when
secondary ID. When the sample sign-on exit is
using pool threads. If an AUTHId is returned, AUTHType
is not applicable.
AUTHTYPE(USERID) and AUTHTYPE(GROUP).
AUTHType
DIsabledact
returns the type of ID to be used for security checking
returns a value showing what CICS is to do with new
for threads on this DB2ENTRY. If an AUTHType is
transactions accessing DB2ENTRY when it has been
returned, AUTHid is blank. The values are:
disabled or is disabling. If DISABLEDACT is not
Group specified, and DB2ENTRY is disabled, new requests are
The 8-character userid and the connected group routed to the pool by default. The values are:
name are used as the authorization ID. The
Pool The CICS DB2 attachment facility routes the
following table shows how these two values are
request to the pool. Message DFHDB2072 is sent
interpreted by DB2.
to the transient data destination specified by
IDs passed to DB2 How DB2 interprets values MSGQUEUEn on the DB2CONN for each
transaction routed to the pool.
(USERID) authorization ID. ABend
RACF connected If the RACF list of group options
The CICS DB2 attachment facility abends the
group name is not active, then DB2 uses the transaction.The abend code is AD26.
connected group name supplied SQlcode
by the CICS attachment facility An SQLCODE is returned to the application
as the secondary DB2
indicating that the DB2ENTRY is disabled.
of group options is active, DB2 DRollback
ignores the connected group
returns returns a value showing whether the CICS DB2
name supplied by the CICS
attachment should initiate a SYNCPOINT rollback if a
appears in the DB2 list of transaction is selected as victim of a deadlock resolution.
secondary DB2 authorization The values are:
IDs.
Rollback
The attachment facility issues a sync point rollback
If no RACF group ID is available for this USERID, before returning control to the application. An SQL
then an 8-character field of blanks is passed to return code of -911 is returned to the program.
DB2 as the group ID.
NORollback
Sign The SIGNID parameter of the DB2CONN is used The attachment facility does not initiate a rollback
as the resource authorization ID. for this transaction. An SQL return code of -913 is
TErm returned to the application.
The terminal identification (four characters padded
ENAablestatus
to eight) is used as an authorization ID. An
returns a cvda indicating whether the DB2ENTRY can
authorization ID cannot be obtained in this manner
be accessed by applications. The values are:
If a transaction is started (using a CICS command) Enabled
and has no terminal associated with it, The DB2ENTRY can be accessed by applications.
AUTHTYPE(TERM) should not be used. DB2ENTRY is installed in an ENABLED state.
TX The transaction identification (four characters Disabled

padded to eight) is used as the authorization ID. The DB2ENTRY cannot be accessed by
applications.

DISabling available for reuse by a new transaction. If no

The DB2ENTRY is in the process of being transaction has reused the thread by the time it has
disabled. New transactions cannot access the been processed by 2 purge cycles, the thread is
DB2ENTRY. Existing transactions using the terminated.
DB2ENTRY will be allowed to complete unless the
THREADS
DB2ENTRY is being disabled with the FORCE
returns the current number of threads active for this
option.
DB2ENTRY.
PLAN
THREADLimit
returns the name of the plan to be used for this
returns the current maximum number of threads for this
DB2ENTRY. If PLAN is returned, PLANEXITNAME is
DB2ENTRY that the CICS DB2 attachment allows active
blank.
before requests are made to wait, overflow to the pool,
PLANExitname or are rejected (see THREADWait).
returns the name of the dynamic plan exit (if any) to be
THREADWait
used for this DB2ENTRY. If PLANEXITname is returned,
returns whether or not transactions should wait for a
PLAN is blank.
DB2ENTRY thread be abended, or overflow to the pool
PRIority if the number of active DB2ENTRY threads reach the
returns the priority of the thread subtasks for this Threadlimit number. The values are:
DB2ENTRY relative to the CICS main task (QR TCB).
TWait
The values are:
If all threads are busy, a transaction waits until
High subtasks attain a higher priority than the CICS one becomes available.
NOTwait
Equal If any threads are busy, a transaction is
subtasks have equal priority with the CICS main terminated with an abend code AD2P.
task.
TPOOL
Low subtasks have a lower priority than the CICS main If all threads are busy, a transaction is diverted to
task. use a pool thread. If the pool is also busy, and
NOTWAIT has been specified for the
PROtectnum
THREADWAIT parameter on the DB2CONN, the
returns the maximum number of protected threads
transaction is terminated with an abend code
allowed for this DB2ENTRY.
AD3T.
PTheads
returns the current number of protected threads for this
DB2ENTRY. A protected thread is an inactive thread

CEMT INQUIRE DB2TRAN CEMT INQUIRE DELETSHIPPED
CEMT INQUIRE DB2TRAN CEMT INQUIRE DELETSHIPPED

Function: Returns attributes of a particular DB2TRAN that Function: Display system settings that control the CICS
associates a transaction or group of transactions with a timeout delete mechanism.
DB2ENTRY.
Description: The CICS timeout delete mechanism is
Description: The DB2TRAN is identified by the name it invoked at user-specified intervals to remove any shipped
was defined with in CEDA. For RCTs migrated to the CSD, terminal definitions that have not been used for longer than a
the name is the same as the transaction for which the user-specified time.
DB2TRAN is being created.
INQUIRE DELETSHIPPED displays the current settings of
Input: If a TRANSID is specified on a DB2ENTRY when the parameters that control the mechanism.
the DB2ENTRY is installed, CICS installs a DB2TRAN
named DFHtttt, where tttt is the TRANSID. Input: Press the Clear key and type CEMT INQUIRE
DELETSHIPPED (the minimum abbreviation is CEMT I DE). You
Sample screen will get a display screen.
To change attributes, you can:

à inquire db2tran
ð Overtype your changes on the INQUIRE screen after
STATUS: RESULTS - OVERTYPE TO
Db2t(DFHTXN\ ) Db2e( DB2ENT2
MODIFY
) Tra( TXN\ )
tabbing to the appropriate field.
Db2t(DFHTXN2 ) Db2e( DB2ENT1 ) Tra( TXN2 )
Db2t(TXN1 ) Db2e( DB2ENT1 ) Tra( TXN1 ) Use the CEMT SET DELETSHIPPED command.
Figure 58. CEMT INQUIRE DB2TRAN screen

Sample screen
an expanded format is displayed as shown in Figure 59. à IN DELE
ð
Del Int( 12ðððð ) Idl( ð2ðððð )
à inquire db2tran
ð
Db2tran(DFHTXN\)
Db2entry( DB2ENT2 )
Transid( TXN\ )
Figure 60. CEMT INQUIRE DELETSHIPPED screen

Figure 59. The expanded display of an individual entry
CICS displays an expanded format as shown in Figure 61.
55──CEMT Inquire DB2Tran──┬─────────────┬──────5
└─(data-area)─┘
5──┬─────────────────────┬─────────────────────5 à IN DELE
ð
└─DB2Entry(data-area)─┘ RESULT - OVERTYPE TO MODIFY
Deletshipped
Interval( 12ðððð )
5──┬────────────────────┬──5% Idle( ð2ðððð )
└─Transid(data-area)─┘
Displayed fields Figure 61. The expanded display
DB2Entry
returns the name of the DB2ENTRY to which this 55──CEMT Inquire DEletshipped──────────────────5
DB2TRAN refers. This is the DB2ENTRY with which this
5──┬─────────────┬──┬─────────────────┬──5%
additional transaction should be associated. └─IDle(value)─┘ └─INterval(value)─┘
Transid
specifies the transaction ID to be associated with the
entry. The transaction id can include wildcard characters
Displayed fields
(see the CICS Resource Definition Guide for information DEl
about use of wildcard characters). identifies this panel as relating to CICS timeout delete
information.
IDle(value)
displays, in the form “0hhmmss+”, the minimum time
that an inactive shipped terminal definition must remain

CEMT INQUIRE DOCTEMPLATE
installed in this region. When the CICS timeout delete | CEMT INQUIRE DOCTEMPLATE
mechanism is invoked, only those shipped definitions
that have been inactive for longer than this time are | Function: Retrieves information about a DOCTEMPLATE
deleted.
The time interval can be in the range 00-99 hours; 00-59 | Description: INQUIRE DOCTEMPLATE returns
minutes; and 00-59 seconds. | information about any currently installed document template
| names.
different value. | Input: Press the Clear key to clear the screen, and type
INterval(value) | CEMT INQUIRE DOCTEMPLATE (the minimum abbreviation is CEMT
displays, in the form “0hhmmss+”, the interval between | I DO). You get a display that lists the names and status of
invocations of the CICS timeout delete mechanism. The | any document templates. Note that you cannot change any
timeout delete mechanism removes any shipped terminal | of the displayed information.
definitions that have not been used for longer than the
| Sample screen
time displayed by the IDLE option.
The time interval can be in the range 00-99 hours; 00-59
minutes; and 00-59 seconds. | à ð
| I DOC
Note: You can reset this value by overtyping it with a | STATUS: RESULTS - OVERTYPE TO MODIFY
| Doc(test1 ) Tsq Nam(test1 ) App Ebc
different value. | Tem(test1 )
| SYSID=HA61 APPLID=CICSHA61
| PF 1 HELP 3 END 5 VAR 7 SBH 8 SFH 9 MSG 1ð SB 11 SF
| Figure 62. CEMT INQUIRE DOCTEMPLATE screen
| If you place the cursor against a specific entry in the list and
| press ENTER, CICS displays an expanded format.
|
| à i doc
ð
| RESULT - OVERTYPE TO MODIFY
| Doctemplate(test1)
| Templatetype(Tsqueue)
| Name(test1)
| Appendcrlf(Append)
| Type(Ebcdic)
| Templatename(test1)
| Ddname()
| Dsname()
| Figure 63. The expanded display of an individual entry

|
| 55──CEMT Inquire DOctemplate──┬─────────┬──────5
| ├─TSq─────┤
| ├─TDq─────┤
| ├─File────┤
| ├─EXitpgm─┤
| └─Member──┘
| 5──┬────────────┬──┬──────────┬──┬────────┬────5
| └─Name(name)─┘ ├─Append───┤ ├─Ebcdic─┤
| └─Noappend─┘ └─Binary─┘
| 5──┬────────────────────┬──────────────────────5
| └─Templatename(name)─┘
| 5──┬──────────────────────────┬──┬────────┬──5%
| └─Templatename──(──name──)─┘ ├─DDname─┤
| └─DSname─┘
| Displayed fields
| APPENDCRLF
| returns whether CICS is to delete trailing blanks from
| and append carriage-return line-feed to each logical
| record of the template.

CEMT INQUIRE DSAS
| DDNAME CEMT INQUIRE DSAS

| returns the DD name of the PDS containing the
| template. The DDName applies only to a template of Function: Retrieve information about the local CICS
| type PDS. If a membername is supplied without a value dynamic storage areas (DSAs).
| for DDNAME, the default value DFHHTML is used.
Description: CEMT INQUIRE DSAS returns the value of
| DOCTEMPLATE
various DSA sizes and limits.
| returns the name of this DOCTEMPLATE definition.
| NAME Input: Press the Clear key and type CEMT INQUIRE DSAS
| returns the name of the location defined in (the minimum abbreviation is CEMT I DSA).
| TEMPLATETYPE.
To change various attributes, you can:
| TEMPLATENAME
Overtype your changes on the INQUIRE screen after
| returns the extended template name by which the
tabbing to the appropriate field (see Figure 64)
| doctemplate is known outside the resource definition
| function. Use the CEMT SET DSAS command.
| TEMPLATETYPE Sample screen

| returns the location of the template. Values are:
| EXITPGM the exit program to be invoked when a

| request is made for this template. à IN DSAS
ð
SOSStatus( NOTSOS )
| FILE the 8-character name of the CICS file
Dsalimit( ð41943ð4 )
| definition for the data set containing the Cdsasize( ðð524288 )
Rdsasize( ðð262144 )
| template. SDsasize( ðð262144 )
Udsasize( ðððððððð )
| MEMBER returns the name of the member in the PDS EDsalimit( ðð2ð97152ð )
ECdsasize( ððð2ð97152 )
| containing the template. ERdsasize( ððð3145728 )
ESdsasize( ðððððððððð )
EUdsasize( ððð1ð48576 )
| PROGRAM returns the name of the program in which
| the template data is stored.
Figure 64. CEMT INQUIRE DSAS screen
| TDQUEUE returns the name of the TD queue in which
| the template is stored.
| TSQUEUE returns the name of the TS queue in which 55──CEMT Inquire DSAs──5%
| the template is stored.
| TYPE(BINARY|EBCDIC) Displayed fields

| returns the format of the template contents.
DSalimit(value)
| BINARY When the template is loaded from the displays the maximum amount of storage, as a total
| template library, no parsing of the template's number of bytes, within which CICS can dynamically
| contents is done. allocate storage for the four individual DSAs that reside
| EBCDIC When the template is loaded from the below the 16MB boundary. (See the CICS System
| template library, the contents are parsed as Definition Guide for a description of the DSALIM system
| EBCDIC text. initialization parameter.)
different value.
If DSALIMIT specifies a value lower than the current
limit, CICS may not be able to implement the new limit
immediately, but will attempt to do so over time as
dynamic storage is freed in the individual DSAs.
SOSStatus
displays whether CICS is short on storage in any of the
dynamic storage areas. The values are:
NOTSOS
CICS is not short on storage in any of the dynamic
storage areas.
SOS CICS is short on storage in dynamic storage areas
above and below 16MB.

CEMT INQUIRE DSAS
SOSABOVE immediately, but will attempt to do so over time as

CICS is short on storage in at least one of the dynamic storage is freed in the individual DSAs.
dynamic storage areas above 16MB.
SOSAbove
SOSBELOW displays whether CICS is short on storage in any of the
CICS is short on storage in at least one of the dynamic storage areas above 16MB. The values are:
dynamic storage areas below 16MB.
NOTSOS
CDsasize(value) CICS is not short on storage in any of the dynamic
displays the size, in bytes, of the CICS dynamic storage storage areas above 16MB.
area (CDSA). The size of this storage area is calculated
SOS CICS is short on storage in at least one of the
and managed by CICS automatically, within the overall
limits specified for all the DSAs that reside below the
16MB boundary. ECdsasize(value)
displays the size, in bytes, of the extended CICS
RDsasize(value)
dynamic storage area (ECDSA) above the 16MB
displays the current size of the read-only dynamic
boundary. The size of this storage area is calculated and
storage area (RDSA). The size of this storage area is
managed by CICS automatically, within the overall limits
calculated and managed by CICS automatically, within
specified for all the DSAs that reside above the 16MB
the overall limits specified for all the DSAs that reside
boundary.
below the 16MB boundary.
ERdsasize(value)
SDsasize(value)
displays the size, in bytes, of the extended read-only
displays the current size of the shared dynamic storage
dynamic storage area (ERDSA) above the 16MB
area (SDSA). The size of this storage area is calculated
boundary. The size of this storage area is calculated and
and managed by CICS automatically, within the overall
managed by CICS automatically, within the overall limits
limits specified for all the DSAs that reside below the
specified for all the DSAs that reside above the 16MB
16MB boundary.
boundary.
Udsasize(value)
ESdsasize(value)
displays the size, in bytes, of the user dynamic storage
displays the current size of the extended shared
area (UDSA) below the 16MB boundary.
dynamic storage area (ESDSA). The size of this storage
EDsalimit(value) area is calculated and managed by CICS automatically,
displays the maximum amount of storage, as a total within the overall limits specified for all the DSAs that
number of bytes, within which CICS can dynamically reside above the 16MB boundary.
allocate storage for the four individual DSAs that reside
EUdsasize(value)
above the 16MB boundary. (See the CICS System
displays the size, in bytes, of the extended user dynamic
Definition Guide for a description of the EDSALIM
storage area (EUDSA) above the 16MB boundary. The
system initialization parameter.)
size of this storage area is calculated and managed by
Note: You can reset this value by overtyping it with a CICS automatically, within the overall limits specified for
different value. all the DSAs that reside above the 16MB boundary.
If EDSALIMIT specifies a value lower than the current
limit, CICS may not be able to implement the new limit

CEMT INQUIRE DSNAME
CEMT INQUIRE DSNAME

55──CEMT Inquire DSName────────────────────────5
Function: Retrieve information about an external data set. ┌─ALl────────────────┐
5──┼────────────────────┼──5%
Description: INQUIRE DSNAME returns information ├─(value)────────────┤
├─┬─VSam─┬───────────┤
about the status of a data set managed by CICS file control. │ └─BDam─┘ │
The data set name is either the name specified on the DSN ├─FIlecount(value)───┤
parameter of the data set’s DD statement, or the DSNAME ├─┬─VAlid───┬────────┤
parameter of the data set’s file resource definition. Its main │ └─INvalid─┘ │
├─┬─Path─┬───────────┤
purpose is to allow you to monitor failing VSAM data sets. │ └─BASE─┘ │
Many of the attributes cannot be determined until a file that ├─┬─FWDRECOVAble─┬───┤
references the data set has been opened. If this has not │ ├─NOTrecovable─┤ │
happened, blank values are returned for most attributes. │ ├─RECOVERAble──┤ │
│ └─UNDetermined─┘ │
| Note: CEMT has to retrieve QUIESCESTATE information ├─┬─Static───────┬───┤
| from the ICF catalog. This can slow down processing │ ├─Dynamic──────┤ │
| of this command. QUIESCESTATE is not supplied by │ └─UNDetermined─┘ │
├─FRlog(value)───────┤
| default but is retrieved and displayed if requested. ├─┬─AVailable───┬────┤
│ └─UNAvailable─┘ │
Input: Press the Clear key to clear the screen. There are ├─┬─NOLostlocks──┬───┤
two ways of commencing this transaction: │ ├─REMLostlocks─┤ │
│ └─RECOVERLocks─┘ │
Type CEMT INQUIRE DSNAME (the minimum abbreviation is ├─┬─RETAined───┬─────┤
| CEMT I DSN). You get a display that lists the current │ └─NORetained─┘ │
| status except QUIESCESTATE. To retrieve ├─┬─Quiesced───┬─────┤
│ └─UNQuiesced─┘ │
| QUIESCESTATE you can place the cursor at the
├─BASEDsname(value)──┤
| beginning of the displayed item (in front of the Dsn field) └─FWDRECOVLsn(value)─┘
| and press the enter key.
Type CEMT INQUIRE DSNAME (CEMT I DSN) followed by as
many of the other attributes as are necessary to limit the ALl
range of information that you require. So, for example, if is the default.
you enter cemt i dsn vs not, the resulting display will (value)
show you the details of only those external data sets specifies one or more names (1-44 characters) of an
that are VSAM data sets and are not recoverable. external data set.
overtype them with the required values. Sample screen
à IN DSN
ð
Dsn(CICSTS13.CICS.CICSH###.DFHCSD ) Vsa
| Fil(ððð1) Val Bas Sta Ava
| Dsn(CICSTS13.CICS.CICSHT61.FILEA ) Vsa
| Fil(ððð1) Val Bas Sta Ava
Figure 65. CEMT INQUIRE DSNAME screen
| Note: There are blank fields on the screen. With the

| exception of QUIESCESTATE, these show where a
| value does not apply or is ‘negative’; that is, the value
| begins with ‘No’. To modify these fields, locate them
| by tabbing (they appear in the same sequence as in
| the expanded format), and overtype with input valid
| for that field. You may find it more convenient to use
| the expanded format when setting one of these
| values, (negating is easier because you are
| overtyping a displayed field with its negative causing
| the result to become non-displayed).
Because of the large number of keywords supported for this

command, only two lines of information for each result are

CEMT INQUIRE DSNAME
displayed. The full set of keywords can be displayed by with blanks on the CEMT display), or discard
moving the cursor to the beginning of a displayed item (in the file definition entirely.
front of the Dsn field) and pressing the ENTER key. You get
If you have a base data set with one or more
a display of all the keyword information for the displayed
alternate indexes, you are unable to remove the
item, as follows:
data set name block for the base until you have
removed all references to the base data set and
all references to paths.
à IN DSN
ð Recovered
Dsname(CICSTS13.CICS.CICSH###.DFHCSD)
Accessmethod(Vsam) The data set has been restored from a backup
Action( )
Filecount(ððð1) version and forward recovery has run and
Validity(Valid)
Object(Base) completed successfully. CICS normally updates
Recovstatus(Notrecovable)
Backuptype(Static) the backup-while-open (BWO) attributes for the
Frlog()
Availability( Available )
Lostlocks()
base cluster data set BASEDSNAME, using
Retlocks(Noretained)
Uowaction( )
MVS/DFP 3.2 Callable Services.
Basedsname(CICSTS13.CICS.CICSH###.DFHCSD)
Quiescestate( Unquiesced )
Fwdrecovlsn()
If the BWO attributes are not updated after the
restore of a backup copy of a data set that was
taken using BWO, CICS fails a subsequent file
Figure 66. The expanded display of an individual entry open because the data set is marked as
down-level.
Displayed fields Resetlocks (vsam only)
DSName(value) Purges shunted UOW log records for
indicates that this panel relates to an external data set backout-failed and commit-failed UOWs that hold
inquiry and displays the 44-character name of an locks on this data set, and releases the retained
external data set. locks:
Backout-failed UOWs are those that failed
Accessmethod(value)
during backout processing.
displays the access method of the data set. The values
are: Commit-failed UOWs are those that have
updated RLS data sets, and have failed to
VSam release locks during the second phase of
Virtual storage access method (VSAM). 2-phase commit syncpoint processing.
BDam If you specify this option, you are accepting
Basic direct access method (BDAM). backout failure and some loss of data integrity
Action (input only field) rather than retaining locks and delaying
specifies the action to be taken on this data set. The transactions, and therefore it should be used only
values are: as a last resort.
For backout-failed and commit-failed UOWs that
Remove
hold locks on the data set, all records relating to
This option is used when a data set is no longer
this data set are removed from the system log and
required on the local system. It deletes the data
all retained record locks held by this CICS for the
set name block for the named data set. The
data set are released. Diagnostic messages are
REMOVE option can be used only when there are
written to the CSFL transient data queue for each
no file control resource definition entries that refer
backout-failed log record that is removed as a
to the specified data set. If any file definitions refer
result of the RESETLOCKS operation.
to the data set name when you enter SET
DSNAME REMOVE, you receive an error RESETLOCKS applies only to shunted UOW log
message indicating that the use count of the data records that are classed as backout-failed and
set name block is not zero. To ensure that no file commit-failed. Therefore it cannot be issued for a
definitions refer to the data set name: BDAM data set. Backout-failed and commit-failed
log records are not shunted for BDAM data sets.
Close all files that refer to the data set. These
files can be found using the command: You might use RESETLOCKS if backout-failed or
CEMT INQUIRE FILE(\) DSNAME(dsname) commit-failed log records are holding up lost locks
recovery for the data set, and there is no other
Either remove the data set name from each way of resolving them.
file entry (by over-typing the data set name

CEMT INQUIRE DSNAME
Notes: VAlid
The data-set name has been validated against the
1. This option does not apply to shunted
VSAM catalog by opening a file against that data
in-doubt UOWs. Try to resolve the shunted
set.
in-doubt UOWs that hold locks on the data set
in other ways before issuing RESETLOCKS; INvalid
for example, by using COMMIT, BACKOUT, The data-set name has not been validated against
or FORCE (see the CEMT SET DSNAME the VSAM catalog by opening a file against that
command for information about these data set.
options).
Object
2. RESETLOCKS can fail during the commit displays the type of the data set. The values are:
phase (for example, if an error occurs while
CICS is trying to release the RLS locks), in Path (VSAM only)
which case the UOWs revert to being shunted This data set is a path leading to another data set.
as commit-failed UOWs. BASE
Retry The named data set is a base data set, as
Specifies that shunted UOW log records, caused opposed to a path data set.
by failed backout and commit processing as a
Recovstatus
result of the failure of this data set, should be
displays the recovery status of the data set. The values
retried. This is similar in operation to the EXEC
are:
CICS RESYNC command, but applies to
backout-failed and commit-failed UOWs only, and FWDRECOVAble
not to in-doubt UOWs. All updates to the data set are logged for both
backout and forward recovery.
You should use RETRY when the data set has
shunted backout- or commit-failed UOWs NOTrecovable
associated with it, and you believe that some or all Updates to the data set are not logged.
of the data set problems are either transient or
This response may also be returned as the result
have been resolved.
of use of the XFCNREC global user exit. A
Messages, issued at the time of a data set failure program enabled at XFCNREC may indicate that
that causes UOWs to be shunted, recommend the file opens should proceed even if there is a
actions that are required to recover from the mismatch in the backout recovery requirements for
failure. different files associated with same data set. In
these circumstances, the data set is marked as
RETRY does not affect data integrity, and can be
NOTRECOVABLE to indicate that its data integrity
used safely at any time to enable some failed
can no longer be guaranteed.
recovery work to complete.
The condition remains until cleared by a CEMT or
FIlecount(value)
EXEC CICS SET DSNAME REMOVE command,
displays information on how many different files are
or by an initial or cold start of CICS (if the
currently associated with this data set. You can
associated data set is not in backout-failed state).
associate a file with a data set by a job control DD
While the data set is in this state, backout logging
statement, or dynamically by a DSNAME parameter on
is performed for a particular request based on the
the file definition. If a file has been associated by a job
specification in the file definition. Therefore
control DD statement, the file name cannot be changed
backout logging may occur for requests via one
by a CEDA command or by a CEMT or EXEC CICS
file and not via another.
SET FILE DSNAME command.
RECOVERAble
FILECOUNT does not show how many files are open
All updates to the data set are logged for backout.
against the data set; it only shows how many files are
associated with the data set. If a file is associated with UNDetermined
a data set and is then closed and associated with a The recovery status of the data set is not known
different data set, the FILECOUNT of the first data set because files accessing the data set have not
decreases by 1, and the FILECOUNT of the second data been opened for output.
set increases by 1.
Backuptype
Validity displays the backup type of the data set. The values are:
displays the validity of the data-set name. The values
Static
are:
The data set is accessed in non-RLS mode and is
not eligible for BWO processing. All the files in this
data set must be closed and the data set

CEMT INQUIRE DSNAME
serialized by a backup manager such as UNAvailable

DFSMS/MVS before a data set backup copy can The data set is marked by CICS as not available
be made. for use. The CICS region is unable to open the
data set in either RLS or non-RLS mode.
Dynamic
The data set is accessed in RLS mode and is
AVAILABILITY can be reset by specifying AVAILABLE.
eligible for BWO processing. Data set backup is
allowed while it is open for output, using a data Lostlocks
set backup manager such as DFSMShsm or displays whether there are any lost locks for this data
DFSMSdss. 2 set. The possible values displayed are:
Notapplic
NOLostlocks
The data set has not been opened by the CICS
The data set has no lost locks.
region in which the command is issued, or the
data set is BDAM or a VSAM PATH. NOTAPPLIC REMLostlocks
is also returned if the dataset has been opened in The data set has lost locks, hence is unavailable,
RLS mode. The VSAM catalog should be referred but no recovery is required on this CICS. (The lost
to get the BWO status. locks belong to a another (remote) CICS region.)
RECOVERLocks
FRlog(value)
The data set has lost locks and therefore is
displays the numeric journal identifier of the journal
unavailable. This CICS system is performing
being used to log the updates for forward recovery if this
lost-locks recovery.
data set is forward recoverable (FWDRECOVABLE). The
FRLOG value is undefined if the data set is not forward Retlocks
recoverable. You can define a data set as forward displays whether there are any retained record locks, as
recoverable either in the ICF catalog or, if it is accessed a result of deferred recovery work by this CICS region,
in non-RLS mode, in the file resource definition. This for the specified data set.
option is meaningful only for data sets accessed in LSR
or NSR mode, and for which the forward recovery RETAined
attributes are obtained from the CICS file resource This CICS region has deferred recovery work
definition. causing retained locks for the data set. One effect
of this is that, if the data set was last opened in
For data sets accessed in RLS mode (if DFSMS 1.3 is
RLS mode, the locks are RLS locks and therefore
installed), or non-RLS mode data sets for which CICS
the data set cannot be opened in non-RLS mode.
obtains the recovery attributes from the ICF catalog,
CICS displays a value of zero. Another effect is that any FILE definitions that
specify this data set cannot be changed to specify
Availability a different data set.
displays information indicating whether the data set is
If the data set is a BDAM data set, or a VSAM
currently flagged, in this CICS region, as available or
data set accessed in non-RLS mode, the locks are
unavailable for use. The availability indicator is a local
CICS record locks, otherwise they are RLS record
flag that a CICS region maintains in a data set name
locks.
block (DSNB) for each data set. If the file is a BDAM
data set, no information is returned. The values are: NORetained
This CICS region has no deferred recovery work
AVailable
for the base data set, and therefore no retained
The data set is available for use according to the
locks.
CICS data set name block. CICS can issue either
RLS or non-RLS open requests for this data set. Note: Noretained can also mean that the CICS
region is currently processing deferred
Note: Although a data set is available according
recovery work. When the recovery work is
to information held by CICS, an open
successfully completed, the value remains
request could still fail if the ICF catalog
as NORETAINED until more deferred work
indicates otherwise. This can occur, for
is created. If the recovery work is not
example, if data set recovery is pending or
successfully completed, the value reverts
actually in progress.
to RETAINED.
2 Hierarchical storage manager (DFSMShsm) and data set services (DFSMSdss), which perform data set backup and recovery operations,
are components of IBM Data Facility Storage Management Subsystem (DFSMS/MVS) program product.

CEMT INQUIRE DSNAME
Quiescestate Any OUWs that fail backout are shunted. No RLS

displays the RLS quiesce state of the data set. The ACBs can open against this data set, but non-RLS
information is obtained from the ICF catalog entry for the open requests are permitted.
data set. The values displayed are:
Uowaction (input only field)
Quiesced specifies the action to be taken for all shunted units of
A data set has been quiesced. It means that RLS work that reference this data set. The values are:
ACBs cannot open against the data set and no
Backout
CICS region has an RLS ACB currently open
Specifies that all shunted in-doubt units of work
against this data set. However, the data set can
that hold locks on the data set should be backed
be opened in non-RLS mode.
out.
UNQuiesced
Commit
This is the normal value for a data set that is not
Specifies that all shunted in-doubt units of work
quiescing or has not been quiesced. It indicates
that hold locks on the data set should be
that RLS or non-RLS ACBs can be opened
committed. Specifies that all shunted in-doubt
against the data set, the mode being established
units of work that hold locks on the data set
by the first open. After an ACB is opened in one
should be forced to BACKOUT or COMMIT, as
mode, other ACBs can be opened only in the
specified by the ACTION attribute on the
same mode.
transaction resource definition.
If a data set is quiescing because a SET DSNAME BASEDsname(value) (VSAM only)
QUIESCE command was issued in the same region as When PATH is displayed as well, this is the name of the
the CEMT I DSN command, the words “BEING base data set with which this path is associated.
QUIESCED” are displayed.
When BASE is displayed as well, this is the same as the
If a data set is quiescing, the words “BEING name shown in the Dsn(value) field.
QUIESCED” are displayed for the CICS region in which
the command was issued. FWDRECOVLsn(value)
displays the name of the log stream that is used to log
If quiesce does not apply (for example, for a BDAM data
the updates if this data set is defined as forward
set), nothing is displayed.
recoverable. CICS returns nulls if the data set is not
Quiescestate can be reset by specifying forward recoverable.
Quiesced|Unquiesced or:
The log stream name returned is either:
Immquiesced
The log stream name specified directly in the ICF
Causes all existing CICS open RLS ACBs
catalog, or
throughout the sysplex to be closed and the data
set to be marked as quiesced in the ICF catalog. For a non-RLS access mode data set that does not
Each CICS in the sysplex abends all in-flight have forward recovery attributes in the ICF catalog,
UOWs that are accessing the data set before it is a log stream name identified by CICS through a
closing ACBs, causing in-flight UOWs to back out. journal name generated from the FWDRECOVLOG
value.

CEMT INQUIRE DUMPDS
CEMT INQUIRE DUMPDS

55──CEMT Inquire DUmpds──5%
Function: Retrieve information about the CICS dump data
sets.
Displayed fields
Description: INQUIRE DUMPDS tells you which dump DUmpds
data set (A or B) is currently open. indicates that this panel relates to a dump data set
inquiry.
Instead of using the SET command, you can overtype your
changes on the INQUIRE screen after tabbing to the Currentdds(value)
appropriate field. See “Overtyping a display” on page 47. displays a 1-character indicator as to which of the two
dump data sets is active. This can be A or B.
For information on using dumps, see the CICS Problem
Determination Guide. Openstatus
displays the status of the active CICS dump data set.
Input: Press the Clear key and type CEMT INQUIRE DUMPDS The values are:
(the minimum abbreviation is CEMT I DU).
Open
You will get a display screen, a sample of which is shown The active CICS dump data set is open.
below. If you want to change any of the values shown, you Closed
can then tab to the highlighted or blank fields and overtype The active CICS dump data set is closed.
them as required.
Switch
Sample screen The currently active dump data set is to become
inactive, and the currently inactive data set is to
become active.
à IN DUMPDS
ð Note: You can reset this value by overtyping it with a
Dum Cur(A) Ope different value.
Switchstatus
Figure 67. CEMT INQUIRE DUMPDS screen displays whether there is to be an automatic switch to
the inactive dump data set when the active dump data
Note: There are blank fields on the screen where a value set is full. The values are:
begins with ‘No’. To modify these fields, locate them Autoswitch
by tabbing (they appear in the same sequence as in The switch occurs only when the active dump
the expanded format), and overtype with input valid data set is full, but not subsequently.
for that field. You may find it more convenient to use Noautoswitch
the expanded format when setting one of these When the active dump data set is full, there is not
values, (negating is easier because you are to be an automatic switch to the inactive dump
overtyping a displayed field with its negative causing data set.
Note: Because this is a ‘negative’ attribute, the
If you place the cursor against the result and press ENTER, field appears blank. You can, however, tab
CICS displays an expanded format as shown in Figure 68. to this field and overtype it with a different
value.

à IN DUMPD
ð different value.
Dumpds
Currentdds(A)
Openstatus( Open )
Switchstatus( Noautoswitch )
Figure 68. The expanded display

CEMT INQUIRE ENQ
|
| CEMT INQUIRE ENQ
| 55──CEMT Inquire Enq──┬────────────┬───────────5
| └─Uow(value)─┘
| Function: Retrieve information about enqueues held or
| waited on by a UOW, or about UOWs holding or waiting on a | 5──┬────────────────┬──┬───────────────┬───────5
| └─TRansid(value)─┘ └─TAskid(value)─┘
| specified enqueue.
| 5──┬──────────┬──┬─────────────┬───────────────5
| Description: INQUIRE ENQ returns information about the | ├─ACtive───┤ ├─Dataset─────┤
| └─RETained─┘ ├─File────────┤
| enqueues held by a UOW. Enqueues are used by CICS to | ├─EXecenq─────┤
| lock recoverable resources such as file records or queues to | ├─ADdrexecenq─┤
| the UOW that is updating them. User enqueues obtained by | ├─TDq─────────┤
| the EXEC CICS ENQ command are also returned. | └─TSq─────────┘
| 5──┬────────┬──┬─────────────────┬─────────────5
| You can use INQUIRE ENQ to indicate which records and | ├─Owner──┤ └─Netuowid(value)─┘
| queues would be affected if the UOW were forced. | └─Waiter─┘
| 5──┬─────────────────┬──┬─────────────────┬────5
| The transaction also returns information about UOWs that | └─ENqfails(value)─┘ └─RESource(value)─┘
| are waiting on the enqueues. This enables you to diagnose
| 5──┬─────────────┬──┬──────────────────┬───────5
| enqueue deadlocks between tasks wanting to update the | └─RLen(value)─┘ └─QUalifier(value)─┘
| same resources.
| 5──┬─────────────┬──5%
| Enqueues are typically held in active state, which means that | └─QLen(value)─┘
| other tasks are allowed to wait for the enqueue. However, if
| the UOW that owns the enqueue suffers an in-doubt failure,
| Sample screen
| the enqueue is usually converted to the retained state until
| the in-doubt failure can be resolved. INQUIRE ENQ also
| retrieves information about these enqueues and can be used
| to identify which records and queues would be affected if the |
| à INQ ENQ
ð
| STATUS: RESULTS
| UOW were forced. | Enq(AC143ðð1D4A726ð1) Tra(CECI) Tas(ððððð38) Act Exe Own
| Res(ACCOUNTS.DBASE1 ) Rle(ð15) Enq(ðððððððð)
| Enq(AC143ðð1D4A726ð1) Tra(CECI) Tas(ððððð38) Act Add Own
| Notes: | Res(g... ) Rle(ðð4) Enq(ðððððððð)
| 1. Both UOW-lifetime and task-lifetime enqueues are

| returned by INQUIRE ENQ. (For an explanation of | Figure 69. CEMT INQUIRE ENQ screen
| UOW- and task-lifetime enqueues, see the
| MAXLIFETIME option of the EXEC CICS ENQ command | Note: There are blank fields on the screen where a value
| in the CICS System Programming Reference manual.) | does not apply or is ‘negative’; that is, the value
| begins with ‘No’. To modify these fields, locate them
| 2. On an in-doubt failure, user enqueues are released,
| by tabbing (they appear in the same sequence as in
| unless the EXEC CICS ENQ command specified
| the expanded format), and overtype with input valid
| MAXLIFETIME(TASK) and it is not the end-of-task
| syncpoint that suffers the failure.
| values, (negating is easier because you are
| Input: Press the Clear key to clear the screen. There are
| two ways of commencing this transaction:
| the result to become non-displayed).
| Type CEMT INQUIRE ENQ (the minimum abbreviation is
| CEMT I ENQ). You get a display that lists all enqueues for | If you place the cursor against a specific entry in the list and
| all the current UOWs. | press ENTER, CICS displays an expanded format as shown
| in Figure 70.
| Type CEMT INQUIRE ENQ (CEMT I ENQ) followed by as
| many of the other attributes as are necessary to limit the
| range of information that you require. So, for example, if
| you enter cemt i enq d, the resulting display shows you |
| à INQ ENQ
ð
| RESULT
| the details only of enqueues on records in VSAM data | Enq
| Enq(AC143ðð1D4A726ð1)
| sets open in non-RLS mode or CICS-maintained data | Transid(CECI)
| Taskid(ððððð38)
| tables. | State(Active)
| Type(Execenq)
| Relation(Owner)
| Duration()
| Resource(ACCOUNTS.DBASE1)
| Rlen(ð15)
| Enqfails(ðððððððð)
| Netuowid(..GBIBMIYA.IYA2T5C2...Mx...)
| Qualifier()
| Qlen(ððð)

CEMT INQUIRE ENQ
| Displayed fields | The data displayed depends on the type of enqueue, as

| shown in Table 2 on page 82.
| Duration(value)
| displays the elapsed time (in seconds) since the | Note: Nondisplayable characters appear as periods.
| enqueue f entered its current state of OWNER, WAITER | You can use PF2 on the expanded panel: to see
| or RETAINED. | the value in hexadecimal.
| ENQFails(value) | RLen(value)
| displays, for enqueues held in retained state, the number | displays the length of the data, in the range 0 through
| of failed enqueue attempts for this resource since the | 255, displayed in the RESOURCE field.
| enqueue was last acquired. This indicates how many | State
| UOWs have received LOCKED responses due to this | displays the state that the enqueue is held in. The
| enqueue. The ENQFAILS option helps you identify | values are:
| which UOWs are causing “bottlenecks.”
| ACtive
| For enqueues held in action state, ENQFAILS displays
| The enqueue is held in active state.
| zero.
| RETained
| ENQScope(value) | The enqueue is held in retained state. Its owning
| If the enqueue has sysplex scope, ENQSCOPE displays | UOW has been shunted, or is in the process of
| the 4-character name which was used to qualify the | being shunted.
| sysplex-wide ENQUEUE request issued by this CICS
| region. If it has region scope, ENQSCOPE displays | TAskid(value)
| blanks. | displays the number of the task associated with the
| UOW. If the UOW is shunted, it is the task number
| All CICS systems with the same ENQSCOPE value
| associated with the UOW before it was shunted.
| share the same sysplex Enqueue name space.
| TRansid(value)
| Netuowid(value)
| displays the 4-character identifier of the transaction
| displays a 27-character string containing the
| associated with the UOW. If the UOW is shunted, it is
| network-wide LU6.2 name of the UOW that owns or is
| the identifier of the transaction associated with the UOW
| waiting for the enqueue.
| before it was shunted.
| Note: Nondisplayable characters appear as periods.
| You can use PF2 on the expanded panel: to see | TYpe
| the value in hexadecimal. | displays the type of resource being enqueued upon. The
| values are:
| QUalifier(value)
| displays a 1- through 255-character qualifier (for | Dataset
| example, record id) that further identifies the resource | The resource is a record in a VSAM data set (or a
| associated with the enqueue lock. The data displayed | CICS-maintained data table). RESOURCE
| depends on the type of enqueue, as shown in Table 2 | contains the name of the data set and QUALIFIER
| on page 82. If no QUALIFIER data applies (that is for | contains the record identifier.
| EXECENQ, ADDREXECENQ, or TSQ), a value of zero | File The resource is a record in either a BDAM file or a
| is displayed. | user-maintained data table. RESOURCE contains
| the name of the file and QUALIFIER contains the
| QLen(value)
| record identifier.
| displays the length of the data, in the range 0 through
| 255, displayed in the QUALIFIER field. | When the file is a BDAM file then the record
| identifier is prefixed by the BDAM block identifier.
| RELation | Note that truncation occurs if this combination
| displays whether the data is associated with the owner | exceeds 255 characters.
| of the enqueue or with a task waiting for the enqueue.
| The values are: | EXecenq
| The resource is associated with an EXEC CICS
| Owner | ENQ request. RESOURCE contains the enqueue
| The (value), NETUOWID, TASKID, and TRANSID | argument passed on the request.
| are those of the owner of the enqueue.
| ADdrexecenq
| Waiter | The resource is associated with an EXEC CICS
| The (value), NETUOWID, TASKID, and TRANSID | ENQ request. RESOURCE contains the address
| are those of a waiter for the enqueue. | enqueue argument passed on the request (that is,
| the LENGTH parameter was omitted on the
| RESource(value)
| request)
| displays a 1- through 255-character string containing the
| name of the resource associated with the enqueue lock.

CEMT INQUIRE ENQMODEL
| TDq The resource is a logically-recoverable transient | CEMT INQUIRE ENQMODEL

| data queue. RESOURCE contains the name of the
| queue. QUALIFIER contains either the string | Function: Retrieve information about enqmodel definitions
| “FROMQ” or “TOQ,” indicating whether a read or | on the local system.
| write lock is held for the queue.
| A READQ TD request acquires the “FROMQ” lock, | Input: Press the Clear key and type CEMT INQUIRE
| whereas a WRITEQ TD request acquires the | ENQMODEL (the minimum abbreviation is CEMT I ENQM).
| “TOQ” lock associated with the queue. A
| You get a display screen, a sample of which is shown below.
| DELETEQ TD request acquires both the “TOQ”
| If you want to change any of the values shown, you can then
| and the “FROMQ” locks.
| tab to the highlighted or blank fields and overtype them as
| TSq The resource is a recoverable temporary storage | required.
| queue. RESOURCE contains the name of the
| queue. | Sample screen
| The data displayed in the RESOURCE and QUALIFIER

| fields depends on the resource type, as shown in | à ð
| INQ ENQMODEL
| Table 2. | STATUS: RESULTS - OVERTYPE TO MODIFY
| Enqm(\ ) NOT FOUND
| Table 2. Data displayed in RESOURCE and QUALIFIER

| Type Resource Qualifier
| DATASET Dataset name Record identifier
| Figure 71. CEMT INQUIRE ENQMODEL screen
| EXECENQ EXEC enqueue None
| argument | Note: There are blank fields on the screen where a value
| ADDREXECENQ Address of EXEC None | does not apply or is ‘negative’; that is, the value
| enqueue | begins with ‘No’. To modify these fields, locate them
| argument | by tabbing (they appear in the same sequence as in
| FILE File name Record identifier | the expanded format), and overtype with input valid
| TDQ TD queue name FROMQ or TOQ
| TSQ TS queue name None | values, (negating is easier because you are
| Uow(value) | the result to become non-displayed).
| displays the 16-character local identifier of the |
| associated unit of work.
| 55──CEMT Inquire ENQModel──────────────────────5
| 5──┬─(value)─────────┬──┬──────────┬──5%
| ├─ENQSCOPE(value)─┤ ├─DISABLED─┤
| └─ENQNAME(value)──┘ ├─ENABLED──┤
| └─WAITING──┘
| Displayed fields
| ENQMODEL
| The 8-character identifier of the resource definition
| ENQSCOPE
| Returns the 4-character name used to qualify SYSPLEX
| ENQUEUE requests issued by this CICS region. Four
| blanks indicates that the ENQ is LOCAL.
| ENQNAME
| The 1 - 255 character resource or generic name.
| EXEC ENQ requests issued by this CICS region are
| checked against this resource or generic name. If a
| match is found, and enqscope was specified, the
| enqueue is to be sysplex-wide, qualified by the
| 4-character enqscope.

CEMT INQUIRE EXCI
| DISABLED CEMT INQUIRE EXCI

| Matching ENQ requests are rejected, and the issuing
| task abended abcode ENQ_DISABLED. Matching Function: Retrieve information about jobs using the
| INSTALL/CREATE/DISCARD requests are processed. external CICS interface.
| ENABLED
Description: INQUIRE EXCI identifies the names of batch
| Matching ENQ requests are processed in the normal
jobs currently connected to CICS through the interregion
| way.
communication (IRC) facility. These jobs are using the
| WAITING external CICS interface (EXCI) to link to a server program
| Matching ENQ requests are rejected, and the issuing running in CICS.
| task abended abcode ENQ_DISABLED. There are
| INSTALL/CREATE/DISCARD requests waiting to be Input: Press the Clear key to clear the screen. There are
| processed. two ways of commencing this transaction:
Type CEMT INQUIRE EXCI (the minimum abbreviation is
CEMT I E). You get a display that lists the current status.
Type CEMT INQUIRE EXCI (CEMT I E) followed by
Task(number) to limit the scope of the inquiry.
55──CEMT Inquire Exci──┬──────────────┬──5%

├─Task(number)─┤
| └─Urid(value)──┘
Sample screen
à INQ EXCI
ð
STATUS: RESULTS
Exc(HADBS1..CICSWK1 - MV29 ) Tas(ðððð121)
| Exc(AHCLN2..TRNSL 1 - MV29 ) Tas(ðððð125)
| Uri(B 67B1F77EB7D 21 1 1 )
Figure 72. CEMT INQUIRE EXCI screen

If you place the cursor against a specific entry in the list and
press ENTER, CICS displays an expanded format as shown
in Figure 73.
à INQ EXCI
ð
RESULT
Exc(HADBS1..CICSWK1 - MV29 ) Tas(ðððð121)
Task(ðððð121)
Displayed fields

CEMT INQUIRE FEPI
Exci(value) CEMT INQUIRE FEPI

indicates that this panel relates to an EXCI inquiry.
The value consists of: Comments: For information on CEMT INQUIRE
FECONNECTION, CEMT INQUIRE FEPOOL, CEMT
jobname.stepname.procname - mvsid
INQUIRE FEPROPSET, and CEMT INQUIRE FETARGET,
One or both of the stepname and procname may not be see the CICS Front End Programming Interface User's
present, indicated by the periods (.) being adjacent to Guide.
one another.
The mvsid identifies the MVS system on which the job is
running. If XCF/MRO is in use, the job can reside on a
different MVS image from that on which CICS is running.
Task(value)
displays the task number of the mirror transaction
running on behalf of a specific batch job.
Information about jobs using the external CICS interface
is available only after that job has issued at least one
DPL request. A nonzero task number indicates that a
DPL request is currently active. A zero task number
indicates that an external CICS interface session is still
open (connected) for that job, although no DPL request
is currently active.
| Urid(value)
| displays, when the job is using RRMS to coordinate
| updates, and when there is an active DPL request for
| the session, a 32-character string containing the
| hexadecimal representation of the RRMS Unit of
| Recovery Identifier.

CEMT INQUIRE FILE
CEMT INQUIRE FILE

┌─ALl─────┐
55──CEMT Inquire FIle──┼─────────┼─────────────5
Function: Retrieve information about VSAM, BDAM, and └─(value)─┘
remote files, and files that refer to data tables.
5──┬────────┬──┬────────┬──┬───────────┬───────5
├─Vsam───┤ ├─OPen───┤ ├─ENabled───┤
Description: The values that are returned to you can vary ├─BDam───┤ └─CLosed─┘ ├─UNenabled─┤
according to when the command is issued. For example, if └─REMote─┘ └─DIsabled──┘
the file is closed when you issue the command, much of the 5──┬────────┬──┬──────────┬──┬───────────┬─────5
information you receive tells you the state of the file when it ├─REAd───┤ ├─UPdate───┤ ├─ADdable───┤
is next opened. If the file has never been opened, you └─NORead─┘ └─NOUpdate─┘ └─NOAddable─┘
receive default or null values for some of the options, which 5──┬──────────┬──┬──────────┬──────────────────5
could change when the file is opened. ├─BRowse───┤ ├─DElete───┤
└─NOBrowse─┘ └─NODelete─┘
Input: Press the Clear key to clear the screen. There are 5──┬─────────────┬──┬───────┬──┬────────┬──────5
two ways of commencing this transaction: ├─EXclusive───┤ ├─OLd───┤ ├─RLs────┤
└─NOEXclusive─┘ └─Share─┘ └─NOTRls─┘
Type CEMT INQUIRE FILE (the minimum abbreviation is
CEMT I FI). You get a display that lists the current status 5──┬────────────┬──┬───────────────┬───────────5
| of all files installed. ├─EMptyreq───┤ └─DSname(value)─┘
└─NOEMptyreq─┘
Type CEMT INQUIRE FILE (CEMT I FI) followed by as 5──┬───────────┬──┬────────┬───────────────────5
many of the other attributes as are necessary to limit the | ├─NOTTable──┤ ├─LOAd───┤
range of information that you require. So, for example, if | ├─CIcstable─┤ └─NOLoad─┘
you enter cemt i fi v op en up, the resulting display | ├─USertable─┤
| └─CFTable───┘
will show you the details of only those files that are
VSAM, open, enabled, and updatable. 5──┬─────────────────┬─────────────────────────5
| └─CFDtpool(value)─┘
5──┬──────────────────┬──┬────────────┬────────5
overtype them with the required values. | └─Tablename(value)─┘ ├─LOCKING────┤
| └─COntention─┘
5──┬───────────────────┬───────────────────────5
└─Maxnumrecs(value)─┘
5──┬──────────────────┬────────────────────────5
| └─Keylength(value)─┘
5──┬───────────────────┬──5%
| └─RECordsize(value)─┘
(value)
specifies one or more names (1-8 characters) of files
defined to CICS.
ALl
is the default. Information about all files is given, unless
you specify a selection of files to be queried.
Sample screen
à IN FILE
ð
Fil(DFHCMACD) Vsa Ope Ena Rea Sha
Dsn( CICSTS13.CICS.DFHCMACD )
Fil(DFHCSD ) Vsa Clo Une Rea Upd Add Bro Del Sha
Dsn( CICSTS13.CICS.CICSH.DFHCSD )
| Fil(DFHDBFK ) Vsa Clo Ena Rea Upd Add Bro Del Sha
| Fil(DFHLRQ ) Vsa Ope Ena Rea Upd Add Bro Del Sha
| Dsn( CICSTS13.CICS.CICSH.DFHLRQ )
Fil(FILEA ) Vsa Clo Ena Rea Upd Add Bro Del Sha
| Dsn( CICSTS13.CICS.CICSH.FILEA ) Cft Loa
Figure 74. CEMT INQUIRE FILE screen


CEMT INQUIRE FILE
by tabbing (they appear in the same sequence as in Note: You can reset this value by overtyping it with a
the expanded format), and overtype with input valid different value.
| CFDtpool(name)
| displays, for a file that refers to a coupling facility data
| table, the 8-character name of the coupling facility data
| table pool in which the CFDT resides.
| If the pool name is not defined, the name is displayed as
If you place the cursor against a specific entry in the list and | 8 blanks. If the pool name is specified, it is always
press ENTER, CICS displays an expanded format as shown | displayed even if the file definition does not refer to a
in Figure 75. | coupling facility data table.
Deletestatus
displays whether you can delete records from the file.
à INQ FILE
ð The values are:
File(DFHCSD)
Accessmethod(Vsam)
Openstatus( Closed ) DElete
Enablestatus( Unenabled )
Readstatus( Read ) You can delete records from the file.
Updatestatus( Update )
Addstatus( Addable )
Browsestatus( Browse ) NODelete
Deletestatus( Delete )
Exclstatus(
Disposition( Share )
) You cannot delete records from the file.
Rlsaccess( Notrls )
Emptystatus( Noemptyreq )
Dsname( CICSTS13.CICS.CICSH.DFHCSD
Table( Nottable )
)
Loadtype( Noload )
Cfdtpool( ) different value.
+ Tablename( )
Updatemodel( )
Maxnumrecs( ðððððððð ) Disposition
Keylength( ððð )
Recordsize( ððððð ) displays the disposition of this file. The values are:
OLd The disposition of the data set associated with the

Figure 75. The expanded display of an individual entry file is defined as unshared for dynamic allocation.
Share
Displayed fields The disposition of the data set associated with the
Accessmethod file is defined as shared for dynamic allocation.
displays the access method of the file. The values are:
Vsam different value.
Virtual storage access method (VSAM).
DSname(value)
BDam displays the name (1–44 characters) of the VSAM or
Basic direct access method (BDAM). BDAM data set with which this file is associated.
REMote | For a coupling facility data table, CICS displays the
The file is defined as remote. | name of the source data set if the file specifies that the
Addstatus | table is initially loaded from a data set, otherwise CICS
displays whether new records can be added to the file. | displays blanks.
The values are: | CICS also displays blanks for files that have their
| DSNAME specified on a DD statement in the CICS JCL
ADdable
| if the file has not been opened since the last cold or
New records can be added to the file.
| initial start.
NOAddable
| Note: If the file is disabled, you can change this name
New records cannot be added to the file.
| by overtyping it with a different value.
Note: You can reset this value by overtyping it with a Emptystatus (VSAM only)
different value. displays whether the data set is to be made empty when
| a file that references it is next opened. This is valid only
Browsestatus
| for data sets that have been defined as reusable and are
displays whether you can browse the file. The values
| accessed in non-RLS mode. The values are:
are:
EMptyreq
BRowse
Applies only to a VSAM file that has been defined
You can browse records in the file.
to VSAM as a cluster with the REUSE parameter.
NOBrowse
You cannot browse records in the file.

CEMT INQUIRE FILE
It indicates that when a file is next opened, its | Notes:

data is erased.
| 1. If the file is closed and the key length is not defined
NOEMptyreq | in the file definition, CICS displays a zero value.
Applies only to VSAM files. It indicates that when
| 2. If the file is closed and a key length is defined on
a file is next opened, its data is not erased.
| the file definition, CICS displays the value from the
| file definition.
different value. | 3. Generally, if a file is open, CICS obtains the key
| length from the associated data set, in which case
Enablestatus
| CICS displays the value from the data set.
displays whether transactions can access the file. The
| However, files that refer to coupling facility data
values are:
| tables defined with LOAD(NO) must get their
ENabled | keylength from the file definition, in which case
The file is available for use by transactions and, if | CICS returns the defined value when the file is
closed, it is opened on the first request. | open. This value must also match that of the
| coupling facility data table if it has already been
UNenabled
| created.
The file is not available for use by transactions
except for those that are currently using it. If there | Loadtype
are any such users, ‘BEING CLOSED’ is also | displays the load type for a coupling facility data table.
displayed. | The values are:
This status is the same as DISABLED except that | LOAD
it occurs implicitly when a SET FILE CLOSE is | The coupling facility data table is, or is to be,
requested. The file is enabled implicitly by a SET | preloaded from a source data set.
FILE OPEN command.
| NOLOAD
DIsabled | The coupling facility data table is not preloaded
The file is not available for use by transactions | from a source data set.
except for those that are currently using it. If there
are any such users, ‘BEING DISABLED’ is also Maxnumrecs(value)
displayed. displays the maximum number of records that the data
table for this file can hold.
The file can be reenabled by a SET FILE
ENABLED command. (See also UNENABLED.) | Notes:
It is not possible to disable a remote file. | 1. If the file resource definition specifies a
| MAXNUMRECS numeric value, even though the
Note: You can reset this value by overtyping it with | object is not a table (NOTTABLE is displayed on the
Enabled or Disabled. | TABLE option), CICS displays the specified value.
| The value can be in the range 1 through
Exclstatus (BDAM only)
| 99 999 999.
displays whether records on this file are to be placed
under exclusive control when a read for update is | 2. If the file resource definition is specified with
issued. The values are: | MAXNUMRECS(NOLIMIT), meaning the number of
| records is unlimited, CICS displays a value of zero.
EXclusive | (Internally, CICS holds NOLIMIT as the maximum
Records on the file are protected from | positive fullword value (+2147483647 or
simultaneous update. | X'7FFFFFFF').
NOEXclusive | 3. If the file is remote, CICS displays a value of minus
Records on the file are not protected from | 1 (-1).
simultaneous update.
| 4. If the object is a coupling facility data table:
FIle(value)
| The maximum number of records can be
indicates that this panel relates to a file inquiry and
| altered by a coupling facility data table server
displays an 8-character file name.
| command, leaving the file definition
| Keylength(value) | MAXNUMRECS value unchanged. CICS
| displays the length of the record key for a file associated | displays the value in the file definition until the
| with a VSAM KSDS or a file associated with a coupling | file is opened, after which CICS displays the
| facility data table. If the file is associated with a BDAM | actual MAXNUMRECS value defined to the
| data set, the value is the length of the logical key used | server.
| for deblocking.

CEMT INQUIRE FILE
| If the value is changed again by a coupling Note: You can reset this value by overtyping it with a
| facility data table server command, CICS different value.
| obtains and displays the new value only after a
| RECordsize(value)
| file control operation on the table. Until then,
| displays the actual size of fixed-length records, or the
| CICS continues to display the old value.
| maximum size of variable-length records.
| You can use the server DISPLAY TABLE
| If the file is not open, CICS displays the value specified
| console command to obtain the current value
| in the installed file definition. If the file definition does not
| for a coupling facility data table.
| specify a record size, CICS displays a zero value.
Note: You can reset this value by overtyping it with a | Generally, if a file is open, CICS obtains the record size
different value. The new value takes effect only | from the associated data set, in which case CICS
when a new data table is created (which | displays the value from the data set. However, files that
happens on each file open for a | refer to coupling facility data tables defined with
CICS-maintained or user-maintained data table, | LOAD(NO) must get their record size from the file
but only when the table does not already exist for | definition, in which case CICS returns the defined value
a CF data table). | when the file is open. This value must also match that of
| the coupling facility data table if it has already been
Openstatus
| created.
displays the open status of the file. The values are:
OPen
Rlsaccess (VSAM only)
The file is open. If the file is OPEN ENABLED, it is
displays whether the file is defined to be accessed in
available for data accesses by CICS transactions.
RLS mode. The values are:
If it is OPEN DISABLED, it must first be enabled
before it is available. RLs The file is defined to be accessed in RLS mode.
CLosed NOTRls
The file is closed; the access method does not The file is defined to be accessed in a non-RLS
allow accesses to the data until the file is opened. mode (LSR or NSR)
The file can be opened either explicitly by the user
or, if the file has the ENABLED attribute, implicitly Note: You can reset this value by overtyping it with a
by CICS on the next reference to the file. different value.
A file with the DISABLED attribute can be enabled Table
only by a SET FILE ENABLED command. A file displays whether the file name specified on the FILE
with the UNENABLED attribute can be enabled by parameter represents a data table. The values are:
a SET FILE ENABLED command or SET FILE
OPEN command. NOTTable
The file name does not represent a data table.
The CLOSED status may be a temporary status
for a file that has just come out of LOADMODE | CFTABLE
status. | The file name represents a coupling facility data
| table.
Note: You can reset this value by overtyping it with one CICSTABLE
of the above Openstatus values, or with: The file name represents a CICS-maintained data
table.
Forceclose
Specifies that the file is to be closed, and USERTABLE
the tasks of any existing users of the file The file name represents a user-maintained data
are to be abended. table.
Readstatus Note: You can reset this value by overtyping it with a

displays whether you can read records from the file. The different value.
values are:
| Tablename(value)
| displays the table name specified for the coupling facility
REAd | data table on the file resource definition, if one is
You can read records in the file. | specified, or displays the file name if no table name was
| specified on the file resource definition.
NORead
You cannot read records in the file. | CICS displays blanks if the file does not refer to a
| coupling facility data table

CEMT INQUIRE GTFTRACE
| Updatemodel (CFDT only) CEMT INQUIRE GTFTRACE

| displays the update model specified for the coupling
| facility data table in the installed file definition. The Function: Show the GTF status.
| values are:
Description: CEMT INQUIRE GTFTRACE tells you
| CONTENTION
whether CICS tracing to the MVS Generalized Tracing
| The coupling facility data table is updated using
Facility (GTF) is started or stopped.
| the contention model.
| LOCKING This command is intended for use at terminals that do not
| The coupling facility data table is updated using support the CETR full-screen tracing transaction.
| the locking model.
For background information about GTF tracing, see the CICS
Updatestatus Problem Determination Guide.
displays whether the file is updatable. The values are:
UPdate
GTFTRACE (the minimum abbreviation is CEMT I G).
You can update records in the file.
NOUpdate You will get a display screen, a sample of which is shown
You cannot update records in the file. below. If you want to change the displayed value, you can
then tab to the highlighted field and overtype it as required.
different value. Sample screen
à IN GTFTRA
ð
Gtf Sto
Figure 76. CEMT INQUIRE GTFTRACE screen
à IN GTFT
ð
Gtftrace
Status( Stop )
55──CEMT Inquire Gtftrace──5%
Displayed fields
Gtftrace
indicates that this panel relates to a GTFTRACE inquiry.
STArt
(GTF) is in progress.
STOpped
(GTF) is not in progress.
different value.

CEMT INQUIRE INTTRACE CEMT INQUIRE IRBATCH
CEMT INQUIRE INTTRACE CEMT INQUIRE IRBATCH

Function: Show the status of CICS internal tracing. Function: Retrieve information about jobs using the
external CICS interface.
Description: INQUIRE INTTRACE tells you whether CICS
internal tracing is in progress. Description: CEMT INQUIRE IRBATCH is retained for
compatibility. You should use CEMT INQUIRE EXCI.
support the full-screen tracing transaction CETR.

INTTRACE (the minimum abbreviation is CEMT I IN).

below. If you want to change the displayed value, you can
then tab to the highlighted field and overtype it as required.
Sample screen
à IN INTTRA
ð
Int Sta
Figure 78. CEMT INQUIRE INTTRACE screen
à IN INTT
ð
Inttrace
Status( Start )
55──CEMT Inquire INttrace──5%
Displayed fields
INttrace
indicates that this panel relates to an INTTRACE inquiry.
STArt
CICS internal tracing is in progress.
STOpped
CICS internal tracing is not in progress.
different value.

CEMT INQUIRE IRC
CEMT INQUIRE IRC IRc

indicates that this panel relates to an IRC inquiry.
Function: Show the IRC status. Openstatus(value)
displays whether the interregion communication (IRC)
Description: INQUIRE IRC tells you whether the
facility is open or closed. The values are:
interregion communication (IRC) facility is open or closed.
Closed
Input: Press the Clear key and type CEMT INQUIRE IRC (the Interregion communication for this CICS system is
minimum abbreviation is CEMT I IRC). terminated after tasks using the session have
terminated normally.
below. Open
Interregion communication for this CICS system is
Sample screen initialized. This allows connections to be
established between this system and other
systems. You can control the availability of
à ð individual connections with the INSERVICE or
IN IRC
STATUS: RESULTS - OVERTYPE TO MODIFY OUTSERVICE settings on the connection names,
Irc Clo
using CEMT INQUIRE CONNECTION or CEMT
SET CONNECTION.
The DFHIR3780 message is issued to the console
log if the region made an unsuccessful attempt to
Figure 80. CEMT INQUIRE IRC screen
start IRC.
CICS displays an expanded format as shown in Figure 81. Notes:
1. You can reset this value by overtyping it with a

different value, or with:
à IN IRC
ð Immclose
Irc
Openstatus( Closed ) All tasks using IRC sessions are to be
Return(ðððððððð)
Reason(ðððððððð) abended when they next try to use the
session. Interregion communication is
terminated when all tasks that were using IRC
have been abended or have terminated
Figure 81. The expanded display normally.
2. The values of Return and Reason will be nonzero
55──CEMT Inquire IRc──5% only after certain SET (or overtype) failures. These
are accompanied by a message number, which you
should refer to in the CICS Messages and Codes
Displayed fields manual.

CEMT INQUIRE JMODEL
CEMT INQUIRE JMODEL If you place the cursor against a specific entry in the list and
Function: Retrieve information about journal models and in Figure 82.
log stream names.
Description: The INQUIRE JMODEL command enables à IN JMODE

ð
you to inquire on installed journal models to obtain RESULT
Jmodel(DFHJð2)
corresponding log stream names. Journalname(DFHJð2)
Type(Mvs)
Streamname(BELL.TESTLOG.FWDRECOV)
Input: Press the CLEAR key to clear the screen. There are
Type CEMT INQUIRE JMODEL (the minimum abbreviation is
CEMT I JM). You get a display that lists the current Figure 82. The expanded display of an individual entry
status.
Displayed fields
Type CEMT INQUIRE JMODEL (CEMT I JM) followed by as
many of the other attributes as are necessary to limit the JModel(value)
range of information that you require. So, for example, if indicates that this panel relates to a journal model
you enter cemt i jm sm, the resulting display will show inquiry and displays the 8–character name of an
you the details of only those journal models that are of installed journal model.
SMF log stream type.
Journalname
displays the 8–character journal name, which can be a
┌─All─────┐ specific or a generic name, for which this journal model
55──CEMT Inquire JModel──┼─────────┼───────────5 can be used.
└─(value)─┘
STreamname
5──┬────────────────────┬──┬───────┬───────────5 displays the MVS log stream name (LSN) associated
└─(Journalnamevalue)─┘ ├─Mvs───┤
├─SMf───┤ with this journal model. The name can be a specific
└─Dummy─┘ | LSN, or a template using any 3 of the 4 symbols
5──┬───────────────────┬──5% | &USERID, &APPLID, &JNAME and &SYSID.
└─STreamname(value)─┘ An LSN or template can be up to 26 characters in
length.
(value) Type
specifies one or more journal models. displays the log stream type. The possible types are:
All is the default. Mvs Records for journals defined with this journal
model are written to an MVS log stream.
Sample screen
SMf Records for journals defined with this journal
model are written to the MVS SMF data set.
à ð Dummy
IN JMODE
STATUS: RESULTS Records for journals defined with this journal
Jmo(DFHJð2 ) Jou(DFHJð2 ) Mvs
Str(BELL.TESTLOG.FWDRECOV ) model are not written to any log stream.
Jmo(DFHLOG ) Jou(DFHLOG ) Mvs
Str(&USERID..&APPLID..&JNAME. )
Jmo(DFHSHUNT) Jou(DFHSHUNT) Mvs
Str(&USERID..&APPLID..&JNAME. )
For information on changing JMODEL definitions, see the
CICS Resource Definition Guide.

CEMT INQUIRE JOURNALNAME
CEMT INQUIRE JOURNALNAME Note: Blank fields on the screen indicate that a value does
not apply or is ‘negative’; that is, it begins with ‘No’.
Function: Show the status of the CICS system log and
If you place the cursor against a specific entry in the list,
general logs.
Description: The INQUIRE JOURNALNAME command
enables you to inquire on the status of the CICS system log
and general logs. It replaces the INQUIRE JOURNALNUM à IN JOUR
ð
command. Journalname(DFHLOG)
Type(Smf)
Status( Enabled )
Input: Press the CLEAR key to clear the screen. There are Action( )
Streamname(CICSHT##.CICSHTA1.DFHLOG)
Type CEMT INQUIRE JOURNALNAME (the minimum
abbreviation is CEMT I JO). You get a display that lists Figure 84. The expanded display
the current status.
Type CEMT INQUIRE JOURNALNAME (CEMT I JO) followed by
Displayed fields
as many of the other attributes as are necessary to limit Action(value)
the range of information that you require. So, for specifies the action you want CICS to take for the
example, if you enter cemt i jo sm, the resulting display specified journal name. The values are:
will show you the details of only those logs that are of
SMF log stream type. Flush
The log buffers are written out to the log stream
Input but the journal is not closed.
You can use this option to ensure that all current
records are written out to the log stream before
┌─All─────┐
55──CEMT Inquire JOurnalname──┴─(value)─┴──────5 the stream is processed using a batch utility.
5──┬───────┬──┬──────────┬─────────────────────5 Reset
├─Mvs───┤ ├─Enabled──┤ The journal is disabled but can be reenabled by
├─SMf───┤ ├─DIsabled─┤ the SET JOURNALNAME RESET command.
└─DUmmy─┘ └─FAiled───┘
5──┬───────────────────┬──5% JOurnalname(value)
└─STreamname(value)─┘ indicates that this panel relates to a journal name inquiry
and displays a 1– to 8–character journal name.
(value) Status
specifies one or more journal names. displays the status of the journal. The possible values
are:
To inquire on journals defined with a numeric identifier in
the range 1–99, specify journal name DFHJnn, where nn Enabled
is the journal number. The journal is installed and available for use.
To inquire on the system log, specify DFHLOG. DIsabled
The journal has been disabled by a CEMT, or
To inquire on the log-of-logs, specify DFHLGLOG.
EXEC CICS, SET JOURNALNAME(...) command.
All is the default. It cannot be used until it is re-enabled by the
STATUS(ENABLED) or ACTION(RESET) options
Sample screen on a SET JOURNALNAME command.
FAiled
The journal has experienced a log stream failure.
à IN JOUR
ð It cannot be used until it is re-enabled by the
Journaln(DFHJð2 ) Smf Ena STATUS(ENABLED) or ACTION(RESET) options
Journaln(DFHLGLOG) Mvs Ena
Str(CICSHT##.CICSHTA1.DFHLGLOG ) on a a SET JOURNALNAME command, or until
Journaln(DFHLOG ) Mvs Ena
Str(CICSHT##.CICSHTA1.DFHLOG ) following the next CICS restart. The log stream
Journaln(DFHSHUNT) Mvs Ena
Str(CICSHT##.CICSHTA1.DFHSHUNT ) should be deleted from the MVS system logger
inventory before being used again.
Figure 83. CEMT INQUIRE JOURNALNAME screen Note: You can reset STATUS with ENABLED or
DISABLED.

CEMT INQUIRE LINE
STreamname(value) CEMT INQUIRE LINE

displays the MVS log stream name associated with the
journal. CICS displays 8 blanks (X'40') if the journal is Function: Retrieve information about lines connected to
defined with a type of DUMMY or SMF. terminals. This request is valid only for non-VTAM terminals.
Type
Input: Press the Clear key to clear the screen. There are
displays the type of log stream. The possible types are:
Mvs Records for journals defined with this journal Type CEMT INQUIRE LINE(value) (the minimum
model are written to an MVS log stream. abbreviation is CEMT I L(value)). You get a display that
SMf Records for journals defined with this journal lists the current status of the named line.
model are written to the MVS SMF data set. Type CEMT INQUIRE LINE(termid) (CEMT I L(termid))
DUmmy followed by as many of the other attributes as are
Records for journals defined with this journal necessary to limit the range of information that you
model are not written to any log stream. require.
You can specify a list of identifiers (see “List of resource

identifiers” on page 47), but you cannot use the symbols *
and + to specify a family of identifiers. You can then tab to
the highlighted or blank fields and overtype them with the
required values.
55──CEMT Inquire Line──(value)─────────────────5

5──┬───────────────┬──┬────────────────┬───────5
└─NUmber(value)─┘ └─NEgpoll(value)─┘
5──┬────────────┬──5%
├─Inservice──┤
└─Outservice─┘
Sample screen
à INQ LINE(TTT1)
ð
STATUS: RESULTS
Lin(TTT1) Neg( ððð8ð ) Ins
Figure 85. CEMT INQUIRE MODENAME screen

If you place the cursor against a specific entry in the list,

CICS displays an expanded format as shown in Figure 86 on
page 95.

CEMT INQUIRE MODENAME

à INQ LINE(TTT1)
ð
RESULT
Line(TTT1)
Number()
Function: Retrieve information about connection sessions.
Negpoll( ððð8ð )
Purgetype( ) Description: INQUIRE MODENAME returns information
about the named group of sessions that has been defined for
a connection to a remote system or to another CICS region.
Displayed fields two ways of commencing this transaction:
Inservice Type CEMT INQUIRE MODENAME (the minimum abbreviation
The line is available for use. Changing the status of the is CEMT I MOD). You get a display that lists the current
line does not affect the equivalent status of the terminals status.
on it.
Type CEMT INQUIRE MODENAME (CEMT I MOD) followed by
Line(value) as many of the other attributes as are necessary to limit
indicates that this panel relates to a LINE inquiry and the range of information that you require. So, for
displays the identifier of a terminal on the line. This example, if you enter cemt i mod acq, the resulting
request is valid only for non-VTAM terminals. display will show you the details of all modenames that
are acquired.
NEgpoll(value)
displays the negative poll delay interval (0–20000 Mode names need not be unique. You cannot specify a list
milliseconds). For a TCAM line, this specifies the of names, but you can use the symbols * and + to specify a
interval before control is passed to the terminal error family of mode names.
program (DFHTEP) when a CICS task is not ready to
accept a record from an input process queue. A mode name consisting of eight blanks is valid. To specify
this name, enclose the string of blanks within single quotation
If the CICS task issues a read before the interval
marks:
expires, processing continues normally and DFHTEP is
not notified. The default value is zero. MODENAME(' ')
NUmber(value)
displays the relative line number of a pooled line. For
information about pooled lines, see the CICS Resource
Definition Guide. ┌─ALl─┐
55──CEMT Inquire MODename───┴─────┴────────────5
Outservice
The line is not available for use. Changing the status of 5──┬─────────┬──┬───────────────────┬──────────5
the line does not affect the equivalent status of the └─(value)─┘ └─COnnection(value)─┘
terminals on it. 5──┬────────────────┬──┬──────────────────┬────5
└─Maximum(value)─┘ └─AVailable(value)─┘
5──┬───────────────┬──5%
└─ACTive(value)─┘
(value)
specifies one or more names (1-8 characters) of a group
of sessions.
ALl
is the default.
Sample screen
à I MODE
ð
Mod(SNASVCMG) Con(C ) Max(ðð2) Ava( ððð ) Act(ððð)
Mod(MODE1 ) Con(C ) Max(ðð1) Ava( ððð ) Act(ððð)
Figure 87. CEMT INQUIRE MODENAME screen

Note: There are blank fields on the screen where a value Closed
does not apply or is ‘negative’; that is, the value CICS releases all sessions within the group. The
begins with ‘No’. To modify these fields, locate them sessions are quiesced and unbound. No further
by tabbing (they appear in the same sequence as in sessions can be acquired by another CICS
the expanded format), and overtype with input valid system. No further activity is possible on the
for that field. You may find it more convenient to use sessions within the group until the group is
the expanded format when setting one of these reacquired by the same CICS system in which it
values, (negating is easier because you are has been closed.
ACTive(value)
displays the number of sessions within the group (or
If you place the cursor against a specific entry in the list, “modename”) that are currently in use (“bound”).
AVailable(value)
displays the currently negotiated number of sessions
within the group that can be allocated for use at one
à I MODE
ð time.
Modename(MODE1)
Connection( C ) Note: You can reset this value by overtyping it with a
Maximum(ðð1)
Available( ððð ) different value.
Active(ððð)
Acqstatus( )
COnnection(value)
displays the 4-character identifier of the remote system
Figure 88. The expanded display with which this group of IRC or ISC sessions is
connected.
Displayed fields
Maximum(value)
Acqstatus (input only field) displays the maximum number of sessions that are
specifies the acquisition status of sessions. The values supported at one time within this group of sessions, in
are: the range 0–999.
Acquired MODename(value)
CICS should acquire (or “bind”) all the negotiated indicates that this panel relates to a MODENAME inquiry
contention-winner sessions within the group. and displays one or more names (1-8 characters) of a
group of sessions.

CEMT INQUIRE MONITOR
CEMT INQUIRE MONITOR Conversest

displays whether conversational tasks are to have
Function: Retrieve information about the status of CICS separate performance class records produced for each
monitoring. pair of terminal control I/O requests (Converse or
Send/Receive pair). The values are:
Description: INQUIRE MONITOR tells you whether
Converse
monitoring is switched on or off, which classes of monitoring
Separate performance class records will be
data are to be collected, and the current settings of the
produced.
monitoring options.
Noconverse
Input: Press the Clear key to clear the screen, and type Separate performance class records will not be
CEMT INQUIRE MONITOR (the minimum abbreviation is CEMT I produced.
MON). You get a display that lists the current status.
Sample screen different value.
Eventclass
displays whether the SYSEVENT class of monitoring
à IN MONITOR
ð data is being collected. The values are:
Mon Off Fre( ðððððð ) Gmt Sub(IYAH)
Event
SYSEVENT-class monitoring data is being
collected.
Figure 89. CEMT INQUIRE MONITOR screen
Note: There are implications with using the Event
class of monitoring and MVS 5.1 WLM. For
information, see the CICS Performance
Guide.
by tabbing (they appear in the same sequence as in Noevent
the expanded format), and overtype with input valid SYSEVENT-class monitoring data is not being
for that field. You may find it more convenient to use collected.
values, (negating is easier because you are Note: You can reset this value by overtyping it with a
overtyping a displayed field with its negative causing different value.
Exceptclass
If you place the cursor against the result and press ENTER, displays whether the exception class of monitoring data
CICS displays an expanded format as shown in Figure 90. is being collected. The values are:
Except
Exception-class monitoring data is being collected.
à IN MON
ð Noexcept
Monitor
Status( Off ) Exception-class monitoring data is not being
Perfclass( Noperf )
Eventclass( Noevent ) collected.
Exceptclass( Noexcept )
Conversest( Noconverse )
Syncpointst( Nosyncpoint )
Frequency( ðððððð ) Note: You can reset this value by overtyping it with a
Time(Gmt)
Subsystemid(CICS) different value.
Frequency(value)
Figure 90. The expanded display displays the interval for which monitoring automatically
produces a transaction performance class record for any
long-running transaction that has been in the system for
55──CEMT Inquire MONitor──┬───────┬────────────5
├─Gmt───┤ a greater time than the interval. FREQUENCY values
└─Local─┘ can be either 000000 (meaning that FREQUENCY
5──┬────────────────────┬──5% monitoring is inactive), or in the range 001500–240000.
└─SUbsystemid(value)─┘ Note: You can reset this value by overtyping it with a
different value.
Displayed fields MONitor

indicates that this panel relates to a MONITOR inquiry.

CEMT INQUIRE MONITOR
Perfclass Syncpointst
displays whether the performance class of monitoring displays whether a transaction performance class record
data is being collected. The values are: is produced when a transaction takes an explicit or
implicit syncpoint (unit-of-work), except when the
Perf Performance-class monitoring data is being
syncpoint is part of task termination or a syncpoint
collected.
rollback. The values are:
Noperf
Syncpoint
Performance-class monitoring data is not being
A transaction performance class record will be
collected.
produced.
Note: You can reset this value by overtyping it with a Nosyncpoint
different value. A transaction performance class record will not be
produced.
Status
displays whether monitoring is active. The values are:
On Monitoring data is accumulated continuously, and different value.
is collected (written out to an SMF data set) for
Time
each of the classes of monitoring data that is
displays whether the time stamp fields in the
active.
performance class monitoring data are returned in GMT
Off No monitoring data is accumulated or collected, or local time to an application using the EXEC CICS
irrespective of the settings of the monitoring data COLLECT STATISTICS MONITORING(taskno)
classes. command. The values are:
Gmt The time stamp fields in the performance class

data are Greenwich mean time (GMT).
different value.
Local
SUbsystemid(value)
The time stamp fields in the performance class
displays a 4-character name used as the subsystem
data are local time.
identification in the monitoring SYSEVENT class records.
The subsystem identification defaults to the first 4
For programming information on the EXEC CICS
characters of the VTAM generic APPLID.
COLLECT STATISTICS command, see the CICS
For information on the SYSEVENT class of monitoring System Programming Reference manual.
data and the VTAM generic APPLID, see the CICS
Performance Guide.

CEMT INQUIRE NETNAME

à IN NETNAME
ð
Function: Retrieve information about a network. Net(IGKS2ð5 ) Tra(CEMT) Pri( ððð ) Pag Ins Ati Tti
Ter(S2ð5) Acq
Description: If you are familiar with network names, you

may prefer to use this command as an alternative to CEMT
INQUIRE TERMINAL. Figure 91. CEMT INQUIRE NETNAME screen
Input: Press the Clear key to clear the screen. There are Note: There are blank fields on the screen where a value
two ways of commencing this transaction: does not apply or is ‘negative’; that is, the value
Type CEMT INQUIRE NETNAME (the minimum abbreviation begins with ‘No’. To modify these fields, locate them
is CEMT I N). You get a display that lists the current by tabbing (they appear in the same sequence as in
status. the expanded format), and overtype with input valid
Type CEMT INQUIRE NETNAME (CEMT I N) followed by as the expanded format when setting one of these
many of the other attributes as are necessary to limit the values, (negating is easier because you are
range of information that you require. So, for example, if overtyping a displayed field with its negative causing
you enter cemt i n ins ati, the resulting display will the result to become non-displayed).
show you the details of only those netnames that are in
service and available for use. If you place the cursor against a specific entry in the list and
You can then tab to the highlighted or blank fields and press ENTER, CICS displays an expanded format as shown
overtype them with the required values. in Figure 92.
┌─ALl─────┐
55──CEMT Inquire Netname──┼─────────┼──────────5
à IN NET
ð
└─(value)─┘ Netname(IG2S944D)
Transaction(CEMT)
Priority( ððð )
5──┬────────────────────┬──────────────────────5 Pagestatus( Pageable )
└─TRansaction(value)─┘ Atistatus( Ati )
Ttistatus( Tti )
Nature(Local)
5──┬─────────────────┬──┬──────────────┬───────5 Purgetype( )
└─PRiority(value)─┘ ├─PAgeable─────┤ Terminal(944D)
Termstatus( Acquired )
└─AUtopageable─┘ Createsess( Nocreate )
Task(ððð33)
Remotesystem()
5──┬────────────┬──┬───────┬──┬───────┬────────5 Rname()
├─Inservice──┤ ├─ATi───┤ ├─TTi───┤ Rnetname()
Cid()
└─Outservice─┘ └─NOAti─┘ └─NOTti─┘
5──┬───────────┬──┬─────────────────┬──────────5
├─RTerminal─┤ └─TErminal(value)─┘ Figure 92. The expanded display of an individual entry
├─RSession──┤
├─Session───┤
└─Local─────┘ Displayed fields
5──┬──────────┬──┬──────────┬──────────────────5 Atistatus
├─ACquired─┤ ├─CReate───┤ displays whether the terminal is available for use by
├─COldacq──┤ └─NOCreate─┘ transactions that are automatically initiated from within
└─RELeased─┘
CICS or, if the terminal is an ISC session, by
5──┬─────────────┬──┬─────────────────────┬────5 transactions that are using this session as an alternate
└─TAsk(value)─┘ └─REMotesystem(value)─┘
facility to communicate with another system. The values
5──┬──────────────┬──┬─────────────────┬───────5 are:
└─RNAme(value)─┘ └─RNEtname(value)─┘
5──┬────────────┬───┬────────┬───5% ATi The terminal is available for use.
└─CId(value)─┘ └─Userid─┘ NOAti
The terminal is not available for use.
(value)
Notes:
specifies an 8-character network name.
ALl
different value.
is the default.
2. A terminal cannot be defined with both NOATI and
Sample screen NOTTI.

CId(value) Session
displays an 8-character correlation-identifier that is set The terminal is an ISC or IRC session.
only for sessions, and only after a session has been
Local
acquired. (The value relates to the previously acquired
The terminal is directly attached to this system
session if there was one, if the session is not acquired).
and is a physical device or a function of a cluster
CID is set as follows:
controller.
For LU6.2 sessions, it is an 8-character
Netname(value)
hexadecimal token which is common to the two end
indicates that this panel relates to a NETNAME inquiry
sessions that are connected together.
and displays an 8-character network name.
For MRO sessions, it is set to the termid of the
For a physical terminal, the Netname is the name by
session on the system to which this session is
which this terminal is known to VTAM.
connected.
For ISC sessions, the Netname is the name by
For LU6.1 sessions to IMS, it is set to the value of
which the session (or group of sessions) is known to
NETNAMEQ as defined or negotiated.
VTAM.
For other LU6.1 sessions, it is set to the value
For IRC sessions, the Netname is the name used
supplied by the other end of the 6.1 session.
by the connected region to logon to the interregion
Using CID, you can relate the two parts of an LU6.2, communication program (DFHIRP).
MRO, or LU61 conversation together:
For EXCI sessions, the Netname is DFHGEN for
For LU6.2, you can inquire on the same CID. generic sessions and, for specific sessions, it is the
For MRO, you can locate the session with the value of the user_name parameter used in the EXCI
terminal name. INITIALISE_USER call.
For LU6.1 to IMS, you can inquire on the netname. When an inquiry is made on DFHGEN, the name is
For other LU6.1, you can use the name to inquire an 8-character field with a leading and trailing blank
on the connected system. (' DFHGEN '). The name must be enclosed in
quotes and include the blanks, so you enter the
Createsess (vtam only)
command on the screen as follows:
displays whether the terminal can be acquired
automatically by ATI transactions. This cannot be CEMT INQ NETNAME(' DFHGEN ')
specified for IRC sessions. The values are: For remote devices, the Netname is the name by
which the device is known to the VTAM in the
CReate owning region.
If the terminal is not in session, CICS acquires it if Pagestatus
it is needed to satisfy an ATI request. displays whether pages after the first in a series are
NOCreate written to the terminal on request from the operator or
If the terminal is not in session, CICS does not automatically. The values are:
acquire it to satisfy an ATI request. A session
PAgeable
must be started by, for example, a logon request
Pages are written on request.
or a CEMT SET TERMINAL ACQUIRED
command before the ATI request can be satisfied. AUtopageable
Pages are written automatically.
If NOCREATE is set for an LU6.1 ISC session and
there are no allocatable sessions left, the
connection is placed OUTSERVICE.
different value.
Note: You can reset this value by overtyping it with a PRiority(value)
different value. displays a 3-character string indicating the priority of this
terminal relative to other terminals. The priority of a task
Nature
is the sum of the transaction priority, the terminal priority,
displays the nature of the terminal—that is, whether it is
and the operator priority. Priority has no meaning for
a physical device or a session, and whether it is local or
terminals that are ISC sessions being used as
remote. The values are:
alternative facilities. The value is in the range 0–255,
RTerminal where 255 is the highest priority.
The terminal is owned by another CICS region. Note: You can reset this value by overtyping it with a
RSession different value.
The terminal is a session of a connection that is
owned by another CICS region.

Purgetype (input only field) For IRC sessions, OUTSERVICE means that the
specifies whether the transactions running with the connection to the MRO partner is OUTSERVICE.
named terminal are to be purged. The values are:
In an LU6.1 ISC session, the connection is set
PUrge OUTSERVICE if there are no allocatable sessions
Transactions are to be terminated only if system left.
and data integrity can be maintained. A
transaction is to be purged if its definition specifies Note: For physical terminals and LU6.1 sessions, you
SPURGE=NO. can reset this value by overtyping it with a
different value.
Forcepurge
Transactions are to be purged immediately. This TAsk(value)
can lead to unpredictable results and should be displays the task number of the transaction that is
used only in exceptional circumstances. running on this terminal.
REMotesystem(value) TErminal(value)
displays the 4-character name of a connection, if the displays a 4-character terminal identifier (1-4 characters)
subject of the inquiry is a remote terminal. The named as specified in an installed terminal definition.
connection can be either a connection entry that links
Termstatus (vtam only)
towards the terminal-owning region (TOR), or an indirect
displays whether CICS is in session with the logical unit
connection that provides the netname of the TOR.
represented by this terminal. The values are:
Otherwise this field is blank.
ACquired
RNAme(value) CICS is in session with the logical unit
displays the 4-character name by which this terminal is represented by the terminal.
known in the system in which it is defined (the TOR).
RELeased
RNAME applies only to terminals defined as remote; for
CICS is not in session with the logical unit
others, blanks are displayed.
represented by the terminal. If you set this option
RNEtname(value) to RELEASED, a session is terminated
displays the 8-character netname of the owning TOR, if immediately if you also specify the PURGE option,
the subject of the inquiry is a remote terminal. If this field otherwise the session is terminated when the
is blank and the terminal is remote, the system named current active transaction finishes.
in the REMOTESYSTEM field has not been installed,
and no value was specified for the REMOTESYSNET Note: For physical terminals and LU6.1 sessions, you
option when the terminal was defined. can reset this value by overtyping it with a
different value or with:
Servstatus
displays whether the terminal is available for use. The COldacq
values are: This is a special form of ACQUIRED,
where no resynchronization is required. If
Inservice
the previous session abended, the use of
The terminal is available for use. For VTAM,
COLDACQ overrides CICS integrity
INSERVICE means that the terminal can be
control. This could lead to integrity
ACQUIRED. For IRC sessions, INSERVICE
problems. Also, you should check the
means that the connection to the MRO partner is
CSMT log for an activity keypoint after the
INSERVICE.
restart of a session following a CICS
Outservice failure. If there is no activity keypoint, you
The terminal is not available for use. Setting a should issue COLDACQ again after the
terminal OUTSERVICE means that the terminal next emergency restart.
can no longer be used by transactions. If PURGE
or FORCEPURGE is also specified, any TRansaction(value)
transaction using the terminal is terminated displays a 4-character string indicating the name of the
abnormally. If PURGE or FORCEPURGE is not transaction currently being processed with this terminal
specified, the transaction is allowed to terminate as its principal facility or as a secondary facility.
normally, but no further transactions are allowed to
use the terminal. For VTAM, setting a terminal Ttistatus
OUTSERVICE also causes it to be released and displays whether the terminal can be used by the
the operator to be signed off, either immediately or transactions that are initiated from this terminal. The
when the current transaction has terminated. values are:
TTi This terminal can be used by transactions.

CEMT INQUIRE PARTNER
NOTti CEMT INQUIRE PARTNER

This terminal cannot be used by transactions.
Function: Retrieve information about the partner table.
Notes:
Description: INQUIRE PARTNER returns information
from the partner table (side information table) installed in
different value.
your system. There is no SET PARTNER function. However
2. A terminal cannot be defined with both NOATI and the INQUIRE PARTNER screen does allow you to type a D in
NOTTI. the left-hand margin by the partnername to be discarded (the
CEMT DISCARD PARTNER function).
Userid(data-area)
returns the 8-character identifier of the user signed on at For information on partners, see the CICS Resource
this terminal or session. Definition Guide.
If there is no signed-on user, the default userid—as
specified in the DFLTUSER system initialization Input: Press the Clear key to clear the screen. There are
parameter—is returned. two ways of commencing this transaction:
Type CEMT INQUIRE PARTNER (the minimum abbreviation
is CEMT I PA). You get a display that lists the current
status.
Type CEMT INQUIRE PARTNER (CEMT I PA) followed by as
many of the other attributes as are necessary to limit the
range of information that you require.
┌─All─────┐
55──CEMT Inquire PArtner──┼─────────┼──────────5
└─(value)─┘
5──┬────────────────┬──┬────────────────┬──────5
└─NETWork(value)─┘ └─NETName(value)─┘
5──┬────────────────┬──┬────────────────┬──────5
└─Profile(value)─┘ └─Ltpname(value)─┘
5──┬───────────────┬──5%
└─Tpname(value)─┘
(value)
specifies the 8-character partner name as specified in
the installed partner definition.
All is the default.
Sample screen
à I PART
ð
STATUS: RESULTS
Par(IST1ISC2) Netn(IYMVM2 ) Pro(DFHCICSA)
Ltp(ð4) Tpn(IST1 )
Par(IST2ISC2) Netn(IYMVM2 ) Pro(DFHCICSA)
Ltp(ð4) Tpn(IST2 )
Figure 93. CEMT INQUIRE PARTNER screen
in Figure 94 on page 103.

CEMT INQUIRE PROCESSTYPE
| CEMT INQUIRE PROCESSTYPE

à I PART
ð
RESULT
Partner(IST1ISC2)
Network()
| Function: Retrieve information about a CICS business
Netname(IYMVM2)
Profile(DFHCICSA)
| transaction services process-type.
Ltpname(ð4)
Tpname(IST1)
| Description: INQUIRE PROCESSTYPE returns
| information about the BTS PROCESSTYPE definitions
Figure 94. The expanded display of an individual entry | installed on this CICS region. In particular, it shows the
| current state of audit logging for each displayed
Displayed fields | process-type.
Ltpname(value) | Input: Press the Clear key to clear the screen. There are
displays the length of the name of the remote | two ways of commencing this transaction:
transaction program (TPNAME), in bytes.
| Type CEMT INQUIRE PROCESSTYPE (the minimum
NETName(value) | abbreviation is CEMT I PROC). You get a screen that lists
displays the 8-character name of the node at which the | the current status.
partner is located. | Type CEMT INQUIRE PROCESSTYPE (CEMT I PROC) followed
NETWork(value) | by as many of the other attributes as are necessary to
displays the 8-character name of the network in which | limit the range of information that you require. So, for
the partner is located. | example, if you enter cemt i proc en, the resulting
| display will show you the details of only those
PArtner(value) | process-types that are enabled.
indicates that this panel relates to a PARTNER inquiry
and displays the 8-character partner name as specified | To change various attributes, you can:
in the installed partner definition. | Overtype your changes on the INQUIRE screen after
Profile(value) | tabbing to the appropriate field.
displays the 8-character name of the CICS profile | Use the CEMT SET PROCESSTYPE command.
associated with the partner.
|
Tpname(value) | ┌─ALl─────┐
displays the 64-character name of the remote | 55──CEMT Inquire PROCesstype──┼─────────┼──────5
transaction program. | └─(value)─┘
Note: Nondisplayable characters appear as periods. | 5──┬─────────────┬──┬─────────────────┬────────5
You can use the PF2 key on the expanded panel | └─FIle(value)─┘ └─AUditlog(value)─┘
to see the hexadecimal value. | 5──┬──────────┬──┬──────────┬──5%
| ├─ACtivity─┤ ├─Enabled──┤
| ├─FUll─────┤ └─Disabled─┘
| ├─Off──────┤
| └─Process──┘
| ALl
| is the default. Information about all process-types is
| displayed, unless you specify a selection of
| process-types to be queried.
| (value)
| is the name (1-8 characters) of one or more
| PROCESSTYPE definitions installed in the process-type
| table (PTT).
| Sample screen

CEMT INQUIRE PROCESSTYPE
| Off No audit trail records are written.

|
| à I PROC
ð | Process
| STATUS: RESULTS - OVERTYPE TO MODIFY
| Pro(PROCESSTYPE12 ) Fil(FILE12 ) Aud(ADTLOG12) Pro Ena
| Process-level auditing. Audit records are written
| Pro(PROCESSTYPE13 ) Fil(FILE13 ) Aud(ADTLOG12) Off Ena
| Pro(PTYPE2B ) Fil(FILE2B ) Aud(DFHJ2B ) Ful Ena
| from the process audit points only.
| Pro(PTYPE39 ) Fil(FILE39 ) Aud(DFHJ39 ) Off Ena
| Pro(SALESTYPE1 ) Fil(SALESF1 ) Aud(PLOG51 ) Off Dis
| Pro(SALESTYPE4 ) Fil(SALESF4 ) Aud(PLOG51 ) Act Ena
| Pro(SALESTYPE6 ) Fil(SALESF6 ) Aud(PLOG51 ) Off Ena
| For details of the records that are written from the
| process, activity primary, and activity secondary audit
| Figure 95. CEMT INQUIRE PROCESSTYPE screen | points, see the CICS Business Transaction Services
| manual.
| press ENTER, CICS displays an expanded format as shown | AUditlog(value)
| in Figure 96. | displays the 8-character name of the CICS journal used
| as the audit log for processes of this type.
| Enablestatus
|
| à I PROC
ð | displays whether new processes of this type can be
| Processtype(SALESTYPE4 ) | created. The values are:
| File(SALESF4 )
| Enablestatus( Enabled )
| Auditlog(PLOG51 ) | Disabled
| Auditlevel(Activity )
| The installed definition of the process-type is
| disabled. New processes of this type cannot be
| Figure 96. The expanded display of an individual entry | defined.
| Displayed fields | Enabled
| The installed definition of the process-type is
| Auditlevel | enabled. New processes of this type can be
| displays the level of audit logging currently active for | defined.
| processes of this type. The values are:
| FIle(value)
| ACtivity | displays the 8-character name of the CICS repository file
| Activity-level auditing. Audit records are written | on which the process and activity records for processes
| from: | of this type are stored.
| 1. The process audit points
| PROCesstype(value)
| 2. The activity primary audit points.
| indicates that this panel relates to a PROCESSTYPE
| FUll Full auditing. Audit records are written from: | inquiry and displays the 8-character name of a
| 1. The process audit points | process-type.
| 2. The activity primary and secondary audit
| points.

CEMT INQUIRE PROFILE CEMT INQUIRE PROGRAM
CEMT INQUIRE PROFILE CEMT INQUIRE PROGRAM

Function: Retrieve information about a transaction profile. Function: Retrieve information about programs, maps, or
partition sets.
Description: INQUIRE PROFILE returns information
about the profiles installed in your system. There is no SET Description: INQUIRE PROGRAM returns information
PROFILE function. However, the INQUIRE PROFILE screen about the programs, map sets, and partition sets that are
does allow you to type a “D”. in the left-hand margin by the defined to your system.
name of the profile to be discarded (the DISCARD PROFILE
| Note: JVM programs return a subset of values.
function).
Input: Press the Clear key and type CEMT INQUIRE PROFILE two ways of commencing this transaction:
(the minimum abbreviation is CEMT I PROF).
Type CEMT INQUIRE PROGRAM (the minimum abbreviation
You will get a display screen, a sample of which is shown is CEMT I PROG). You get a display that lists the current
below. status.
Type CEMT INQUIRE PROGRAM (CEMT I PROG) followed by
┌─All─────┐ as many of the other attributes as are necessary to limit
55──CEMT Inquire PROFile──┼─────────┼──5% the range of information that you require. So, for
└─(value)─┘ example, if you enter cemt i prog c e, the resulting
display will show you the details of only those programs
that are written in C language and are enabled.
(value)
is the name of a specific profile.
All is the default.
Sample screen
à IN PROFILE
ð
STATUS: RESULTS
Prof(DFHCICSA)
Prof(DFHCICSE)
Prof(DFHCICSF)
Prof(DFHCICSR)
Prof(DFHCICSS)
Prof(DFHCICST)
Prof(DFHCICSV)
Figure 97. CEMT INQUIRE PROFILE screen
Displayed fields
PROFile(value)
indicates that this panel relates to a PROFILE inquiry
and displays the 8-character name of a profile installed
in your system.

CEMT INQUIRE PROGRAM
CLASS(clasid) command returns a ‘CLASS NOT

┌─ALl──────────┐ FOUND’ message.
55──CEMT Inquire PROGram──┼──────────────┼─────5
├─(value)──────┤
└─CLass(value)─┘
Sample screen
5──┬───────────────┬──┬────────────┬───────────5
└─LENgth(value)─┘ ├─PLi────────┤
├─CObol──────┤ à IN PROG
ð
├─C──────────┤ STATUS: RESULTS - OVERTYPE TO MODIFY
Prog(CNCLTASK) Len(ððððððð) Cob Pro Ena Pri Ced
├─LE37ð──────┤ Res(ððð) Use(ððððððð) Bel Uex Ful
Prog(DFH$AALL) Len(ððð2936) Ass Pro Ena Pri Ced
├─ASsembler──┤ Res(ððð) Use(ððððððð) Bel Uex Ful
Prog(DFH$ABRW) Len(ððð252ð) Ass Pro Ena Pri Ced
├─NOTDEfined─┤ Res(ððð) Use(ðððððð1) Bel Uex Ful
| └─JAVA───────┘ Prog(DFH$ACOM) Len(ððð1128) Ass Pro Ena
Res(ððð) Use(ððððððð) Bel Uex Ful
Pri Ced
Prog(DFH$AGA ) Len(ðððð52ð) Map Ena Pri

5──┬──────────────┬──┬──────────┬──────────────5 Res(ððð) Use(ðððððð2)
Prog(DFH$AGB ) Len(ðððð448) Map Ena Pri
├─PROgram──────┤ ├─Enabled──┤ Res(ððð) Use(ððððððð)
├─Mapset───────┤ └─DIsabled─┘ Prog(DFH$AGC ) Len(ðððð512) Map Ena Pri
Res(ððð) Use(ððððððð)
└─PArtitionset─┘ Prog(DFH$AGD ) Len(ðððð576) Map Ena Pri
Res(ððð) Use(ððððððð)
+ Prog(DFH$AGK ) Len(ðððð392) Map Ena Pri
┌─PRIvate─┐ Res(ððð) Use(ððððððð)
5──┼─────────┼──┬─────────────┬──┬────────┬────5
└─Shared──┘ ├─REQuired────┤ ├─CEDf───┤
└─NOTRequired─┘ └─NOCedf─┘ Figure 98. CEMT INQUIRE PROGRAM screen
5──┬────────────┬──┬─────────────────┬─────────5
| ├─DYnamic────┤ └─REScount(value)─┘ Note: There are blank fields on the screen where a value
| └─NOTDYnamic─┘ does not apply or is ‘negative’; that is, the value
5──┬─────────────────┬──┬───────┬──────────────5
└─USecount(value)─┘ ├─ANy───┤ by tabbing (they appear in the same sequence as in
└─Below─┘ the expanded format), and overtype with input valid
5──┬──────────┬──┬───────────┬─────────────────5 for that field. You may find it more convenient to use
├─CEXeckey─┤ ├─DPlsubset─┤ the expanded format when setting one of these
└─UExeckey─┘ └─Fullapi───┘ values, (negating is easier because you are
5──┬────────────┬──┬─────────────────────┬─────5 overtyping a displayed field with its negative causing
| ├─Quasirent──┤ └─REMotesystem(value)─┘ the result to become non-displayed).
| └─Threadsafe─┘
5──┬──────────┬──┬─────────┬───────────────────5 If you place the cursor against a specific entry in the list and
| ├─JVM──────┤ ├─DEBug───┤ press ENTER, CICS displays an expanded format as shown
| ├─LE37ð────┤ └─NODebug─┘ in Figure 99 and Figure 100.
| ├─NONLE37ð─┤
| └─UNKNOWN──┘
5──┬─────────────────┬──5% à ð
| └─JVMClass(value)─┘ IN PROG
Program(DFH$AALL)
Length(ððð2936)
Language(Assembler)
Progtype(Program)
(value) Status( Enabled )
Sharestatus( Private )
is a program identifier (1–8 characters), which is the Copystatus( Notrequired )
Cedfstatus( Cedf )
name of a specific program entry in the table of installed | Dynamstatus(Notdynamic)
Rescount(ððð)
Usecount(ððððððð)
program definitions. If you omit the program name, the Dataloc(Below)
Execkey(Uexeckey)
ALL option is assumed by default. Executionset( Fullapi )
| Concurrency(Threadsafe)
Remotesystem()
You cannot specify the CLASS option and a program | Runtime( Le37ð )
| Jvmdebug( Nodebug )
name.
ALl
is the default. Figure 99. The expanded display of an individual entry (first panel)
CLass(value)
is the 2-character suffix of a program list table (PLT). | à ð
Use this option to inquire on those programs defined in | IN PROG
the specified PLT. Note that, unlike a shutdown PLT, it is | Program(DFH$AALL)
| Jvmdebug( Nodebug )
| Jvmclass( )
not mandatory to define a program definition for a | Jvmclass( )
| Jvmclass( )
startup PLT. However, if you want to use the CLASS | Jvmclass( )
| Jvmclass( )
option, you must define and install a program resource
definition for the PLT specified by “clasid”.
If the clasid specified is the suffix of a PLT that does not | Figure 100. The expanded display of an individual entry (second
have a program definition, the INQUIRE PROGRAM | panel)

Displayed fields NEwcopy

CICS uses a new copy of the program when all
Cedfstatus the transactions currently using the program have
displays what action the execution diagnostic facility finished (RESCOUNT equal to zero). CICS loads
(EDF) is to take for this program when the program runs the new version either from the DFHRPL library
under EDF. The values are: concatenation or uses an LPA-resident version,
CEDf depending on the PRIVATE or SHARED options.
When EDF is active, CEDF initiation and PRIVATE is the default setting.
termination screens are shown by CEDF while this Note: NEWCOPY cannot be specified for a
program is running. Other screens are also shown program specified with the HOLD option.
unless the program was translated using the
PHasein
NOEDF translator option.
CICS uses a new copy of the program now for all
NOCedf new transaction requests. CICS continues to use
All CEDF activities, including initiation and the old copy for all currently running transactions
termination screens, stop while this program is until they have finished (RESCOUNT equal to
being processed. zero). CICS loads the new version either from the
DFHRPL library concatenation or uses an
| Concurrency
LPA-resident version, depending on the PRIVATE
| Displays the concurrency attribute of the specified
or SHARED options. PRIVATE is the default
| program. The values are:
setting.
| Threadsafe Note: PHASEIN cannot be specified for a
| The program is defined as being threadsafe, using program specified with the HOLD option.
| appropriate serialization techniques to access
| shared resources. It does not need the automatic PHASEIN performs a REFRESH PROGRAM
| serialization provided by the CICS QR TCB, and function to inform the loader domain that a new
| can safely run on an open TCB. version of the program has been cataloged and
that this version of the named program should be
| Quasirent used in all future ACQUIRE requests.
| The program is defined as not threadsafe, and
| requires the automatic serialization provided by Until the program goes to a zero RESCOUNT and
| QR TCB. a subsequent ACQUIRE PROGRAM has been
performed, CEMT INQUIRE PROGRAM ( ) will
Copystatus return information on the first copy of the program.
displays the load status of the specified program.
Dataloc
The values are: displays whether the program is able to accept data
NOTRequired addresses higher than 16MB. The values are:
The program status is such that you do not have ANy The program can handle 31-bit addresses. The
to specify CEMT SET PROGRAM NEWCOPY or address of the data can be above or below the
CEMT SET PROGRAM PHASEIN to make the 16MB boundary. CICS returns an address above
program available. (If the program is already the 16MB boundary if possible.
available for use and if you have put a new
version in the DFHRPL concatenation, you need Below
to issue a NEWCOPY or PHASEIN to replace the The program can handle only 24-bit addresses
current version.) and must therefore be given addresses of data
located below the 16MB boundary. If necessary,
REQuired CICS copies data below the 16MB boundary
A search for the program failed during a load before passing its address to the application
operation, and the program has been marked as program.
not loadable to avoid the overhead of further load
attempts. | Dynamstatus
| displays whether, if the program is the subject of a
You need to specify CEMT SET PROGRAM
| program link request, the request can be dynamically
NEWCOPY or CEMT SET PROGRAM PHASEIN
| routed. The values are:
to enable the program to be loaded. However,
before doing this, you should ensure that there is | DYnamic
a copy of the program in the DFHRPL library | If the program is the subject of a program-link
concatenation. | request, the CICS dynamic routing program is
| invoked. Providing that a remote server region is
You can reset this value by overtyping it. The values
| not named explicitly on the SYSID option of the
are:
| EXEC CICS LINK command, the routing program

| can route the request to the region on which the | Nodebug

| program is to execute. | The JVM is not to operate in debugging mode for
| this program.
| NOTDYnamic
| If the program is the subject of a program-link | Debug
| request, the dynamic routing program is not | The JVM is to operate in debugging mode for this
| invoked. | program.
| For a distributed program link (DPL) request, the Language
| server region on which the program is to execute displays the language in which the program is written.
| must be specified explicitly on the The values are:
| REMOTESYSTEM option of the PROGRAM
| definition or on the SYSID option of the EXEC PLi, CObol, C, LE370, or ASsembler
| CICS LINK command; otherwise it defaults to the Supported languages. In the case of LE370, the
| local region. program exploits multi-language support, or has
been compiled by the SAA Language
| For information about the dynamic routing of DPL Environment/370 (LE/370)-enabled compiler.
| requests, see the CICS Intercommunication Guide. | Note: It is intented in a future release to report
| C++ programs separately, and for Java
Execkey
| program objects to return a Language
displays which access key the program is executing in.
| value of JAVA. JVM and Java program
The values are:
| objects will be distinguished by using the
CEXeckey | RUNTIME option, which will report JVM for
The program is executing in CICS access key, | JVM programs and LE370 for Java
and has read and write access to both CICS-key | program objects. (A Java program object is
and user-key storage. | a Java program that has been bound by
| the VisualAge for Java, Enterprise ToolKit
UExeckey
| for OS/390.)
The program is executing in user access key, and
has write access to user-key storage, but | Java The program is written in JAVA. This value is
read-only access to CICS-key storage. | currently returned for JVM programs only.
Executionset | NOTAPplic
displays whether the program is restricted to the API | The language was not specified in the resource
subset as for a distributed program link request. The | definition, and has not been loaded.
values are: NOTDEfined
The language in which the program has been
DPlsubset
written is not defined.
The program is restricted to the DPL API subset,
as for a distributed program link request, when it LENgth(value)
runs in the local CICS region. displays the size of the program in bytes. The value
A program is always restricted to the DPL subset returned is 0000000 if the program has not been loaded
when it is invoked in a remote region via a DPL | during this CICS run. No value is returned if the module
request, even if this option is not specified. | is a remote program or a JVM program.
Fullapi PROGram(value)
The program is not restricted to the DPL subset of indicates that this panel relates to a PROGRAM inquiry
the CICS API when it runs in the local CICS and displays an 8-character program identifier (1–8
region, and can use the full API. characters), which is the name of a specific program
entry in the table of installed program definitions.
A program is always restricted to the DPL subset
when it is invoked in a remote region via a DPL Progtype
request, regardless of this option. displays the type of program. The values are:
Note: You can reset this value by overtyping it with a PROgram

different value. The entry is defined in the CICS system definition
as a program.
| JVMCLass
Mapset
| displays the name of the class specified on the program
The entry is defined in the CICS system definition
| definition, up to a maximun of 255 characters.
as a map set.
| JVMDEbug
| indicates whether the JVM is to operate in debugging
| mode for this program. The values are:

PArtitionset The values are:

The entry is defined in the CICS system definition
Shared
as a partition set.
CICS is using, or will use, a shared copy of the
REMotesystem(value) program from the link pack area (LPA). If no LPA
displays the 4-character name of the remote system in version is available, the program is loaded from
which the program is to execute. DFHRPL.
REScount(value) PRIvate
displays a 3-character string identifying the number of The next new copy of the program is to be loaded
separate invocations of this program that are taking from the DFHRPL library.
| place at the time of this inquiry. No value is returned if
| the module is a remote program or a JVM program.
different value.
| RUNTIME
Status
| displays information about the runtime environment of
displays whether the program is available for use. The
| the program. The values are:
values are:
| Jvm The program in a JAVA program running under
Enabled
| the control of a JVM.
The program is available for use.
| LE370
DIsabled
| The program is running with LE370 runtime
The program is not available for use.
| support.
Note: Programs beginning with “DFH” cannot be
| NONLE370
disabled because these characters are
| The program is running with language-specific
reserved for use by CICS.
| runtime support.
| UNknown Note: You can reset this value by overtyping it with a
| The runtime environment in unknown because the different value.
| program has not been loaded by CICS, therefore
USecount(value)
| the source language cannot be deduced, which
displays a 10-character string identifying the total
| dictates the runtime environment to be used.
number of times the program has been executed since
Sharestatus | the start of the current CICS session. No value is
displays, when the next NEWCOPY or PHASEIN | returned if the module is a remote program, or a JVM
request is received, where the next new copy of the | program.
program is to be loaded from.

CEMT INQUIRE REQUESTMODEL CEMT INQUIRE RRMS
| CEMT INQUIRE REQUESTMODEL | CEMT INQUIRE RRMS

| Function: Retrieves information about a | Function: Retrieve RRMS information.
| REQUESTMODEL
| Description: INQUIRE RRMS tells you if CICS does or
| Description: INQUIRE REQUESTMODEL returns | does not accept inbound transactional EXCI work.
| information about any currently installed Request models.
| Input: Press the Clear key and type CEMT INQUIRE RRMS
| Input: Press the Clear key to clear the screen, and type | (the minimum abbreviation is CEMT I R).
| CEMT INQUIRE REQUESTMODEL (the minimum abbreviation is
| CEMT I RE). You get a display that lists the names and status | You will get a display screen, a sample of which is shown
| of any request models. | below.
| Sample screen | Sample screen
|
| à ð |
| à IN RRMS
ð
|
I RE
| STATUS: RESULTS
|
Req(DFHGFACT) Omgm(com::ibm::CosLifeCycle ) | Rrm Ope
| Omgi(GenericFactory )
| SYSID=HA61 APPLID=CICSHA61
| Figure 103. CEMT INQUIRE RRMS screen
| PF 1 HELP 3 END 5 VAR 7 SBH 8 SFH 9 MSG 1ð SB 11 SF
|
| Figure 101. CEMT INQUIRE REQUESTMODEL screen | 55──CEMT Inquire Rrms──5%
| press ENTER, CICS displays an expanded format. | Displayed fields
| Closed
| à ð | indicates that CICS will not accept inbound transactional
| I RE
| RESULT - OVERTYPE TO MODIFY | EXCI work.
| Requestmodel(DFHGFACT)
| Omgmodule(com::ibm::CosLifeCycle)
| Omginterface(GenericFactory) | Open
| Omgoperation(\)
| Transid(CIOF) | indicates that CICS will accept inbound transactional
| EXCI work.
| Displayed fields
| REQUESTMODEL(data-value)
| specifies an 8-character request model name.
| OMGMODULE(data-area)
| returns the 58-character field containing the pattern
| defining the name scope of the interface and operation
| values for this REQUESTMODEL.
| OMGINTERFACE(data-area)
| matching the interface name for this REQUESTMODEL.
| OMGOPERATION(data-area)
| matching the IDL operation name for this
| REQUESTMODEL.
| TRANSID(name)
| returns the 4-character name of the CICS transaction to
| be executed when a request matching the specification
| of the REQUESTMODEL is received.

CEMT INQUIRE STATISTICS
CEMT INQUIRE STATISTICS Displayed fields

Endofday(hhmmss)
Function: Retrieve statistics information.
displays the end-of-day time for recording statistics. At
end-of-day, the current values of the CICS statistics
Description: INQUIRE STATISTICS tells you the interval
counters are written out to an SMF data set and the
during which statistics are accumulated, the end-of-day time
statistics counters are reset.
for shutdown (or logical end-of-day) statistics, the time at
which statistics are next recorded (that is, written to an SMF End-of-day times must be in the range 000000-235959.
data set), and whether statistics recording is currently on or The default end-of-day time is 12 midnight (000000).
off.
Interval(hhmmss)
For details of how to print statistics using the CICS-supplied displays the length of time during which the statistics
utility program DFHSTUP, see the CICS Operations and counters are incremented. At the end of each interval,
Utilities Guide. the accumulated statistics are recorded and the statistics
counters are reset.
Input: Press the Clear key and type CEMT INQUIRE Note: You can reset this value by overtyping it with a
STATISTICS (the minimum abbreviation is CEMT I ST). different value.
You will get a display screen, a sample of which is shown Interval times must be in the range 000100-240000. The
below. If you want to change any of the values shown, you default interval value is 030000. The interval value can
can then tab to the highlighted or blank fields and overtype be adjusted, but will have no effect unless the statistics
them as required. recording status is set ON. You can set the statistics
recording status ON or OFF using the RECORDING
Sample screen option on this command or by using the STATRCD
system initialization parameter.
The arrival of the ENDOFDAY time always causes the
à IN STATI
ð current interval to be ended (possibly prematurely) and a
Sta On Int( ð3ðððð ) End( ðððððð ) Nex(15ðððð) new interval to be started. Only end-of-day statistics are
recorded at the end-of-day time, even if it coincides
exactly with the expiry of an interval.
Changing the ENDOFDAY value has an immediate
Figure 104. CEMT INQUIRE STATISTICS screen
effect on the times at which INTERVAL statistics are
Note: There are blank fields on the screen where a value recorded. New interval expiry times are recalibrated in
does not apply or is ‘negative’; that is, the value accordance with the new end-of-day time.
begins with ‘No’. To modify these fields, locate them When you change the INTERVAL value or the
by tabbing (they appear in the same sequence as in ENDOFDAY value (and also when CICS is initialized),
the expanded format), and overtype with input valid the length of the current (or first) interval is adjusted so
for that field. You may find it more convenient to use that it expires after an integral number of intervals from
the expanded format when setting one of these the end-of-day time.
These rules are illustrated by the following example,
where I indicates an interval recording, INTERVAL is set
at 3-hourly intervals, CICS is initialized at 0815 hours,
If you place the cursor against the result and press ENTER, and E indicates the ENDOFDAY setting at 1700 hours.
CICS displays an expanded format as shown in Figure 105. ┌]─ CICS initialized with
│ ENDOFDAY(17ðððð)
│ INTERVAL(ð3ðððð)
à ð │
IN STAT
│
Statistics
Recording( Off )
│
Record( ) │
Reset( )
Interval( ð3ðððð ) │
Endofday( ðððððð )
Nexttime(ðððððð) │
6
]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬
ð8 ð9 1ð 11 12 13 14 15 16 17
Figure 105. The expanded display I I E
55──CEMT Inquire STAtistics──5%

CEMT INQUIRE STATISTICS
Note: In this example, there would have been an (Requested statistics are those called for by a CEMT
interval at 0800 hours if CICS had been PERFORM STATISTICS command or by an EXEC
initialized earlier. CICS PERFORM STATISTICS RECORD command.)
The values are:
If you want your end-of-day recordings to cover 24
hours, set INTERVAL to 240000. On Interval statistics are being recorded. Counters are
incremented as usual, and are reset at the expiry
Nexttime(hhmmss)
of each interval and at end-of-day.
displays the time at which statistics are next recorded
and reset. This is the expiry time of the current interval Off Interval statistics are not being recorded. Counters
or the end-of-day time, whichever is earlier. are still incremented as usual, and the recording of
end-of-day, requested, and unsolicited statistics is
Record (input only field)
still made.
specifies whether existing statistics are to be written to
an SMF data set. The value is:
Record different value.
Existing statistics are to be written to an SMF data
Reset (input only field)
set. The statistics are those collected since the
specifies whether the statistics counters are to be reset.
last ENDOFDAY or INTERVAL collection, or since
The value is:
the last time the RESETNOW function was used
in this or the PERFORM STATISTICS command. Reset
The statistics counters are to be reset. The reset
Notes: takes effect only if the recording option is changed
from OFF to ON or from ON to OFF. For
1. When both Rec(ord) and Res(et) are specified,
information about the effect of reset on each
statistics counters are written to the SMF data set
individual counter, see the description of the CICS
and reset. The statistics that you are given are
statistics tables in the CICS Performance Guide.
those collected since the last ENDOFDAY or
INTERVAL collection, or since the last time the The action, for each counter, is one of the
RESETNOW function was used in this or the following:
PERFORM STATISTICS command. Not reset
2. RECORD RESET take effect only when the Reset to zero
recording status is changed. Reset to 1
Reset to current value (this applies to peak
Recording values)
displays whether the recording of interval statistics is An exception to the above.
switched on or off. End-of-day statistics, requested
statistics, and unsolicited statistics are always recorded, STAtistics
irrespective of the setting of the ON or OFF option. indicates that this panel relates to a STATISTICS
inquiry.

CEMT INQUIRE STREAMNAME
CEMT INQUIRE STREAMNAME If you place the cursor against a specific entry in the list and
Function: Retrieve information about currently connected in Figure 107.
MVS log streams.
Description: The INQUIRE STREAMNAME command à IN STRE

ð
allows you to inquire on the currently connected MVS log RESULT
Streamname(BELL.CICSHT61.DFHLOG)
streams. Usecount(ðððððð1)
Status(Ok)
Systemlog(Syslog)
Type CEMT INQUIRE STREAMNAME (the minimum
abbreviation is CEMT I STR). You get a display that lists Displayed fields
the current status.
Status
Type CEMT INQUIRE STREAMNAME (CEMT I STR) followed by
displays the status of the log stream. The values are:
the range of information that you require. So, for Ok No errors have been detected
example, if you enter cemt i str fai sys, the resulting
Failed
display will show you the details of only those
The MVS system logger has detected a problem
streamnames that are failed and that are the system log.
with the specified log stream.
overtype them with the required values. STReamname(value)
indicates that this panel relates to a STREAMNAME
inquiry and displays an MVS system logger log stream
┌─ALl─┐ name.
55──CEMT Inquire STReamname───┴─────┴──────────5
Systemlog
5────(value)────┬─────────────────┬────────────5 displays whether this log stream is the system log. The
└─Usecount(value)─┘
values are:
5──┬────────┬──┬──────────┬──5%
├─Failed─┤ ├─Syslog───┤ Syslog
└─Ok─────┘ └─Nosyslog─┘ The log stream is the system log.
Nosyslog
(value) The log stream is not the system log.
specifies an MVS system logger log stream name. The
Usecount(value)
name can be a specific LSN of up to 26 characters in
displays the number of CICS journal names and forward
length.
recovery logs that are currently using the log stream.
ALl The use count is always at least 1, because CICS does
is the default. not maintain any information about a log stream that no
longer has any users, in which case an INQUIRE
Sample screen STREAMNAME command returns an ERROR condition.
If the log stream name refers to the CICS system log,
the use count is always 1. This is so even when user
à IN STRE
ð application programs write recovery records to the CICS
STATUS: RESULTS
Str(BELL.CICSHT61.DFHLOG ) Use(ðððððð1) Ok Sys
system log.
Figure 106. CEMT INQUIRE STREAMNAME screen

CEMT INQUIRE SYDUMPCODE
CEMT INQUIRE SYDUMPCODE You can then tab to the highlighted or blank fields and
Function: Retrieve information about the system dump
code table.
┌─ALl─────┐
55──CEMT Inquire SYDumpcode──┼─────────┼───────5
Description: INQUIRE SYDUMPCODE allows you to see └─(value)─┘
the current settings of the entries in the system dump table.
5──┬───────────┬──┬─────────┬──────────────────5
‘NO’ settings (NOSYSDUMP, for example) are shown as ├─SYsdump───┤ ├─RELated─┤
blank. └─NOSYsdump─┘ └─Local───┘
The INQUIRE command tells you: 5──┬────────────┬──┬────────────────┬──────────5

├─SHutdown───┤ └─Maximum(value)─┘
The system dump code or message identifier └─NOSHutdown─┘
Whether or not CICS takes a system dump 5──┬────────────────┬──┬───────┬──5%
Whether the system dump request is local or related └─Current(value)─┘ ├─Dae───┤
Whether or not CICS is to shut down following the dump └─NODae─┘
The current number of dumps taken
The maximum number of dumps
Whether or not a dump produced by CICS is eligible for (value)
suppression by the MVS Dump Analysis and Elimination is an 8-character system dump code. See the CICS
(DAE) component. Messages and Codes manual for details of the codes.
ALl
A system dump code is the CICS message number with the
is the default.
DFH prefix removed. Typically this leaves a 6-character
code comprising 2 alphabetic characters and 4 numeric Sample screen
characters, for example AP0001. The command syntax
permits up to 8 characters for the dump code and the dump
codes you specify are padded with trailing spaces.
à I SYD
ð
Each message has its own system default actions that you Syd(APððð1 ) Sys Loc Max( ð1ð ) Cur(ðððð) Dae
Syd(APððð2 ) Sys Loc Max( 999 ) Cur(ðððð)
cannot necessarily override with the SET command. For
example, when a serious error occurs, CICS shuts down
even if you have asked for no shut down. See the CICS Figure 108. CEMT INQUIRE SYDUMPCODE screen
Messages and Codes manual for information about the
system action for each message. Note: There are blank fields on the screen where a value
There are other system parameters that take priority over begins with ‘No’. To modify these fields, locate them
your dump table entries. For example, EXEC CICS SET by tabbing (they appear in the same sequence as in
SYSTEM DUMPING NOSYSDUMP, or a DUMP=NO system the expanded format), and overtype with input valid
initialization parameter inhibits system dumping. For for that field. You may find it more convenient to use
information on using dumps, see the CICS Problem the expanded format when setting one of these
Determination Guide. values, (negating is easier because you are
The transaction dump command SET TRDUMPCODE can
also cause CICS to produce system dumps for the specified
transaction dump code. If you place the cursor against the result and press ENTER,
Type CEMT INQUIRE SYDUMPCODE (the minimum à ð
I SYD
abbreviation is CEMT I SYD). You get a display that lists RESULT - OVERTYPE TO MODIFY
Sydumpcode(APððð1)
the current status. Sysdumping( Sysdump )
Dumpscope( Local )
Shutoption( Noshutdown )
Type CEMT INQUIRE SYDUMPCODE (CEMT I SYD) followed by Maximum( ð1ð )
Current(ðððð)
as many of the other attributes as are necessary to limit Action(
Daeoption( Dae )
)
the range of information that you require. So, for

example, if you enter cemt i syd sy sh, the resulting
display will show you the details of only those system Figure 109. The expanded display
dump codes for which a system dump is to be taken and
CICS is to be shut down. Displayed fields

CEMT INQUIRE SYDUMPCODE
Action (input only field) RELated

specifies the action to be taken with this system dump A system dump request is to be sent for this
code. The values are: system dump code.
Reset Local
The current number of calls for this dump code is A system dump request is not to be sent to other
reset to zero. MVS images in the sysplex for this system dump
code.
Remove
This system dump code is removed from the
system dump code table.
different value.
Add This system dump code is added to the system
Maximum(value)
dump code table.
displays the maximum number of dump calls for this
Current(value) system dump code which result in system dumps being
displays the number of dump calls that have been made taken. The value is in the range 0-999 and can be
for this dump code since it was last reset. specified by using SYDUMAX in the SIT parameter. A
value of 999 means the default, ‘no limit’.
Daeoption
displays whether a dump taken for CICS is eligible for Note: You can reset this value by overtyping it with a
suppression by the MVS dump analysis and elimination different value.
(DAE) component. The values are:
Shutoption
Dae A system dump is eligible for suppression by the displays whether CICS is to be shut down after the
DAE component. occurrence of an error corresponding to this dump code.
NODae SHutdown
A system dump will not be suppressed by the CICS is to be shut down.
DAE component. (However, be aware of the
NOSHutdown
SUPPRESS and SUPPRESSALL options in the
CICS is not to be shut down.
ADYSETxx parmlib member. These are controlled
by the VRADAE and VRANODAE keys in the
SDWA. They may lead to dump suppression even
different value.
though NODAE is set here. For information about
DAE, SUPPRESS, and SUPPRESSALL, see the SYDumpcode(value)
OS/390 MVS Diagnosis: Tools and Service Aids indicates that this panel relates to a SYDUMPCODE
manual. inquiry and displays an 8-character system dump code.
See the CICS Messages and Codes manual for details
Note: You can reset this value by overtyping it with a of the codes.
different value.
Sysdumping
Dumpscope(value) displays whether a system dump is taken for this system
displays whether a system dump request is to be sent to dump code. The values are:
MVS images in the sysplex which are running XCF/MRO
SYsdump
connected CICS regions related to the CICS region on
A system dump is taken for this system dump
which the dump is initiated.
code.
Note: A related CICS region is one in which the unit of
NOSYsdump
work identifiers, in the form of APPC tokens, of
A system dump is not taken for this system dump
one or more tasks match those in the CICS
code.
region that issued the dump request.

different value.

CEMT INQUIRE SYSTEM
CEMT INQUIRE SYSTEM Note: You can reset this value by overtyping it with a
different value.
Function: Retrieve information about CICS. AKp(value)
displays the activity keypoint trigger value, which is the
Description: INQUIRE SYSTEM returns information about
number of logging operations between the taking of
the CICS system.
keypoints. It is in the range 200–65535. A value of zero
indicates that there is no activity keypointing.
Input: Press the Clear key to clear the screen, and type
CEMT INQUIRE SYSTEM (the minimum abbreviation is CEMT I Note: You can reset this value by overtyping it with a
SYS). You get a display that lists the current status. You can different value.
then tab to the highlighted or blank fields and overtype them
Cicstslevel(value)
with the required values.
displays a 6-character value identifying the version,
release and modification level of the CICS Transaction
55──CEMT Inquire SYStem──5% Server for OS/390 product under which the CICS
region is running. The value is of the form vvrrmm, and
CICS TS Release 3 returns 010300.
CMdprotect(value)
Overtype your changes on the INQUIRE screen after displays whether command protection, which validates
tabbing to the appropriate field (see Figure 110) start addresses passed on in CICS commands, is active
Use the CEMT SET SYSTEM command. or not (that is, whether the CMDPROT system
initialization parameter specifies YES or NO). The values
Sample screen are:
CMdprot
Command protection is active. CICS checks to
à inq sys
ð ensure that the task itself has write access to the
| Actopentcbs(ððð) Progautoctlg( Ctlgmodify ) storage referenced on the command before writing
Aging( 32768 ) Progautoexit( DFHPGADX )
Akp( ð4ððð )
Cicstslevel(ð1ð3ðð)
Progautoinst( Autoactive )
Reentprotect(Reentprot)
to the storage on the task’s behalf.
Cmdprotect(Nocmdprot) Release(ð53ð)
Db2conn()
Dfltuser(BELL)
Runaway( ððð5ððð )
Scandelay( ð5ðð )
NOCmdprot
|
Dsalimit( ð524288ð )
Dsrtprogram( NONE )
Sdtran(CESD)
Sosstatus(Notsos)
Command protection is not active. CICS does not
Dtrprogram( DFHDYP
Dumping( Sysdump )
) Storeprotect(Active)
Time( ððð1ððð )
check to ensure that the task itself has write
|
Edsalimit( ðð2ð97152ð )
Forceqr( Noforce )
Tranisolate(Active)
access to the storage referenced on the command
| Logdefer( ððð3ð )
before writing to the storage on the task’s behalf.
| Maxopentcbs( ðð5 )
Maxtasks( ð32 )
Mrobatch( ðð1 )
Oslevel(ð2ð5ðð) Db2conn(value)
RESPONSE: NORMAL
SYSID=HT61 APPLID=CICSHT61
TIME: 11.1ð.5ð DATE: 11.ð4.98
displays the name of the currently installed DB2CONN.
PF 1 HELP 3 END 5 VAR 7 SBH 8 SFH 9 MSG 1ð SB 11 SF
DFltuser(value)
displays the userid of the default user for this instance of
Figure 110. CEMT INQUIRE SYSTEM screen
the CICS region.
Displayed fields DSAlimit(value)
displays the maximum amount of storage, as a total
| Actopentcbs(value)
number of bytes, within which CICS can dynamically
| displays the number of open TCBs of all modes that are
| currently active (that is, allocated to a user task).
below the 16MB boundary. (See the CICS System
AGing(value) Definition Guide for a description of the DSALIM system
displays the time factor for CICS to use in the priority initialization parameter.)
aging algorithm for incrementing the priority of a task. Note: You can reset this value by overtyping it with a
The value is expressed as “milliseconds per unit of different value.
priority”, and is in the range 0–65535.
If DSALIMIT specifies a value lower than the current
The priority aging factor is defined initially by the limit, CICS may not be able to implement the new limit
PRTYAGE system initialization parameter, in which the immediately, but will attempt to do so over time as
value represents the number of milliseconds that must dynamic storage is freed in the individual DSAs.
elapse before the priority of a waiting task can be
adjusted upward by 1. See the CICS System Definition | DSRtprogram(pgrmid)
Guide for information about the PRTYAGE parameter. | displays the name of the distributed routing program.
| Note: You can reset this value by overtyping it with a
| different value.

CEMT INQUIRE SYSTEM
| DTrprogram(pgrmid) MAxtasks(value)
| displays the name of the dynamic routing program. displays the maximum number of tasks, both active and
suspended, allowed at any one time in the CICS system.
It must have a value in the range 1–999.
| different value.
Notes:
EDsalimit(value)
displays the maximum amount of storage, as a total 1. You can reset this value by overtyping it with a
number of bytes, within which CICS can dynamically different value.
2. The value assigned to MAXTASKS might be less
above the 16MB boundary. (See the CICS System
than the requested value, because of CICS storage
Definition Guide for a description of the EDSALIM constraints. If this occurs, the message CEILING
system initialization parameter.)
REACHED is displayed when the request is made.
MRobatch(value)
different value.
displays the number of MRO requests from connected
If EDSALIMIT specifies a value lower than the current regions which are to be batched before this region is
limit, CICS may not be able to implement the new limit posted. It is a value in the range 1–255.
immediately, but will attempt to do so over time as
dynamic storage is freed in the individual DSAs.
different value.
| Forceqr(value)
OSlevel(value)
| displays whether CICS is to force user application
displays the version, release, and modification level of
| programs that are defined as threadsafe to run on the
the OS/390 product on which CICS is running. For
| quasi-reentrant (QR) TCB. The values are:
example, OS/390 Version 2 Release 4 Modification 0 is
| Force shown as 0240.
| CICS forces all user application programs
Progautoctlg
| specified with the
displays whether autoinstalled program definitions are to
| CONCURRENCY(THREADSAFE) attribute to run
be cataloged. The values are:
| under the QR TCB, as if they were specified with
| CONCURRENCY(QUASIRENT). CTLGAll
| Nforce All autoinstalled program definitions are to be
| CICS is to honor the cataloged and restored on a warm or emergency
| CONCURRENCY(THREADSAFE) attribute on start.
| user application programs, and allow user CTLGModify
| programs to run on an open TCB to avoid Autoinstalled program definitions are to be
| unnecessary TCB switching. cataloged only if they are modified (for example,
by a CEMT SET PROGRAM command), so that
| Logdefer(value)
the modified definitions are restored on a warm or
| displays the log deferral interval in milliseconds, which is
emergency restart.
| the period of time used by CICS Log Manager when
| determining how long to delay a forced journal write CTLGNone
| request before invoking the MVS system logger. It is in No autoinstalled program definitions are to be
| the range 0-65535. See the CICS System Definition cataloged. They are autoinstalled again after a
| Guide for information about the Logdefer parameter and warm or emergency start.
| associated SIT parameter LGDFINT.
different value.
| different value.
Progautoexit(value)
| Maxopentcbs(value)
displays the name of the user-provided program that is
| displays the maximum number of open TCBs, of all
called by the program autoinstall code to select or
| modes, that CICS is allowed to attach. The value can be
modify a model definition.
| in the range 1–999.
| Note: Until open TCB support is extended to allow
different value.
| task-related user exits to run on CICS-managed
| TCBs (mode L8), this value is applicable to JVM Progautoinst
| TCBs only (mode J8). displays whether autoinstall for programs is active or
inactive. The values are:

CEMT INQUIRE SYSTEM
AUTOActive CICS runaway-task detection is based upon task time

Autoinstall for programs is active. On first use, if a (that is, the interval is reset each time a task receives
program, mapset, or partitionset is not defined, the control of the processor, and is then decremented while
definition is created dynamically. the task is in control). You do not, therefore, need to
allow for the effect of other jobs when setting the
AUTOInactive
runaway value.
Autoinstall is not active. If a program is not
defined, a PGMIDERR or transaction abend SCandelay(value)
occurs when it is referenced. displays the maximum number of milliseconds between
the receipt of a VTAM request, and the time when CICS
Note: You can reset this value by overtyping it with a begins to process the request. The number is in the
different value. range 0–5000, and is less than or equal to the TIME
value.
Reentprotect(value)
displays whether read-only storage is in use for reentrant Notes:
programs (that is, whether the RENTPGM system
initialization parameter specifies PROTECT or
different value.
NOPROTECT). The values are:
2. In the summary report of the dispatcher statistics,
NOReentprotect
SCANDELAY is referred to as ICVTSD.
CICS allocates storage for the read-only DSAs
(RDSA and ERDSA) from CICS-key storage. SDTran(value)
Reentrant programs do not have the protection of displays the 4-character name of the transaction to be
residing in read-only storage, and can be modified run at the beginning of normal or immediate shutdown.
by programs executing in CICS key. This may be the name of a user-supplied transaction, or
the CICS-supplied default transaction, CESD.
REEntprotect
CICS allocates storage for the RDSA and ERDSA Sosstatus(value)
from key-0, non-fetch protected, storage. CICS displays whether CICS is short on storage in any of the
loads reentrant programs into this storage, and the dynamic storage areas. The values returned are:
programs are protected by residing in read-only
storage. NOTsos
RELease(value) (supported for compatibility only) storage areas.
displays a 4-digit number (value 0530 for this release of
SOSAbove
CICS TS) representing the level of the CICS code
CICS is short of storage in at least one of the
running this region.
This field is maintained for compatibility with previous
SOSBelow
releases of CICS only. As an exclusive element of CICS
Transaction Server for OS/390, CICS does not have a
storage areas below 16MB.
product version and release number of its own. To
determine the release number of the product, see the SOS CICS is short of storage in at least one of the
value displayed for CICSTSLEVEL. dynamic storage areas.
RUnaway(value) Storeprotect(value)
displays the interval, in milliseconds, for which a task displays whether storage protection is active in the CICS
can have control before it is assumed to be looping. region. The values returned are:
Note: You can reset this value by overtyping it with a ACtive
different value. CICS is operating with the CICS storage
If you are resetting this value, you can specify 0, or a protection facility.
value in the range 500–2700000. The value you specify Inactive
is rounded down to a multiple of 500. CICS is operating without the CICS storage
protection facility.
CICS purges a task if the task has not given up control
after this interval (that is, CICS assumes that the task is See the description of the STGPROT system
looping). If you specify zero, runaway task control is initialization parameter in the CICS System Definition
inoperative (that is, tasks do not get purged if they Guide for background information about CICS storage
appear to be looping). The value is independent of, and protection.
can be less than, the value in the TIME operand.

CEMT INQUIRE TASK
Time(value) CEMT INQUIRE TASK

displays the interval, in milliseconds, for which CICS
releases control to the operating system if no Function: Retrieve information about a user task.
transactions are ready to resume processing. This
interval is known as the ‘region exit interval’. Description: INQUIRE TASK returns information about
Notes: user tasks. Only information about user tasks can be
displayed or changed; information about CICS-generated
1. You can reset this value by overtyping it with a system tasks or subtasks cannot be displayed or changed.
different value. It can have a value in the range System tasks are those tasks started (and used internally) by
100–3600000, and must be greater than or equal to CICS, and not as a result of a user transaction.
the SCANDELAY value.
2. In the summary report of the dispatcher statistics, Input: Press the Clear key to clear the screen. There are
TIME is referred to as ICV. two ways of commencing this transaction:
Type CEMT INQUIRE TASK (the minimum abbreviation is
Tranisolate
CEMT I TA). You get a display that lists the current
displays the status of transaction isolation. The values
status.
returned are:
Type CEMT INQUIRE TASK (CEMT I TA) followed by as
ACtive many of the other attributes as are necessary to limit the
Transaction isolation is active in the CICS region. range of information that you require. So, for example, if
Inactive you enter cemt i ta i, the resulting display will show
CICS is running without transaction isolation, you the details of only those tasks for which the data is
either because the support is not available, or it not shared with other tasks (isolated).
was not requested at CICS initialization.
tabbing to the appropriate field (see “Overtyping a
display” on page 47).
Use the CEMT SET TASK command.

CEMT INQUIRE TASK

┌─ALl───────────┐ does not apply or is ‘negative’; that is, the value
55──CEMT Inquire TAsk──┼───────────────┼───────5 begins with ‘No’. To modify these fields, locate them
├─(value)───────┤
└─TClass(value)─┘ by tabbing (they appear in the same sequence as in
5──┬───────────────┬──┬─────────────────┬──────5
└─TRanid(value)─┘ └─FAcility(value)─┘
5──┬──────────────┬──┬──────┬──────────────────5 values, (negating is easier because you are
├─Running──────┤ ├─TAsk─┤
├─DIspatchable─┤ ├─TErm─┤ overtyping a displayed field with its negative causing
└─SUspended────┘ └─DEst─┘ the result to become non-displayed).
5──┬─────────────────┬─────────────────────────5 If you place the cursor against a specific entry in the list and
└─PRiority(value)─┘
5──┬──────────────────┬──┬───────────────┬─────5 in Figure 112.
└─STartcode(value)─┘ └─USerid(value)─┘
5──┬────────────┬──┬──────────────┬────────────5
└─UOw(value)─┘ └─HTYpe(value)─┘
à I TASK
ð
5──┬───────────────┬──┬──────────────┬─────────5 RESULT - OVERTYPE TO MODIFY
Task(ððððð26)
└─HValue(value)─┘ └─HTIme(value)─┘ Tranid(CEMT)
Facility(S262)
5──┬─────────┬──┬───────────────┬──────────────5 Runstatus(Suspended)
Ftype(Term)
├─Backout─┤ └─BRidge(value)─┘ Priority( 255 )
Purgetype( )
└─Commit──┘ Startcode(TO)
Userid(CICSUSER)
5──┬───────────────────┬───────────────────────5 Uow(BðC9D8D11144ððð7)
Htype(ZCIOWAIT)
└─IDentifier(value)─┘ Hvalue(DFHZARQ1)
Htime(ððð159)
Indoubt(Backout)
5──┬────────────────────┬──┬────────┬──────────5 Indoubtwait(Wait)
Bridge()
└─Indoubtmins(value)─┘ ├─Nowait─┤ Identifier()
└─Wait───┘ Indoubtmins(ðððððð)
Db2plan()
| Activityid()
5──┬────────────────┬──────────────────────────5 | Activity()
| Process()
└─DB2plan(value)─┘ | Processtype()
| Tcb(QR)
5──┬───────────────────┬───────────────────────5
| └─ACTIVITYId(value)─┘ TIME:
SYSID=JOHN APPLID=I
11.26.4ð DATE: ð8
PF 1 HELP 2 HEX 3 END 5 VAR 7 SBH 8 SFH 1ð SB 11 SF
5──┬─────────────────┬──┬────────────────┬─────5
| └─ACTIVITY(value)─┘ └─PROCESS(value)─┘
5──┬────────────────────┬──5%
| └─PROCESSType(value)─┘
Displayed fields
| Activity(value)
(value) | displays the 16-character, user-assigned, name of the
is the CICS-generated task number, in the range | CICS business transaction services activity that this task
1–99999. | is executing on behalf of.
ALl | Activityid(value)
is the default. | displays the 52-character, CICS-assigned, identifier of
TClass(value) | the CICS business transaction services activity that this
is the 8-character transaction class name to which the | task is executing on behalf of.
transaction belongs. BRidge(value)
| Returns the 4-character name of the bridge monitor
You cannot specify a list of identifiers, nor can you use the
| transaction if the current task is running in a 3270 bridge
symbols * and + to specify a family of tasks.
| environment, and was started by a bridge monitor
| transaction with a START BREXIT TRANSID command.
Sample screen
| Otherwise, blanks are returned.
FAcility(value)
à IN TASK
ð displays a 4-character string identifying the name of the
Tas(ððððð26) Tra(CEMT) Fac(S262) Sus Ter Pri( 255 )
terminal or queue that initiated the task. If no FACILITY
Sta(TO) Use(CICSUSER) Uow(BðC9D8D11144ððð7) Hty(ZCIOWAIT)
Tas(ððððð3ð) Tra(CEMT) Fac(S263) Run Ter Pri( 255 )
value is displayed, the task was started without a facility.
Sta(TO) Use(CICSUSER) Uow(BðC9D8E9C3B1FBO9)
Ftype
displays the type of facility that initiated this task. The
values are:
Figure 111. CEMT INQUIRE TASK screen

CEMT INQUIRE TASK
TAsk Nowait
The task was initiated from another task. The UOW is not to wait, pending recovery from
the failure. CICS is to take immediately whatever
TErm
action is specified on the ACTION attribute of the
The task was initiated from a terminal.
TRANSACTION definition.
DEst The task was initiated by a destination trigger level
Wait The UOW is to wait, pending recovery from the
as defined in the destination control table (DCT).
failure, to determine whether recoverable
HTIme(value) resources are to be backed out or committed.
displays the time (in seconds) that the task has been in
the current suspended state. For further information about the meaning of the
ACTION and WAIT attributes of the TRANSACTION
HTYpe(value)
definition, see the CICS Resource Definition Guide.
displays the reason why the task is suspended. A null
value indicates that there is no hold-up, except for the IDentifier(value)
necessity of reaching the head of the queue. | returns a 48-character field containing user data
| provided by the bridge exit, if the task was initiated in
HValue(value)
| the 3270 bridge environment, or blanks, otherwise. This
| displays a 16-character resource name, such as a file
| field is intended to assist in online problem resolution.
| name, or a value such as a TCLASS value.
| For example, it could contain the MQ correlator for the
For information on the values that can appear in the
| MQ bridge, or a Web token.
HTYPE and HVALUE options, and how they can be
used as an aid in problem determination, see the PRiority(value)
“resource type” and “resource name” details in the CICS displays the priority of the task, in the range 0–255
Problem Determination Guide. where 255 is the highest priority.
Indoubtmins(value) Note: You can reset this value by overtyping it with a

displays the length of time, in minutes, after a failure different value.
during the in-doubt period, before the task is to take the
| Process(value)
action returned in the Indoubt field. The returned value is
| displays the 36-character name of the CICS business
valid only if the unit of work is in-doubt and Indoubtwait
| transaction services process that this task is executing
returns WAIT.
| on behalf of.
See also Indoubt and Indoubtwait.
| Processtype(value)
Indoubt(value) | displays the 8-character process-type of the CICS
displays the action (based on the ACTION attribute of | business transaction services process that this task is
the TRANSACTION resource definition) to be taken if | executing on behalf of.
the CICS region fails or loses connectivity with its
DB2plan(value)
coordinator while a unit of work is in the in-doubt period.
displays the 1- to 8- character name of the DB2 plan
The action is dependent on the values returned in being used by this task, or blanks if no DB2 plan is
Indoubtwait and Indoubtmins; if Indoubtwait returns being used.
WAIT, the action is not taken until the time returned in
Indoubtwait expires. Purgetype (input only field)
specifies whether a task is to be purged or forcepurged.
The values are:
The values are:
Backout
Purge
All changes made to recoverable resources are to
The task is to be terminated. Termination occurs
be backed out.
only when system and data integrity can be
Commit maintained.
Forcepurge
be committed, and the unit of work marked as
The task is to be terminated immediately. System
completed.
integrity is not guaranteed. In some extreme
Indoubtwait(value) cases, for example if a task is forcepurged during
displays how (based on the WAIT attribute of the backout processing, CICS terminates abnormally.
TRANSACTION definition) a unit of work (UOW) is to If you want to terminate a task but do not want to
respond if a failure occurs while it is in an in-doubt state. terminate CICS, you should use PURGE instead
The values are: of FORCEPURGE.
In some BTAM situations, further user action is
required to complete the purging of the task. If a

CEMT INQUIRE TASK
task is in a terminal read on a BTAM nonlocal TAsk(value)

terminal and that task is canceled, it can require indicates that this panel relates to a TASK inquiry and
input from another terminal on the same line displays a CICS-generated task number in the range
before the cancel operation completes. 1–99999.
Runstatus | Tcb(value)
displays the status of this task. The values are: | displays the type of TCB under which the task is
| running. The values are:
Running
The task is running. | CKOPEN
| The task is running under a CICS key open TCB
DIspatchable
| (for example, a JVM (mode J8) TCB).
The task is dispatchable.
| INTERNAL
SUspended
| The task is running under one of the CICS internal
The task is suspended.
| TCBs. An internal TCB can be one of the
STartcode(value) | following:
displays how this task was started. The values are:
| The concurrent mode (CO) TCB
D A distributed program link (DPL) request. The | The file-owning mode (FO) TCB
program cannot issue I/O requests against its | The resource-owning mode (RO) TCB
principal facility or any syncpoint requests. | The ONC/RPC mode (RP) TCB
| The sockets listener mode (SL) TCB
DS A distributed program link (DPL) request, as for
| The secure sockets layer mode (SO) TCB
code D, with the exception that the program can
| A sockets mode (S8) TCB
issue syncpoint requests.
| The FEPI mode (SZ) TCB.
QD A transient data trigger level was reached.
| QR The task is running under the CICS QR TCB.
S Start command (no data)
| UKOPEN
SD Start command (with data) | The task is running under a user key open TCB.
TO The operator typed a transaction code at the TRanid(value)
terminal. displays a 4-character string identifying the transaction
TP The transaction was started by presetting the name associated with the task.
transaction ID for the terminal.
UOw(value)
U User-attached task. displays the 16-character local identifier of the unit of
work associated with this task.
USerid(value)
displays the user currently associated with the task.

CEMT INQUIRE TCLASS
CEMT INQUIRE TCLASS Sample screen
Function: Retrieve information about tasks within a task

class. à IN TCLASS
ð
Tcl(DFHTCIND) Max( ð1ð ) Act(ððð) Pur( ððððððð )
Description: INQUIRE TCLASS returns information about Que(ðððððð)
Tcl(DFHTCLð1) Max( ðð1 ) Act(ððð) Pur( ððððððð )
the current and maximum number of tasks, the purge Que(ðððððð)
threshold, and the status of a user-defined task class. Que(ðððððð)
Que(ðððððð)
Input: Press the Clear key to clear the screen. There are Que(ðððððð)
two ways of commencing this transaction: Que(ðððððð)
Que(ðððððð)
| Type CEMT INQUIRE TCLASS (the minimum abbreviation is Tcl(DFHTCLð7) Max( ðð1 ) Act(ððð) Pur(
Que(ðððððð)
ððððððð )
+ Tcl(DFHTCLð8) Max( ðð1 ) Act(ððð) Pur( ððððððð )

| CEMT I TCL). You get a display that lists the current Que(ðððððð)
status.
| Type CEMT INQUIRE TCLASS (CEMT I TCL) followed by as Figure 113. CEMT INQUIRE TASK screen
range of information that you require. So, for example, if If you place the cursor against a specific entry in the list and
you enter cemt i tc p(value), the resulting display will press ENTER, CICS displays an expanded format as shown
show you the details of only those transaction classes in Figure 114.
that have a purge threshold of the value indicated.
To change various attributes, use the CEMT SET TCLASS à ð

IN TCLASS
command. RESULT - OVERTYPE TO MODIFY
Tclass(DFHTCIND)
Maxactive( ð1ð )
┌─ALl─────┐
55──CEMT Inquire TClass──┼─────────┼───────────5 Figure 114. The expanded display of an individual entry
└─(value)─┘
5──┬──────────────────┬──┬───────────────┬─────5 Displayed fields
└─Maxactive(value)─┘ └─ACtive(value)─┘
5──┬────────────────────┬──────────────────────5 ACtive(value)
└─Purgethresh(value)─┘ displays the total number of transactions that are
currently active in a user-defined transaction class.
5──┬───────────────┬──5%
└─Queued(value)─┘ Maxactive(value)
displays the largest number of transactions in the
transaction class which are allowed to run concurrently.
(value)
The value can be in the range 0-999.
is the 8-character transaction class name.
ALl different value.
is the default.
Purgethresh(value)
displays the limit at which the queuing transactions are
purged for the transaction class. It can have a value in
the range 0000000–1000000. Zero means that the
transactions are not purged. A nonzero number “n”
means that the first (n-1) transactions to arrive are
queued and the nth is purged.
different value.
Queued(value)
displays the total number of current tasks that are
suspended because the class maximum has been
reached.
TClass(value)
indicates that this panel relates to a TCLASS inquiry and
displays an 8-character transaction class name.

CEMT INQUIRE TCPIP CEMT INQUIRE TCPIPSERVICE
| CEMT INQUIRE TCPIP | CEMT INQUIRE TCPIPSERVICE

| Function: Inquire about CICS internal TCP/IP support | Function: Retrieve information about TCP/IP ports on
| status. | which CICS internal TCP/IP support is currently listening on
| behalf of other CICS services.
| Description: INQUIRE TCPIP returns information about
| the current status of CICS internal TCP/IP support. | Description: INQUIRE TCPIPSERVICE returns
| information about the state of a service using CICS internal
| Input: Press the Clear key to clear the screen. There are | TCP/IP support.
| Type CEMT INQUIRE TCPIP (the minimum abbreviation is
| CEMT I TCPIP). You get a display that lists the current
| status. | Type CEMT INQUIRE TCPIPSERVICE (the minimum
| abbreviation is CEMT I TCPIPS). You get a display that
| Type CEMT INQUIRE TCPIP (CEMT I TCPIP) followed by as
| lists the current status.
| many of the other attribute settings that you wish to
| view. | Type CEMT INQUIRE TCPIPSERVICE (CEMT I TCPIPS)
| followed by as many of the other attribute settings that
| To change various attributes, you can: | you wish to view.
| Overtype your changes on the INQUIRE screen after
| To change various attributes, you can:
| tabbing to the appropriate field (see “Overtyping a
| display” on page 47). | Overtype your changes on the INQUIRE screen after
| Use the CEMT SET TCPIP command.
| display” on page 47).
|
| Use the CEMT SET TCPIPSERVICE command.
| 55──INQUIRE TCPIP──┬───────────────────┬──5%
| └─OPENSTATUS(value)─┘ |
| 55──INQUIRE TCPIPSERVICE(value)────────────────5
| OPENSTATUS(value) | 5──┬────────────────┬──────────────────────────5
| └─Backlog(value)─┘
| displays the status of CICS internal TCP/IP support. The
| values are: | 5──┬─────────────────────┬─────────────────────5
| └─CLOsetimeout(value)─┘
| 5──┬───────────────────┬───────────────────────5
| OPEN CICS internal sockets support is open. | └─Connection(value)─┘
| CLOSED CICS internal sockets support has not yet | 5──┬──────────────────┬────────────────────────5
| been activated, or has been terminated. | └─IPaddress(value)─┘
| 5──┬───────────────────┬──┬─────────────┬──────5
| CLOSING CICS internal sockets support is in the
| ├─OPENSTATUS(value)─┤ └─Port(value)─┘
| process of closing. | ├─OPEN──────────────┤
| IMMCLOSING CICS internal sockets support is in the | ├─CLOSING───────────┤
| ├─CLOSED────────────┤
| process of immediate termination. | └─IMMCLOSING────────┘
| 5──┬────────────────┬──────────────────────────5
| ├─SSLTYPE(value)─┤
| ├─NO─────────────┤
| ├─YES────────────┤
| └─CLIENTAUTH─────┘
| 5──┬────────────────────┬──────────────────────5
| ├─SOcketclose(value)─┤
| ├─Wait───────────────┤
| └─TImeout────────────┘
| 5──┬─────────────────────┬─────────────────────5
| └─TCPIPService(value)─┘
| 5──┬────────────────┬──┬──────────────────┬────5
| └─TRansid(value)─┘ └─TSqprefix(value)─┘
| 5──┬────────────┬──5%
| └─URM(value)─┘

CEMT INQUIRE TCPIPSERVICE
| Backlog | SSL
| Change the maximum number of requests which can be | returns a CVDA value indicating the status of SSL
| queued in TCP/IP waiting to be processed by the | support for this service. CVDA values are
| service.
| YES
| Closetimeout | Non client authentication SSL flows are processed
| returns a fullword value containing the number of | on this port
| seconds specified for the timeout period. This can be 0
| NO
| through 86400 (24 hours).
| Non SSL flows are processed on this port
| Connection
| CLIENTAUTH
| The number of current sockets connections for this
| SSL client authentication flows are processed on
| service
| this port
| Ipaddress
| STATUS(cvda)
| returns an IP address. If you specify an IP address in
| returns a CVDA value indicating the state of the service.
| the TCPIPSERVICE definition, that address is returned,
| CVDA values are:
| otherwise the default IP address is returned. If there is
| more than one IP address on an OS/390 system, only | OPEN CICS internal sockets support is open.
| the default is returned.
| CLOSED CICS internal sockets support has not yet
| Port | been activated, or has been terminated.
| returns the number of the port on which CICS is listening
| CLOSING CICS internal sockets support is in the
| on behalf of this service.
| process of closing.
| Service | IMMCLOSING CICS internal sockets support is in the
| 8-character name identifying this service. | process of immediate termination.
| Socketclose | Transid
| returns a CVDA value indicating whether a timeout value | 4-character transaction id used on the attach for the task
| is in effect for the TCPIPSERVICE. CVDA values are: | started to process a new request.
| WAIT | TSQprefix
| NO was specified on the definition. Socket receives | returns the 6–character prefix used when the service
| will wait for data indefinitely. | generates TS queue names.
| TIMEOUT | URM
| A value was specified for the SOCKETCLOSE | 8 character name of Service URM invoked by attached
| parameter on the definition. | task.

CEMT INQUIRE TDQUEUE
CEMT INQUIRE TDQUEUE Sample screen
Function: Retrieve information about transient data

queues. à IN TDQ
ð
Tdq(CADL) Ind Nam(CSSL)
Description: INQUIRE TDQUEUE returns information Tdq(CAIL)
Tdq(CCPI)
Ind Nam(CSSL)
Ind Nam(CSSL)
about a named transient data queue that is defined in the Tdq(CCSE)
Tdq(CCSO)
Ind Nam(CCSO)
Ext Ena Ope
destination control table (DCT). Tdq(CDBC)
Mod Out Dat(ðð1) Ddn(COUT
Ind Nam(CSSL)
)
Tdq(CDUL) Ind Nam(CSSL)

Tdq(CESE) Ext Ena Ope
Input: Press the Clear key to clear the screen. There are Tdq(CESO) Ext
Shr Out Dat(ðð1) Ddn(CEEMSG
Ena Ope
)
two ways of commencing this transaction: Tdq(CMIG)

Shr Out Dat(ðð1) Ddn(CEEOUT
Ind Nam(CSSL)
)
Tdq(CPLD) Ind Nam(CPLI)

Type CEMT INQUIRE TDQUEUE (the minimum abbreviation Tdq(CPLI) Ext Ena Ope
Mod Out Dat(ðð1) Ddn(PLIMSG )
Tdq(CRDI) Ind Nam(CSSL)
is CEMT I TD). You get a display that lists the current + Tdq(CSCS) Ind Nam(CSSL)
status.
Type CEMT INQUIRE TDQUEUE (CEMT I TD) followed by as Figure 115. Example CEMT INQUIRE TDQUEUE screen
range of information that you require. So, for example, if Note: There are blank fields on the screen where a value
you enter cemt i td ind en, the resulting display will does not apply or is ‘negative’; that is, the value
show you the details of only those transient data queues begins with ‘No’. To modify these fields, locate them
that are indirect and enabled. by tabbing (they appear in the same sequence as in
To change various attributes, you can: for that field. You may find it more convenient to use
Overtype your changes on the INQUIRE screen after the expanded format when setting one of these
tabbing to the appropriate field (see “Overtyping a values, (negating is easier because you are
display” on page 47). overtyping a displayed field with its negative causing
Use the CEMT SET TDQUEUE command.
┌─All─────┐ in Figure 116.
55──CEMT Inquire TDqueue──┼─────────┼──────────5
└─(value)─┘
5──┬─────────────────────┬──┬──────────┬───────5
└─TRIggerlevel(value)─┘ ├─INDirect─┤ à IN TDQ
ð
├─EXtra────┤ RESULT - OVERTYPE TO MODIFY
Tdqueue(CCSO)
├─INTra────┤ Triggerlevel( )
Type(Extra)
└─REMote───┘ Nameind()
Enablestatus( Enabled )
Openstatus( Open )
5──┬────────────────┬──┬──────────┬────────────5 Termid()
└─NAmeind(value)─┘ ├─ENabled──┤ Tranid()
Userid()
└─DIsabled─┘ Disposition(Mod)
Iotype(Output)
Indoubt()
5──┬────────┬──┬───────────────┬───────────────5 Indoubtwait()
Databuffers(ðð1)
├─OPen───┤ └─TErmid(value)─┘ Ddname(COUT)
└─Closed─┘ Dsname(BELL.CICSHT61.JOBð4382.Dðððð1ð5.?)
5──┬───────────────┬──┬───────────────┬────────5
└─TRAnid(value)─┘ └─Userid(value)─┘ Figure 116. The expanded display of an individual entry
5──┬─────┬──┬────────┬──┬────────┬─────────────5
├─Shr─┤ ├─INPut──┤ ├─Queue──┤ Displayed fields
├─OLd─┤ ├─OUtput─┤ └─REJect─┘
└─Mod─┘ └─RDback─┘ Disposition (extrapartition queues only)
5──┬────────┬──┬────────────────────┬──────────5 displays the status of the associated data set:
├─Wait───┤ └─DAtabuffers(value)─┘
└─NOwait─┘ Shr The data set existed before this job step and can
be read by other concurrent jobs.
5──┬───────────────┬──┬───────────────┬──5%
└─DDname(value)─┘ └─DSname(value)─┘ OLd The data set existed before this job step.
Mod The system first assumes that the data set exists.
For an existing sequential data set, MOD causes
(value)
the read/write mechanism to be positioned after
is the identifier (1-4 characters) of a transient data
the last record in the data set. The read/write
queue.
mechanism is positioned after the last record each
All is the default. time the data set is opened for output.

If the system cannot find volume information for OPen

the data set on the DD statement, in the catalog, The queue is open.
or passed with the data set from a previous step,
Closed
the system assumes that the data set is being
The queue is closed.
created in this job step. For a new data set, MOD
causes the read/write mechanism to be positioned
Notes:
at the beginning of the data set.
Enablestatus (all except indirect and remote queues)
different value.
displays a value indicating whether the queue can be
accessed by applications. The values are: 2. Queues no longer have to be enabled before
they can be opened or closed. It is advisable
ENabled for a queue to be disabled before it is opened
The queue can be accessed by applications. or closed.
DIsabled
Queue
The queue cannot be accessed by applications,
The UOW is in-doubt and waiting; any locks held by
although it can still be open. Queues with names
the UOW for this queue remain active until the final
beginning with “C” cannot be disabled because
state of the UOW is known. This means that tasks
they are usually reserved for use by CICS.
are suspended rather than receiving the LOCKED
response. When the final state of the UOW is
Notes:
known, any changes that it has made are committed
1. You can reset this value by overtyping it with a or backed out. Until then, any further requests of
different value. the following types that need one of the active locks
must wait:
2. A queue can be disabled only if there are no current
users. If units of work (UOWs) are currently using READQ, if the indoubt UOW has issued
the queue, the queue enters a “disable pending” READQ or DELETEQ requests
state. The last UOW to complete its operation on
WRITEQ, if the indoubt UOW has issued
the queue fully disables the queue.
WRITEQ or DELETEQ requests
3. When a queue is in a “disable pending” state, the
DELETEQ, if the indoubt UOW has issued
value of the ENABLESTATUS option cannot be
READQ, WRITEQ or DELETEQ requests.
altered.
REJect
Indoubt(value) (intrapartition queues only)
The UOW is in-doubt and is waiting. Any locks held
indicates the action CICS is to take for an in-doubt unit
by the UOW for this queue are retained until the
of work (UOW) if the definition for this queue specifies
final state of the UOW is known. When the final
WAIT(YES).
state is known, any changes the UOW has made
Iotype (extrapartition queues only) are committed or backed out. Until then, any further
displays the type of data set to be used: requests that need one of the retained locks are
rejected, and a LOCKED response is returned.
INPut INDOUBT=REJECT causes a LOCKED response to
An input data set. be raised in exactly the same circumstances as
OUtput those in which INDOUBT=QUEUE causes a
An output data set. transaction to wait.
RDback Tdqueue(value)
An input data set that is to be read backward. indicates that this panel relates to a TDQUEUE
inquiry and displays the 4-character identifier of a
| Member (extrapartition queues only)
transient data queue. Queue names beginning with
| returns a 1- to 8-character name that indicates the
“C” are normally reserved for use by CICS.
| member name of a partitioned data set. This is
| blank if the QSAM data set is not a partitioned data TErmid(value)
| set. displays the 4-character name of the terminal or
session to be associated with this queue when
NAmeind(value) (indirect queues only)
automatic transaction initiation (ATI) occurs. See
displays a 4-character string identifying the name of
also Tranid and Triggerlevel.
the queue pointed to by the indirect queue.
TRAnid(value)
Openstatus (extrapartition queues only)
displays the 4-character identifier of the transaction
displays whether the extrapartition queue is open or
that is to be initiated automatically when the queue
closed. The values are:
trigger level is reached.

TRIggerlevel(value) (intrapartition queues only) NOwait

displays the number of requests for output to a The UOW is not to wait. Any changes made to
queue that must accrue before automatic recoverable resources are to be backed out or
transaction initiation (ATI) occurs. committed, as specified by the ACTION attribute on
the transaction resource definition.
Note: You can reset this value by overtyping it with
a different value. Wait
The number can be between 0 and 32767. The UOW is to wait, and any action required while
waiting is determined by the WAITACTION attribute.
Type
This attribute overrides the WAIT parameter defined
displays the type of this transient data queue. The
on the UOW’s transaction definition. See the CICS
values are:
Messages and Codes manual for an explanation of
INDirect the interactions of in-doubt attributes on the
The queue type is indirect. The name of the TDQUEUE and TRANSACTION definitions.
final target queue is shown in the next field.
DAtabuffers(value) (extrapartition queues only)
EXtra displays the number of buffers that can be used by the
The queue type is extrapartition. associated QSAM data set in the range 1 through 255.
INTra Note: An extrapartition queue can be input or output,
The queue type is intrapartition. but not both.
REMote
DDname(value) (extrapartition queues only)
The queue type is remote.
displays a 1-8 character value that may refer to a data
Userid set defined in the startup JCL.
displays the 8-byte identifier associated with the
DSname(value) (extrapartition queues only)
intrapartition queue intended for ATI.
displays the name of the associated QSAM data set
Indoubtwait(value) (intrapartition queues only) (1-44 characters in length), or a dummy data set (or
specifies whether an in-doubt unit of work (UOW) (which dummy data set name) that indicates whether the data
has modified a logically recoverable queue) should wait set will be used by this transient data queue. This option
for resynchronization with its coordinator to determine is applicable for output resources only.
whether to commit or back out the changes.

CEMT INQUIRE TERMINAL
CEMT INQUIRE TERMINAL Overtype your changes on the INQUIRE screen after
Function: Retrieve information about terminals. display” on page 47).
Use the CEMT SET TERMINAL command.
Description: INQUIRE TERMINAL returns information
about a named terminal defined in the terminal control table
(TCT). ┌─ALl──────────┐
55──CEMT Inquire TErminal──┼──────────────┼────5
In an SNA environment, a terminal is the CICS ├─(value)──────┤
representation of an SNA logical unit with which CICS can be └─CLass(value)─┘
in communication. (SNA environment means that CICS is 5──┬────────────────────┬──────────────────────5
using VTAM or ACF/TCAM GSA as the access method for └─TRansaction(value)─┘
communication with SNA logical units.) 5──┬────────────────┬──┬─────────────────┬─────5
| └─COnsole(value)─┘ └─PRiority(value)─┘
This logical unit can be: 5──┬──────────────┬──┬────────────┬────────────5
A physical terminal (such as a 3277) ├─PAgeable─────┤ ├─Inservice──┤
└─AUtopageable─┘ └─Outservice─┘
A function of a cluster controller (such as a 3790 Type 2
5──┬───────┬──┬───────┬──┬───────────┬─────────5
batch function) ├─ATi───┤ ├─TTi───┤ ├─RTerminal─┤
An intersystem communication (ISC) or interregion └─NOAti─┘ └─NOTti─┘ ├─RSession──┤
├─Session───┤
communication (IRC) session that has been generated └─Local─────┘
by the CEDA transaction
5──┬────────────────┬──┬──────────┬────────────5
A remote terminal └─NEtname(value)─┘ ├─ACquired─┤
A remote session; that is, a session of a remote
connection. 5──┬──────────┬──┬─────────────┬───────────────5
├─CReate───┤ └─TAsk(value)─┘
└─NOCreate─┘
If you are familiar with network names, you may prefer to use
the command that uses these names. See “CEMT INQUIRE 5──┬─────────────────────┬─────────────────────5
NETNAME” on page 99. └─REMotesystem(value)─┘
5──┬──────────────┬──┬─────────────────┬───────5
| The terminal entry displayed can also be an MVS console. └─RNAme(value)─┘ └─RNEtname(value)─┘
5──┬───────────────┬──┬────────────┬──5%
The message “TEMP OUT SERVICE” can be displayed if └─Userid(value)─┘ └─CId(value)─┘
recovery is in progress for the terminal. The ”TEMP OUT
SERVICE” indicator is reset by simply refreshing the screen,
or by overtyping the “INS” field with “INS” or “OUT”. If “TEMP (value)
OUT SERVICE” continues to be displayed, the cause of the is a terminal identifier (1-4 characters) as specified in an
indicator should be investigated. installed terminal definition.
If the terminal name is, for example, S201, this option is
coded thus:
CEMT INQUIRE TERMINAL(S2ð1)
Type CEMT INQUIRE TERMINAL (the minimum abbreviation
is CEMT I TE). You get a display that lists the current ALl
status. is the default. For example, if you inquire about
Type CEMT INQUIRE TERMINAL (CEMT I TE) followed by as terminals, you receive information about all terminals,
many of the other attributes as are necessary to limit the unless you specify a terminal identifier, a terminal class
range of information that you require. So, for example, if identifier, or a system identifier.
you enter cemt i te i at, the resulting display will show CLass(value)
you the details of only those terminals that are in service is the 1- or 2-character suffix of a terminal list table
and available for use. Or if you enter cemt i te (TLT).
rem(cicr), the display will show you only remote
terminals (or remote ISC or IRC sessions) owned by the If you do not specify a termid or class identifier, by default
system that the local CICS knows as CICR. you receive information about all the terminals.
To change various attributes, you can: Sample screen

Notes:
à IN TERM
ð
STATUS: RESULTS - OVERTYPE TO MODIFY 1. You can reset this value by overtyping it with a
Ter(CBRF) Pri( ððð ) Pag Ins Ati Tti Rte
Net(CBRF ) Rem(CBR ) Rna(CBRF) different value.
Ter(CERR) Pri( ððð ) Pag Ins Tti Loc
| Con(\ERRCON\ )
Ter(CTSO) Pri( ððð ) Pag Ins Tti Loc 2. A terminal cannot be defined with both NOATI and
| Con(PKING )
| Ter(KING) Pri( ððð ) Pag Ins Tti Loc NOTTI.
| Con(PRUEKING )
| Ter(RNAL) Pri( ððð ) Pag Ins Tti Loc
| Con(INTERNAL )
CId(value)
Ter(S225) Tra(CEMT) Pri( ððð ) Pag Ins Ati Tti Loc
Net(IGCS225 ) Acq Tas(ððððð68)
Ter(S28ð) Tra(CEMT) Pri( ððð ) Pag Ins Ati Tti Loc displays an 8-character correlation-identifier that is set
Net(IGCS28ð ) Acq Tas(ððððð63)
Ter(TC12) Tra(CEMT) Pri( ððð ) Pag Ins Ati Tti Loc only for sessions, and only after a session has been
Net(IYCWTC12) Acq Tas(ððððð72)
Ter(-AAZ) Pri( ððð ) Aut Ins Ati Tti Ses acquired. (The value relates to the previously acquired
Net(TMPLATE1) Rel Rem(CBPS)
Ter(-AAð) Pri( ððð ) Aut Ins Ati Tti Ses session if there was one, if the session is not acquired).
Net(TMPLATE1) Rel Cre Rem(CBPS)
+ Ter(-AA1) Pri( ððð ) Aut Out Ati Tti Ses
Net(TMPLATE1) Rel Cre Rem(CBPS)
CID is set as follows:
For LU6.2 sessions, it is an 8-character token that is

common to the two end sessions that are connected
Figure 117. CEMT INQUIRE TERMINAL screen
together.
Note: There are blank fields on the screen where a value For MRO sessions, it is set to the termid of the
does not apply or is ‘negative’; that is, the value session on the system to which this session is
begins with ‘No’. To modify these fields, locate them connected.
by tabbing (they appear in the same sequence as in For LU6.1 sessions to IMS, it is set to the value of
the expanded format), and overtype with input valid NETNAMEQ as defined or negotiated.
the expanded format when setting one of these For other LU6.1 sessions, it is set to the value
values, (negating is easier because you are supplied by the other end of the 6.1 session.
the result to become non-displayed). Using CID, you can relate the two parts of an LU6.2,
MRO, or LU61 conversation together:
For LU6.2, you can inquire on the same CID.
For MRO, you can locate the session with the
in Figure 118.
terminal name.
For LU6.1 to IMS, you can inquire on the netname.
For other LU6.1, you can use the name to inquire
à IN TERM
ð on the connected system.
Terminal(bell)
Transaction()
Priority( ððð )
| COnsole(value)
Pagestatus( Pageable )
Servstatus( Inservice ) | displays, for an MVS console only, a 12-byte string that
Atistatus( Noati )
Ttistatus( Tti ) | contains the identifier of the console, in two parts. If the
Nature(Local)
Purgetype( ) | device is not a console, CICS returns 12 blanks.
Netname()
| Console(BELL)
Termstatus( ) | If the console is autoinstalled, or is defined explicitly with
Createsess( )
Task(ððððð) | a console name, the name is returned in the first 8
Remotesystem()
Rname() | bytes, and the last 4 bytes are blank.
Rnetname()
+ Cid()
| If the console is defined by a numeric identifier, the
| string is divided into two parts, separated by a period (.)
| in the ninth byte position. The 12-byte string contains
Displayed fields | the following information:
ATistatus | The first 8 bytes contain the MVS console name, if it

displays whether the terminal is available for use by | is known, or the string ‘*UNKNOWN’ if it isn't.
transactions that are automatically initiated from within | A period separating the name from the numeric ID.
CICS or, if the terminal is an ISC session, by
| The last 3 bytes contain the numeric console ID.
transactions that are using this session as an alternate
facility to communicate with another system. The values Createsess (vtam only)
are: displays whether the terminal can be acquired
automatically by ATI transactions. This cannot be
ATi The terminal is available for use.
specified for IRC sessions. The values are:
NOAti
The terminal is not available for use.

CReate Note: You can reset this value by overtyping it with a

If the terminal is not in session, CICS acquires it if different value.
it is needed to satisfy an ATI request.
PRiority(value)
NOCreate displays a 3-character string identifying the priority of a
If the terminal is not in session, CICS does not terminal relative to other terminals. The priority of a task
acquire it to satisfy an ATI request. A session is the sum of the transaction priority, the terminal priority,
must be started by, for example, a logon request and the operator priority. Priority has no meaning for
or a CEMT SET TERMINAL ACQUIRED terminals that are ISC sessions being used as
command before the ATI request can be satisfied. alternative facilities.
If NOCREATE is set for an LU6.1 ISC session and Note: You can reset this value by overtyping it with a
there are no allocatable sessions left, the different value.
connection is placed OUTSERVICE.
The value is in the range 0–255, where 255 is the
highest priority.
You can rest this value by overtyping it with a different
value. Purgetype (input only field)
specifies whether transactions running with the named
Nature
terminal are to be purged. The values are:
displays the nature of the terminal—that is, whether it is
a physical device or a session; and whether it is local or Purge
remote. The values are: Transactions will be terminated only if system and
data integrity can be maintained. A transaction is
RTerminal
purged if its definition specifies SPURGE=NO.
The terminal is a remote device.
Forcepurge
RSession
Transactions are to be purged immediately. This
The terminal is a session of a remote connection.
can lead to unpredictable results and should be
Session used only in exceptional circumstances.
The terminal is an ISC or IRC session.
REMotesystem(value)
Local
displays the 4-character name of a connection, if the
The terminal is directly attached to this system
subject of the inquiry is a remote terminal. The named
and is a physical device or a function of a cluster
connection can be either a connection entry that links
controller.
toward the terminal-owning region (TOR), or an indirect
NEtname(value) connection that provides the netname of the TOR.
displays an 8-character network name. Otherwise this field is blank.
For a physical terminal, the Netname is the name by
RNAme(value)
which this terminal is known to VTAM.
displays the 4-character name by which this terminal is
For ISC sessions, it is the name by which the session known in the system in which it is defined (the TOR).
(or group of sessions) is known to VTAM. RNAME applies only to terminals defined as remote; for
others, blanks are displayed.
For IRC sessions, it is the name used by the connected
region to log on to the interregion communication RNEtname(value)
program (DFHIRP). displays the 8-character netname of the owning TOR, if
For a remote terminal, it is the name by which the the subject of the inquiry is a remote terminal. If this field
terminal is known to the VTAM in the remote region. is blank and the terminal is remote, the indirect
(For a remote terminal routed from a pre-CICS connection, displayed in REMOTESYSTEM, contains the
Transaction Server for OS/390 region, Netname is netname of the TOR.
blank.)
Servstatus
Pagestatus displays whether the terminal is available for use. The
displays whether pages after the first in a series are values are:
written to the terminal on request from the operator or
Inservice
automatically. The values are:
The terminal is available for use. For VTAM,
PAgeable Ins(ervice) means that the terminal can be
Pages are written on request. ACQUIRED. For IRC sessions, Ins(service) means
that the connection to the MRO partner is
AUtopageable
INSERVICE.
Pages are written automatically.

Outservice RELeased
The terminal is not available for use. Setting a CICS is not in session with the logical unit
terminal Out(service) means that the terminal can represented by the terminal. If you set this option
no longer be used by transactions. If PURGE or to RELEASED, a session is terminated
FORCEPURGE is also specified, any transaction immediately if you also specify the PURGE option,
using the terminal is terminated abnormally. If otherwise the session is terminated when the
PURGE or FORCEPURGE is not specified, the current active transaction finishes.
transaction is allowed to terminate normally, but
no further transactions are allowed to use the For physical terminals and LU6.1 sessions, you can
terminal. For VTAM, setting a terminal reset this value by overtyping it with a different value or
Out(service) also causes it to be released and the with:
operator to be signed off, either immediately or
Coldacq
when the current transaction has terminated. For
CICS is in session with the logical unit
IRC sessions, Out(service) means that the
represented by the terminal, where no
connection to the MRO partner is OUTSERVICE.
resynchronization is required.
In an LU6.1 ISC session, the connection is set
Out(service) if there are no allocatable sessions TRansaction(value)
left. displays a 4-character string identifying the name of the
transaction currently being processed with this terminal
Note: For physical terminals and LU6.1 sessions, you as its principal facility or as a secondary facility.
can reset this value by overtyping it with a
Ttistatus
different value.
displays whether the terminal can be used by the
TAsk(value) transactions that are initiated from this terminal. The
displays the task number of the transaction that is values are:
running on this terminal.
TTi This terminal can be used by transactions.
TErminal(value) NOTti
indicates that this panel relates to a TERMINAL inquiry This terminal cannot be used by transactions.
and displays a 4-character terminal identifier as defined
in an installed terminal definition. This includes all Notes:
terminals and sessions, but not logical device codes
(LDCs), model TCTTEs, mode groups, or system 1. You can reset this value by overtyping it with a
entries. See also Netname. different value.
2. A terminal cannot be defined with both NOATI and
Termstatus (vtam only)
NOTTI.
displays whether CICS is in session with the logical unit
represented by this terminal. The values are: Userid(data-area)
returns the 8-character identifier of the user signed on at
ACquired
this terminal or session.
CICS is in session with the logical unit
represented by the terminal. If there is no signed-on user, the default userid—as
specified in the DFLTUSER system initialization
parameter—is returned.

CEMT INQUIRE TRANSACTION
CEMT INQUIRE TRANSACTION (value)

is a 1–4 character transaction identifier. Only
Function: Retrieve information about transactions. transactions that have been defined in the CICS system
definition (CSD) file and installed on the running CICS
Description: INQUIRE TRANSACTION returns system are accessible through CEMT.
information about transaction definitions.
ALl
is the default.
two ways of commencing this transaction: CLass(value)
Type CEMT INQUIRE TRANSACTION (the minimum is the 2-character suffix of a transaction list table (XLT).
abbreviation is CEMT I TRANS). You get a display that
lists the current status. Sample screen
Type CEMT INQUIRE TRANSACTION (CEMT I TRANS) followed
by as many of the other attributes as are necessary to
limit the range of information that you require. So, for
à IN TRAN
ð
example, if you enter cemt i trans en pu, the resulting Tra(AADD) Pri( ðð1 ) Pro(DFH$AALL) Tcl(
Prf(DFHCICST) Uda Bel Iso
DFHTCLðð ) Ena Pur
Tra(ABRW) Pri( ðð1 ) Pro(DFH$ABRW) Tcl( DFHTCLðð ) Ena Pur

display will show you the details of only those Prf(DFHCICST) Uda Bel Iso
Tra(ADYN) Pri( ðð1 ) Pro(DFH99 ) Tcl( DFHTCLðð ) Ena Pur
transactions that are enabled and system-purgeable. Prf(DFHCICST) Uda Bel Iso
Tra(AINQ) Pri( ðð1 ) Pro(DFH$AALL) Tcl( DFHTCLðð ) Ena Pur
To change various attributes, you can: Tra(AMNU) Pri( ðð1 ) Pro(DFH$AMNU) Tcl(
DFHTCLðð ) Ena Pur
Tra(AORD) Pri( ðð1 ) Pro(DFH$AREN) Tcl( DFHTCLðð ) Ena Pur

Overtype your changes on the INQUIRE screen after Prf(DFHCICST) Uda Bel Iso
Tra(AORQ) Pri( ðð1 ) Pro(DFH$ACOM) Tcl( DFHTCLðð ) Ena Pur
tabbing to the appropriate field (see “Overtyping a Tra(AREP) Pri( ðð1 ) Pro(DFH$AREP) Tcl( DFHTCLðð ) Ena Pur
display” on page 47). + Tra(AUPD) Pri( ðð1 ) Pro(DFH$AALL) Tcl( DFHTCLðð ) Ena Pur
Use the CEMT SET TRANSACTION command.
Figure 119. CEMT INQUIRE TRANSACTION screen

55──CEMT Inquire TRAnsaction───────────────────5
┌─ALl──────────┐ If you place the cursor against a specific entry in the list and
5──┼──────────────┼──┬─────────────────┬───────5 press ENTER, CICS displays an expanded format as shown
├─(value)──────┤ └─PRIority(value)─┘ in Figure 120.
└─CLass(value)─┘
5──┬────────────────┬──┬───────────────┬───────5
└─PROgram(value)─┘ └─TClass(value)─┘
à IN TRAN
ð
5──┬──────────┬──┬──────────────┬──────────────5 RESULT - OVERTYPE TO MODIFY
Transaction(AADD)
├─Enabled──┤ ├─PUrgeable────┤ Priority( ðð1 )
Program(DFH$AALL)
└─Disabled─┘ └─NOTPurgeable─┘ Tclass( DFHTCLðð )
Status( Enabled )
5──┬───────────────┬──┬──────────┬─────────────5 | Routing(Dynamic)
| Routestatus(Notroutable)
└─PRFile(value)─┘ ├─CDatakey─┤ Purgeability( Purgeable )
Prfile(DFHCICST)
└─Udatakey─┘ Taskdatakey(Udatakey)
Taskdataloc(Below)
Isolatest(Isolate)
5──┬───────┬──┬───────────┬────────────────────5 Trprof()
├─ANy───┤ ├─ISolate───┤ Indoubt
Brexit
└─BElow─┘ └─NOIsolate─┘
5──┬───────────────┬──┬─────────┬──────────────5 Figure 120. The expanded display of an individual entry
└─TRprof(value)─┘ ├─BAckout─┤
└─COmmit──┘
Displayed fields
5──┬───────────────┬───────────────────────────5
└─BRexit(value)─┘ BRexit(value)
5──┬─────────────────────┬─────────────────────5 returns the 8-character name of the bridge exit defined
└─FAcilitylike(value)─┘ by the BREXIT parameter of the named transaction
5──┬────────────────────┬──┬────────┬──────────5 resource definition.
└─INdoubtmins(value)─┘ ├─NOWait─┤ If BREXIT is not defined, blanks are returned.
└─Wait───┘
5──┬─────────────┬──5% FAcilitylike(value)
| ├─Routable────┤ returns the 4-character name of the terminal defined by
| └─NOTRoutable─┘ the FACILITYLIKE parameter of the PROFILE
associated with the named transaction resource
definition.

INdoubtmins(value) Isolatest
displays the length of time, in minutes, after a failure displays whether the transaction’s user-key task-lifetime
during the in-doubt period, before the transaction is to storage is isolated from the user-key programs of other
take the action returned in the Indoubt field. The transactions. The values are:
returned value is valid only if the unit of work is in-doubt
ISolate
and Indoubtwait returns WAIT.
The transaction’s user-key task-lifetime storage is
See also Indoubt and Indoubtwait. accessible only by the user-key programs of its
own task. The transaction’s user-key task-lifetime
Indoubt
storage is isolated from all the user-key programs
displays the action (based on the ACTION attribute of
of all other tasks.
the TRANSACTION resource definition) to be taken if
the CICS region fails or loses connectivity with its NOIsolate
coordinator while a unit of work is in the in-doubt period. The transaction’s user-key task-lifetime storage is
accessible by its own programs, and also by
The action is dependent on the values returned in
user-key programs of other transactions defined
Indoubtwait and Indoubtmins; if Indoubtwait returns
with the ISOLATE(NO) option.
WAIT, the action is not normally taken until the time
returned in Indoubtmins expires. (For exceptions to this PRFile(value)
rule, see Indoubtwait.) displays the name of the profile definition that defines
The values are: additional options associated with this transaction.
BAckout PRIority(value)
All changes made to recoverable resources are to displays a value indicating the priority of a transaction
be backed out. relative to other transactions. When a transaction is
running as a CICS task, the priority of a task is the sum
COmmit
of the transaction priority, the terminal priority, and the
operator priority.
be committed, and the unit of work marked as
completed. Note: You can reset this value by overtyping it with a
different value.
Indoubtwait
The value is in the range 0–255, where 255 is the
displays (based on the WAIT attribute of the
highest priority.
TRANSACTION definition) how CICS is to respond if a
failure occurs while a unit of work (UOW) is in an PROgram(value)
in-doubt state. The values are: displays an 8-character string identifying the name of the
first program to be executed when this transaction is
NOWait
started.
The UOW is not to wait, pending recovery from
the failure. CICS is to take immediately whatever Purgeability
action is specified on the ACTION attribute of the displays whether the transaction is purgeable in system
TRANSACTION definition. stall conditions. The values are:
Wait The UOW is to wait, pending recovery from the
PUrgeable
failure, to determine whether recoverable
The transaction is system-purgeable. This value
resources are to be backed out or committed.
relates to the SPURGE parameter on the
Note: Even if Indoubtwait returns WAIT, there transaction resource definition and indicates that
may be aspects of the UOW that force CICS can purge the transaction in a deadlock
CICS to take an immediate decision—that time-out situation. See the CICS Resource
is, to take immediately the action specified Definition Guide for information about the
on the ACTION attribute of the transaction SPURGE and DTIMEOUT parameters on a
definition. This can happen if, for example, transaction resource definition.
the UOW contains:
NOTPurgeable
Subordinate LU6.1 sessions The transaction cannot be purged.
Subordinate MRO sessions to
pre-CICS Transaction Server for Note: You can reset this value by overtyping it with a
OS/390 systems. different value.
| Routstatus
For further information about the meaning of the
| displays whether, if the transaction is the subject of an
ACTION and WAIT attributes of the TRANSACTION
| eligible EXEC CICS START command, it will be routed
definition, see the CICS Resource Definition Guide.
| using the enhanced routing method. The values are:

| NOTRoutable this storage, but user-key programs have

| If the transaction is the subject of a START read-only access.
| command, it will be routed using the “traditional”
Udatakey
| method.
CICS obtains storage for the transaction from
| Routable user-key storage. Application programs that
| If the transaction is the subject of an eligible execute in any key have read-write access to this
| START command, it will be routed using the storage.
| enhanced method.
See the description of the TASKDATAKEY parameter on
the transaction resource definition in the CICS Resource
| For details of the enhanced and “traditional” methods of
| routing transactions invoked by EXEC CICS START
Definition Guide.
| commands, see the CICS Intercommunication Guide. Taskdataloc
displays whether certain CICS control blocks (including
Status
EIB and TWA) for a transaction are acquired above or
displays whether the transaction is available for use. The
below the 16MB line. The values are:
values are:
ANy The transaction accepts task-related data
Enabled
anywhere.
The transaction is available for use.
BElow
Disabled
The transaction requires any task-related data
The transaction is not available for use.
(TWA and EIB plus any internal control blocks) to
Note: If a transaction is disabled, this does not be located below the 16MB line.
prevent a START command that names
this transaction from being shipped to a TClass(value)
remote region. When a task is attached for displays an 8-character string identifying the name of the
the requested transaction, CICS checks transaction class to which the transaction belongs. If the
that the transaction is enabled in the transaction does not belong to a class, DFHTCL00 is
remote region. returned.
Note: You can reset this value by overtyping it with a different value.
different value.
To remove a transaction from its TCLASS, set this field
Taskdatakey to DFHTCL00. An added or changed TCLASS must be
displays the storage key in which CICS obtains all one that has already been defined.
storage for use by the transaction. This includes the task
TRAnsaction(value)
life-time storage—the transaction work area (TWA) and
indicates that this panel relates to a TRANSACTION
the EXEC interface block (EIB)—and the storage that
inquiry and displays a 4-character transaction identifier.
CICS obtains on behalf of programs that run under the
Only transactions that have been defined in the CICS
transaction.
system definition (CSD) file and installed on the running
The values are: CICS system are accessible through CEMT.
CDatakey TRprof(value)
CICS obtains storage for the transaction from displays the name of the transaction routing profile that
CICS-key storage. Application programs that defines additional options associated with this
execute in CICS key have read-write access to transaction if it is defined as a remote transaction.

CEMT INQUIRE TRDUMPCODE
CEMT INQUIRE TRDUMPCODE Sample screen
Function: Retrieve information about transaction dump

codes. à IN TRDU
ð
Trd(ATNI) Tra Loc Max( 999 ) Cur(ððð2)
Description: The INQUIRE function allows you to see the Trd(ERRS) Tra Loc Max( 999 ) Cur(ððð1)
current settings of the entries in the transaction dump table.

See the CICS Problem Determination Guide for information
on using dumps. Figure 121. CEMT INQUIRE TRDUMPCODE screen
Note: SHUTDOWN and MAXIMUM must not be used in the Note: There are blank fields on the screen where a value
same command. does not apply or is ‘negative’; that is, the value
Input: Press the Clear key to clear the screen. There are by tabbing (they appear in the same sequence as in
two ways of commencing this transaction: the expanded format), and overtype with input valid
Type CEMT INQUIRE TRDUMPCODE (the minimum for that field. You may find it more convenient to use
abbreviation is CEMT I TRD). You get a display that lists the expanded format when setting one of these
the current status. values, (negating is easier because you are
Type CEMT INQUIRE TRDUMPCODE (CEMT I TRD) followed by
the range of information that you require. So, for If you place the cursor against a specific entry in the list and
example, if you enter cemt i trd sy sh, the resulting press ENTER, CICS displays an expanded format as shown
display will show you the details of only those in Figure 122.
transaction dump codes for which system dumps are to
be taken and for which the CICS system is to shut
down.
à IN TRDU
ð
To change various attributes, you can: Trdumpcode(ATNI)
Trandumping( Trandump )
Sysdumping( Nosysdump )
Overtype your changes on the INQUIRE screen after Shutoption( Noshutdown )
Dumpscope( Local )
tabbing to the appropriate field (see “Overtyping a Maximum( 999 )
Current(ððð2)
display” on page 47). Action( )
Use the CEMT SET TRDUMPCODE command.

┌─ALl─────┐ Displayed fields

55──CEMT Inquire TRDumpcode──┼─────────┼───────5
└─(value)─┘ Action (input only field)
5──┬────────────┬──┬───────────┬───────────────5 displays whether the specified transaction dump code is
├─Trandump───┤ ├─SYsdump───┤ to be reset, removed from the dump code table, or
└─NOTrandump─┘ └─NOSYsdump─┘ added to the dump code table. The values are:
5──┬────────────┬──┬─────────┬─────────────────5 Reset
├─SHutdown───┤ ├─RELated─┤
└─NOSHutdown─┘ └─Local───┘ The current count of dump calls for this dump
code is to be reset to zero.
5──┬────────────────┬──┬────────────────┬──5%
└─Maximum(value)─┘ └─Current(value)─┘ Remove
This code is to be removed from the dump code
table.
(value)
is a 4-byte transaction dump code. See the CICS Add The specified transaction dump code is to be
Messages and Codes manual for information on added to the dump code table.
transaction dump codes. Current(value)
ALl displays the number of dump calls that have been made
is the default. for this transaction dump code since the number was
last reset to zero. The CURRENT value can be reset
explicitly (using a SET SYDUMPCODE RESET
command), or automatically whenever CICS shuts down.
different value.

CEMT INQUIRE TRDUMPCODE
Dumpscope NOSHutdown
displays whether a system dump request is to be sent to The CICS system is not to shut down.
MVS images in the sysplex which are running XCF/MRO
connected CICS regions related to the CICS region on Note: You can reset this value by overtyping it with a
which the dump is initiated. different value.
Note: A related CICS region is one in which the unit of Sysdumping
work identifiers, in the form of APPC tokens, of displays whether a system dump is to be taken for this
one or more tasks match those in the CICS transaction dump code. The values are:
SYsdump
RELated A system dump is to be taken.
A system dump request is to be sent for this
NOSYsdump
system dump code.
A system dump is not to be taken.
Local
A system dump request is not to be sent to other Note: You can reset this value by overtyping it with a
MVS images in the sysplex for this system dump different value.
code.
Trandumping
Note: You can reset this value by overtyping it with a displays whether a transaction dump is to be taken for
different value. this transaction dump code. The values are:
Maximum(value) Trandump
displays the largest number of dump calls for this dump A transaction dump is to be taken.
code that result in dumps being taken. The value is in NOTrandump
the range 0-999 and can be specified by using A transaction dump is not to be taken.
TRDUMAX in the SIT parameter. A value of 999 means
the default, ‘no limit’. Note: You can reset this value by overtyping it with a
different value.
Shutoption
displays whether the CICS system is to shut down after TRDumpcode(value)
the occurrence of an error corresponding to this dump indicates that this panel relates to a TRDUMPCODE
code. The values are: inquiry and displays a 4-character transaction dump
code. See the CICS Messages and Codes manual for
SHutdown
information on transaction dump codes.
The CICS system is to shut down.

CEMT INQUIRE TSMODEL
| CEMT INQUIRE TSMODEL |

| à I TSM
ð
| RESULT
| Function: Retrieve information about TS models. | Tsmodel(DFHWEB)
| Prefix(DFHWEB)
| Location(Main)
| Recovstatus(Notrecovable)
| Description: The INQUIRE TSMODEL command returns | Securityst(Nosecurity)
| Poolname()
| information about temporary storage models (TS models). | Remotesystem()
| Remoteprefix()
| Type CEMT INQUIRE TSMODEL (the minimum abbreviation
| is CEMT I TSM). You get a display that lists the current | Displayed fields
| status.
| Securityst(value)
| Type CEMT INQUIRE TSMODEL (CEMT I TSM) followed by as
| displays the security status for this model. The values
| many of the other attributes as are necessary to limit the
| are:
| range of information that you require. So, for example, if
| you enter cemt i tsm main, the resulting display will | Security
| show you the details of only those temporary storage | security checking will be performed for queue
| models associated with temporary storage queues which | names matching this model.
| are to be resident in main storage.
| Nosecurity
| To change various attributes, overtype your changes on the | security checking will not be performed for queue
| INQUIRE screen after tabbing to the appropriate field (see | names matching this model.
| “Overtyping a display” on page 47). | LOcation(value)
| | displays the location where temporary storage queues
| associated with this TS model reside. The values are:
| ┌─ALl─────┐
| 55──CEMT Inquire TSModel──┼─────────┼──────────5 | AUxiliary
| └─(value)─┘
| TS queues associated with this TS model are held
| ┌──
───────────────────────────┐ | on the CICS temporary storage VSAM data set
| 5───6┬─────────────────────────┬┴──5% | DFHTEMP, or in temporary storage pools in the
| ├─LOCATION(value)─────────┤
| ├─POOLNAME(data-area)─────┤ | coupling facility.
| ├─PREFIX(data-area)───────┤ | MAIn
| ├─RECOVSTATUS(value)──────┤
| ├─REMOTEPREFIX(data-area)─┤ | TS queues associated with this TS model are held
| ├─REMOTESYSTEM(data-area)─┤ | in main storage.
| └─SECURITYST(value)───────┘
| POolname(value)
| displays an 8-character shared pool name.
| ALl | PRefix(value)
| is the default. | displays the prefix for this model as a 16-character
| (value) | string.
| is the name of the temporary storage model for which | RECovstatus(value)
| information is requested. | displays the recovery status of the temporary storage
| queue. The values are:
| Sample screen
| Recoverable
| The temporary storage queue is recoverable.
|
| à I TSM
ð | Notrecovable
| STATUS: RESULTS
| Tsm(DFHWEB ) Pre(DFHWEB ) Mai | The temporary storage queue is not recoverable.
| REMOTEPrefix(value)
| displays the remoteprefix for this model as a
| 16-character string.
| REMOTESystem(value)
| Figure 123. CEMT INQUIRE TSMODEL screen
| displays the remotesystem name for this model as a
| If you place the cursor against a specific entry in the list and | 4-character string.
| press ENTER, CICS displays an expanded format as shown
| in Figure 124.

CEMT INQUIRE TSPOOL
| TSmodel(value) | CEMT INQUIRE TSPOOL

| indicates that this panel relates to a TSMODEL inquiry
| and displays the 8-character name of a temporary | Function: Retrieve information about a TS pool.
| storage model.
| Note: Nondisplayable characters appear as periods. | Description: The INQUIRE TSPOOL command returns
| You can use PF2 on the expanded panel to see | information about a temporary storage pool (TS pool).
| the value in hexadecimal.
| Type CEMT INQUIRE TSPOOL (the minimum abbreviation is
| CEMT I TSP). You get a display that lists the current
| status.
| Type CEMT INQUIRE TSPOOL (the minimum abbreviation is
| CEMT I TSP) followed by as many of the other attributes
| as are necessary to limit the range of information that
| you require. So, for example, if you enter cemt i tsp
| connected, the resulting display will show you the details
| of only those shared temporary storage pools that are
| connected.
| To change various attributes, overtype your changes on the

| INQUIRE screen after tabbing to the appropriate field (see
| “Overtyping a display” on page 47).
|
| ┌─ALl─────┐
| 55──CEMT Inquire TSPool──┼─────────┼───────────5
| └─(value)─┘
| 5──┬──────────────────┬──5%
| └─CONNSTATUS(cvda)─┘
| ALl
| is the default.
| (value)
| is the name of the temporary storage pool for which
| information is requested.
| Sample screen
|
| à I TSP
ð
| STATUS: RESULTS
| Tsp(DFHWEB ) Unc
| Figure 125. CEMT INQUIRE TSPOOL screen
| press ENTER, CICS displays an expanded format as shown
| in Figure 126.
|
| à I TSP
ð
| RESULT
| Tspool(DFHWEB)
| Connstatus(Unconnected)

CEMT INQUIRE TSQUEUE / TSQNAME
| Displayed fields CEMT INQUIRE TSQUEUE / TSQNAME

| Connstatus(value)
Function: Retrieve information about temporary storage
| displays the connection status of this TS pool. The
queues.
| values are:
| Connected | This section applies also to the alternative command, CEMT

| This TS pool is connected. | INQUIRE TSQNAME. Use either to Inquire about names up
| to 8 characters long, use INQUIRE TSQNAME to Inquire
| Unconnected | about names up to 16 characters long.
| This TS pool is not connected.
| Tspool(value) Description: The INQUIRE TSQUEUE command returns

| indicates that this panel relates to a TSPOOL inquiry information about temporary storage queues (TS queues).
| and displays the 8-character name of a temporary The INQUIRE TSQUEUE command operates on all the
| storage pool. temporary storage queues that exist in the CICS region,
including those created internally by CICS for use by CICS
| Note: Nondisplayable characters appear as periods. itself (for example, queues used by BMS). You can identify
| You can use PF2 on the expanded panel to see the temporary storage queues created by CICS for its own
| the value in hexadecimal. use by queue names that begin with the following character
strings:
** BMS paging
$$ BMS route
X'fa' to X'ff' CICS
CEBR Default CEBR queue name
DF CICS
DFHM Message cache for message-protected
tasks
DFxxxx CICS REQIDS (where x is hexadecimal)
| Type CEMT INQUIRE TSQUEUE (the minimum abbreviation
| is CEMT I TSQ). You get a display that lists the current
status.
Type CEMT INQUIRE TSQUEUE (CEMT I TSQ) followed by as
range of information that you require. So, for example, if
you enter cemt i tsq main, the resulting display will
show you the details of only those temporary storage
queues that are resident in main storage.
To change various attributes, overtype your changes on the

INQUIRE screen after tabbing to the appropriate field (see
“Overtyping a display” on page 47).

CEMT INQUIRE TSQUEUE / TSQNAME
┌─ALl─────┐ à INQ TSQ

ð
| 55──CEMT Inquire TSQueue──┼─────────┼──────────5 RESULT - OVERTYPE TO MODIFY
Tsqueue(AXBYQUEUENAME1)
└─(value)─┘ Numitems(ðððð3)
Length(ððððððð192)
Location(Main)
5──┬─────────────────┬──┬─────────────────┬────5 Action( )
| ├─SYSID(value)────┤ └─Numitems(value)─┘ Transid(CECI)
Recovstatus(Notrecovable)
| └─POOLNAME(value)─┘ Maxitemlen(ððð64)
Minitemlen(ððð64)
Lastusedint(ðððð1357)
5──┬────────────────────┬──────────────────────5
└─LAstusedint(value)─┘
5──┬───────────────┬──┬───────────┬────────────5
└─LEngth(value)─┘ ├─MAIn──────┤
└─AUxiliary─┘
5──┬───────────────────┬───────────────────────5 | type a ‘B’ (upper or lower case), CICS invokes the CEBR
└─MAXitemlen(value)─┘
| transaction to browse the contents of this TS queue, (see
5──┬───────────────────┬───────────────────────5 | Chapter 6, “CEBR—temporary storage browse” on page 19
└─MInitemlen(value)─┘
| for details).
| 5──RECOVSTATUS(value)──┬────────────────┬──5%
└─Transid(value)─┘ | Not all TS queues visible on the CEMT INQUIRE TSQUEUE
| results panel are necessarily browsable via CEBR.
| Specifically, this applies to queues resident in a shared TS
ALl | POOL when the POOLNAME is specified on the INQUIRE
is the default. | TSQUEUE request.
(value)
| Such queues are browsable if there is a tsmodel or TST
is the name of the temporary storage queue for which
| entry mapping the queue name to the TSPOOL.
information is requested.
| Note: For this release only you can also browse queues in
Sysid(value) | a shared pool by specifying a SYSID which maps to
specifies the system name that corresponds to the | the shared pool via an entry in the SYSID table.
temporary storage pool name if the request is to be sent | However, the SYSID required for the mapping is not
to a TS server. | available to CEMT, so entering ‘B’ next to the queue
This is an input-only value, and must be specific—you | at first gives a NOT FOUND response from CEBR. If
cannot specify generic names for SYSID. If the SYSID is | an appropriate SYSID is then provided by the user,
not found in a TST TYPE=SHARED entry, CICS returns | the reference to the shared pool can be resolved.
a SYSID NOT FOUND error.
| If there is no suitable entry in the SYSID table and no
| Poolname(value) | TSMODEL mapping the queue name to the shared pool, the
| specifies the 8-character POOLNAME of a temporary | queue cannot be browsed and CEBR will indicate that the
| storage pool if the request is to be sent to a TS server. | requested queue does not exist.
| If the POOLNAME is not found, CICS returns a
| POOLERR.
Displayed fields
LAstusedint(value)
Sample screen displays the elapsed time interval in binary seconds
since the queue was last referenced.
à ð LEngth(value)
INQ TSQ
STATUS: RESULTS - OVERTYPE TO MODIFY displays the total length in bytes of all the items in the
Tsq(AXBYQUEUENAME1 ) Num(ðððð3) Len(ððððððð192) Mai
Tra(CECI) Max(ððð64) Min(ððð64) Las( ðððð1267 ) temporary storage queue. For information about how
Tsq(RDOQUEUENAME4 ) Num(ðððð1) Len(ðððððððð64) Aux
Tra(CECI) Rec Max(ððð64) Min(ððð64) Las( ðððððð97 ) CICS calculates the length of items, see the CICS
Tsq(RDOQUEUENAME5 ) Num(ðððð2) Len(ððððððð128) Aux
Tra(CECI) Rec Max(ððð64) Min(ððð64) Las( ðððððð86
Tsq(RDQUEUENAME5 ) Num(ðððð3) Len(ððððððð192) Mai
) System Programming Reference.
Tra(CECI) Max(ððð64) Min(ððð64) Las( ðððððð76 )
LOcation(value)
displays where the temporary storage queue resides.
Figure 127. CEMT INQUIRE TSQUEUE screen The values are:
If you place the cursor against a specific entry in the list and AUxiliary
press ENTER, CICS displays an expanded format as shown The temporary storage queue is held on the CICS
in Figure 128. temporary storage VSAM data set DFHTEMP, or
in temporary storage pools in the coupling facility.

CEMT INQUIRE UOW
MAIn CEMT INQUIRE UOW

The temporary storage queue is held in main
storage. Function: Retrieve information about units of work
MAXitemlen(value) (UOWs).
displays the length in bytes of the largest item in the
Description: INQUIRE UOW returns information about a
temporary storage queue. For information about how
named unit of work, or about all the UOWs currently in the
CICS calculates the length of items, see the CICS
system. It displays the state of the UOW (for example,
System Programming Reference.
INDOUBT) and whether it is active, waiting, or shunted.
MInitemlen(value)
displays the length in bytes of the smallest item in the If you suspect a problem with either a recoverable data set
temporary storage queue. For information about how or a connection, you can use INQUIRE UOW to display
CICS calculates the length of items, see the CICS UOWs that have been shunted due to a connection or data
System Programming Reference. set failure. The command, in some cases, displays the name
of the resource that caused the UOW to be shunted, plus the
Numitems(value) transaction, user, and terminal that started it.
displays the number of items in the temporary storage
Important: In an intercommunication environment, a unit of
queue.
work can include actions that are to be taken by two
| Recovstatus(value) or more connected systems. Such a unit of work is
| displays the recovery status of the temporary storage known as a distributed unit of work, because the
| queue. The values are: resources to be updated are distributed across more
than one system. A distributed unit of work is made
| Recoverable up of two or more local units of work, each of which
| The temporary storage queue is recoverable. represents the work to be done on one of the
| Notrecovable participating systems.
| The temporary storage queue is not recoverable.
Note that INQUIRE UOW always returns information
Transid(value) about local UOWs—that is, for a distributed UOW it
displays the 4 character id of the transaction that created returns information only about the work required on
the TS queue. the system on which the command is issued. You
can assemble information about a distributed UOW
TSqueue(value)
by matching the network-wide UOW identifier
indicates that this panel relates to a TSQUEUE inquiry
returned in the NETUOWID field against the
| and displays the 16-character name of a temporary
network-wide identifiers of local UOWs on other
storage queue.
systems.
Note: Nondisplayable characters appear as periods.
You can use PF2 on the expanded panel to see For further information about local and distributed
the value in hexadecimal. UOWs, see the CICS Intercommunication Guide.
Type CEMT INQUIRE UOW (the minimum abbreviation is
CEMT I UOW). You get a display that lists all the current
UOWs.
Type CEMT INQUIRE UOW (CEMT I UOW) followed by as
you enter cemt i uow sh con, the resulting display will
show you the details of only those UOWs that have
been shunted due to the failure of a connection.

CEMT INQUIRE UOW
┌─ALl─────┐ à IN UOW
ð
55──CEMT Inquire UOW──┼─────────┼──────────────5 RESULT - OVERTYPE TO MODIFY
Uow(AB8FFF37584B66ð1)
└─(value)─┘ Uowstate( Inflight )
Waitstate(Active)
Transid(CSSY)
5──┬──────────┬──┬─────────┬───────────────────5 Taskid(ðððððð5)
├─Backout──┤ ├─ACtive──┤ Age(ðððð4233)
Termid()
├─COMmit───┤ ├─WAITIng─┤ Netname()
Userid(BELL)
├─INDoubt──┤ └─SHunted─┘ Waitcause()
Link()
├─INFlight─┤ Sysid()
├─HBackout─┤ Netuowid(..GBIBMIYA.CICSHT61........)
└─HCommit──┘
5──┬────────────────┬──┬───────────────┬───────5
└─TRansid(value)─┘ └─TAskid(value)─┘ Figure 130. The expanded display of an individual entry
5──┬────────────┬──┬───────────────┬───────────5
└─AGe(value)─┘ └─TErmid(value)─┘ Displayed fields
5──┬────────────────┬──┬───────────────┬───────5 AGe(value)
└─NETName(value)─┘ └─Userid(value)─┘ displays the age of the UOW in seconds. This is the
5──┬────────────┬──┬─────────────┬─────────────5 number of seconds since the UOW entered its current
├─CONnection─┤ └─Link(value)─┘ state, or since the start of the UOW.
├─Dataset────┤
├─Rlsserver──┤ Link(value)
├─WAITCommit─┤ displays the 8-character netname of the remote system
├─WAITForget─┤ that caused the UOW to wait or be shunted, or blanks if
└─WAITRmi────┘
the UOW is not waiting for a connection.
5──┬──────────────┬──┬─────────────────┬──5%
└─SYsid(value)─┘ └─NETUowid(value)─┘ NETName(value)
displays the 8-character network name of the terminal
from which the UOW was started.
(value)
is a 16-character local identifier of a UOW. If the UOW was started from an ISC or MRO session,
NETNAME displays the network name of the remote
ALl region.
is the default. If you do not specify a UOW identifier, you
If the UOW was not started from a terminal, nor from an
receive information about all UOWs in the system.
ISC or MRO session, NETNAME displays blanks.
Sample screen NETUowid(value)
displays a 27-character string containing the LU6.2
name for the UOW within this network—that is, the
à IN UOW
ð network-wide identifier of the UOW.
Uow(AB8FFF37584B66ð1) Inf Act Tra(CSSY)
Age(ðððð4ð9ð)
Tas(ðððððð5)
Use(BELL )
Uow(AB8FFF3758786Cð1) Inf Act Tra(CSSY)
Age(ðððð4ð9ð)
Tas(ðððððð6)
Use(BELL )
You can use PF2 on the expanded panel: to see
Uow(AB8FFF376D9B66ð1) Inf Act Tra(CSTP)
Age(ðððð4ð9ð)
Tas(ðððððð8)
Use(BELL )
the value in hexadecimal.
Uow(AB9ððBD865417Cð4) Inf Act Tra(CSNE) Tas(ððððð18)
Age(ððððð7ðð)
Uow(AB9ððBE2ð1ðAC4ð1) Inf Act Tra(CEMT)
Use(BELL
Tas(ððððð43)
) You can assemble information about a distributed UOW
Age(ððððð689) Ter(S21D) Netn(IGBS21D ) Use(BELL )
by matching the network-wide UOW identifier against the
network-wide identifiers of local UOWs on other
systems.
Figure 129. CEMT INQUIRE UOW screen
SYsid(value)
Note: There are blank fields on the screen where a value displays the 4-character sysid of the connection that
does not apply or is ‘negative’; that is, the value caused the UOW to wait or be shunted, or blanks if the
begins with ‘No’. To modify these fields, locate them UOW is not waiting for a connection or the connection
by tabbing (they appear in the same sequence as in has been discarded.
for that field. You may find it more convenient to use TAskid(value)
the expanded format when setting one of these displays the task number originally associated with this
values, (negating is easier because you are UOW. If the UOW is shunted, the task terminates. In this
overtyping a displayed field with its negative causing case, the number may have been reused by another
the result to become non-displayed). task.
in Figure 130.

CEMT INQUIRE UOW
TErmid(value) Userid(value)
displays the 4-character ID of the terminal from which displays the 8-character user ID with which this
this UOW was started. This is the principal facility for the transaction was started.
task. If the transaction is the mirror transaction, CSMI, it
UOW(value)
is the session.
indicates that this panel relates to a UOW inquiry and
TRansid(value) displays a 16-character UOW local identifier.
displays the 4-character ID of the transaction that started
Waitcause
this UOW.
displays, if the UOW is waiting or shunted, the type of
Uowstate resource that caused it to be so.
displays the state of the UOW. The values are:
Note: In the case of a wait, it is the UOW that is
Backout waiting, not the task.
This UOW is being backed out, or has failed to The values are:
back out one or more of the recoverable resources
involved in the UOW. CONnection
This UOW is waiting or was shunted due to the
COMmit
failure of a session to the coordinator of the UOW
A decision to commit the UOW has been made,
during the in-doubt period. NETNAME and SYSID
but the UOW is waiting or has been shunted. This
contain the netname and system name of the
may be because the decision has not yet been
failed link.
communicated to all participants in the syncpoint,
or because a failure has occurred during commit Dataset
processing. This UOW is waiting or was shunted due to the
failure of one or more data sets. Use the INQUIRE
INDoubt
UOWDSNFAIL command to identify the data sets
This UOW is in the in-doubt state.
involved and the reasons why they have caused
INFlight the UOW to fail.
The UOW is running normally.
RLsserver
HBackout This UOW is waiting or was shunted due to the
The UOW has been forcibly backed out. A forced failure of an RLS server.
decision is taken when a UOW is unable to wait
| RRms
for in-doubt resolution—for example, the
| This UOW is waiting or has been shunted
transaction may have been defined as WAIT(NO),
| because communication has been lost with
or have been backed out with a CEMT SET UOW
| RRS/MVS.
command.
WAITCOmmit
HCommit
This UOW is waiting or was shunted because a
The UOW has been forcibly committed.
failure occurred during commit processing.
Note: You can reset this value by overtyping it with: WAITForget

This UOW is waiting for FORGET from
COMmit participants in the syncpoint. Use the INQUIRE
Attempt to force syncpoint commit UOWLINK command to obtain the netnames and
processing, as specified for this UOW. sysids of the participants.
Backout WAITRmi
Attempt to force syncpoint backout This UOW is waiting for FORGET from the RMI.
processing, as specified for this UOW. Use the INQUIRE UOWLINK command to obtain
Force the entry name and qualifier of the task-related
Attempt to force the UOW to backout or user exit.
commit, as specified on the ACTION
Waitstate
option of the TRANSACTION resource
displays whether syncpoint processing of the UOW has
definition.
been deferred. The values are:
All these values are valid only for UOWs that ACtive
have been shunted in-doubt. For information The UOW is running normally, or is being
about the in-doubt attributes of TRANSACTION unshunted.
resource definition, see the CICS Resource
WAITIng
Definition Guide. Syncpoint processing has completed on this
system, but not on all systems involved in the

CEMT INQUIRE UOWDSNFAIL
distributed UOW. Values of WAITFORGET or CEMT INQUIRE UOWDSNFAIL

WAITRMI, and BACKOUT or COMMIT indicate
how the UOW was resolved on this system. Function: Obtain information about failed units of work
SHunted that have updated CICS file-control-managed data sets.
Syncpoint processing of the UOW has been
deferred. SHUNTED further indicates that the task, Description: INQUIRE UOWDSNFAIL returns information
terminal and program storage have been released, about UOW failures that are associated with specific data
and locks have been retained. sets. If you enter the basic command (CEMT INQUIRE
UOWDSNFAIL) without any attributes to act as a filter, CICS
displays all failed UOWs for all data sets.
Because this command returns information about UOW

failures, if a UOW that had suffered a failure is in the process
of being retried when the command is issued, the UOW will
not be displayed by INQUIRE UOWDSNFAIL (it is not
currently shunted or failed). If the retry is successful, the
UOW no longer has a failure with respect to that particular
data set. If the retry is not successful, the UOW will be
shunted again, and INQUIRE UOWDSNFAIL will display it as
failed with respect to the data set.
Alternatively, if you are interested only in those failed UOWs

for specific data sets, you can use the DSNAME parameter
as a filter by specifying either a specific or generic data set
name. You can also use other attributes as filters, such as
CONNECTION for UOWs that failed indoubt, or DATASET
for UOWs that failed during backout for some reason. See
the list of reasons for UOW failures, and the associated
causes, which you can use for filtering the results of
INQUIRE UOWDSNFAIL commands.
Input: Press the Clear key to clear the screen and enter
the basic command as CEMT INQUIRE UOWDSNFAIL. (The
minimum abbreviation is CEMT I UOWD.) You get a display of
all the failed UOWs, if any. Otherwise, CICS returns the NOT
FOUND error condition
Alternatively, enter the command with one or more valid

attributes to filter the results of the inquiry. For example, if
you enter cemt i uowd ds(applb.\), the resulting display will
show you the details of only those failed UOWs that are
associated with data sets with a high-level qualifier of
APPLB.

Cause
55──CEMT Inquire UOWDsnfail──UOw(value)────────5 displays which failed component has caused the UOW
5──DSname(value)──┬────────┬───────────────────5 to have retained locks for this data set. The values are:
├─NOtrls─┤
└─RLS────┘ CAche
A cache structure, or connection to it, has failed.
5──┬────────────┬──┬──────────────┬────────────5
├─CAche──────┤ ├─Backupnonbwo─┤ CONnection
├─CONnection─┤ ├─COMmitfail───┤ There is an intersystem connection error, which
├─DATASET────┤ ├─DATASETFull──┤
├─RLSServer──┤ ├─DEAdlock─────┤ has caused the UOW to fail while in-doubt. The
└─UNdefined──┘ ├─DELexiterror─┤ name of the system to which connectivity was lost
├─Failedbkout──┤ is returned on the SYSID parameter and its
├─INDExrecfull─┤ netname is returned on the NETNAME parameter.
├─IOerror──────┤
CICS returns additional information in the
├─Openerror────┤
├─RLSGone──────┤ REASON parameter about the CONNECTION
├─INDOubt──────┤ failure.
├─RRCommitfail─┤
├─RRIndoubt────┤ DATASET
└─Lckstrucfull─┘ The backout of a UOW has failed for this data set.
5──┬──────────────┬──┬────────────────┬──5% The reason for the data set failure is returned in
└─Sysid(value)─┘ └─NEtname(value)─┘ the REASON parameter.
RLSServer
The SMSVSAM server has failed. The reason for
Sample screen the data set failure is returned in the REASON
parameter.
UNdefined
à INQ UOWDSN
ð The UOW is probably in-flight following an
STATUS: RESULTS
Dsn(RLS.ACCOUNTS.ESDS.DBASE1
Uow(AA6DBð8ðC4ðCEEð1)
) Dat Del
Rls
emergency restart.
Dsn(RLS.ACCOUNTS.ESDS.DBASE1 ) Dat Ind
Uow(AA6DBð8AC66B4ððð) Rls
DSname(value)
displays the 44-character data set name of a data set
that has retained locks for this UOW.
Figure 131. CEMT INQUIRE UOWDSNFAIL screen
NEtname(value)
Note: There are blank fields on the screen where a value displays the 8-character netname (when the cause is
does not apply or is ‘negative’; that is, the value CONNECTION) of the remote system to which
begins with ‘No’. To modify these fields, locate them connectivity has been lost.
Reason
displays, when the cause is RLSSERVER,
CONNECTION, or DATASET, the specific reason for the
error against this data set. The values are:
overtyping a displayed field with its negative causing Backupnonbwo
the result to become non-displayed). A non-BWO backup was in progress while the
UOW was being backed out. When the backup
If you place the cursor against a specific entry in the list and completes, CICS automatically retries the UOW.
in Figure 132. COMmitfail
An error occurred at some point when the locks
were in the process of being released. This is an
error that can normally be resolved by recycling
à INQ UOWDSN
ð the server (which should happen automatically).
RESULT
Uowdsnfail
Dsname(RLS.ACCOUNTS.ESDS.DBASE1)
The locks were acquired as a result of recoverable
Cause(Dataset)
Reason(Delexiterror) requests having been issued against the data set.
Uow(AA6DBð8ðC4ðCEEð1)
Sysid()
Netname()
DATASETFull
Rlsaccess(Rls)
No space is available on the direct access device
for adding records to a data set. You need to
reallocate the data set with more space. You can
then retry the backout using SET DSNAME
RETRY.

See the section on moving data sets in the CICS error. One likely reason could be that the data set
Recovery and Restart Guide. was quiesced.
DEAdlock (non-rls data sets only) RLSGone
A deadlock was detected. This may go away if the An error occurred when backing out the UOW
UOW is retried. because the RLS server is down. This may also
be the reason why the UOW went into backout
DELexiterror
originally. This is an error that can be resolved by
Backout of a write to an ESDS failed because a
recycling the server (which should happen
logical delete global user exit program was not
automatically). Generally, when the server
enabled, or a logical delete global user exit
recovers, the UOWs are retried automatically. In
program decided not to execute the logical delete.
very exceptional circumstances, it may be
Failedbkout necessary to issue a SET DSNAME(...) RETRY
This occurs as a result of a severe error being command to retry UOWs that were not retried
identified, and is possibly an error in either CICS when the server returned.
or VSAM. The problem may go away if the UOW
RRCommitfail
is retried. Note that CICS performs some
An error occurred whilst RLS locks for the unit of
first-failure data capture (FFDC) at the point where
work were being released. For this data set, the
the error is first detected.
locks being released were all repeatable read
INDExrecfull locks so, if the failure was due to the RLS server
A larger alternate index record size needs to be being unavailable, the locks will have been
defined for the data set. See the section on released. If the failure was due to some other
moving data sets in the CICS Recovery and error from the SMSVSAM server, the locks may
Restart Guide. still be held.
This error can also occur when a unique alternate RRIndoubt
index key, for a non-RLS data set, has been The unit of work had issued repeatable read
reused and CICS is now backing out the request requests against the data set, and has now failed
which had removed that key value. indoubt. The locks will have been released, so this
INDOubt failure does not prevent you from running a batch
The unit of work had issued recoverable requests job against the data set. However, if you want to
against the data set, and has now failed in-doubt. open the data set in non-RLS mode from CICS,
The connection to the coordinating system needs you need to resolve the in-doubt failure before you
to be reestablished. can define the file as having RLSACCESS(NO). If
the unit of work has updated any other data sets,
IOerror
or any other resources, you should try to resolve
A hard I/O error occurred. To correct this error,
the in-doubt correctly. If the unit of work has only
restore a full backup copy of the data set and
performed repeatable reads against VSAM data
perform forward recovery. If you use CICSVR as
sets and has made no updates to other resources,
your forward recovery utility, the backout is
it is safe to force the unit of work using the SET
automatically retried for an RLS data set. For a
DSNAME or SET UOW commands.
non-RLS data set, use the RETRY option of the
SET DSNAME command to drive the backout
Each Reason corresponds to only one Cause value, as
retry.
shown in the following table:
Lckstrucfull
An attempt to acquire a lock during backout of an Cause Reason
update to this data set failed because the RLS CACHE NOTAPPLIC
lock structure was full. You must allocate a larger CONNECTION INDOUBT
lock structure in an available coupling facility and CONNECTION RRINDOUBT
rebuild the existing lock structure into it, then use DATASET BACKUPNONBWO
DATASET DELEXITERROR
the SET DSNAME (...) RETRY command to drive
DATASET DATASETFULL
the backout retry. DATASET DEADLOCK
Notapplic DATASET FAILEDBKOUT
The value for CAUSE is not CONNECTION, DATASET INDEXRECFULL
DATASET IOERROR
RLSSERVER, or DATASET.
DATASET LCKSTRUCFULL
Openerror DATASET OPENERROR
Error on opening the file for backout. A console RLSSERVER COMMITFAIL
message notifies you of the reason for the open RLSSERVER RLSGONE
RLSSERVER RRCOMMITFAIL
UNDEFINED Not applicable

CEMT INQUIRE UOWENQ
Rlsaccess CEMT INQUIRE UOWENQ

displays whether the data set was last opened in this
CICS region in RLS or non-RLS mode. The values are: | Function: Retrieve information about enqueues held or
RLS The last open in this CICS region was in RLS | waited on by a UOW, or about UOWs holding or waiting on a
mode. | specified enqueue.
NOtrls Description: INQUIRE UOWENQ returns information

The last open in this CICS region was in non-RLS about the enqueues held by a UOW. Enqueues are used by
mode. CICS to lock recoverable resources such as file records or
queues to the UOW that is updating them. User enqueues
Sysid(value)
obtained by the EXEC CICS ENQ command are also
displays the 4-character sysid (when the cause is
returned.
CONNECTION) of the remote system to which
connectivity has been lost. You can use INQUIRE UOWENQ to indicate which records
UOw(value) and queues would be affected if the UOW were forced.
displays the 16-character local identifier of the
The transaction also returns information about UOWs that
associated unit of work.
are waiting on the enqueues. This enables you to diagnose
UOWDsnfail enqueue deadlocks between tasks wanting to update the
indicates that this panel relates to an inquiry about the same resources.
cause of a UOW failure.
Enqueues are typically held in active state, which means that
other tasks are allowed to wait for the enqueue. However, if
the UOW that owns the enqueue suffers an in-doubt failure,
the enqueue is usually converted to the retained state until
the in-doubt failure can be resolved. INQUIRE UOWENQ
also retrieves information about these enqueues and can be
used to identify which records and queues would be affected
if the UOW were forced.
Notes:
1. Both UOW-lifetime and task-lifetime enqueues are
returned by INQUIRE UOWENQ. (For an explanation of
UOW- and task-lifetime enqueues, see the
MAXLIFETIME option of the EXEC CICS ENQ command
in the CICS System Programming Reference manual.)
2. On an in-doubt failure, user enqueues are released,
unless the EXEC CICS ENQ command specified
MAXLIFETIME(TASK) and it is not the end-of-task
syncpoint that suffers the failure.
Type CEMT INQUIRE UOWENQ (the minimum abbreviation is
CEMT I UOWE). You get a display that lists all enqueues
for all the current UOWs.
Type CEMT INQUIRE UOWENQ (CEMT I UOWE) followed by as
you enter cemt i uowe d, the resulting display will show
you the details only of enqueues on records in VSAM
data sets open in non-RLS mode or CICS-maintained
data tables.

CEMT INQUIRE UOWENQ
Displayed fields
55──CEMT Inquire UOWEnq──┬────────────┬────────5
└─Uow(value)─┘ | Duration(value)
5──┬────────────────┬──┬───────────────┬───────5 | displays the elapsed time (in seconds) since the
└─TRansid(value)─┘ └─TAskid(value)─┘ | enqueue f entered its current state of OWNER, WAITER
5──┬──────────┬──┬─────────────┬───────────────5 | or RETAINED.
├─ACtive───┤ ├─Dataset─────┤
└─RETained─┘ ├─File────────┤ | ENQFails(value)
├─EXecenq─────┤ | displays, for enqueues held in retained state, the number
├─ADdrexecenq─┤ | of failed enqueue attempts for this resource since the
├─TDq─────────┤ | enqueue was last acquired. This indicates how many
└─TSq─────────┘ | UOWs have received LOCKED responses due to this
5──┬────────┬──┬─────────────────┬─────────────5 | enqueue. The ENQFAILS option helps you identify
├─Owner──┤ └─Netuowid(value)─┘ | which UOWs are causing “bottlenecks.”
└─Waiter─┘
| For enqueues held in action state, ENQFAILS displays
5──┬─────────────────┬──┬─────────────────┬────5
└─ENqfails(value)─┘ └─RESource(value)─┘ | zero.
5──┬─────────────┬──┬──────────────────┬───────5 | ENQScope(value)
└─RLen(value)─┘ └─QUalifier(value)─┘ | If the enqueue has sysplex scope, ENQSCOPE displays
5──┬─────────────┬──5% | the 4-character name which was used to qualify the
└─QLen(value)─┘ | sysplex-wide ENQUEUE request issued by this CICS
| region. If it has region scope, ENQSCOPE displays
| blanks.
Sample screen
| All CICS systems with the same ENQSCOPE value
| share the same sysplex Enqueue name space.
à INQ UOWE
ð Netuowid(value)
STATUS: RESULTS
Uow(AC143ðð1D4A726ð1) Tra(CECI) Tas(ððððð38) Act Exe Own
displays a 27-character string containing the
Res(ACCOUNTS.DBASE1 ) Rle(ð15) Enq(ðððððððð)
Uow(AC143ðð1D4A726ð1) Tra(CECI) Tas(ððððð38) Act Add Own network-wide LU6.2 name of the UOW that owns or is
Res(g... ) Rle(ðð4) Enq(ðððððððð)
waiting for the enqueue.
Figure 133. CEMT INQUIRE UOWENQ screen You can use PF2 on the expanded panel: to see
does not apply or is ‘negative’; that is, the value QUalifier(value)
begins with ‘No’. To modify these fields, locate them displays a 1- through 255-character qualifier (for
by tabbing (they appear in the same sequence as in example, record id) that further identifies the resource
the expanded format), and overtype with input valid associated with the enqueue lock. The data displayed
for that field. You may find it more convenient to use depends on the type of enqueue, as shown in Table 3
the expanded format when setting one of these on page 150. If no QUALIFIER data applies (that is for
values, (negating is easier because you are EXECENQ, ADDREXECENQ, or TSQ), a value of zero
overtyping a displayed field with its negative causing is displayed.
the result to become non-displayed). QLen(value)
displays the length of the data, in the range 0 through
255, displayed in the QUALIFIER field.
in Figure 134. RELation
displays whether the data is associated with the owner
of the enqueue or with a task waiting for the enqueue.
à INQ UOWE
ð The values are:
RESULT
Uowenq
Uow(AC143ðð1D4A726ð1)
Owner
Transid(CECI)
Taskid(ððððð38) The (value), NETUOWID, TASKID, and TRANSID
State(Active)
Type(Execenq) are those of the owner of the enqueue.
Relation(Owner)
Resource(ACCOUNTS.DBASE1)
Rlen(ð15) Waiter
Enqfails(ðððððððð)
Netuowid(..GBIBMIYA.IYA2T5C2...Mx...) The (value), NETUOWID, TASKID, and TRANSID
Qualifier()
Qlen(ððð) are those of a waiter for the enqueue.

CEMT INQUIRE UOWENQ
RLen(value) Note that truncation occurs if this combination

displays the length of the data, in the range 0 through exceeds 255 characters.
255, displayed in the RESOURCE field.
EXecenq
RESource(value) The resource is associated with an EXEC CICS
displays a 1- through 255-character string containing the ENQ request. RESOURCE contains the enqueue
name of the resource associated with the enqueue lock. argument passed on the request.
The data displayed depends on the type of enqueue, as ADdrexecenq
shown in Table 3. The resource is associated with an EXEC CICS
Note: Nondisplayable characters appear as periods. ENQ request. RESOURCE contains the address
You can use PF2 on the expanded panel: to see enqueue argument passed on the request (that is,
the value in hexadecimal. the LENGTH parameter was omitted on the
request)
State
TDq The resource is a logically-recoverable transient
displays the state that the enqueue is held in. The
data queue. RESOURCE contains the name of the
values are:
queue. QUALIFIER contains either the string
ACtive “FROMQ” or “TOQ,” indicating whether a read or
The enqueue is held in active state. write lock is held for the queue.
RETained A READQ TD request acquires the “FROMQ” lock,
The enqueue is held in retained state. Its owning whereas a WRITEQ TD request acquires the
UOW has been shunted, or is in the process of “TOQ” lock associated with the queue. A
being shunted. DELETEQ TD request acquires both the “TOQ”
and the “FROMQ” locks.
TAskid(value)
displays the number of the task associated with the TSq The resource is a recoverable temporary storage
UOW. If the UOW is shunted, it is the task number queue. RESOURCE contains the name of the
associated with the UOW before it was shunted. queue.
TRansid(value) The data displayed in the RESOURCE and QUALIFIER

displays the 4-character identifier of the transaction fields depends on the resource type, as shown in
associated with the UOW. If the UOW is shunted, it is Table 3.
the identifier of the transaction associated with the UOW
before it was shunted. Table 3. Data displayed in RESOURCE and QUALIFIER
Type Type Resource Qualifier
displays the type of resource being enqueued upon. The DATASET Dataset name Record identifier
values are:
EXECENQ EXEC enqueue None
Dataset argument
The resource is a record in a VSAM data set (or a ADDREXECENQ Address of EXEC None
CICS-maintained data table). RESOURCE enqueue
contains the name of the data set and QUALIFIER argument
contains the record identifier. FILE File name Record identifier
File The resource is a record in either a BDAM file or a TDQ TD queue name FROMQ or TOQ
user-maintained data table. RESOURCE contains
TSQ TS queue name None
the name of the file and QUALIFIER contains the
record identifier.
Uow(value)
When the file is a BDAM file then the record displays the 16-character local identifier of the
identifier is prefixed by the BDAM block identifier. associated unit of work.

CEMT INQUIRE UOWLINK
CEMT INQUIRE UOWLINK Sample screen
Function: Retrieve information about connections involved

in units of work. à I UOWL
ð
Uowl(ð184ððð9) Uow(AC142A977E6F32ð4) Con Lin(IYLX1 )
Description: INQUIRE UOWLINK returns information Coo Appc War Sys(ISC1) Net(..GBIBMIYA.IYCWTC13..p...
Uowl(ð1C4ððð6) Uow(AC142A977E6F32ð4) Con Lin(IYLX3 )
about a connection involved in a unit of work. The connection Sub Irc War Sys(MRO3) Net(..GBIBMIYA.IYCWTC13..p...
can be to a remote system, or to a task-related user exit. If it

is to a remote system, INQUIRE UOWLINK displays the Figure 135. CEMT INQUIRE UOWLINK screen
netname of the connection, its sysid, and whether it is the
coordinator or subordinate. If it is to a task-related user exit, Note: There are blank fields on the screen where a value
INQUIRE UOWLINK displays the exit’s entry name and does not apply or is ‘negative’; that is, the value
qualifier. begins with ‘No’. To modify these fields, locate them
Input: Press the Clear key to clear the screen. There are the expanded format), and overtype with input valid
two ways of commencing this transaction: for that field. You may find it more convenient to use
Type CEMT INQUIRE UOWLINK (the minimum abbreviation the expanded format when setting one of these
is CEMT I UOWL). You get a display that lists all the values, (negating is easier because you are
current UOW-links. overtyping a displayed field with its negative causing
Type CEMT INQUIRE UOWLINK (CEMT I UOWL) followed by
as many of the other attributes as are necessary to limit If you place the cursor against a specific entry in the list and
the range of information that you require. So, for press ENTER, CICS displays an expanded format as shown
example, if you enter cemt i uowl rmi, the resulting in Figure 136.
display will show you details only of UOW-links to
external resource managers.
à I UOWL
ð
┌─ALl─────┐ Uowlink(ð184ððð9)
Uow(AC142A977E6F32ð4)
55──CEMT Inquire UOWLink──┼─────────┼──────────5 Type(Connection)
Link(IYLX1)
└─(value)─┘ Action( )
Role(Coordinator)
Protocol( )
5──┬────────────┬──┬────────────┬──────────────5 Resyncstatus( )
└─UOw(value)─┘ ├─CONnection─┤ Sysid( )
Rmiqfy( )
└─RMI────────┘ Netuowid( )
| Urid
5──┬─────────────┬──┬─────────────┬────────────5
└─LInk(value)─┘ ├─COOrdinator─┤
├─SUbordinate─┤ Figure 136. The expanded display of an individual entry
└─UNKnown─────┘
5──┬───────────┬──┬─────────────┬──────────────5 Displayed fields
├─Irc───────┤ ├─COLdstart───┤
├─APpc──────┤ ├─STarting────┤ LInk(value)
├─LU61──────┤ ├─Warmstart───┤ displays, for a TYPE value of CONNECTION, the
├─NOtapplic─┤ ├─UNAvailable─┤ 8-character netname of the remote system. For a TYPE
| └─Rrms──────┘ ├─UNConnected─┤ value of RMI, LINK displays the entry name of the
└─NOtapplic───┘
task-related user exit. For a TYPE value of CFTABLE,
5──┬──────────────┬──┬───────────────┬─────────5 LINK displays the 8–character name of the coupling
└─SYsid(value)─┘ └─RMIQfy(value)─┘ facility data table pool.
5──┬─────────────────┬──5%
└─NEtuowid(value)─┘ NEtuowid(value)
displays a 27-character string containing the
network-wide LU6.2 name for the UOW.
(value)
is an 8-byte token identifying the UOW-link for which
You can use PF2 on the expanded panel to see
data is to be returned.
ALl
Protocol
is the default.
displays the communication protocol used by the
connection. The values are:
Irc Inter-Region Communication. This is an MRO

connection.

CEMT INQUIRE UOWLINK
APpc COOrdinator
Advanced Program to Program Communication. This connection is to the syncpoint coordinator for
the UOW.
LU61
LUTYPE 6.1. SUbordinate
This connection is to a syncpoint subordinate for
| Rrms
the UOW.
| indicates that the UOW is coordinated by
| RRS/MVS. UNKnown
The syncpoint role of this connection cannot be
REsyncstatus
determined.
displays the resynchronization status of the connection.
The values are: SYsid(value)
displays the 4-character sysid of the connection. If the
COLd
connection has been discarded, or the connection-type
The connection has been cold started by the
| is RMI, or the PROTOCOL field is showing RRMS,
partner system. The partner can no longer
SYSID displays blanks.
coordinate any in-doubts for this system; nor can
this system pass to the partner any decisions Type
remembered for it. displays the type of connection. The values are:
STarting CFTable
The connection is being acquired, but the A connection to a CFDT server.
exchange lognames process has not yet
CONnection
completed.
A connection defined by a CONNECTION
Ok The connection is operating normally. If there has resource definition.
been a failure of the partner system, the partner
RMI A connection to an external resource manager
has been restarted and the connection able to
using the resource manager interface (RMI).
resynchronize the associated UOW.
UNAvailable UOWLink(value)
The connection is not currently acquired. indicates that this panel relates to an inquiry about a
UOW-link and displays the 8-character UOW-link
UNConnected
identifier.
There is no associated connection.
UOw(value)
RMIQfy(value)
displays the 16-character local identifier of the
displays, for a connection type of RMI, the 8-character
associated unit of work.
entry qualifier of the task-related user exit. For a
connection type of CONNECTION, RMIQFY displays | URid(value)
blanks. | If the PROTOCOL field displays RRMS, this field
| contains the hexadecimal representation of the RRMS
Role
| unit of recovery identifier. For other values of the
displays the role of the connection. The values are:
| PROTOCOL field, URID displays blanks.

CEMT INQUIRE VTAM
CEMT INQUIRE VTAM Deregistered

CICS was registered as a member of the generic
Function: Inquire on the state of the connection between resource named by the GRNAME and has
CICS and VTAM. deregistered successfully.
Unregistered
Description: INQUIRE VTAM inquires on the state of the A generic resource name (GRNAME) was
connection between CICS and VTAM, and also on the specified, but CICS has not made any attempt to
generic resource name (GRNAME) and the persistent register.
session delay interval (PSDI).
Unavailable
Input: Press the Clear key and type CEMT INQUIRE VTAM A generic resource name (GRNAME) was
(the minimum abbreviation is CEMT I V). You will get a specified, but the version of VTAM that CICS is
display screen, a sample of which is shown below. connected to does not support generic resources.
To change various attributes, you can: If CICS makes an unsuccessful attempt to register, the
status is shown as UNREGISTERED, and the words
REGISTER ERROR appear alongside.
display” on page 47). If CICS makes as unsuccessful attempt to deregister,
the status is shown as REGISTERED, and the words
Use the CEMT SET VTAM command.
DEREGISTER ERROR appear alongside.
Sample screen Openstatus
displays the status of the connection between CICS and
VTAM. The values are:
à IN VT
ð
STATUS: RESULTS - OVERTYPE TO MODIFY Open
Vta Ope Psd( ðððððð )
There is a connection between CICS and VTAM.
Closed
Figure 137. CEMT INQUIRE VTAM screen
The connection between CICS and VTAM has
If you place the cursor against the result and press ENTER, terminated.
different value, or with:
à IN VT
ð Immclose
Vtam
The connection between CICS and VTAM
Openstatus( Open )
Psdinterval( ðððððð ) is in the process of closing following an
Grstatus()
Grname() EXEC CICS SET VTAM IMMCLOSE or
CEMT SET VTAM IMMCLOSE command.
Figure 138. The expanded display Forceclose
The connection between CICS and VTAM
is in the process of closing following an
55──CEMT Inquire Vtam──5% EXEC CICS SET VTAM FORCECLOSE or
CEMT SET VTAM FORCECLOSE
command.
Displayed fields
Grname(value) Psdinterval(value)
displays the 8-character generic resource name under displays the persistent session delay interval, expressed
which this CICS region is registered to VTAM. in the form hhmmss. It specifies if and for how long
sessions are held in recovery-pending state after CICS
Grstatus fails.
displays the status of generic resource registration. The
values are:
different value.
Registered The permitted range is 000000 to 235959 inclusive.
CICS registered successfully as a member of the
VTAM generic resource named by the GRNAME 000000
option. If CICS fails, sessions are terminated.

CEMT INQUIRE WEB
Hhmmss | CEMT INQUIRE WEB

If CICS fails, sessions are held in
recovery-pending state by VTAM for up to the | Function: Retrieve information about CICS Web support.
interval specified.
| Description: INQUIRE WEB returns information about the
Vtam
| state of CICS Web support.
indicates that this panel relates to a VTAM inquiry.
| Input: Press the Clear key and type CEMT INQUIRE WEB (the
| minimum abbreviation is CEMT I W). You will get a display
| screen, a sample of which is shown below.
| To change various attributes, you can:

| Overtype your changes on the INQUIRE screen after
| display” on page 47).
| Use the CEMT SET WEB command.
| Sample screen
|
| à IN W
ð
| Web Gar( ððð6ð ) Tim( ðððð5 ) Loc
| Figure 139. CEMT INQUIRE WEB screen
| If you place the cursor against the result and press ENTER,
| CICS displays an expanded format as shown in Figure 138
| on page 153.
|
| à I WEB
ð
| Web
| Garbageint( ððð6ð )
| Timeoutint( ðððð5 )
| Figure 140. The expanded display

|
| 55──INQUIRE WEB───┬────────────┬───────────────5
| └─Garbageint─┘
| 5──(data-value)───┬────────────┬───────────────5
| └─Timeoutint─┘
| (1) ─────────────────────────────5%
5──(data-value)──
| Note:
| 1 Conditions: INVREQ, NOTAUTH
| Displayed fields
| GARBAGEINT
| is the interval at which the Web garbage collection task
| runs to clean up Web 3270 state data for which the
| terminal timeout interval has expired.
| TIMEOUTINT
| is the period of time after which inactive Web 3270
| sessions are eligible for garbage collection.

CEMT PERFORM commands CEMT PERFORM DELETSHIPPED
CEMT PERFORM commands CEMT PERFORM DELETSHIPPED
The CEMT PERFORM commands are not concerned with Function: Cause the CICS timeout delete mechanism to
resource status. They are used to: be invoked immediately.
Cause the CICS timeout delete mechanism to be Description: The CICS timeout delete mechanism
invoked immediately (PERFORM DELETSHIPPED) removes any shipped terminal definitions that have not been
Dump and continue processing (PERFORM DUMP or used for longer than the time specified on the DSHIPIDL
PERFORM SNAP) system initialization parameter, or on a subsequent SET
DELETSHIPPED IDLE command. The interval between
| End an affinity owned by CICS (PERFORM scheduled invocations of the mechanism is specified on the
| ENDAFFINITY) DSHIPINT system initialization parameter, or on a
Reset the date and time of day (PERFORM RESET) subsequent SET DELETSHIPPED INTERVAL command.
Rebuild the RACF resource profile (PERFORM PERFORM DELETSHIPPED invokes timeout delete
SECURITY REBUILD) immediately.
Shut down the CICS region (PERFORM SHUTDOWN)
Notes:
Request statistics to be recorded (PERFORM
STATISTICS RECORD). 1. Shipped definitions are not deleted if there is an
automatic initiate descriptor (AID) associated with the
Descriptions of the CEMT PERFORM commands follow in terminal.
alphabetic order. The operands for each of the commands 2. Issuing a PERFORM DELETSHIPPED command does
are also presented in alphabetic order. not reset the start of the time interval until the next
invocation of the timeout delete mechanism. In other
words, causing the timeout delete mechanism to be
invoked immediately does not affect the time remaining
until the next scheduled invocation.
Syntax
55──CEMT Perform DEletshipped──5%

CEMT PERFORM DUMP|SNAP CEMT PERFORM ENDAFFINITY
CEMT PERFORM DUMP|SNAP CEMT PERFORM ENDAFFINITY

Function: Obtain a CICS system dump. Function: End an affinity owned by CICS.
Description: To get a CICS system to dump and continue Description: Where CICS is a member of a VTAM
processing, you can use either the CEMT PERFORM DUMP generic resource group, PERFORM ENDAFFINITY instructs
command or the CEMT PERFORM SNAP command. Both VTAM to end an affinity owned by CICS, whether or not the
commands produce a “snapshot” of the CICS system. connection has been deleted. If the connection has not been
deleted, it must be out of service and have no recovery
The use of CEMT PERFORM DUMP or CEMT PERFORM information outstanding—that is, its RECOVSTATUS (as
SNAP prevents all other tasks from running. Consequently, displayed by CEMT INQUIRE/SET CONNECTION) must be
terminal operators may experience delays in response. NORECOVDATA.
Syntax Generic resources and affinities are described in the CICS

Intercommunication Guide.
55──CEMT Perform──┬─DUmp─┬──┬──────────────┬──5% Syntax

└─SNap─┘ └─Title(value)─┘
55──CEMT Perform Endaffinity──NETName(value)───5

Options
5──┬──────────────┬──5%
DUmp └─NETId(value)─┘
specifies that a system dump is to be produced.
SNap Options
specifies that CICS is to issue the MVS SDUMP macro
to produce an SDUMP (system dump) of the CICS NETId(value)
region. specifies the 8-character name by which the network
containing the connected LU is known to VTAM.
Title(value)
If you do not specify a NETID, CICS takes the value
specifies a title of up to 32 characters; it is added at the
from the installed connection, if it exists. If you do not
beginning of the dump. If your title includes spaces, you
specify a NETID and the connection does not exist, the
must enclose the whole title within single quotation
command fails.
marks (' ').
NETName(value)
specifies the 8-character APPLID of the connected LU. If
the connected LU is a member of a generic resource,
you must specify its member name, not the generic
resource name.
Note: There is no facility in VTAM for inquiring on affinities,

so CICS has no certain knowledge that an affinity
exists for a given connection. Whenever there is a
possibility that an affinity has been created that you
must end explicitly, CICS issues message
DFHZC0177. This message gives the NETNAME and
NETID to be passed to VTAM.
If a request to end an affinity is rejected by VTAM

because no such affinity exists, CICS issues
message DFHZC0181. This may mean either that
you entered the NETNAME or NETID incorrectly, or
that you (or CICS) was wrong in supposing that an
affinity existed.

CEMT PERFORM RESET CEMT PERFORM SECURITY
CEMT PERFORM RESET CEMT PERFORM SECURITY

Function: Synchronize the CICS date and time-of-day with Function: Rebuild the in-store RACF resource profiles.
the system date and time-of-day. The RACF resource profiles are rebuilt by reissuing the
RACLIST macro for the active class names.
This command should be executed following a change to the
system date or to the time-of-day. Syntax
For example, when setting clocks forward or back an hour to
adjust for Summer and Winter time, use this command to 55──CEMT Perform SEcurity───┬─────────┬───5%
ensure that CICS immediately updates the correct local time. └─Rebuild─┘
CICS generally obtains and stores the local time at specific

times of day only (for example, at start up, and midnight). If the external security manager is RACF 2.1 or an equivalent
Thus you should execute this command whenever you product, the PERFORM SECURITY command is not required
change the system date or time-of-day while CICS is to refresh the classes used for resource checks. A message
running. Note that to obtain the time, CICS issues an MVS of NOT REQUIRED is displayed and no action is taken.
STCK macro and modifies this by the local time difference, if
any. Whenever an application program issues an EXEC Options
CICS ASKTIME command, CICS updates the EIBTIME field
Rebuild
in the exec interface block, always with the local time. To
is an optional keyword. It does not alter the action of the
ensure that your applications are receiving the correct time,
transaction.
use CEMT PERFORM REST whenever you alter the MVS
time.
Syntax
55──CEMT Perform Reset──5%

CEMT PERFORM SHUTDOWN
CEMT PERFORM SHUTDOWN Takeover

specifies that this CICS region should be closed down,
Function: Shut down the CICS region. The shutdown can and the alternate CICS region is to take over. This is
be either controlled or immediate. valid only if the XRF=YES system initialization parameter
was specified for CICS startup.
Syntax
Xlt(value)
specifies the 2-character suffix of a transaction list table
55──CEMT Perform SHUTdown──┬────────────┬──────5 (XLT) to be used for the shutdown.
└─Xlt(value)─┘ Transactions listed in the specified XLT can be initiated
5──┬────────────┬──┬───────────────┬───────────5 after the SHUTDOWN request, and before the system
└─Plt(value)─┘ ├─Sdtran(value)─┤ quiesces. The default XLT should contain an entry for
└─NOSdtran──────┘
the master terminal transaction. This ensures that you
5──┬──────────────────────────┬────────────────5 can issue an immediate shutdown if, for example, a task
└─Immediate──┬───────────┬─┘ is found to be suspended after an ordinary
└─NORestart─┘
(nonimmediate) shutdown has been requested.
5───┬──────────┬────┬──────┬───5%
└─Takeover─┘ └─Dump─┘ Table 4 shows the effect of the TAKEOVER and
IMMEDIATE options on the active CICS system.
Options Table 4. Effect of the TAKEOVER and IMMEDIATE options on

Dump the active CICS system
A dynamic storage dump is produced upon completion CEMT PERFORM SHUTDOWN
of the termination process. (normal) TAKEOVER IMMEDIATE
Immediate Tasks finish finish terminate
specifies that the system is shut down immediately, SNA unbind leave leave
terminating all active tasks and SNA sessions. If session
IMMEDIATE is not specified, all tasks are allowed to (XRF)
finish, and SNA sessions are allowed to terminate SNA unbind unbind unbind
normally. session
(non-XRF)
NORestart
specifies that, if the CICS region is registered to VTAM
as a member of a generic resource, it is to be Table 5 shows the effect of the TAKEOVER and
deregistered as part of shutdown. IMMEDIATE options on the alternate CICS system.
NOSdtran Table 5. Effect of the TAKEOVER and IMMEDIATE options on

No shutdown assist transaction is to be run at CICS the alternate CICS system
shutdown.
CEMT PERFORM SHUTDOWN
The default shutdown transaction, if neither SDTRAN nor (normal) TAKEOVER IMMEDIATE
NOSDTRAN are specified, is CESD.
CICS shuts down takes over takes over
Plt(value) alternate
specifies the 2-character suffix of a program list table
(PLT) to be used for the shutdown. For further information on XRF, see the CICS/ESA 3.3 XRF
Guide.
Sdtran
The 4-character identifier of the shutdown assist
transaction

CEMT PERFORM STATISTICS
CEMT PERFORM STATISTICS ALL RESETNOW resets the counters for the collection
of statistics. RESETNOW only works if the ALL operand
Function: Write the statistics for a named resource type is set, that is, ALL RESETNOW.
immediately to the SMF data set, rather than wait for the AUtoinstall
current statistics-gathering interval to expire. The recording Autoinstall statistics are to be written immediately to the
is made irrespective of the ON or OFF setting of statistics. SMF data set.
See also page “CEMT INQUIRE STATISTICS” on page 111
and page “CEMT SET STATISTICS” on page 194 for a Connection
description of the CEMT INQUIRE and SET STATISTICS Connection statistics are to be written immediately to the
commands. SMF data set.
Description: You can request either statistics for all DB2

resources (ALL), or statistics for individual resources in CICS DB2 statistics are to be written immediately to the
various combinations by selecting one or more keywords SMF data set.
from the list. DIspatcher
Dispatcher statistics are to be written immediately to the
The message ‘STATS MISSING’ appears when the resource
SMF data set.
type is either not functioning or not available. As much data
is recorded as possible. Enqueue
Enqueue statistics are to be written immediately to the
See the CICS Operations and Utilities Guide for information SMF data set.
about printing statistics using the CICS-supplied utility
program DFHSTUP, and for information about the reports FEpi
produced by DFHSTUP. FEPI statistics are to be written immediately to the SMF
data set.
Syntax
FIle
File control statistics are to be written immediately to the
55──CEMT Perform STatistics───┬────────┬───────5 SMF data set.
└─RECORd─┘
Journalname
┌──
─────────────────────┐ CICS journal statistics are to be written immediately to
5───6┬─ALl──┬──────────┬─┬┴──5%
│ └─RESetnow─┘ │ the SMF data set.
├─AUtoinstall───────┤
├─Connection────────┤
├─DB2───────────────┤ Note: The JOURNALNUM resource name is obsolete,
├─DIspatcher────────┤ and replaced by the JOURNALNAME resource
├─Enqueue───────────┤ name.
├─FEpi──────────────┤
├─FIle──────────────┤ Lsrpool
├─Journalname───────┤ LSRPOOL statistics are to be written immediately to the
├─Lsrpool───────────┤ SMF data set.
├─Monitor───────────┤
├─PROGAuto──────────┤ Monitor
├─PROGRam───────────┤
├─RECOVery──────────┤ Monitoring statistics are to be written immediately to the
├─STAts─────────────┤ SMF data set.
├─STOrage───────────┤
├─STReamname────────┤ PROGAuto
├─SYsdump───────────┤ Autoinstalled program statistics are to be written
├─TAblemgr──────────┤ immediately to the SMF data set.
├─TCLass────────────┤
| ├─TCPipservice──────┤ PROGRam
├─TDqueue───────────┤ Program statistics are to be written immediately to the
├─TErminal──────────┤
├─TRAnsaction───────┤ SMF data set.
├─TRDump────────────┤
├─TSqueue───────────┤ RECORd
└─Vtam──────────────┘ is an optional keyword. It does not alter the action of the
transaction.
RECOVery
Options
Recovery statistics are to be written immediately to the
ALl SMF data set.
Statistics for all resources are to be written immediately
to the SMF data set.

CEMT SET COMMANDS
RESetnow
The statistics counters are to be reset. CEMT SET commands
STAts The SET command changes the status of one or more
Statistics domain statistics are to be written immediately named instances of a resource (such as a terminal), a
to the SMF data set. particular subgroup of resources (such as a class of
terminals), or all resources of a particular type (such as all
STOrage terminals).
Storage manager statistics are to be written immediately
to the SMF data set. The SET command makes the changes that you specify, and
displays the new status of the resources. No changes are
STReamname
made if there are syntax errors in the SET command.
Log stream statistics are to be written immediately to the
SMF data set. To change the attributes of a resource, enter SET (or a
SYsdump suitable abbreviation) on the command line. The keywords
System dump statistics are to be written immediately to you can use with CEMT SET are described in the rest of this
the SMF data set. section.
TAblemgr On every SET command, an argument, a generic argument,

Table manager statistics are to be written immediately to or ALL must be specified. For example:
the SMF data set. SET TERMINAL(TRM1) INSERVICE
| TCLass sets terminal TRM1 in service.
Transaction class statistics are to be written immediately SET TERMINAL(TRM1 TRM2 TRM3) INSERVICE
or
| TCPipservice
SET TERMINAL(TRM1,TRM2,TRM3) INSERVICE
| TCP/IP service statistics are to be written immediately to
| the SMF data set. sets terminals TRM1, TRM2, and TRM3 in service.
SET TERMINAL(TRM\) INSERVICE
TDqueue
Transient data statistics are to be written immediately to sets all terminals with identifiers starting with TRM in service.
the SMF data set. SET TERMINAL ALL INSERVICE
TErminal sets all terminals in service.
Terminal statistics are to be written immediately to the
SMF data set. However,
SET TERMINAL INSERVICE
TRAnsaction
Transaction statistics are to be written immediately to the produces an error.
SMF data set.
TRDump
Transaction dump statistics are to be written immediately
TSqueue
Temporary storage statistics are to be written
immediately to the SMF data set.
Vtam
VTAM statistics are to be written immediately to the SMF
data set.

CEMT SET AUTOINSTALL
CEMT SET AUTOINSTALL Options

| Consoles(value)
Function: Change autoinstall values.
| specifies whether CICS is to autoinstall an MVS console
| device when it receives an MVS MODIFY command
Description: The CEMT SET AUTOINSTALL command
| from a console that is not defined. The CVDA values
| allows you to change some of the values that control the
| are:
| automatic installation (autoinstall) of VTAM terminals and
| MVS consoles. For information about autoinstall, see the | Progauto
CICS Resource Definition Guide. | MVS consoles are to be autoinstalled, and CICS is
| to call the user autoinstall control program to
Syntax: Press the Clear key to clear the screen. There are | obtain the termid and other user-specified
two ways of commencing this transaction: | information.
Type CEMT SET AUTOINSTALL (the minimum abbreviation | Fullauto
is CEMT S AUTO). You get a display that lists the current | MVS consoles are to be autoinstalled by CICS
status, similar to that obtained by CEMT INQUIRE | automatically, without calling the user autoinstall
AUTOINSTALL. You can then tab to the highlighted or | control program. CICS assigns the termid for the
blank fields and overtype them with the required values. | console automatically, using the ¬ (logical not)
Type CEMT SET AUTOINSTALL (CEMT S AUTO) followed by | symbol as the first character.
one or more attribute settings that you wish to change. | Noauto
For example, cemt s aut m(newvalue) p(newname) | Autoinstall for consoles is not allowed.
resets the values for maximum number of requests for a
new program. Maxreqs(value)
specifies the largest number of autoinstall requests that
Typing ? at the beginning of either the first or second line are allowed to queue at one time, in the range 0–999.
gives a syntax prompt. Resetting the values takes effect
You can prevent more terminals from logging on through
immediately.
autoinstall by setting this value to 0. This allows
autoinstalled entries for terminals currently logged on to
55──CEMT Set AUToinstall───────────────────────5 be deleted by the autoinstall program when they log off.
5──┬─────────────────┬──┬────────────────┬─────5 Program(value)
| └─Consoles(value)─┘ └─Maxreqs(value)─┘ specifies the name of the user program that is to control
5──┬────────────────┬──5% the autoinstall process. A default program is supplied.
└─Program(value)─┘

CEMT SET AUXTRACE
CEMT SET AUXTRACE Options

All
Function: Change auxiliary tracing options.
Specifies that automatic switching between the two
auxiliary trace data sets is to occur as necessary until
Description: For more information about traces, see the
the end of this CICS session, without the need for
CICS Problem Determination Guide. See also the description
operator intervention.
of the CETR transaction, Chapter 16, “CETR—trace control”
on page 221. NExt
Automatic switching of the auxiliary trace data set is to
Syntax: Press the Clear key to clear the screen. There are occur when the current trace data set is full, but not
two ways of commencing this transaction: subsequently.
Type CEMT SET AUXTRACE (the minimum abbreviation is
NOswitch
CEMT S AUX). You get a display that lists the current
Switching between the auxiliary trace data sets is not to
status, similar to that obtained by CEMT INQUIRE
occur without operator intervention.
AUXTRACE. You can then tab to the highlighted or
blank fields and overtype them with the required values. Pause
Type CEMT SET AUXTRACE (CEMT S AUX) followed by one Auxiliary tracing is to stop, but the data set is to remain
or more attribute settings that you wish to change. For open. A subsequent START request causes trace
example, cemt s aux sto a stops auxiliary tracing and entries to be written immediately following those that
causes automatic switching to occur as necessary. were written before the PAUSE request.
STArt
Typing ? at the beginning of either the first or second line
CICS is to start auxiliary tracing and open the auxiliary
trace data set if it is currently closed.
immediately.
STOp
CICS is to stop auxiliary tracing and close the auxiliary
55──CEMT Set AUXtrace──┬───────┬───────────────5 trace data set. A subsequent START request causes
├─STArt─┤
├─Pause─┤ new trace entries to be written at the start of the data
└─STOp──┘ set, thereby overwriting the trace entries that were
5──┬──────────┬───┬────────┬───5% written before the STOP request.
├─NOswitch─┤ └─SWitch─┘ SWitch
├─NExt─────┤
└─All──────┘ specifies that an immediate switch from the current
auxiliary trace data set is to be made to the alternate
trace data set.

CEMT SET CONNECTION
CEMT SET CONNECTION ACquired (appc only)

specifies whether CICS is to acquire a session with the
Function: Change the status of connections linked to logical unit represented by the CONNECTION name. To
specific terminals. get more detailed information about the availability status
of the connection elements, use the CEMT INQUIRE
Description: When a connection has been defined as MODENAME command. A connection cannot be both
INDIRECT, no information is given unless the direct ACQUIRED and OUTSERVICE.
connection to which it refers is installed.
ALl
If you want to install a new connection definition when one is Any changes you request are made to all resources of
already installed, you must set the connection OUTSERVICE the specified type that you are authorized to access.
and, if it is VTAM-connected, release it before using the Backout (APPC parallel-session, CICS-to-CICS MRO, and
CEDA INSTALL commands for your new definition. See the LU61 only)
CICS Resource Definition Guide for further information about All UOWs shunted due to the failure of this connection
connections. are to be backed out. The normal resynchronization
process is to be partially overridden: decisions are taken
Syntax: Press the Clear key to clear the screen. There are for any units of work that are in-doubt due to a failure of
two ways of commencing this transaction: the connection; but the decisions are recorded and any
Type CEMT SET CONNECTION (the minimum abbreviation is data inconsistencies are reported when the connection is
CEMT S C) followed by one or more connection identifiers next acquired.
or ALL. You get a display that lists the current status,
CAncel
similar to that obtained by CEMT INQUIRE
Automatic initiate descriptors (AIDs) queuing for the
CONNECTION. You can then tab to the highlighted or
specified connection are to be canceled.
AIDs representing scheduled and allocated requests
Type CEMT SET CONNECTION (CEMT S C) followed by one
waiting in the local CICS system for the specified
or more connection identifiers or ALL, followed in turn by
connection are canceled. However, TD AIDs with an
one or more attribute settings that you wish to change.
associated triggered task already started are not be
For example, cemt s c al i resets the values for all
canceled. In addition, the following CICS system AIDs
connections to make them available for use (inservice).
are not purged unless FCANCEL is specified.
gives a syntax prompt. Resetting the values takes effect Table 6. System AIDs requiring FCANCEL to remove them
immediately. Description Tranid
Remote delete AIDs
55──CEMT Set Connection──┬─(value)─┬───────────5 Remote scheduler AIDs CRSR
└─ALl─────┘
LU6.2 service manager 1 AIDs CLS1
5───┬────────────┬───┬────────────┬────────────5
└─NOTpending─┘ ├─INService──┤ LU6.2 service manager 3 AIDs CLS3
└─OUtservice─┘ Remote scheduler PURGE AIDs CRSQ
5──┬──────────┬──┬────────────┬────────────────5 Resource manager resync AIDs CRSY
├─ACquired─┤ ├─PUrge──────┤
└─RELeased─┘ ├─FORCEPurge─┤ Autoinstalled terminal delete AIDs CATD
├─CAncel─────┤
Autoinstalled terminal restart AIDs CATR
└─FCancel────┘
5──┬──────────┬──┬─────────────┬───────────────5
├─COmmit───┤ └─ENdaffinity─┘ When a canceled SCHEDULE request is found to have
├─Backout──┤ a precursor in a remote CICS system; that is, the AID
├─FORCEUow─┤ was originally scheduled in a remote system, the remote
└─RESync───┘ AID is canceled asynchronously.
5──┬─────────────┬──5%
Message DFHTF0100 is written to CSMT to indicate
└─NORecovdata─┘
how many AIDs have been deleted for the connection
and how many remain.
Options An ‘AIDS CANCELED’ message appears on the CEMT
panel whenever AIDs are deleted using the CANCEL
(value)
option of the CEMT SET CONNECTION command.
One or more names (1–4 characters) defined for an
interregion communication (IRC) or an intersystem COmmit (APPC parallel-session, CICS-to-CICS MRO, and
communication (ISC) connection. LU61 only)

CEMT SET CONNECTION
lead to unpredictable results and should be used only in

All UOWs shunted due to the failure of this connection exceptional circumstances.
are to be committed. The normal resynchronization
In some extreme cases (for example, if an error occurs
process is to be partially overridden: decisions are taken
during backout processing), CICS might terminate
for any units of work that are in-doubt due to a failure of
abnormally.
the connection; but the decisions are recorded and any
data inconsistencies are reported when the connection is FORCEPURGE replaces PURGE FORCE which is
next acquired. retained only for compatibility purposes. You should use
FORCEPURGE in new applications.
ENdaffinity (appc and lu6.1 only)
specifies, where CICS is a member of a VTAM generic FORCEUow (APPC parallel-session, CICS-to-CICS MRO,
resource group, that VTAM is to end an affinity owned and LU61 only)
by CICS. This option is valid only for APPC and LU6.1 All UOWs shunted due to the failure of this connection
connections. The connection must be out of service and, are to be forced to back out or commit, as specified in
for APPC, in NORECOVDATA state. the ACTION option of the TRANSACTION definition. The
normal resynchronization process is to be partially
Notes:
overridden: decisions are taken for any units of work that
1. There is no facility in VTAM for inquiring on are in-doubt due to a failure of the connection; but the
affinities, so CICS has no certain knowledge that an decisions are recorded and any data inconsistencies are
affinity exists for a given connection. Whenever reported when the connection is next acquired.
there is a possibility that an affinity has been
INService
created that you must end explicitly, CICS issues
The system is in service; that is, it is available for use.
message DFHZC0177. This message gives the
NETNAME of the suspect connection. For an MRO connection, all sessions are placed in
service and the following occurs:
2. If a request to end an affinity is rejected by VTAM
because no such affinity exists, CICS issues If both the issuing system and system “sysid” have
message DFHZC0181. IRC open, and the issuing system has status
INSERVICE within system “sysid”, connections are
3. A response of 'NETID 0 USE PRFRM' means that
established and made available between the two
you cannot use SET CONNECTION to end the
systems.
affinity because the value of NETID in the installed
connection is 0. (NETID is the name by which the Otherwise, the status of the system (and the status
network containing the connected LU is known to of the underlying sessions) is set INSERVICE, so
VTAM.) To end the affinity, you must use the that when both systems have IRC open and are
PERFORM ENDAFFINITY command, on which you INSERVICE with respect to each other, connections
must specify the correct NETID. are established. Note that INQUIRE indicates that
systems (and their underlying sessions) are
This response can also result from repeatedly hitting
INSERVICE even though no connections can be
the ENTER key after the affinity has been ended.
used.
4. Generic resources and affinities are described in the
The status of the underlying sessions for a system
CICS Intercommunication Guide.
is always the same as that for the system itself.
FCancel
For an ISC system, the following occurs:
All AIDs, including system AIDs, queuing for the
specified connection are to be canceled. See Table 6 on LU6.1 system (that is, links to “sysid” are through
page 163 for a list of those system AIDS that require intersystem communication)—all underlying
FCANCEL to remove them. This can lead to sessions are placed in service.
unpredictable results and should be used only in
APPC system—causes the SNASVCMG sessions to
exceptional circumstances.
be placed in service thereby enabling the
Note: FCANCEL does not remove transient data AIDs connection subsequently to be established.
with an associated triggered task. These aids
may be removed by purging the associated task. NORecovdata (appc only)
specifies that the normal resynchronization process is to
An ‘AIDS CANCELED’ message appears on the CEMT
be overridden. NORECOVDATA forces in-doubt units of
panel whenever AIDs are deleted using the FCANCEL
work (according to the transaction definitions), targets
option of the CEMT SET CONNECTION command.
any resyncs that were outstanding for the connection,
FORCEPurge (vtam only) and erases the logname previously received from the
All transactions running on sessions on the connected partner system. The state of the connection is reset.
system are immediately terminated abnormally. This can Note: You should use SET CONNECTION
NORECOVDATA only in exceptional

CEMT SET CONNECTION
circumstances. It erases recovery information Notes:

and may compromise data integrity for units of
1. If you specify NOTPENDING you cannot specify
work that have updated resources on remote
COMMIT, BACKOUT, FORCEUOW, RESYNC, or
systems.
NORECOVDATA. For advice on which option to
Examples of circumstances in which you might need to use, see page 166.
use it are:
2. NOTPENDING has no effect on MRO connections
You need to discard a connection, or issue a SET to pre-CICS Transaction Server for OS/390
CONNECTION ENDAFFINITY command, and it is systems. However, the cold start of a pre-CICS
not possible for the quiesce protocols with the Transaction Server for OS/390 MRO partner causes
partner system to be completed. (Neither action is the SET CONNECTION NOTPENDING function to
possible for an APPC connection if recovery data is be performed automatically, session by session.
outstanding.)
The exchange lognames function and the
An operational or logic error results in a logname resynchronization function are described in the CICS
mismatch for the connection. The connection state Intercommunication Guide and the Systems Network
must be reset to allow the exchange lognames Architecture—LU6.2 Reference: Peer Protocols manual.
process to complete.
OUtservice
Note: If you specify NORECOVDATA you cannot The system is out of service; that is, it is not available
specify COMMIT, BACKOUT, FORCEUOW, for use.
RESYNC, or NOTPENDING.
For an MRO connection, all sessions are placed out of
NOTpending (appc and cics-to-cics mro only) service (immediately if PURGE is specified, or when
specifies, for either of the following kinds of connection, tasks have terminated if it is not) and the following
that the normal resynchronization process is to be occurs:
overridden:
If the connection is currently ACQUIRED, the
A connection to a CICS Transaction Server for sessions are broken (quiesced). The connection
OS/390 partner that has performed an initial start cannot be used until it is once again placed
INSERVICE.
A connection to a pre-CICS Transaction Server for
OS/390 partner that has performed a cold start. If the connection is currently RELEASED, the status
of the connection is set OUTSERVICE and it cannot
NOTPENDING forces all in-doubt units of work be used until it is INSERVICE again.
(according to the transaction definition) that were created
The status of the underlying sessions for a
by the connection before the initial (or cold) start of the
connection is always the same as that for the
partner. It also forgets any resyncs (waitforget
connection itself.
UOW-links) that are outstanding for the connection, and
created before the initial (or cold) start of the partner. For an ISC system, the following occurs:
The PENDING condition indicates the existence of LU6.1 system—all underlying sessions owned by
recovery information (either shunted UOWs or decisions the system are released and placed out of service:
remembered for the partner) on a connection that has immediately if PURGE or FORCEPURGE is
experienced a lognames mismatch with its partner. For a specified; or when tasks have terminated if neither
CICS Transaction Server for OS/390 partner, a PURGE nor FORCEPURGE is specified.
lognames mismatch indicates that the partner has
If the response to an INQUIRE CONNECTION
performed an initial start. For a pre-CICS Transaction
command shows OUTSERVICE, it does not imply
Server for OS/390 partner, a lognames mismatch
that the connection has been explicitly set as SET
indicates that the partner has performed a cold start. In
OUTSERVICE; in particular circumstances, you
either case, the recovery protocol has been corrupted by
cannot reinstall this connection.
a loss of log data at the partner.
APPC system—this option is valid only if the system
It is not possible to set a connection to NOTPENDING
is released. All sessions owned by the ISC system
state (forcing in-doubt and erasing NOFORGET UOWs)
are then out of service and released.
until this system has made contact with the partner and
received a new logname from it. PUrge (vtam only and irc only)
Decisions for a whole connection can be forgotten, but Transactions running on the connected system are
that does not affect the memory of a decision for any abnormally terminated. Transactions are terminated only
other connection involved in the UOW. if system and data integrity can be maintained. A
transaction is not purged if its definition specifies
SPURGE=NO.

CEMT SET CONNECTION
RELeased (appc only) connection. Before issuing SET CONNECTION

specifies whether CICS is to release a session with the FORCEUOW, you may want to use the SET UOW
logical unit represented by the CONNECTION name. To command to specify commit or backout for each
get more detailed information about the availability status in-doubt unit of work explicitly, rather than letting it
of the connection elements, use the CEMT INQUIRE default, Local procedures determine the importance
MODENAME command. of the data and the method of using the INQUIRE
UOW, INQUIRE UOWENQ, and INQUIRE
RESync (mro to CICS Transaction Server for OS/390 and
UOWLINK commands to establish the correct
later systems and appc only) (APPC parallel-session, actions.
CICS-to-CICS MRO, and LU61 only)
Any UOWs shunted due to the failure of this connection 3. You can specify only one of the BACKOUT,
are to be retried (that is, exchange lognames COMMIT, FORCEUOW, RESYNC, NOTPENDING,
resynchronization for this connection is to be attempted). and NORECOVDATA options. SET CONNECTION
This process should normally be started automatically NORECOVDATA should be used only in exceptional
when a connection is acquired or when a UOW is circumstances.
unshunted. The normal resynchronization process is to 4. To force all in-doubt units of work caused by a
be partially overridden: decisions are taken for any units failure of the connection in the same direction, use
of work that are in-doubt due to a failure of the SET CONNECTION COMMIT or SET
connection; but the decisions are recorded and any data CONNECTION BACKOUT.
inconsistencies are reported when the connection is next
5. The BACKOUT, COMMIT, FORCEUOW, or
acquired.
RESYNC options of SET CONNECTION and SET
Notes: UOW do not clear resync information. If you want to
do this, you must use SET CONNECTION
1. The COMMIT, BACKOUT, FORCEUOW and
NOTPENDING or SET CONNECTION
RESYNC operations are synchronous with setting
NORECOVDATA.
the state of the UOW; that is, an INQUIRE UOW
following SET CONNECTION BACKOUT, COMMIT, 6. You can issue BACKOUT, COMMIT, FORCEUOW,
FORCEUOW, or RESYNC returns the new UOW or RESYNC commands before issuing SET
states. CONNECTION NOTPENDING or SET
CONNECTION NORECOVDATA.
2. Specifying one of these options unshunts all units of
work that have failed due to a failure of the

CEMT SET DB2CONN
CEMT SET DB2CONN

Function: Set attributes of the CICS DB2 connection including the pool and command thread attributes.
Syntax: Press the Clear key to clear the screen. To commence this transaction:
Type CEMT SET DB2CONN (the minimum abbreviation is CEMT S DB2C). You get a display that lists the current status, similar
to that obtained by CEMT INQUIRE DB2CONN. You can then tab to the highlighted or blank fields and overtype them with
the required values.
Type CEMT SET DB2CONN (CEMT S DB2C) followed by one or more attribute settings that you wish to change.
Typing ? at the beginning of either the first or second line gives a syntax prompt. Resetting the values takes effect immediately.
┌──
───────────────────────────┐ ┌─────────────────────────────┐
55──CEMT Set DB2Conn───6┬─────────────────────────┬┴───6┬─────────────────────────┬┴──5%
├─┬─ACCOUNTREC(cvda)─┬────┤ ├─DB2ID(data-area)────────┤
│ ├─UOW──────────────┤ │ ├─MSGQUEUE1(data-area)────┤
│ ├─TASK─────────────┤ │ ├─MSGQUEUE2(data-area)────┤
│ ├─TXID─────────────┤ │ ├─MSGQUEUE3(data-area)────┤
│ └─NONE─────────────┘ │ ├─┬─NONTERMREL(cvda)─┬────┤
├─AUTHID(data-area)───────┤ │ ├─RELEASE──────────┤ │
├─┬─AUTHTYPE(cvda)─┬──────┤ │ └─NORELEASE────────┘ │
│ ├─GROUP──────────┤ │ ├─PLAN(data-area)─────────┤
│ ├─SIGN───────────┤ │ ├─PLANEXITNAME(data-area)─┤
│ ├─TERM───────────┤ │ ├─┬─PRIORITY(cvda)─┬──────┤
│ ├─TX─────────────┤ │ │ ├─HIGH───────────┤ │
│ ├─OPID───────────┤ │ │ ├─EQUAL──────────┤ │
│ └─USERID─────────┘ │ │ └─LOW────────────┘ │
├─COMAUTHID(data-area)────┤ ├─PURGECYCLEM(data-area)──┤
├─┬─COMAUTHTYPE(cvda)─┬───┤ ├─PURGECYCLES(data-area)──┤
│ ├─CGROUP────────────┤ │ ├─SECURITY(REBUILD)───────┤
│ ├─CSIGN─────────────┤ │ ├─SIGNID(data-area)───────┤
│ ├─CTERM─────────────┤ │ ├─┬─STANDBYMODE(cvda)─┬───┤
│ ├─CTX───────────────┤ │ │ ├─NOCONNECT─────────┤ │
│ ├─COPID─────────────┤ │ │ ├─CONNECT───────────┤ │
│ └─CUSERID───────────┘ │ │ └─RECONNECT─────────┘ │
├─COMTHREADLIM(data-area)─┤ ├─STATSQUEUE(data-area)───┤
├─┬─CONNECTERROR(cvda)─┬──┤ ├─TCBLIMIT(data-area)─────┤
│ ├─ABEND──────────────┤ │ ├─THREADLIMIT(data-area)──┤
│ └─SQLCODE────────────┘ │ └─┬─THREADWAIT(cvda)─┬────┘
└─┬─CONNECTST(cvda)───┬───┘ ├─TWAIT────────────┤
├─CONNECTED─────────┤ ├─NOTWAIT──────────┤
├─NOTCONNECTED──────┤ └─N9ð6─────────────┘
└─FORCENOTCONNECTED─┘
Options may be an accounting record produced for each

UOW.
ACcountrec
specifies the minimum amount of DB2 accounting TXID
required for transactions requiring pool threads. The The CICS DB2 attachment facility causes an
specified minimum may be exceeded, as described in accounting record to be produced when the
the following options. CVDA values are: transid using the thread changes.
Because pool threads are typically used by a
UOW
number of different transaction IDs, there is an
The CICS DB2 attachment facility causes an
increased chance that a transaction containing
accounting record to be produced for each UOW,
multiple UOWs will use a different thread for each
assuming that the thread has been released at the
UOW (assuming the thread is released at
end of the UOW.
syncpoint. In this case an accounting record may
TASK be produced for each UOW.
NONE
minimum of one accounting record for each CICS
No accounting records are required for
task to be produced.
transactions using pool threads.
a different thread for each of its UOWs (assuming
accounting record for each thread when the thread

CEMT SET DB2CONN
is terminated. Additionally, authorization changes OPID

cause accounting records to be produced. The operator identification associated with the
userid that is associated with the CICS transaction
AUTHId
is used as the authorization ID (three characters
specifies what id should be used for security checking
padded to eight).
for pool threads. If AUTHID is specified, AUTHType
may not be specified. USERID
AUTHType CICS transaction is used as the authorization ID.
specifies the type of ID that can be used for pool
When the DB2 sample sign-on exit DSN3@SGN
threads. If AUTHType is specified AUTHID may not be
is used with AUTHTYPE(USERID), the exit sends
specified. CVDA values are:
the user ID to DB2 as the primary authorization ID
GROUP and the RACF group ID to DB2 as the secondary
Specifies the 8-character USERID and the ID. When the sample sign-on exit is used, there is
connected group name as the authorization ID. no difference between AUTHTYPE(USERID) and
The following table shows how these two values AUTHTYPE(GROUP).
are interpreted by DB2.
COMAUTHId
IDs passed to DB2 How DB2 interprets values specifies which id should be used for security checking
when using command threads. If COMAUTHid is
(USERID) authorization ID. specified, COMAUTHType may not be specified.
RACF-connected If the RACF list of group options COMAUTHType
group name is not active, DB2 uses the specifies the type of id that can be used for security
connected group name supplied checking when using command threads. If
by the CICS attachment facility COMAUTHType is specified, COMAUTHid may not be
as the secondary DB2
specified. CVDA values are:
of group options is active, DB2 CGROUP
Specifies the 8-character USERID and the
name supplied by the CICS
connected group name as the authorization ID.
appears in the DB2 list of The following table shows how these two values
secondary DB2 authorization are interpreted by DB2.
IDs.
To use the GROUP option the CICS system must CICS sign-on user ID Represents the primary DB2
have SEC=YES specified in the CICS system (USERID) authorization ID.
initialization table (SIT). RACF-connected If the RACF list of group options
If no RACF group ID is available for this USERID, connected group name supplied
an 8-character field of blanks is passed to DB2 as by the CICS attachment facility
the group ID. as the secondary DB2
SIGN
Specifies the SIGNID parameter of the DB2CONN ignores the connected group
should be used as the resource authorization ID. name supplied by the CICS
TERM attachment facility, but the value
Specifies the terminal identification (four appears in the DB2 list of
characters padded to eight) as an authorization ID.
IDs.
An authorization ID cannot be obtained in this
manner if a terminal is not connected with the
To use the CGROUP option the CICS system
transaction.
must have SEC=YES specified in the CICS
If a transaction is started (using a CICS command) system initialization table (SIT).
and has no terminal associated with it,
an 8-character field of blanks is passed to DB2 as
TX Specifies the transaction identification (four the group ID.
characters padded to eight) as the authorization
CSIGN
ID.
Specifies the SIGNID parameter of the DB2CONN
should be used as the resource authorization ID.

CEMT SET DB2CONN
CTERM DB2 subsystem is not active, the response

Specifies the terminal identification (four returned is dependant on the setting of
characters padded to eight) as an authorization ID. STANDBYMODE: If DB2 is not initialized, and
An authorization ID cannot be obtained in this STANDBYMODE(NOCONNECT) is specified on
manner if a terminal is not connected with the the DB2CONN, INVREQ and RESP2=39 is
transaction. returned. If you specify
STANDBYMODE(CONNECT) or
If a transaction is started (using a CICS command)
STANDBYMODE(RECONNECT), NORMAL with
and has no terminal associated with it, the
RESP2=38 is returned indicating that the CICS
COMAUTHTYPE(TERM) should not be used.
DB2 attachment is in standby mode and will
CTX Specifies the transaction identification (four connect to DB2 as soon as it becomes active.
characters padded to eight) as the authorization
NOTCONNECTED
ID.
| CEMT initiates a quiesce stop of the CICS DB2
COPID | connection and implicitly uses the NOWAIT option,
The operator identification associated with the | meaning that control returns immediately to CEMT
userid that is associated with the CICS transaction | before the quiesce is complete.
sign-on facility is used as the authorization ID
FORCENOTCONNECTED
(three characters padded to eight).
FORCENOTCONNECTED force stops the
CUSERID connection by force purging transactions currently
The 8-character userid associated with the CICS using DB2. Control is not returned until the
transaction is used as the authorization ID. connection is stopped.
When the DB2 sample sign-on exit DSN3@SGN
is used with AUTHTYPE(USERID), the exit sends DB2Id
the USERID to DB2 as the primary authorization specifies the name of the DB2 subsystem that the CICS
ID and the RACF group ID to DB2 as the DB2 attachment should connect to. DB2ID can only be
secondary ID. When the sample sign-on exit is changed when CICS is not connected to a DB2 system.
MSGQUEUE1
COMAUTHTYPE(CUSERID) and
specifies the first transient data destination to which
COMAUTHTYPE(CGROUP).
unsolicited messages from the CICS DB2 attachment
are sent.
COMTHREADLim
specifies the current maximum number of command MSGQUEUE2
threads that the CICS DB2 attachment allows active specifies the second transient data destination to which
before requests overflow to the pool. unsolicited messages from the CICS DB2 attachment
are sent.
CONNECTError
returns a value when CICS is not connected to DB2 MSGQUEUE3
because the adapter is in 'standby mode'. The value specifies the third transient data destination to which
shows how this information is to be passed back to an unsolicited messages from the CICS DB2 attachment
application that has issued a SQL request. CVDA values are sent.
are:
NONTERMREL
ABEND specifies whether or not non-terminal transactions
The application is abended with abend code release threads for reuse at intermediate syncpoints.
AEY9. CVDA values are:
SQLCODE RELEASE
The application receives a -923 SQLCODE. non-terminal transactions release threads for
reuse at intermediate syncpoints.
CONNECTst
NORELEASE
sets the status of the CICS DB2 connection; that is, to
non-terminal transactions do not release threads
start or to stop the CICS DB2 connection. CVDA values
for reuse at intermediate syncpoints.
are:
CONNECTED PLAN
This is equivalent to issuing DSNC STRT to start specifies the name of the plan to be used for all threads
the CICS DB2 attachment. If the requested DB2 in the pool. If PLAN is specified, PLANEXITNAME may
subsystem is active, control returns when CICS not be specified.
and DB2 have been connected. If the requested

CEMT SET DB2CONN
PLANExitname TSO SETROP TS RACLIST(xxxxxxxx) REFRESH

specifies the name of the dynamic plan exit to be used for RACF 2.1 or later
for pool threads. If you change the PLAN and
SIgnid
PLANExitname while there are active transactions for
specifies the authorization ID to be used by the CICS
the pool, the next time the transaction releases the
DB2 attachment when signing on to DB2 for pool and
thread, the plan/exit will be determined using the new
DB2ENTRY threads specifying AUTHTYPE(SIGN), and
rules. If PLANExitname is specified, PLAN may not be
command threads specifying COMAUTHTYPE(CSIGN).
specified.
STANndbymode
PRiority
specifies the action to be taken by the CICS DB2
specifies the priority of the pool thread subtasks relative
attachment if DB2 is not active when an attempt is made
to the CICS main task (QR TCB). CVDA values are:
to start the connection from CICS to DB2. CVDA values
HIGH are:
subtasks attain a higher priority than the CICS
NOCONNECT
The CICS DB2 attachment should terminate.
EQUAL
CONNECT
subtasks have equal priority with the CICS main
The CICS DB2 attachment goes into 'standby
task.
mode' to wait for DB2.
LOW
RECONNECT
subtasks have a lower priority than the CICS main
The CICS DB2 attachment goes into 'standby
task.
mode' and waits for DB2. Having connected to
PURGECYCLEM DB2, if DB2 subsequently fails the CICS DB2
specifies in minutes the length of time of the protected attachment reverts again to standby mode and
thread purge cycle. The default is 0,30; that is, 30 subsequently reconnects to DB2 when it comes up
seconds. again.
is released. It is terminated only after two completed STATSqueue
purge cycles, if it has not been reused in the meantime. specifies the transient data destination for CICS DB2
Hence if the purge cycle is set to 30 seconds after it is attachment statistics produced when the CICS DB2
released, a protected thread is purged 30 - 60 seconds attachment is shutdown.
after it is released. An unprotected thread is terminated
TCBLimit
when it is released (at syncpoint or end of task) if there
specifies the maximum number of subtasks that can be
are no other transactions waiting for a thread on that
identified to DB2.
DB2ENTRY.
THREADLimit
PURGECYCLES
specifies the current maximum number of pool threads
specifies in seconds the length of time of the protected
the CICS DB2 attachment allows active before requests
thread purge cycle. The default is 0,30; that is, 30
are made to wait or are rejected according to the
seconds.
THREADWait parameter.
THREADWwait
is released. It is terminated only after two completed
specifies whether or not transactions should wait for a
purge cycles, if it has not been reused in the meantime.
pool thread or be abended if the number of active pool
Hence if the purge cycle is set to 30 seconds after it is
threads reach the THREADlimit number.
released, a protected thread is purged 30 - 60 seconds
after it is released. An unprotected thread is terminated The CICS DB2 attachment issues a unique abend code
when it is released (at syncpoint or end of task) if there AD3T, message DFHDB2011 when THREADWAIT=NO
are no other transactions waiting for a thread on that is coded and the number of pool threads is exceeded.
DB2ENTRY. CVDA values are:
SECURITY(REBUILD) TWAIT
specifies that the CICS DB2 attachment should force all If all threads are busy, a transaction must wait
existing threads to sign-on again at the next thread until one becomes available. A transaction can
reuse. It should be used when RACF profiles have been wait as long as CICS allows it to wait, generally
updated by issuing the following commands: until a thread becomes available.
CEMT PERFORM SECURITY REBUILD for RACF NOTWAIT

1.9.2 or earlier If all threads are busy, the transaction is
terminated with abend code AD3T or AD2P.

CEMT SET DB2ENTRY
Note that when you change the value of AUTHId, CEMT SET DB2ENTRY
AUTHType, COMAUTHId, COMAUTHType or SIgnid, a
surrogate user security check is invoked if security is active. Function: Sets the attributes of a particular DB2ENTRY
This ensures that the userid under which SET is being used to define resources for a specific transaction or a group
executed is authorized to act on behalf of the userid being of transactions when accessing DB2.
set.
Description: The entry is identified by the name it was
Note that when the SET DB2CONN command is specified all identified with in CEDA. For RCTs migrated to the CSD, the
parameters, except the DB2ID (the connected subsystem), name is the name of the first transaction on the DSNCRCT
can be set when the CICS DB2 attachment is active. DB2ID TYPE=ENTRY statement.
can only be changed by stopping and restarting the
attachment. All parameters on SET DB2ENTRY can be set while the
CICS DB2 attachment is active and the transactions are
If you change the PLAN and PLANEXITNAME while there active.
are active transactions for that entry, or the pool, the next
time the transaction releases the thread, the plan/exit will be Syntax: Press the Clear key to clear the screen. There are
determined using the new rules. two ways of commencing this transaction
Type CEMT SET DB2ENTRY (the minimum abbreviation is
CEMT S DB2E) with either a value corresponding to a DB2
entry name or ALL. You get a display that lists the
current status, similar to that obtained by CEMT
INQUIRE DB2ENTRY. You can then tab to the
highlighted or blank fields and overtype them with the
required values.
Type CEMT SET DB2ENTRY (CEMT S DB2E) with either the
name of an entry or ALL, followed by one or more
attribute settings that you wish to change. For example,
cemt s db2e all ena enables all DB2ENTRYs.

immediately.

CEMT SET DB2ENTRY
This option applies to DB2ENTRYs that are used

55──CEMT Set DB2Entry──┬─────────────┬─────────5 by more than one transaction ID. As threads are
└─(data-area)─┘ typically released st syncpoint, a transaction
┌──
───────────────────────────┐ containing multiple UOWs may use a different
5───6┬─────────────────────────┬┴──5% thread for each UOW. The result may be that an
├─┬─ACCOUNTREC(cvda)─┬────┤
accounting record is produced per UOW.
│ ├─UOW──────────────┤ │
│ ├─TASK─────────────┤ │ NONE
│ ├─TXID─────────────┤ │ No accounting records are required for
│ └─NONE─────────────┘ │
├─AUTHID(data-area)───────┤ transactions using threads from this DB2ENTRY.
├─┬─AUTHTYPE(cvda)─┬──────┤ DB2 does, however, produce at least one
│ ├─GROUP──────────┤ │
│ ├─SIGN───────────┤ │ accounting record for each thread when the thread
│ ├─TERM───────────┤ │ is terminated. Additionally, authorization changes
│ ├─TX─────────────┤ │ cause accounting records to be produced.
│ ├─OPID───────────┤ │
│ └─USERID─────────┘ │ AUTHID
├─┬─DISABLEDACT(cvda)─┬───┤ specifies the id to be used for security checking when
│ ├─ABEND─────────────┤ │ using this DB2ENTRY. If AUTHId is specified,
│ ├─SQLCODE───────────┤ │
│ └─POOL──────────────┘ │ AUTHTYpe may not be specified.
├─┬─ENABLESTATUS(cvda)─┬──┤
│ ├─ENABLED────────────┤ │ AUTHTYPE
│ ├─DISABLED───────────┤ │ returns the type of id that can be used for security
│ └─FORCEDISABLED──────┘ │ checking when using this DB2ENTRY. If AUTHTYpe is
├─PLAN(data-area)─────────┤ specified, AUTHid may not be specified. CVDA values
├─PLANEXITNAME(data-area)─┤
are:
├─┬─PRIORITY(cvda)─┬──────┤
│ ├─HIGH───────────┤ │ GROUP
│ ├─EQUAL──────────┤ │
│ └─LOW────────────┘ │ Specifies the 8-character USERID and the
├─PROTECTNUM(data-area)───┤ connected group name as the authorization ID.
├─THREADLIMIT(data-area)──┤ The following table shows how these two values
└─┬─THREADWAIT(cvda)─┬────┘ are interpreted by DB2.
├─TWAIT────────────┤
├─NOTWAIT──────────┤ IDs passed to DB2 How DB2 interprets values
└─TPOOL────────────┘
(USERID) authorization ID.
Options RACF-connected If the RACF list of group options
ACcountrec connected group name supplied
specifies the minimum amount of DB2 accounting by the CICS attachment facility
required for transactions using this DB2ENTRY. The as the secondary DB2
specified minimum may be exceeded, as described in authorization ID. If the RACF list
the following options. CVDA values are: of group options is active, DB2
UOW name supplied by the CICS
The CICS DB2 attachment facility causes an attachment facility, but the value
accounting record to be produced for each UOW, appears in the DB2 list of
assuming that the thread is released at the end of
IDs.
the UOW.
TASK To use the GROUP option the CICS system must
The CICS DB2 attachment facility causes a have RACF external security SEC=YES specified
minimum of one accounting record to be produced in the CICS system initialization table (SIT).
for each CICS task.
A transaction containing multiple UOWs may use an 8-character field of blanks is passed to DB2 as
a different thread for each of its UOWs (assuming the group ID.
may be an accounting record produced for each SIGN
UOW. Specifies the SIGNID parameter of the DB2CONN
should be used as the resource authorization ID.
TXID
The CICS DB2 attachment facility produces at
least one accounting record to be produced when
the transid using the thread changes.

CEMT SET DB2ENTRY
TERM | FORCEDISABLED
Specifies the terminal identification (four | All tasks using the DB2ENTRY and those queued
characters padded to eight) as an authorization ID. | against the DB2ENTRY are forcepurged. The
An authorization ID cannot be obtained in this | DB2ENTRY is then disabled.
manner if a terminal is not connected with the
PLAN
transaction.
specifies the name of the plan to be used for this
If a transaction is started (using a CICS command) DB2ENTRY.
and has no terminal associated with it,
If PLAN is specified, PLANEXITNAME cannot be
specified.
TX Specifies the transaction identification (four
characters padded to eight) as the authorization PLANEXITNAME
ID. specifies the name of the dynamic plan exit to be used
for this DB2ENTRY. If you change the PLAN and
OPID
PLANExitname while there are active transactions for
The operator identification associated with the
the DB2ENTRY the next time the transaction releases
CICS transaction is used as the authorization ID
the thread, the plan/exit is determined using the new
(three characters padded to eight).
rules. If PLANExitname is specified, PLAN cannot be
USERID specified.
PRIORITY
specifies the priority of the thread tasks for the
When the DB2 sample sign-on exit DSN3@SGN DB2ENTRY relative to the CICS main task (QR TCB).
is used with AUTHTYPE(USERID), the exit sends CVDA values are:
the user ID to DB2 as the primary authorization ID
and the RACF group ID to DB2 as the secondary HIGH
ID. When the sample sign-on exit is used, there is subtasks attain a higher priority than the CICS
no difference between AUTHTYPE(USERID) and main task from which the subtask was generated.
AUTHTYPE(GROUP). EQUAL
subtasks have equal priority with the CICS main
DISABLEDACT
subtask.
specifies what CICS is to do with new transactions that
access a DB2ENTRY when it has been disabled or is LOW
disabling. CVDA values are: subtasks have a lower priority than the CICS main
task.
POOL
The CICS DB2 attachment facility routes the PROTECTNUM
request to the pool. Message DFHDB2072 is sent specifies the maximum number of protected threads for
to the transient data destination specified by this DB2ENTRY.
MSGQUEUEn on the DB2CONN for each
THREADLIMIT
transaction routed to the pool.
specifies the maximum number of threads for this
ABEND DB2ENTRY that the CICS DB2 attachment allows active
The CICS DB2 attachment facility abends the before requests are made to wait, are rejected, or are
transaction.The abend code is AD26. routed to the pool.
SQLCODE
THREADWAIT
An SQLCODE is returned to the application
specifies whether or not transactions should wait for a
indicating that the DB2ENTRY is disabled.
DB2ENTRY thread, be abended, or overflow to the pool
ENABLESTATUS(cvda) should the number of active DB2ENTRY threads reach
specifies whether the DB2ENTRY can be accessed by the THREADLimit number. CVDA values are:
applications. CVDA values are:
TWAIT
ENABLED If all threads are busy, the transaction waits until
The DB2ENTRY can be accessed by applications. one becomes available.
DISABLED NOTWAIT
The DB2ENTRY cannot be accessed by If all threads are busy, the transaction is
applications. A DB2ENTRY has to be disabled terminated with an abend code AD2P.
before it can be reinstalled or discarded. TPOOL
If all threads are busy, the transaction is diverted
to use the pool of threads. If the pool is also busy,
and NOTWAIT has been specified for the

CEMT SET DB2TRAN
THREADWAIT parameter on the DB2CONN. The CEMT SET DB2TRAN

transaction is terminated with abend code AD3T.
Function: specify this to set the attributes of a particular
All parameters on SET DB2ENTRY can be set whilst the DB2TRAN associated with a DB2ENTRY.
CICS DB2 attachment is active and the transactions are
active. Description: The DB2TRAN is identified by the name it
was defined with in CEDA. For RCTs migrated to the CSD,
the name matches the name of the transaction for which the
DB2TRAN is being created.
If a transid is specified on a DB2ENTRY when the

DB2ENTRY is installed, CICS installs a DB2TRAN named
DFHxxxx, where xxxx is the transid.
two ways of commencing this transaction
Type CEMT SET DB2TRAN (the minimum abbreviation is
CEMT S DB2T) with either a value corresponding to a DB2
transaction name or ALL. You get a display that lists the
INQUIRE DB2TRAN. You can then tab to the highlighted
or blank fields and overtype them with the required
values.
Type CEMT SET DB2TRAN (CEMT S DB2T) with either the
name of a DB2TRAN or ALL, followed by one or more
attribute settings that you wish to change. For example,
cemt s db2t all db2e(entry1) will set all DB2TRANs to
refer to a DB2ENTRY named entry1.

immediately.
55──CEMT Set DB2Tran───────────────────────────5

┌──
───────────────────────┐
5───6┬─────────────────────┬┴──5%
├─DB2Entry(data-area)─┤
└─Transid(data-area)──┘
Options
DB2Entry
specifies the name of the DB2ENTRY to which this
DB2TRAN refers; that is, the DB2ENTRY with which this
additional transid should be associated.
Transid
specifies the transaction id to be associated with the
entry. The transaction id can include wildcard characters
(see the CICS Resource Definition Guide for information
about use of wildcard characters). If you change
TRANSID for a DB2TRAN while the attachment is
active, all transactions with a thread continue to use the
thread from that entry until it is released for reuse.
When that transaction issues the next SQL statement,
the thread is acquired from the entry or pool based upon
the new definition.
DB2TRAN parameters may be set at any time.

CEMT SET DELETSHIPPED
CEMT SET DELETSHIPPED Options

IDle(value)
Function: Change system settings that control the CICS
specifies, in the form “0hhmmss+”, the minimum time
timeout delete mechanism.
that an inactive shipped terminal definition must remain
installed in this region. When the CICS timeout delete
Syntax: The CICS timeout delete mechanism is invoked at
mechanism is invoked, only those shipped definitions
user-specified intervals to remove any shipped terminal
that have been inactive for longer than this time are
definitions that have not been used for longer than a
deleted.
user-specified time.
The time interval can be in the range 00-99 hours; 00-59
SET DELETSHIPPED allows you to change the values that minutes; and 00-59 seconds.
control the mechanism.
At CICS startup, the interval is set to the value specified
Press the Clear key to clear the screen. There are two ways on the DSHIPIDL system initialization parameter.
of commencing this transaction: INterval(value)
Type CEMT SET DELETSHIPPED (the minimum abbreviation specifies, in the form “0hhmmss+”, the interval between
is CEMT S DE). You get a display that lists the current invocations of the CICS timeout delete mechanism. The
status, similar to that obtained by CEMT INQUIRE timeout delete mechanism removes any shipped terminal
DELETSHIPPED. You can then tab to the highlighted or definitions that have not been used for longer than the
blank fields and overtype them with the required values. time specified by the IDLE option.
Type CEMT SET DELETSHIPPED (CEMT S DE), followed by The time interval can be in the range 00-99 hours; 00-59
one or more attributes that you wish to change. For minutes; and 00-59 seconds. If you specify 0, the
example, cemt s de idl(ð15ðððð) specifies that shipped timeout delete mechanism is not invoked.
terminal definitions are to remain installed for at least At CICS startup, the interval is set to the value specified
fifteen hours after they become inactive. on the DSHIPINT system initialization parameter. By
resetting the interval, you can change the time of day at
55──CEMT Set DEletshipped──────────────────────5 which a mass delete operation takes place.
5──┬─────────────────┬──┬─────────────┬──5% Note: The revised interval starts from the time the
└─INterval(value)─┘ └─IDle(value)─┘ command is issued, not from the time the
timeout delete mechanism was last invoked, nor
from the time of CICS startup.

CEMT SET DSAS CEMT SET DSNAME
CEMT SET DSAS CEMT SET DSNAME

Function: Change the system storage attributes. Function: Change the status of an external data set.
Syntax: Press the Clear key to clear the screen. There are Description: With the SET DSNAME command, you can
two ways of commencing this transaction: change the status of a VSAM base data set. You can use
the command to perform the following actions on a data set:
Type CEMT SET DSAS. You get a display that lists the
current status, similar to that obtained by CEMT Mark a VSAM data set as quiesced, or unquiesced,
INQUIRE DSAS. You can then tab to the highlighted or throughout the sysplex.
Make a VSAM data set available or unavailable to a
Type CEMT SET DSAS followed by one or more attribute CICS region. (The availability function does not operate
settings that you wish to change. For example, cemt s across the sysplex—a SET DSNAME(...) AVAILABILITY
dsa ds(value) ed(value) will reset the values for command is effective only within the CICS region in
dynamic storage below the 16MB boundary and above which it is issued.)
the 16MB boundary.
Retry all UOW log records that are shunted because of
the failures of this data set (other than in-doubt failures).
gives a syntax prompt. Resetting the values takes effect Force any UOWs that are shunted because of in-doubt
immediately. failures, and which have updated this data set, to
complete.
55──CEMT Set DSAs──┬─────────────────┬─────────5 Purge shunted UOW log records that hold retained locks
└─Dsalimit(value)─┘ (other than those due to in-doubt failures) for any
records in the data set, and release the retained locks,
5──┬──────────────────┬──5%
└─EDsalimit(value)─┘ Cancel any attempt to recover lost RLS locks for the
data set using the UOWACTION and
ACTION(RESETLOCKS) options.
Options
The SET DSNAME command does not distinguish between
Dsalimit(value)
data sets accessed in RLS and non-RLS mode.
specifies the maximum amount of storage, as a total
number of bytes, within which CICS can dynamically The new options for the SET DSNAME command are subject
allocate storage for the four individual DSAs that reside to the following rules relating to the order of processing and
below the 16MB boundary. See the CICS System the combinations of keywords and multiple keywords on the
Definition Guide for a description of the DSALIM system same command:
initialization parameter.) If DSALIMIT specifies a value
lower than the current limit, CICS may not be able to If REMOVE is specified, no other attribute is allowed.
implement the new limit immediately, but will attempt to Options are processed in the following order:
do so over time as dynamic storage is freed in the
1. RECOVERED
individual DSAs.
2. UNQUIESCED
EDsalimit(value) 3. AVAILABLE
specifies the maximum amount of storage, as a total 4. RETRY
number of bytes, within which CICS can dynamically 5. UOWACTION
allocate storage for the four individual DSAs that reside 6. RESETLOCKS
above the 16MB boundary. See the CICS System 7. UNAVAILABLE
Definition Guide for a description of the EDSALIM 8. QUIESCED.
system initialization parameter.) If EDSALIMIT specifies
a value lower than the current limit, CICS may not be If you specify RETRY, do not also specify UNAVAILABLE or
able to implement the new limit immediately, but will QUIESCED, because this would cause backout retries to fail.
attempt to do so over time as dynamic storage is freed UNQUIESCE should not be specified with other attributes,
in the individual DSAs. because the other options may fail.
Some of the attributes of a data set cannot be set until the

first file that references the data set has been opened.
Where an attribute is not valid until a file has been opened,
an error is returned. Note that QUIESCESTATE is an
attribute that can be set before any files have been opened
against the specified data set.

CEMT SET DSNAME
Syntax: Press the Clear key to clear the screen. There are IMmquiesced
two ways of commencing this transaction: Causes all existing CICS open RLS-mode files
throughout the sysplex to be closed and the data set to
Type CEMT SET DSNAME (the minimum abbreviation is
be marked as quiesced in the ICF catalog. Each CICS in
CEMT S DSN) with either a value corresponding to a data
the sysplex abends all in-flight UOWs that are accessing
set name or ‘ALL’. You get a display that lists the current
the data set before closing files, causing in-flight UOWs
to back out. Any UOWs that fail backout are shunted. No
DSNAME. You can then tab to the highlighted or blank
RLS-mode files can open against this data set, but
non-RLS-mode open requests are permitted.
Type CEMT SET DSNAME (CEMT S DSN) with either a
In addition to closing open files, IMMQUIESCED sets the
dataset_name or ‘ALL’, followed by one or more
file state to UNENABLED if it was ENABLED. A
attributes that you wish to change. For example, cemt s
subsequent SET DSNAME UNQUIESCED command
dsn(applb.\) q quiesces all data sets with a high-level
restores the file state to ENABLED, if it was set
qualifier of APPLB in all CICS regions within the sysplex.
UNENABLED by a QUIESCED or IMMQUIESCED
Resetting the values takes effect immediately. action, but not if the UNENABLED state is due to some
other event. This state change is recorded in the CICS
global catalog.
55──CEMT Set DSName──┬─(value)─┬───────────────5
└─ALl─────┘ Attention
5──┬────────────┬──┬─────────────┬─────────────5 Using the IMMQUIESCED option causes any tasks
├─REMOve─────┤ ├─AVailable───┤ currently using the data set to be terminated
├─RECOVEREd──┤ └─UNAvailable─┘
├─RESetlocks─┤ immediately, using the CICS task FORCEPURGE
└─RETRy──────┘ mechanism. In some extreme cases CICS may
terminate abnormally. For this reason, setting a data
5──┬─────────────┬──┬─────────┬──5%
├─Quiesced────┤ ├─BACkout─┤ set as quiesced using the IMMQUIESCED option
├─UNQuiesced──┤ ├─Commit──┤ should be restricted to exceptional circumstances.
└─IMmquiesced─┘ └─FOrce───┘
Quiesced
Options Causes all existing CICS files open in RLS mode
throughout the sysplex to be closed and the data set to
(value) be marked as quiesced in the ICF catalog. Each CICS in
specifies one or more names (1-44 characters) of an the sysplex waits until all in-flight UOWs that are
external data set. accessing the data set have reached syncpoint before
closing the files; that is, the UOWs are either:
ALl
If you specify the ALL operand on a SET command, any Successfully committed or
change you request is made to all resources of the Successfully backed out, or
specified type that you are authorized to access. Shunted because they failed in-doubt, or
Shunted because they failed commit, or
AVailable
Shunted because they failed backout.
specifies whether the data set is to be marked in this
CICS region as available for use. This command sets No files can open in RLS mode against this data set, but
the availability indicator, which is a local flag that a CICS non-RLS open requests are permitted.
region maintains in a data set name block (DSNB) for
In addition to closing open files, QUIESCED sets the file
each data set. CICS can issue either RLS or non-RLS
state to UNENABLED if it was ENABLED. A subsequent
open requests for this data set.
SET DSNAME UNQUIESCED command restores the file
BACkout state to ENABLED, if it was set UNENABLED by a
Specifies that all shunted in-doubt UOWs that hold locks QUIESCED or IMMQUIESCED action, but not if the
on this data set should be backed out. UNENABLED state is due to some other event. This
state change is recorded in the CICS global catalog.
Commit
Specifies that all shunted in-doubt UOWs that hold locks RECOVEREd
on this data set should be committed. The data set has been restored from a backup version
and forward recovery has run and completed
FOrce successfully. CICS normally updates the
Specifies that all shunted in-doubt UOWs that hold locks backup-while-open (BWO) attributes for the base cluster
on this data set should be forced to BACKOUT or data set BASEDSNAME, using MVS/DFP 3.2 Callable
COMMIT as specified by the ACTION attribute on the Services.
transaction resource definition.

CEMT SET DSNAME
If the BWO attributes are not updated after the restore of Backout-failed and commit-failed log records are not
a backup copy of a data set that was taken using BWO, shunted for BDAM data sets.
CICS fails a subsequent file open because the data set
You might use RESETLOCKS if backout-failed or
is marked as down-level.
commit-failed log records are holding up lost locks
REMOve recovery for the data set, and there is no other way of
This option is used when a data set is no longer resolving them.
required on the local system. It deletes the data set Notes:
name block for the named data set. The REMOVE
option can be used only when there are no file control 1. This option does not apply to shunted in-doubt
resource definition entries that refer to the specified data UOWs. Try to resolve the shunted in-doubt UOWs
set. If any file definitions refer to the data set name that hold locks on the data set in other ways before
when you enter SET DSNAME REMOVE, you receive issuing RESETLOCKS; for example, by using
an error message indicating that the use count of the COMMIT, BACKOUT, or FORCEUOW.
data set name block is not zero. To ensure that no file 2. RESETLOCKS can fail during the commit phase (for
definitions refer to the data set name: example, if an error occurs while CICS is trying to
release the RLS locks), in which case the UOWs
Close all files that refer to the data set. These files
revert to being shunted as commit-failed UOWs.
can be found using the command:
CEMT INQUIRE FILE(\) DSNAME(dsname) RETRy
Specifies that shunted UOW log records, caused by
Either remove the data set name from each file
failed backout and commit processing as a result of the
entry (by over-typing the data set name with blanks
failure of this data set, should be retried. This is similar
on the CEMT display), or discard the file definition
in operation to the EXEC CICS RESYNC command, but
entirely.
applies to backout-failed and commit-failed UOWs only,
If you have a base data set with one or more alternate and not to in-doubt UOWs.
indexes, you are unable to remove the data set name You should use RETRY when the data set has shunted
block for the base until you have removed all references backout- or commit-failed UOWs associated with it, and
to the base data set and all references to paths. you believe that some or all of the data set problems are
RESetlocks (vsam only) either transient or have been resolved.
Purges shunted UOW log records for backout-failed and Messages, issued at the time of a data set failure that
commit-failed UOWs that hold locks on this data set, and causes UOWs to be shunted, recommend the actions
releases the retained locks: that are required to recover from the failure.
Backout-failed UOWs are those that failed during RETRY does not affect data integrity, and can be used
backout processing. safely at any time to enable some failed recovery work
to complete.
Commit-failed UOWs are those that have updated
RLS data sets, and have failed to release locks UNAvailable
during the second phase of 2-phase commit Marks the data set as unavailable, and prevents the data
syncpoint processing. set being opened in either RLS or non-RLS modes. This
command sets or unsets the availability indicator, which
If you specify this option, you are accepting backout is a local flag that a CICS region maintains in a data set
failure and some loss of data integrity rather than name block (DSNB) for each data set.
retaining locks and delaying transactions, and therefore
it should be used only as a last resort. UNQuiesced
Causes the data set to be marked as unquiesced in the
For backout-failed and commit-failed UOWs that hold ICF catalog. RLS or non-RLS mode files can be opened
locks on the data set, all records relating to this data set against this data set, the access mode (RLS or
are removed from the system log and all retained record non-RLS) being established by the first open.
locks held by this CICS for the data set are released.
Diagnostic messages are written to the CSFL transient If a file has been set UNENABLED by a SET DSNAME
data queue for each backout-failed log record that is IMMQUIESCED or QUIESCED command,
removed as a result of the RESETLOCKS operation. UNQUIESCED sets it back to ENABLED, provided that
there have been no other explicit changes to the
RESETLOCKS applies only to shunted UOW log records enablement state in the meantime. This state change is
that are classed as backout-failed and commit-failed. recorded in the CICS global catalog.
Therefore it cannot be issued for a BDAM data set.

CEMT SET DUMPDS CEMT SET ENQMODEL
CEMT SET DUMPDS | CEMT SET ENQMODEL

Function: Change the attributes of a CICS dump data set. | Function: Set the status of enqmodel definitions on the
| local system.
Description: Using SET DUMPDS, you can open or close
the active CICS dump data set, and specify whether or not | Description: Each ENQMODEL definition may be in one
the automatic switch to the inactive dump data set occurs | of the following states
when the active dump data set is full.
| ENABLED Matching ENQ requests will be processed in the
| normal way.
For more information about dumps, see the CICS Problem
| DISABLED Matching ENQ requests will be rejected, and the
| issuing task abended abcode ENQ_DISABLED.
Syntax: Press the Clear key to clear the screen. There are | Matching INSTALL/CREATE/DISCARD requests
two ways of commencing this transaction: | will be processed.
| WAITING Matching ENQ requests will be rejected, and the
Type CEMT SET DUMPDS (the minimum abbreviation is | issuing task abended abcode ENQ_DISABLED.
CEMT S DU). You get a display that lists the current | There are INSTALL/CREATE/DISCARD requests
status, similar to that obtained by CEMT INQUIRE | waiting to be processed.
DUMPDS. You can then tab to the highlighted or blank
fields and overtype them with the required values. | This command provides a means for you to set the
Type CEMT SET DUMPDS (CEMT S DU) followed by one or | ENABLED and DISABLED states for ENQmodel resources
more attribute settings that you wish to change. For | installed on the local system. An enqmodel must be enabled
example, cemt s du o a will open the active dump data | to allow matching EXEC ENQ requests to be processed. It
set and cause autoswitch to occur only when the active | must be disabled to allow a more specific enqmodel to be
dump data set is full. | enabled.
Typing ? at the beginning of either the first or second line | Enqmodels forming nested generic enqnames must be
gives a syntax prompt. Resetting the values takes effect | enabled in order, from the most to the least specific. For
immediately. | example, enable ABCD* then ABC* then AB*.
| If you attempt to enable a more specific enqmodel when a
| less specific enqmodel is already enabled, the result is that
55──CEMT Set DUmpds──┬────────┬────────────────5 | message DFHNQ0107 is issued.
├─Open───┤
├─CLosed─┤ | You cannot enable/disable an enqmodel which is in the
└─Switch─┘ | waiting state.
5──┬──────────────┬──5%
├─Autoswitch───┤ | Syntax
└─Noautoswitch─┘
|
| 55──CEMT Set ENQModel(value)──┬──────────┬──5%
Options | ├─Enabled──┤
| └─DIsabled─┘
Autoswitch
is full, but not subsequently. | Options
CLosed | (value)
The active CICS dump data set is closed. | The 8-character identifier of the resource definition
Noautoswitch | DISABLED
When the active dump data set is full, there is not to be | The ENQMODEL will be put into the WAITING state
an automatic switch to the inactive dump data set. | (See Inquire Enqmodel) until there are no enqueues in
| the local system which match the ENQNAME pattern. It
Open
| will then be DISABLED. Once DISabled, matching ENQ
The active CICS dump data set is opened.
| requests will be rejected, and the issuing task abended
Switch | abcode ENQ_DISABLED.
| ENABLED
| If the enqmodel is DISABLED, it will be ENABLED. Once
active.
| enabled, matching ENQ requests will be processed in
| the normal way.

CEMT SET FEPI CEMT SET FILE
CEMT SET FEPI CEMT SET FILE

Comments: For information on CEMT SET Function: Change some of the attributes of one or more
FECONNECTION, CEMT SET FEPOOL, CEMT SET VSAM or BDAM files.
FEPROPSET, and CEMT SET FETARGET, see the CICS
Front End Programming Interface User's Guide. Syntax: Press the Clear key to clear the screen. There are
Type CEMT SET FILE (the minimum abbreviation is CEMT
S FI) with either a value corresponding to a file name or
ALL. You get a display that lists the current status,
similar to that obtained by CEMT INQUIRE FILE. You
can then tab to the highlighted or blank fields and
Type CEMT SET FILE (CEMT S FI) with either the name of
a file or ALL, followed by one or more attribute settings
| that you wish to change. For example, cemt s fi al op
| en attempts to set all files open and enabled for use.

gives a syntax prompt. Reset values take effect immediately.
| Note: Some attributes can be changed only when the
| specified file is closed and disabled. In these cases,
| the reset values take effect when the file is enabled
| for use again.

CEMT SET FILE
CLosed
55──CEMT Set FIle──┬─(value)─┬─────────────────5 The file is closed; the access method does not allow
└─ALl─────┘ accesses to the data until the file is opened. The file can
5──┬────────────┬──┬──────────┬──┬────────┬────5 be opened either explicitly by the user or, if the file has
├─OPen───────┤ ├─ENabled──┤ ├─REAd───┤ the ENABLED attribute, implicitly by CICS on the next
├─CLosed─────┤ └─DIsabled─┘ └─NORead─┘
reference to the file.
└─Forceclose─┘
5──┬──────────┬──┬───────────┬─────────────────5 When the SET FILE CLOSED command is used, the file
├─UPdate───┤ ├─ADdable───┤ is closed and also disabled (set UNENABLED). (A file
└─NOUpdate─┘ └─NOAddable─┘ disabled in this way prevents access requests from
5──┬──────────┬──┬──────────┬──────────────────5 implicitly opening the file again.) The close is effected at
├─BRowse───┤ ├─DElete───┤ the time of the command only if there are no tasks
└─NOBrowse─┘ └─NODelete─┘ currently accessing the file. If there are current users,
5──┬─────────────┬──┬────────────┬─────────────5 the display indicates CLOSE requested. This means
├─EXclusive───┤ ├─EMptyreq───┤ that, when the last user finishes using the file, it effects
└─NOEXclusive─┘ └─NOEMptyreq─┘ the close.
5──┬───────┬──┬────────┬──┬───────────────┬────5 A file that has been disabled by a SET FILE CLOSED
├─Old───┤ ├─RLs────┤ └─DSname(value)─┘
└─Share─┘ └─NOTRls─┘ command becomes enabled again by a subsequent SET
FILE OPEN command. To distinguish a file that has
5──┬───────────┬──┬────────┬───────────────────5
| ├─NOTTable──┤ ├─LOAd───┤ been disabled by a SET FILE CLOSED from one that
| ├─CIcstable─┤ └─NOLoad─┘ has been disabled by a SET FILE DISABLED command,
├─USertable─┤ the SET FILE CLOSED command closes the file with the
| └─CFTable───┘ UNENABLED attribute.
5──┬─────────────────┬─────────────────────────5 A file with the DISABLED attribute can be enabled only
| └─CFDtpool(value)─┘
by a SET FILE ENABLED command. A file with the
5──┬──────────────────┬──┬────────────┬────────5 UNENABLED attribute can be enabled by a SET FILE
| └─Tablename(value)─┘ ├─COntention─┤
ENABLED or SET FILE OPEN command.
| └─LOCking────┘
5──┬───────────────────┬───────────────────────5 | COntention (CFDT only)
└─Maxnumrecs(value)─┘ | The coupling facility data table is to use the contention
5──┬──────────────────┬────────────────────────5 | model, in which records are not locked when they are
| └─Keylength(value)─┘ | read for update, but an error is returned on a
5──┬───────────────────┬──5% | subsequent REWRITE or DELETE if the record has
| └─RECordsize(value)─┘ | changed or been deleted since it was read for update.
DElete
You can delete records from the file.
Options
DIsabled
(value)
The file is not available for use by transactions except
One or more names (1-8 characters) defined in the file
for those that are currently using it. If there are any such
control table (FCT).
users, ‘BEING DISABLED’ is also displayed. The CEMT
ADdable SET FILE DISABLED command has no effect on
You can add records to the file. existing users; it simply prevents new users from
accessing the file.
ALl
Any change you request is made to all files that you are The file can be reenabled by a SET FILE ENABLED
authorized to access. command. (See also UNENABLED.)
It is not possible to disable a remote file.
BRowse
You can browse records in the file. DSname(value)
specifies the name (1–44 characters) of the VSAM or
| CFDtpool(value)
BDAM data set with which this file is associated. CEMT
| specifies the name of the CFDT pool in which the
SET FILE(value) DSNAME(value) associates the data
| coupling facility data table resides.
set with the file and causes the FILECOUNT of the data
| CFtable set to be incremented by 1. You can use CEMT SET
| The file name represents a coupling facility data table. FILE DSNAME with a null DSNAME value to dissociate
a file from its current data set.
CIcstable
The file name represents a CICS-maintained data table. Note: DSNAME replaced OBJECTNAME.

CEMT SET FILE
EMptyreq (vsam only) | that use this coupling facility data table rely on it
Applies only to a VSAM file that has been defined to | containing the records from the specified source data
VSAM as a cluster with the REUSE parameter, and | set.
which is opened in non-RLS access mode. It indicates
| LOCking (CFDT only)
that when a file is next opened, its data is erased.
| The coupling facility data table is to use the locking
If the file is opened in RLS access mode this parameter | model, in which records are locked when they are
has no effect. | updated.
A CEMT SET FILE EMPTYREC command can be
Maxnumrecs(value)
applied only to files that are closed and either disabled
specifies the maximum number of records that the data
or unenabled, and has no effect on the data until the file
table for this file can hold.
is opened. A SET FILE EMPTYREQ command can be
canceled by a SET FILE NOEMPTYREQ command. | For any type of table, if you want to set a limit, specify a
| value in the range 1 to 99 999 999. If you do not want
ENabled | any limit to apply, specify MAXNUMRECS(0), which
The file is available for use by transactions and, if | CICS interprets as no limit, and sets internally to the
closed, it is opened on the first request. If the command | maximum positive fullword value (+2147483647 or
CEMT SET FILE(value) CLOSED ENABLED is given | X'7FFFFFFF').
while the file is in use, the status of the file becomes
| Note: The new value takes effect only when a new
‘closed-unenabled’. If the command CEMT SET
| data table is created. This happens on each file
FILE(value) CLOSED is given while the file is in use, the
| open for a CICS-maintained or user-maintained
file is disabled to prevent new users accessing the file.
| data table, but only when the table does not
EXclusive | already exist for a CF data table. Once a
Records on the file are protected from simultaneous | coupling facility data table has been created, you
update by being placed under exclusive control when a | can change the maximum number of records
read for update is issued. | only through the CFDT server MVS command
| interface.
Forceclose
Similar to SET FILE CLOSED, except that any existing | To specify MAXNUMRECS for a recoverable coupling
users of the file are abended (abend code ‘AKC3’ or | facility data table, use a value that is between 5 and
‘ATCH’). As for CLOSED, the close is effected by the | 10% more than the maximum number of records that the
last of these users. | table is expected to contain. This allows for additional
| records that might be created internally for processing
Data integrity | recoverable requests. The margin to be left for this
Closing a file using the FORCECLOSE option | internal processing depends on the level of use of the
causes tasks of any current users of the file to be | coupling facility data table, and the nature of that use.
terminated immediately by the CICS task | An effect of this is that the NOSPACE condition (with a
FORCEPURGE mechanism. Data integrity is not | RESP2 of 102) can be raised on a WRITE or REWRITE
guaranteed with this mechanism. In some extreme | request to a recoverable coupling facility data table that
cases (for example, if an error occurs during backout | apparently has fewer records than the MAXNUMRECS
processing) CICS might terminate abnormally. For | limit specifies.
this reason, closing files using the FORCECLOSE
NOAddable
option should be restricted to exceptional
You cannot add records to the file.
circumstances.
NOBrowse
| Keylength(value) You cannot browse records in the file.
| Specifies the key length of records in a coupling facility NODelete
| data table that does not require pre-loading from a You cannot delete records from the file.
| source data set. To set a keylength, specify a value in
| the range 1 through 16. To clear a keylength (set it to NOEMptyreq (vsam only)
| null values), specify KEYLENGTH(0). Applies only to VSAM files. It indicates that when a file is
next opened, its data is not erased.
| You can specify the key length for a file that does not
| currently refer to a coupling facility data table, but which A CEMT SET FILE NOEMPTYREC command can be
| could be switched to use a coupling facility data table at applied only to files that are closed and either disabled
| a later date. or unenabled, and cancels the implicit request in a
previous SET FILE EMPTYREQ command.
| LOAd
| The coupling facility data table requires loading from a NOEXclusive
| source data set before it is fully usable; the transactions Records on the file are not protected from simultaneous
update.

CEMT SET FILE
| NOLoad REAd
| The coupling facility data table does not require loading You can read records in the file.
| from a source data set. It is fully usable as soon as it is
| RECordsize
| created, and is populated entirely by the transactions
| specifies the maximum record size for a coupling facility
| that use it.
| data table that does not require pre-loading from a
NORead | source data set.
You cannot read records in the file.
| You can specify the record size for a file that does not
NOTRls (vsam only) | currently refer to a coupling facility data table, but which
The file is defined to be accessed in a non-RLS mode | could be switched to use a coupling facility data table at
(LSR or NSR). | a later date. Specify a record size of 1- to 32767-bytes,
| or specify a record size of zero to remove a previously
For information about switching from RLS to non-RLS
| defined value.
mode, see the CICS Recovery and Restart Guide.
RLs (vsam only)
NOTTable
The file is defined to be accessed in RLS mode.
The file name does not represent a data table.
Share
NOUpdate
The disposition of the data set associated with the file is
You cannot update records in the file.
defined as shared for dynamic allocation.
Old
| Tablename(value)
The disposition of the data set associated with the file is
| specifies the name of the table for a coupling facility
defined as unshared for dynamic allocation.
| data table.
OPen
UPdate
The file is open. If the file is OPEN ENABLED, it is
You can update records in the file.
available for data accesses by CICS transactions. If it is
OPEN DISABLED, it must first be enabled before it is USertable
available. The file name represents a user-maintained data table.
If the file was unenabled by a previous SET FILE
CLOSED command, the SET FILE OPEN command
reenables the file implicitly.

CEMT SET GTFTRACE CEMT SET INTTRACE
CEMT SET GTFTRACE CEMT SET INTTRACE

Function: Change the status of GTF tracing Function: Switch CICS internal tracing on or off.
Description: SET GTFTRACE allows you to switch CICS Description: SET INTTRACE allows you to switch CICS
tracing to the MVS Generalized Tracing Facility (GTF) on internal tracing on and off.
and off.
This command is intended for use at terminals that do not support the full-screen tracing transaction CETR.
support the CETR full-screen tracing transaction.
For guidance on using GTF tracing, see the CICS Problem two ways of commencing this transaction:
Type CEMT SET INTTRACE (the minimum abbreviation is
CEMT S IN). You get a display that lists the current
INTTRACE. You can then tab to the highlighted field and
Type CEMT SET GTFTRACE (the minimum abbreviation is overtype it with the required value.
CEMT S G). You get a display that lists the current status,
Type CEMT SET INTTRACE (CEMT S IN) followed by the
similar to that obtained by CEMT INQUIRE GTFTRACE.
attribute setting that you wish to change. For example,
You can then tab to the highlighted field and overtype it
cemt s in sta will cause CICS internal tracing to be
with the required value.
started.
Type CEMT SET GTFTRACE (CEMT S G) followed by the
attribute setting that you wish to change. For example, Typing ? at the beginning of either the first or second line
cemt s g sta will cause CICS GTF tracing to be started. gives a syntax prompt. Resetting the values takes effect
immediately.
immediately. 55──CEMT Set INttrace──┬───────┬──5%
├─STArt─┤
└─STOp──┘
55──CEMT Set Gtftrace──┬───────┬──5%
├─STArt─┤
└─STOp──┘ Options
STArt
Options CICS internal tracing is started.
STArt STOp
CICS tracing to the MVS Generalized Tracing Facility CICS internal tracing is stopped.
(GTF) is started.
STOp
(GTF) is stopped.

CEMT SET IRC
CEMT SET IRC

55──CEMT SET IRc──┬─Open─────┬──5%
├─Closed───┤
Function: Open or close the interregion communication └─Immclose─┘
(IRC) facility.
Description: New MRO connections can be installed Options

without first closing IRC. However, if you want to modify
existing MRO connections, IRC must be closed using the Closed
SET IRC CLOSED command. For example: Interregion communication for this CICS system is to be
CEMT SET IRC CLOSED terminated after all tasks using IRC sessions have
CEDA INSTALL GROUP(groupname) terminated normally.
CEMT SET IRC OPEN Immclose
All tasks using IRC sessions are to be abended when
they next try to use the session. Interregion
communication is terminated when all tasks that were
Type CEMT SET IRC (the minimum abbreviation is CEMT S using IRC have been abended or have terminated
IR). You get a display that lists the current status, similar normally.
to that obtained by CEMT INQUIRE IRC. You can then
tab to the highlighted field and overtype it with the Open
required value. Interregion communication for this CICS system is to be
initialized. This allows connections to be established
Type CEMT SET IRC (CEMT S IR) followed by the attribute between this system and other systems, including DL/I
setting that you wish to change. For example, cemt s ir batch regions and non-CICS client programs using the
o will cause interregion communication to be initialized. external CICS interface (EXCI). You can control the
availability of individual connections with the
INSERVICE|OUTSERVICE settings on the connection
names.
immediately.
The DFHIR3780 message and CICS interregion
communication program (IRP) return and reason codes
are displayed if IRC fails to open. For a description of
DFHIR3780, see the CICS Messages and Codes
manual.

CEMT SET JOURNALNAME CEMT SET LINE
CEMT SET JOURNALNAME CEMT SET LINE

Function: Enable or disable a CICS user journal. Function: Change the status of a line.
Description: The SET JOURNALNAME command allows Description: The SET LINE command allows you to
you to enable or disable a CICS user journal. It has no effect purge or forcepurge a line, to put the line in or out of service,
on a journal that is being used as the forward recovery log or and to adjust the relative line number.
auto-journal for a VSAM file until the next time the file is
opened or on the system log. You can specify a list of identifiers (see “List of resource
identifiers” on page 47), but you cannot use the symbols *
You can use SET JOURNALNAME for a journal name that is and + to specify a family of identifiers.
not currently known to CICS. CICS dynamically creates an
entry for the specified journal and, if necessary, defines it to Syntax: Press the Clear key to clear the screen. There are
the MVS system logger using a matching JOURNALMODEL two ways of commencing this transaction:
definition (see the CICS Resource Definition Guide.) Type CEMT SET LINE (the minimum abbreviation is CEMT
S L) with a terminal identifier. You get a display that lists
Syntax the current status, similar to that obtained by CEMT
INQUIRE LINE. You can then tab to the highlighted or
55──CEMT Set Journalname(value)──┬─(value)─┬───5 blank fields and overtype them with the required values.
└─All─────┘ Type CEMT SET LINE (CEMT S L) with a termiinal identifier,
5──┬──────────┬──┬───────┬──5% followed by one or more attribute settings that you wish
├─Enabled──┤ ├─FLush─┤ to change. For example, cemt s l(value) i will make
└─DIsabled─┘ └─Reset─┘ the line available for use (inservice).

Options gives a syntax prompt. Resetting the values takes effect
immediately.
(value)
Specifies the journal name.
To modify journals defined with a numeric identifier in 55──CEMT Set Line(value)──┬───────────────┬────5
the range 1–99, specify journal name DFHJnn, where nn └─NUmber(value)─┘
is the journal number. 5──┬────────────────┬──┬────────────┬──────────5
└─NEgpoll(value)─┘ ├─Inservice──┤
You cannot specify DFHLOG or DFHSHUNT, because └─Outservice─┘
you are not allowed to modify the status of the system
5──┬────────────┬──5%
log. ├─Purge──────┤
└─Forcepurge─┘
All specifies that any changes you request are made to all
resources of the specified type that you are authorized
to access.
Options
DIsabled
(value)
The journal is disabled. It cannot be used again until it is
specifies the identifier of a terminal on the line. This
reenabled by a SET JOURNALNAME(...)
request is valid only for non-VTAM terminals.
STATUS(ENABLED) or ACTION(RESET) command.
Forcepurge
Enabled
All transactions running with terminals on the line are
The journal is open and is available for use.
immediately terminated abnormally. Data integrity is not
FLush guaranteed. In some extreme cases (for example, if an
The log buffers are written out to the log stream but the error occurs during backout processing), CICS might
journal is not closed. terminate abnormally.
You can use this option to ensure that all current records Inservice
are written out to the log stream before the stream is The line is available for use. Changing the status of the
processed using a batch utility. line does not affect the equivalent status of the terminals
on it.
Reset
The journal is disabled, but can be reenabled by the NEgpoll(value)
next SET JOURNALNAME STATUS(ENABLED) or specifies the negative poll delay interval (00000–20000
ACTION(RESET) command for this journal. milliseconds). For a TCAM line, this specifies the interval
before control is passed to the terminal error program

CEMT SET MODENAME
(DFHTEP) when a CICS task is not ready to accept a CEMT SET MODENAME
record from an input process queue.
If the CICS task issues a read before the interval Function: Change the status of a mode name.
expires, processing continues normally and DFHTEP is
not notified. The default value is zero. Description: The SET MODENAME command is used to
reset the connection to a remote system or to another CICS
NUmber(value) region, change the number of sessions available, and
specifies the relative line number of a pooled line. It is acquire or close the sessions associated with the mode
mandatory when inquiring about pooled lines. For name.
information about pooled lines, see the CICS Resource
Definition Guide. Syntax: Press the Clear key to clear the screen. There are
Outservice
The line is not available for use. Changing the status of Type CEMT SET MODENAME (the minimum abbreviation is
the line does not affect the equivalent status of the CEMT S MOD) with either a modename or ALL. You get a
terminals on it. display that lists the current status, similar to that
obtained by CEMT INQUIRE MODENAME. You can
Purge then tab to the highlighted or blank fields and overtype
Tasks running on terminals associated with the line are them with the required values.
abnormally terminated, but task termination occurs only
if system and data integrity can be maintained. Type CEMT SET MODENAME (CEMT S MOD) with either a
modename or ALL, followed by one or more attribute
settings that you wish to change. For example, cemt s
mod(modename) acq will cause CICS to acquire all the
negotiated contention-winner sessions within the group
named by modename.

immediately.
55──CEMT Set MODename──┬─(value)─┬─────────────5

└─ALl─────┘
5──┬───────────────────┬───────────────────────5
└─COnnection(value)─┘
5──┬──────────────────┬──┬──────────┬──5%
└─AVailable(value)─┘ ├─ACQuired─┤
└─CLosed───┘
Options
(value)
specifies one or more names (1-8 characters) of a group
of sessions. Mode names need not be unique. You
cannot specify a list of names, but you can use the
symbols * and + to specify a family of mode names.
A mode name consisting of eight blanks is valid. To
specify this name, enclose the string of blanks within
single quotation marks:
MODENAME(' ')
ACQuired
CICS is to acquire (or “bind”) all the negotiated
contention-winner sessions within the group.
ALl
specifies that any changes you request are done to all
to access.

CEMT SET MONITOR
AVailable(value) CEMT SET MONITOR

specifies the maximum number of sessions within the
group that can be concurrently allocated for use. This Function: Change the status of monitoring.
value has to be the same for both sides involved in the
session. Description: SET MONITOR allows you to select the
classes of monitoring data you want collected, switch
CLosed
monitoring on or off, and set the status of monitoring options.
CICS is to release all sessions within the group. The
For programming information on the monitoring classes, see
sessions are quiesced and unbound. No further sessions
the CICS Customization Guide.
can be acquired by another CICS system. No further
activity is possible on the sessions within the group until Notes:
the group is reacquired by the same CICS system in
which it has been closed. 1. When you change the status of CICS monitoring from
OFF to ON, CICS starts to accumulate monitoring data,
COnnection(value) and to write monitoring records for the active monitoring
specifies an identifier (1–4 characters) defined for an classes, for all tasks that start after the change is made.
IRC or ISC connection. The monitoring status of tasks being processed is not
affected.
2. When you change the status of CICS monitoring from
ON to OFF, CICS stops writing monitoring data
immediately. No monitoring data is accumulated for
tasks that start after the change is made.
3. The monitoring class settings can be changed
irrespective of whether monitoring is ON or OFF.
If monitoring is OFF, you can change the class settings
as required in preparation for the next time STATUS is
set to ON.
If monitoring is ON, changes to the class settings have
the following effects:
a. Changing a class from not-active to active has no
effect on the data written for running tasks.
b. Changing a class from active to not-active prevents
monitoring data for that class being written for
running tasks as follows:
Sysevent
Monitoring data is not written at
transaction termination.
Performance
Any performance class data remaining
in the output buffer is recorded, and no
further data is collected.
Exception
Monitoring data is not written at the
completion of the exception condition.
c. Exception class and performance class data are
gathered during the life of a running transaction.
When you change these settings, you should be
aware of their impact on transactions that are
running. For example, if a transaction is started
when the performance class is set to PERF and
monitoring is ON, performance class data is
accumulated for that transaction. If you switch the
performance class to NOPERF while the transaction
is running, and then back to PERF before the
transaction ends, performance data will be missing
from the final monitoring data for that transaction,

CEMT SET MONITOR
even though, when it started and when it ended, the any long-running transaction that has been in the system
performance class was set to PERF. for a greater time than the interval. Frequency times are
0, or in the range 001500–024000. The default
Syntax: Press the Clear key to clear the screen. There are frequency value is 0, which means that FREQUENCY
two ways of commencing this transaction: monitoring is inactive (that is, no performance class
Type CEMT SET MONITOR (the minimum abbreviation is records are produced for long-running transactions).
CEMT S MON). You get a display that lists the current NOConverse
status, similar to that obtained by CEMT INQUIRE Conversational tasks are not to have separate
MONITOR. You can then tab to the highlighted or blank performance class records produced for each pair of
fields and overtype them with the required values. terminal control I/O requests (Converse or Send/Receive
Type CEMT SET MONITOR (CEMT S MON) followed by one or pair).
more attribute settings that you wish to change. For
NOEVent
example, cemt s mon on p ex will set CICS monitoring
The SYSEVENT class of monitoring data is not to be
ON and collect performance-class and exception-class
collected.
data.
NOEXcept
Typing ? at the beginning of either the first or second line The exception class of monitoring data is not to be
gives a syntax prompt. Resetting the values takes effect collected.
immediately.
NOPerf
The performance class of monitoring data is not to be
55──CEMT Set MONitor──┬─────┬──┬────────┬──────5 collected.
├─ON──┤ ├─Perf───┤
└─OFf─┘ └─NOPerf─┘ NOSyncpoint
5──┬─────────┬──┬──────────┬───────────────────5 A transaction performance class record is not to be
├─EVent───┤ ├─EXcept───┤ produced when a transaction takes an explicit or implicit
└─NOEVent─┘ └─NOEXcept─┘ syncpoint (unit-of-work), except when the syncpoint is
5──┬────────────┬──┬─────────────┬─────────────5 part of task termination or a syncpoint rollback.
├─Converse───┤ ├─SYncpoint───┤
└─NOConverse─┘ └─NOSyncpoint─┘ OFf
5──┬──────────────────┬──5% CICS monitoring is to be switched off. When monitoring
└─Frequency(value)─┘ is OFF, no monitoring data is accumulated or collected,
irrespective of the settings of the monitoring data
classes.
Options
ON
Converse CICS monitoring is to be switched on. When monitoring
Conversational tasks are to have separate performance is ON, monitoring data is accumulated continuously, and
class records produced for each pair of terminal control is collected (written out to an SMF data set) for each of
I/O requests (Converse or Send/Receive pair). the classes of monitoring data that are active.
EVent Perf
The SYSEVENT class of monitoring data is to be The performance class of monitoring data is to be
collected. collected.
EXcept SYncpoint
The exception class of monitoring data is to be collected. A transaction performance class record is to be
produced when a transaction takes an explicit or implicit
Frequency(value) syncpoint (unit-of-work), except when the syncpoint is
specifies the interval for which monitoring produces part of task termination or a syncpoint rollback.
automatically a transaction performance class record for

CEMT SET NETNAME
CEMT SET NETNAME ACquired (vtam only)

CICS is in session with the logical unit represented by
Function: Change the status of networks. the terminal.
ALl
Description: If you are familiar with network names, you
specifies that any changes you request are made to all
may prefer to use this command as an alternative to CEMT
SET TERMINAL (described under “CEMT SET TERMINAL”
to access.
on page 204). However, CEMT SET NETNAME cannot be
used for APPC sessions. ATi (vtam only)
The terminal is available for use by transactions that are
“netname” is the name by which the remote system or initiated automatically from within CICS or, if the terminal
terminal is known to the network. The remaining operands for is an ISC session, by transactions that are using this
NETNAME are identical to those for TERMINAL. session as an alternative facility to communicate with
another system.
Netnames need not be unique, and you cannot specify a list
of names. AUtopageable (vtam only)
Pages after the first in a series are to be written to the
Syntax: Press the Clear key to clear the screen. There are terminal automatically.
COldacq (vtam only)
Type CEMT SET NETNAME (the minimum abbreviation is This is a special form of ACQUIRED, where no
CEMT S N) with netname or ALL. You get a display that resynchronization is required. If the previous session
lists the current status, similar to that obtained by CEMT abended, the use of COLDACQ overrides CICS integrity
INQUIRE NETNAME. You can then tab to the control. This could lead to integrity problems. Also, you
highlighted or blank fields and overtype them with the should check the CSMT log for an activity keypoint after
required values. the restart of a session following a CICS failure. If there
Type CEMT SET NETNAME (CEMT S AUTO) with netname or is no activity keypoint, you should issue COLDACQ
ALL, followed by one or more attribute settings that you again after the next emergency restart.
wish to change. For example, cemt s n(netname) i at
CReate (vtam only)
will reset the named remote system or terminal to
If the terminal is not in session, CICS is to acquire it if it
inservice and available for use.
is needed to satisfy an ATI request. This cannot be
Typing ? at the beginning of either the first or second line specified for IRC sessions.
gives a syntax prompt. Resetting the values takes effect Forcepurge
immediately. All transactions running with this terminal are
immediately terminated abnormally. Data integrity is not
55──CEMT Set Netname──┬─(value)─┬──────────────5 guaranteed. In some extreme cases (for example, if an
└─ALl─────┘ error occurs during backout processing), CICS might
terminate abnormally.
5──┬─────────────────┬──┬──────────────┬───────5
└─PRiority(value)─┘ ├─PAgeable─────┤ Inservice (vtam only)
└─AUtopageable─┘
The terminal is available for use. For VTAM, INSERVICE
5──┬────────────┬──┬───────┬──┬───────┬────────5 means that the terminal can be ACQUIRED.
├─Inservice──┤ ├─ATi───┤ ├─TTi───┤
└─Outservice─┘ └─NOAti─┘ └─NOTti─┘ NOAti (vtam only)
5──┬────────────┬──┬──────────┬────────────────5 The terminal is not available for use by transactions that
├─PUrge──────┤ ├─ACquired─┤ are initiated automatically from within CICS or, if the
└─Forcepurge─┘ ├─COldacq──┤ terminal is an ISC session, by transactions that are
using this session as an alternative facility to
5──┬──────────┬──5% communicate with another system.
├─CReate───┤
└─NOCreate─┘ Note: A terminal cannot be defined with both NOATI
and NOTTI.
Options NOCreate (vtam only)

If the terminal is not in session, CICS is not to acquire it
(value) to satisfy an ATI request. A session must be started by,
specifies the name by which the remote terminal is for example, a logon request or a CEMT SET
known in the network. TERMINAL ACQUIRED command before the ATI
request can be satisfied.

CEMT SET PROCESSTYPE
If NOCREATE is set for an LU6.1 ISC session and there | CEMT SET PROCESSTYPE
are no allocatable sessions left, the connection is placed
OUTSERVICE. | Function: Change the attributes of a CICS business
NOTti (vtam only) | transaction services process-type.
This terminal cannot be used by transactions.
| Description: SET PROCESSTYPE enables you to
Note: A terminal cannot be defined with both NOATI | change the current state of audit logging and the enablement
and NOTTI. | status of BTS PROCESSTYPE definitions installed on this
| CICS region.
Outservice (vtam only)
The terminal is not available for use. Setting a terminal | Note: Process-types are defined in the process-type table
OUTSERVICE means that the terminal can no longer be | (PTT). CICS uses the entries in this table to maintain
used by transactions. If PURGE or FORCEPURGE is | its records of processes (and their constituent
also specified, any transaction using the terminal is | activities) on external data sets. If you are using BTS
terminated abnormally. If PURGE or FORCEPURGE is | in a single CICS region, you can freely use the SET
not specified, the transaction is allowed to terminate | PROCESSTYPE command to modify your
normally, but no further transactions are allowed to use | process-types. However, if you are using BTS in a
the terminal. For VTAM, setting a terminal | CICSPlex, it is strongly recommended that you use
OUTSERVICE also causes it to be released and the | CPSM to make such changes. This is because it is
operator to be signed off, either immediately or when the | essential to keep resource definitions in step with
current transaction has terminated. | each other, across the CICSPlex.
In an LU6.1 ISC session the connection is set
| Syntax
OUTSERVICE if there are no allocatable sessions left.
|
To set an IRC session OUTSERVICE, you must set the
connection to the MRO partner OUTSERVICE. | ┌─ALl─────┐
| 55──CEMT Set PROCesstype──┼─────────┼──────────5
PAgeable (vtam only) | └─(value)─┘
Pages after the first in a series are to be written to the | 5──┬──────────┬──┬──────────┬──5%
terminal only if you request them to be. | ├─ACtivity─┤ ├─Enabled──┤
| ├─FUll─────┤ └─Disabled─┘
PRiority(value) (vtam only) (VTAM only) | ├─Off──────┤
specifies the priority of a terminal relative to other | └─Process──┘
terminals. The priority of a task is the sum of the
transaction priority, the terminal priority, and the operator
priority. Priority has no meaning for terminals that are | Options
ISC sessions being used as alternative facilities. The | ACtivity|FUll|Off|Process
value must be in the range 0–255, where 255 is the | specifies the level of audit logging to be applied to
highest priority. | processes of this type.
PUrge | Note: If the AUDITLOG attribute of the installed
Tasks running on this terminal are abnormally | PROCESSTYPE definition is not set to the name
terminated, but task termination occurs only if system | of a CICS journal, an error is returned if you try
integrity can be maintained. | to specify any value other than OFF.
RELeased (vtam only) | The values are:
CICS is not in session with the logical unit represented
| ACtivity
by the terminal. Setting a terminal RELEASED causes
| Activity-level auditing. Audit records will be written
the session to be terminated. Running transactions are
| from:
allowed to finish unless PURGE or FORCEPURGE is
also specified. | 1. The process audit points
| 2. The activity primary audit points.
TTi (vtam only)
This terminal can be used by transactions. | FUll Full auditing. Audit records will be written from:
| 1. The process audit points
| 2. The activity primary and secondary audit
| points.
| Off No audit trail records will be written.
| Process
| Process-level auditing. Audit records will be written
| from the process audit points only.

CEMT SET PROGRAM
| For details of the records that are written from the CEMT SET PROGRAM
| process, activity primary, and activity secondary audit
| points, see the CICS Business Transaction Services Function: Change the attributes of installed programs.
| manual.
Description: Only programs that have been defined in the
| ALl
CICS system definition (CSD) file and installed on the
| specifies that any changes you specify are made to all
running CICS system are accessible through CEMT.
| process-types that you are authorized to access.
| Enabled Disabled Syntax: Press the Clear key to clear the screen. There are
| specifies whether new processes of this type can be two ways of commencing this transaction:
| created. The values are: Type CEMT SET PROGRAM (the minimum abbreviation is
| Disabled CEMT S PR) with pgrmid, CLASS(value), or ALL. You get
| The installed definition of the process-type is a display that lists the current status, similar to that
| disabled. New processes of this type cannot be obtained by CEMT INQUIRE PROGRAM. You can then
| defined. tab to the highlighted or blank fields and overtype them
with the required values.
| Enabled
| The installed definition of the process-type is Type CEMT SET PROGRAM (CEMT S PR) followed by one or
| enabled. New processes of this type can be more attribute settings that you wish to change. For
| defined. example, cemt s pr(pgrmid) e ne will reset the values
for the named program to make it available for use
| PROCesstype(value) (enabled) and a new copy of the program will be used
| specifies the 8-character name of the process-type when all the transactions currently using the program
| whose attributes are to be changed. have finished (newcopy).

immediately.
55──CEMT Set Program──┬─(value)──────┬─────────5

├─CLass(value)─┤
└─ALl──────────┘
┌─PRIvate─┐
5──┬──────────┬──┼─────────┼──┬─────────┬──────5
├─Enabled──┤ └─Shared──┘ ├─NEwcopy─┤
└─DIsabled─┘ └─PHasein─┘
5──┬────────┬──┬───────────┬───────────────────5
├─CEDf───┤ ├─DPlsubset─┤
└─NOCedf─┘ └─Fullapi───┘
5──┬─────────────────┬──┬─────────┬────────────5
| └─JVMClass(value)─┘ ├─DEBUG───┤
| └─NODEBUG─┘
5──┬───────┬──5%
| ├─JVM───┤
| └─NOJVM─┘
Options
(value)
specifies a program identifier (1–8 characters), which is
the name of a specific program entry in the table of
installed program definitions. If you omit the program
name, the ALL option is assumed by default.
You cannot specify the CLASS option and a program
name.
ALl
specifies that any changes you request are to be made
to all resources of the specified type that you are
authorized to access.

CEMT SET PROGRAM
CEDf (RESCOUNT equal to zero). CICS loads the new

When EDF is active, CEDF initiation and termination version either from the DFHRPL library concatenation or
screens are to be shown by CEDF while this program is uses an LPA-resident version, depending on the
running. Other screens are also to be shown unless the PRIVATE or SHARED options. PRIVATE is the default
program was translated using the NOEDF translator setting.
option.
Note: NEWCOPY cannot be specified either for a
CLass(value) | program specified with the HOLD option. This
specifies the 2-character suffix of a program list table | value is ignored for a JVM program.
(PLT). Use this option to inquire on those programs
| NODebug
defined in the specified PLT. Note that, unlike a
| The JVM is not to operate in debug mode for this
shutdown PLT, it is not mandatory to define a program
| program.
definition for a startup PLT. However, if you want to use
the CLASS option, you must define and install a | NOJvm
program resource definition for the PLT specified by | The program is not to run under the control a a JVM.
“clasid”. | Any value in the JVMCLASS option is ignored and the
| runtime environment of the program is unknown until it is
If the clasid specified is the suffix of a PLT that does not
| next loaded by CICS, at which point its language, and
have a program definition, the INQUIRE PROGRAM
| hence whether it will run with LE370 support, will be
CLASS(clasid) command returns a ‘CLASS NOT
| determined.
FOUND’ message.
You cannot specify CLASS and a program name. NOCedf
All CEDF activities, including initiation and termination
| DEbug screens, are to stop while this program is being
| The JVM is to operate in debugging mode for this processed.
| program.
PHasein
DIsabled CICS is to use a new copy of the program now for all
The program is not available for use. Programs new transaction requests. CICS continues to use the old
beginning with “DFH” cannot be disabled because these copy for all currently running transactions until they have
characters are reserved for use by CICS. finished (RESCOUNT equal to zero). CICS loads the
new version either from the DFHRPL library
DPlsubset
concatenation or uses an LPA-resident version,
The program is restricted to the DPL API subset, as for
depending on the PRIVATE or SHARED options.
a distributed program link request, when it runs in the
PRIVATE is the default setting.
local CICS region.
Note: PHASEIN cannot be specified for a program
A program is always restricted to the DPL subset when it
| specified with the HOLD option. This value is
is invoked in a remote region via a DPL request,
| ignored for a JVM program.
regardless of this option.
PHASEIN performs a REFRESH PROGRAM function to
Enabled
inform the loader domain that a new version of the
The program is available for use.
program has been cataloged and that this version of the
Fullapi named program should be used in all future ACQUIRE
The program is not restricted to the DPL subset of the requests.
CICS API when it runs in the local CICS region, and can Until the program goes to a zero RESCOUNT and a
use the full API. subsequent ACQUIRE PROGRAM has been performed,
CEMT INQUIRE PROGRAM ( ) will return information on
| JVM
the first copy of the program.
| The program is to run under the control of a Java Virtual
| Machine (JVM). PRIvate
The next new copy of the program is to be loaded from
| JVMClass(value)
the DFHRPL library. This is the default action.
| specifies the name of the main JVM class in the JAVA
| program that is to be given control by the JVM. Shared
CICS is to use a shared copy of the program from the
NEwcopy
| LPA as the next new copy of the program. This value is
CICS is to use a new copy of the program when all the
| ignored for a JVM program.
transactions currently using the program have finished

CEMT SET QUEUE CEMT SET STATISTICS
CEMT SET QUEUE CEMT SET STATISTICS

Comments: See “CEMT SET TDQUEUE” on page 203. Function: Change statistics attributes.
(QUEUE is accepted for INQUIRE commands, but the
correct keyword is TDQUEUE.) Description: SET STATISTICS allows you to change
some of the values that control the accumulation and
recording of statistics.
For information about printing statistics using the

CICS-supplied utility program DFHSTUP, see the CICS
Operations and Utilities Guide.
NEXTTIME cannot be specified on an INQUIRE or SET

STATISTICS command, but its value is displayed when
INQUIRE STATISTICS is issued. NEXTTIME indicates the
time at which statistics will next be recorded and reset. If
SET STATISTICS is in the OFF condition, this is at the end
of the day. Otherwise, in the ON condition, it is the earlier
time of either the next interval to occur or the end of the day.
Type CEMT SET STATISTICS (the minimum abbreviation is
CEMT S ST). You get a display that lists the current
STATISTICS. You can then tab to the highlighted or
Type CEMT SET STATISTICS (CEMT S ST) followed by one
or more attribute settings that you wish to change. For
example, cemt s st on res will switch CICS statistics
ON and will reset the statistics counters.

immediately.
55──CEMT Set STatistics──┬─────┬───────────────5

├─ON──┤
└─OFf─┘
5───┬──────────┬────┬───────────┬──────────────5
└─RESetnow─┘ └─RECordnow─┘
5──┬──────────────────┬────────────────────────5
└─Interval(hhmmss)─┘
5──┬──────────────────┬──5%
└─Endofday(hhmmss)─┘
Options
Endofday(hhmmss)
specifies the end-of-day time for recording statistics. At
end-of-day, the current values of the CICS statistics
counters are written out to an SMF data set and the
statistics counters are reset.
End-of-day times must be in the range 000000-235959.
The default end-of-day time is 12 midnight (000000).

CEMT SET STATISTICS
Interval(hhmmss) If you want your end-of-day recordings to cover 24

specifies the length of time during which the statistics hours, set INTERVAL to 240000.
counters are incremented. At the end of each interval,
OFf
the accumulated statistics are recorded and the statistics
The recording of interval statistics is switched OFF.
counters are reset.
(End-of-day, requested, and unsolicited statistics are
Interval times must be in the range 000100-240000. The always recorded.) Counters are still incremented as
default interval value is 030000. These interval settings usual and the recording of end-of-day, requested, and
only take place if you set the statistics recording status unsolicited statistics is still made. Statistics can be
to ON. You can set the statistics recording status ON or recorded at any time by issuing a CEMT PERFORM
OFF using the RECORDING option on this command or STATISTICS command.
by using the STATRCD system initialization parameter.
ON
The arrival of the ENDOFDAY time always causes the
The recording of interval statistics is switched ON.
current interval to be ended (possibly prematurely) and a
Counters are incremented as usual, and are reset at the
new interval to be started. Only end-of-day statistics are
expiry of each interval and at end-of-day. Statistics can
recorded at the end-of-day time, even if it coincides
be recorded at any time by issuing a CEMT PERFORM
exactly with the expiry of an interval.
STATISTICS command.
Changing the ENDOFDAY value has an immediate
RECordnow
effect on the times at which INTERVAL statistics are
The existing statistics are to be written to an SMF data
recorded. New interval expiry times are recalibrated in
set. The statistics that you are given are those collected
accordance with the new end-of-day time.
since the last ENDOFDAY or INTERVAL collection, or
When you change the INTERVAL value or the since the last time the RESETNOW function was used in
ENDOFDAY value (and also when CICS is initialized), this or the PERFORM STATISTICS command.
the length of the current (or first) interval is adjusted so RECORDNOW RESETNOW only takes effect when the
that it expires after an integral number of intervals from recording status is changed.
the end-of-day time.
Note: RECORDNOW RESETNOW both resets the
These rules are illustrated by the following example, statistics counter and also writes the existing
where I indicates an interval recording, INTERVAL is set statistics to an SMF data set. The statistics that
at 3-hourly intervals, CICS is initialized at 0815 hours, you are given are those collected since the last
and E indicates the ENDOFDAY setting at 1700 hours. ENDOFDAY or INTERVAL collection, or since
the last time the RESETNOW function was used
┌]─ CICS initialized with
│ ENDOFDAY(17ðððð) in this or the PERFORM STATISTICS command.
│ INTERVAL(ð3ðððð) RECORDNOW RESETNOW only takes effect
│ when the recording status is changed.
│
│ RESetnow
│ The statistics counters are to be reset. The reset takes
│ effect only if the recording option is changed from OFF
│ to ON or from ON to OFF. For information about the
6
]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬]]]]┬ effect of reset on each individual counter, see the CICS
ð8 ð9 1ð 11 12 13 14 15 16 17 statistics tables in the CICS Performance Guide.
I I E
The action, for each counter, is one of the following:
Note: In this example, there would have been an Not reset

interval at 0800 hours if CICS had been Reset to zero
initialized earlier. Reset to 1
Reset to current value (this applies to peak values)
An exception to the above.

CEMT SET SYDUMPCODE
CEMT SET SYDUMPCODE Type CEMT SET SYDUMPCODE (CEMT S SYD) with code or
ALL, followed by one or more attribute settings that you
Function: Change the attributes of the system dump wish to change. For example, to add a system dump
codes. code:
CEMT SET SYDUMPCODE(value) ADD
Description: SET SYDUMPCODE allows you to define
To remove a system dump code:
the entries that you require in the system dump table. You
control system dumps by creating an entry in the system CEMT SET SYDUMPCODE(value) REMOVE
dump table for each dump code that requires a change from To change the maximum count to 10:
the default action.
CEMT SET SYDUMPCODE(value) MAX(1ð)
A system dump code is the CICS message number with the Shut down CICS on occurrence of this system dump
DFH prefix removed. Typically this leaves a 6-character code:
code comprising 2 alphabetic characters and 4 numeric
CEMT SET SYDUMPCODE(value) SHUTDOWN
characters, for example AP0001. The command syntax
permits up to 8 characters for the dump code, and the dump Typing ? at the beginning of either the first or second line
codes you specify are padded with trailing spaces. gives a syntax prompt. Resetting the values takes effect
immediately.
Each message has its own system default actions that you
cannot necessarily override with the SET command. For
example, when a serious error occurs, CICS shuts down 55──CEMT Set SYDumpcode──┬─(value)─┬───────────5
even if you have asked for no shut down. See the CICS └─ALl─────┘
Messages and Codes manual for information about the 5──┬───────────┬──┬────────────┬───────────────5
system action for each message. ├─SYsdump───┤ ├─SHutdown───┤
└─NOSYsdump─┘ └─NOSHutdown─┘
There are other system parameters that take priority over
5──┬─────────┬──┬────────────────┬─────────────5
your dump table entries. For example, EXEC CICS SET ├─RELated─┤ └─Maximum(value)─┘
SYSTEM NOSYSDUMP, or a DUMP=NO system initialization └─Local───┘
parameter, inhibits system dumping. For more information on 5──┬────────┬──┬───────┬──5%
using dumps, see the CICS Problem Determination Guide. ├─RESet──┤ ├─Dae───┤
├─REMove─┤ └─NODae─┘
The transaction dump command SET TRDUMPCODE can └─ADd────┘
also cause CICS to produce system dumps for the specified
transaction dump code.
Options
The SET command allows you to:
(value)
Add a new entry to the system dump table specifies an 8-character system dump code. See the
Remove an entry from the system dump table CICS Messages and Codes manual for details of the
Indicate whether or not you want a system dump taken codes.
Indicate whether the system dump request is to be local
or related ADd
Indicate whether or not you want CICS to shut down This system dump code is added to the system dump
following the dump code table.
Set the maximum number of dumps
ALl
Reset the counter of the current number of dumps to
zero
Determine whether or not a dump produced by CICS is
to access.
eligible for any suppression by the MVS Dump Analysis
and Elimination (DAE) component. Dae
A system dump is eligible for suppression by the DAE
Syntax: Press the Clear key to clear the screen. There are component.
Local
Type CEMT SET SYDUMPCODE (the minimum abbreviation is
A system dump request is not to be sent to other MVS
CEMT S SYD) with code or ALL. You get a display that
images in the sysplex for this system dump code.
lists the current status, similar to that obtained by CEMT
INQUIRE SYDUMPCODE. You can then tab to the Maximum(value)
highlighted or blank fields and overtype them with the specifies the maximum number of dump calls for this
required values. system dump code that result in system dumps being
taken. The value must be in the range 0-999; a value of
999 means the default, ‘no limit’.

CEMT SET SYDUMPCODE
NODae CICS regions related to the CICS region on which the

A system dump will not be suppressed by the DAE dump is initiated.
component. (However, be aware of the SUPPRESS and
Note: A related CICS region is one in which the unit of
SUPPRESSALL options in the ADYSETxx parmlib
work identifiers, in the form of APPC tokens, of
member. These are controlled by the VRADAE and
VRANODAE keys in the SDWA. They may lead to dump
suppression even though NODAE is set here. For
information about DAE, SUPPRESS, and REMove
SUPPRESSALL, see the OS/390 MVS Diagnosis: Tools This system dump code is removed from the system
and Service Aids manula. dump code table.
NOSHutdown RESet
CICS is not to be shut down after the occurrence of an The current number of calls for this dump code is reset
error corresponding to this dump code. to zero.
NOSYsdump SHutdown
A system dump is not to be taken for this system dump CICS is to be shut down.
code.
SYsdump
RELated A system dump is to be taken for this system dump
A system dump request is to be sent to MVS images in code.
the sysplex which are running XCF/MRO connected

CEMT SET SYSTEM
CEMT SET SYSTEM

Function: Change the system attributes.
Syntax: Press the Clear key to clear the screen. There are two ways of commencing this transaction:
Type CEMT SET. The SYSTEM keyword does not have to be typed. If you type just CEMT SET, SYSTEM is assumed as the
default. You get a display that lists the current status, similar to that obtained by CEMT INQUIRE SYSTEM. You can then
tab to the highlighted or blank fields and overtype them with the required values.
Type CEMT SET followed by one or more attribute settings that you wish to change. For example, cemt s ag(value)
ma(value) resets the values for priority aging and the maximum number of tasks allowed at any one time in the CICS
system.
Typing ? at the beginning of either the first or second line gives a syntax prompt. Resetting the values takes effect immediately.
┌──
────────────────────────┐
55──CEMT Set SYStem───6┬──────────────────────┬┴──5%
├─AGing(value)─────────┤
├─AKp(value)───────────┤
├─DSAlimit(value)──────┤
| ├─DSRtprogram(value)───┤
├─DTrprogram(value)────┤
├─EDsalimit(value)─────┤
| ├─Forceqr─┬─Force───┬──┤
| │ └─NOForce─┘ │
| ├─Logdefer(value)──────┤
| ├─MAXOpentcbs(value)───┤
├─MAxtasks(value)──────┤
├─MRobatch(value)──────┤
├─┬─CTLGAll────┬───────┤
│ ├─CTLGModify─┤ │
│ └─CTLGNone───┘ │
├─Progautoexit(value)──┤
├─┬─AUTOActive───┬─────┤
│ └─AUTOInactive─┘ │
├─RUnaway(value)───────┤
├─SCandelay(value)─────┤
├─Time(value)──────────┤
└─┬─SYsdump───┬────────┘
└─NOSysdump─┘
Options AUTOActive
Autoinstall for programs is active. On first use, if a
AGing(value) program, mapset, or partitionset is not defined, the
specifies the time factor for CICS to use in the priority definition is created dynamically.
aging algorithm for incrementing the priority of a task.
The value is expressed as “milliseconds per unit of AUTOInactive
priority”, and must be in the range 00000–65535. The Autoinstall is not active. If a program is not defined, a
priority aging factor is defined initially by the PRTYAGE PGMIDERR or transaction abend occurs when it is
system initialization parameter, in which the value referenced.
represents the number of milliseconds that must elapse
CTLGAll
before the priority of a waiting task can be adjusted
All autoinstalled program definitions are to be cataloged
upward by 1. See the CICS System Definition Guide for
and restored on a warm or emergency restart.
information about the PRTYAGE parameter.
CTLGModify
AKp(value)
Autoinstalled program definitions are to be cataloged
specifies the activity keypoint trigger value, which is the
only if they are modified (for example, by a CEMT SET
number of write requests to the CICS system log stream
PROGRAM command), so that the modified definitions
output buffer between the taking of keypoints. It must
are restored on a warm or emergency restart.
have a value in the range 00200–65535. You cannot
change this value if AKPFREQ=0 was specified at CTLGNone
system initialization. No autoinstalled program definitions are to be cataloged.
They are autoinstalled again after a warm or emergency
restart.

CEMT SET SYSTEM
DSAlimit(value) MAxtasks(value)
specifies the maximum amount of storage, as a total specifies the maximum number of tasks, both active and
number of bytes, within which CICS can dynamically suspended, allowed at any one time in the CICS system.
allocate storage for the four individual DSAs that reside It must have a value in the range 1–999.
below the 16MB boundary. See the CICS System
Note: The value assigned to MAXTASKS might be less
Definition Guide for a description of the DSALIM system than the requested value, because of CICS
initialization parameter.) If DSALIMIT specifies a value
storage constraints. If this occurs, the message
lower than the current limit, CICS may not be able to
CEILING REACHED is displayed when the
implement the new limit immediately, but will attempt to
request is made.
do so over time as dynamic storage is freed in the
individual DSAs. MRobatch(value)
specifies the number of MRO requests from connected
| DSRtprogram(value)
regions that are to be batched before this region is
| specifies the name of the distributed routing program.
posted. It must have a value in the range 001–255.
| DTrprogram(value)
| NOForce
| specifies the name of the dynamic routing program.
| Do not force user application programs to run under the
EDsalimit(value) | QR TCB. CICS is to honor the
specifies the maximum amount of storage, as a total | CONCURRENCY(THREADSAFE) attribute on user
number of bytes, within which CICS can dynamically | application programs, and allow user programs to run on
allocate storage for the four individual DSAs that reside | an open TCB to avoid unnecessary TCB switching.
above the 16MB boundary. See the CICS System
NOSysdump
Definition Guide for a description of the EDSALIM specifies that system dumps are to be suppressed.
system initialization parameter.) If EDSALIMIT specifies
a value lower than the current limit, CICS may not be Progautoexit(value)
able to implement the new limit immediately, but will specifies the name of the user-provided program that is
attempt to do so over time as dynamic storage is freed called by the program autoinstall code to select or
in the individual DSAs. modify a model definition.
| Force RUnaway(value)
| Force all user application programs to run under the QR specifies the interval, in milliseconds, for which a task
| TCB, even if they are defined with the can have control before it is assumed to be looping.
| CONCURRENY(THREADSAFE) attribute.
You can specify 0, or a value in the range 500–2700000.
| Logdefer(value) The value chosen is rounded down to a multiple of 500.
| specifies the log deferral interval in milliseconds, which CICS purges a task if it has not given up control after
| is the period of time used by CICS Log Manager when this interval (that is, if the task appears to be looping). If
| determining how long to delay a forced journal write you specify zero, runaway task control is inoperative
| request before invoking the MVS system logger. It is in (that is, tasks do not get purged if they appear to be
| the range 0-65535. See the CICS System Definition looping). The value is independent of, and can be less
| Guide for information about the Logdefer parameter and than, the value in the TIME operand.
| associated SIT parameter LGDFINT. CICS runaway-task detection is based upon task time,
that is, the interval is decremented only when the task
| MAXOpentcbs(value)
has control of the processor. You do not, therefore, need
| specifies the maximum number of open TCBs that can
to allow for the effect of other jobs when setting the
| exist concurrently in the CICS region. The value
value.
| specified can be in the range 1 to 999. If you reduce
| MAXOPENTCBS from its previously defined value, and SCandelay(value)
| the new value is less than the number of open TCBs specifies the maximum number of milliseconds between
| currently allocated, CICS detaches TCBs to achieve the the receipt of a VTAM request, and the time when CICS
| new limit only when they are freed by user tasks. begins to process the request. The number must be in
| Transactions are not abended to allow TCBs to be the range 0–5000, and must be less than or equal to the
| detached to achieve the new limit. If there are tasks TIME value.
| queued waiting for an open TCB, and you increase
In the summary report of the dispatcher statistics,
| MAXOPENTCBS from its previously defined value, they
SCANDELAY is referred to as ICVTSD.
| will be resumed when CICS attaches new TCBs up to
| the new limit. SYsdump
specifies that system dumps are not to be suppressed.

CEMT SET TASK
Time(value) CEMT SET TASK

specifies the interval, in milliseconds, for which CICS
releases control to the operating system if no Function: Change the status of tasks.
transactions are ready to resume processing. This
interval is known as the ‘region exit interval’. Description: You cannot specify a list of identifiers, nor
It can have a value in the range 100–3600000, and must can you use the symbols * and + to specify a family of tasks.
be greater than or equal to the SCANDELAY value.
In the summary report of the dispatcher statistics, TIME two ways of commencing this transaction:
is referred to as ICV.
Type CEMT SET TASK (the minimum abbreviation is CEMT
S TA) with (value) or ALL. You get a display that lists the
INQUIRE TASK. You can then tab to the highlighted or
Type CEMT SET TASK (CEMT S TA) with number or ALL,
followed by one or more attribute settings that you wish
to change. For example, cemt s ta(value) pu will make
the specified task purgeable in system-stall conditions.

immediately.
55──CEMT Set TAsk──┬─(value)─┬─────────────────5

└─All─────┘
5──┬─────────────────┬──┬────────────┬──5%
└─PRiority(value)─┘ ├─PUrge──────┤
└─FOrcepurge─┘
Options
(value)
The CICS-generated task number. This is in the range
1–99999.
All Any changes you request are made to all resources of

the specified type that you are authorized to access.
FOrcepurge
The task is terminated immediately. System integrity is
not guaranteed. In some extreme cases, for example if a
task is forcepurged during backout processing, CICS
terminates abnormally. If you want to terminate a task
but do not want to terminate CICS, you should use
PURGE instead of FORCEPURGE.
PRiority(value)
specifies the priority of the task, in the range 0–255
where 255 is the highest priority.
PUrge
The task is terminated. Task termination occurs only
when system and data integrity can be maintained.

CEMT SET TCLASS CEMT SET TCPIP
CEMT SET TCLASS | CEMT SET TCPIP

Function: Reset the maximum number of tasks and the | Function: Modify CICS internal TCP/IP support.
purge threshold for a transaction class.
| Description: SET TCPIP allows you to open or close
Syntax: Press the Clear key to clear the screen. There are | CICS internal sockets support.
| Note: This command has no effect on the sockets support
Type CEMT SET TCLASS (the minimum abbreviation is | provided by the TCP/IP for OS/390 CICS Sockets
CEMT S TC) with (value) or ALL. You get a display that | Feature.
lists the current status, similar to that obtained by CEMT
INQUIRE TCLASS. You can then tab to the highlighted | Syntax: Press the Clear key to clear the screen. There are
or blank fields and overtype them with the required | two ways of commencing this transaction:
values. | Type CEMT SET TCPIP (the minimum abbreviation is CEMT
Type CEMT SET TCLASS (CEMT S TC) followed by one or | S TCPIP). You get a display that lists the current status,
more attribute settings that you wish to change. For | similar to that obtained by CEMT INQUIRE TCPIP. You
example, cemt s tc(value) p(3) will reset the purge | can then tab to the highlighted or blank fields and
threshold value to 3. | overtype them with the required values.
| Type CEMT SET TCPIP (CEMT S TCPIP) with (value) or
| ALL, followed by one or more attribute settings that you
| wish to change. For example, cemt s tcpip status open
immediately.
| opens CICS internal sockets support.
| Typing ? at the beginning of either the first or second line

55──CEMT Set TClass──┬─(value)─┬───────────────5
└─ALl─────┘ | gives a syntax prompt. Resetting the values takes effect
| immediately.
5──┬──────────────────┬────────────────────────5
└─Maxactive(value)─┘ |
5──┬────────────────────┬──5% | 55──CEMT Set TCPIP──┬─(value)─┬────────────────5
└─Purgethresh(value)─┘ | └─ALl─────┘
| 5──┬─Openstatus(cvda)─┬──5%
| ├─OPEN─────────────┤
Options | ├─CLOSE────────────┤
| └─IMMCLOSE─────────┘
(value)
specifies the 8-character transaction class name. If no
transaction class name is assigned, it defaults to | Options
DFHTCL00.
| STATUS
ALl | specifies whether or not TCPIP is to be opened (that is,
specifies that any changes you request are made to all | able to process new incoming work, and complete
resources of the specified type that you are authorized | ongoing work), and if TCP/IP support is to be closed,
to access. | how the close should be done. CVDA values are:
Maxactive(value) | OPEN CICS internal sockets support is to be
specifies the largest number of transactions in the | opened
transaction class which are allowed to run concurrently.
The value can be in the range 0-999. | CLOSE CICS internal sockets is to be closed. If it is
| currently open, CICS is to quiesce all
Purgethresh(value) | internal sockets activity and then close any
specifies the limit at which the queuing transactions are | sockets on which CICS is listening for
purged for the transaction class. It can have a value in | incoming work. Tasks using CICS internal
the range 0–1000000. Zero means that the transactions | sockets are allowed to complete.
are not purged. A nonzero number “n” means that the
| IMMCLOSE CICS internal sockets is to be closed. If it is
first (n-1) transactions to arrive are queued and the nth
| currently enabled, CICS is to terminate
is purged.
| abnormally any tasks using it and then close
| the socket on which CICS is listening for
| incoming work.

CEMT SET TCPIPSERVICE
| CEMT SET TCPIPSERVICE | IMMCLOSE CICS internal sockets support is to stop

| listening for incoming work on the specified
| Function: Modify the status of a service using CICS | port immediately. Any active tasks using this
| internal TCP/IP support | service are terminated abnormally.
| URM
| Description: SET TCPIPSERVICE allows you to update
| specifies the 8-character name of the program to be
| the information relating to a service which uses CICS internal
| used as the Service User-replaceable module by the
| TCP/IP support.
| attached task. You can specify either an installation
| Note: This command has no effect on the sockets support | specific program or the CICS-supplied default for the
| provided by the TCP/IP for OS/390 CICS Sockets | service.
| Feature.
| Note: This program and any programs it invokes must
| be installed before they can be used in the
| Syntax: Press the Clear key to clear the screen. There are
| program autoinstall process. You can do this
| either with explicit PROGRAM definitions or by
| Type CEMT SET TCPIPSERVICE (the minimum abbreviation | autoinstall when some other autoinstall program
| is CEMT S TCPIPS). You get a display that lists the | is in force. Otherwise the program autoinstall
| current status, similar to that obtained by CEMT | process fails when it is next used, and CICS
| INQUIRE TCPIPSERVICE. You can then tab to the | makes it inactive.
| highlighted or blank fields and overtype them with the
| required values.
| Type CEMT SET TCPIPS (CEMT S TCPIPS) with (value) or
| ALL, followed by one or more attribute settings that you
| wish to change. For example, cemt s tcpips status
| open opens CICS internal sockets support.

| gives a syntax prompt. Resetting the values takes effect
| immediately.
|
| 55──CEMT Set TCPIPSERVICE──┬─(value)─┬─────────5
| └─ALl─────┘
| 5──┬────────────────┬──┬──────────────────┬────5
| └─Backlog(value)─┘ ├─Openstatus(cvda)─┤
| ├─OPEN─────────────┤
| ├─CLOSE────────────┤
| └─IMMCLOSE─────────┘
| 5──┬────────────┬──5%
| └─URM(value)─┘
| Options
| BACKLOG
| changes the maximum number of requests which can be
| queued in TCP/IP waiting to be processed by the
| service. The service must be CLOSED before you can
| change this value. If you set BACKLOG to zero, CICS
| does not receive any connections.
| Status
| Changes the status of the service. CVDA values are:
| OPEN CICS internal sockets support is to start

| listening for incoming requests on the
| specified port.
| CLOSE CICS internal sockets support is to stop
| listening for incoming work on the specified
| port. All active tasks using this service are
| allowed to complete.

CEMT SET TDQUEUE
CEMT SET TDQUEUE disabled until the UOW commits or backs out at
syncpoint. You are recommended to issue an EXEC
Function: Change the attributes of transient data queues. CICS SYNCPOINT command before attempting to
update the queue attribute (ATITRANID) using SET
Description: The SET TDQUEUE command changes TDQUEUE.
some of the attributes of a transient data queue. The queue
must not be REMOTE or INDIRECT. Syntax: Press the Clear key to clear the screen. There are
You cannot alter the following attributes unless the queue is Type CEMT SET TDQUEUE (the minimum abbreviation is
fully disabled: CEMT S TD) with destid or ALL. You get a display that
ATIFACILITY lists the current status, similar to that obtained by CEMT
ATITERMID INQUIRE TDQUEUE. You can then tab to the
ATITRANID. highlighted or blank fields and overtype them with the
required values.
To disable a transient data destination, the queue must not
Type CEMT SET TDQUEUE (CEMT S TD) with (value) or ALL,
currently be in use. If it is in use, the queue enters a “disable
followed by one or more attribute settings that you wish
pending” state. The last unit of work (UOW) to use the queue
to change. For example, cemt s td(value) en op will
fully disables it. The TRIGGERLEVEL, OPENSTATUS, and
make a named extrapartition queue accessible by
ENABLESTATUS attributes may be altered regardless of
applications and open.
whether the queue is enabled or disabled. The value of the
ENABLESTATUS attribute cannot be altered while a queue Typing ? at the beginning of either the first or second line
is in a “disable pending” state. gives a syntax prompt. Resetting the values takes effect
immediately.
A transient data queue cannot be disabled:
While it is in use
While tasks are waiting to use it. 55──CEMT Set TDqueue──┬─(value)─┬──────────────5
└─All─────┘
Indirect and remote queues can be disabled at any time 5──┬─────────────────────┬──┬──────────┬───────5
because they have no concept of being “in use”. └─TRIggerlevel(value)─┘ ├─ENabled──┤
└─DIsabled─┘
If tasks are waiting to use an extrapartition queue, a 5──┬────────┬──5%
physically recoverable queue, or a nonrecoverable ├─OPen───┤
intrapartition queue and an attempt is made to disable the └─Closed─┘
queue, the queue enters a “disable pending” state. The last
task to use the extrapartition queue fully disables it.
Options
If an attempt is made to disable a logically recoverable
intrapartition TD queue when there are UOWs enqueued (value)
upon it, the queue enters a “disable pending” state. The last specifies the identifier (1-4 characters) of a transient
UOW to obtain the enqueue fully disables the queue. If a data queue.
UOW has updated a logically recoverable queue and suffers All specifies that any changes you request are made to all
an indoubt failure, the queue cannot be disabled until the resources of the specified type that you are authorized
indoubt failure has been resolved. to access.
If a UOW owns an enqueue on a queue that is in a “disable Closed
pending” state, it is allowed to continue making updates. The queue is closed.
When a queue is in a “disable pending” state, no new tasks DIsabled

can alter the queue’s state or its contents. A disabled The queue cannot be accessed by applications, although
response is returned when a READQ, WRITEQ, or it can still be open. A queue that has suffered an indoubt
DELETEQ request is issued against a destination that is in a failure cannot be disabled.
“disable pending” state.
ENabled
Note: If a task updates a logically recoverable transient The queue can be accessed by applications.
data queue, and attempts to disable the queue and OPen
alter an attribute of the queue (for example, The extrapartition queue is open.
ATITRANID) within the same UOW, the call fails. This
is because the UOW is a user of the queue, and the TRIggerlevel(value)
queue enters a “disable pending” state. The SET specifies the number (0-32767) of requests for output to
operation on the queue attribute, in this case a queue that there must be before automatic transaction
ATITRANID, fails. The queue does not become fully initiation (ATI) occurs. Specifying zero disables ATI.

CEMT SET TERMINAL
CEMT SET TERMINAL

55──CEMT Set TErminal──┬─(value)──────┬────────5
Function: Change the attributes of named terminals. └─ALl──────────┘
Description: The SET TERMINAL command changes 5──┬─────────────────┬──┬──────────────┬───────5

└─PRiority(value)─┘ ├─PAgeable─────┤
some of the values of a named terminal defined in the └─AUtopageable─┘
terminal control table (TCT). It cannot be used for APPC
5──┬────────────┬──┬───────┬──┬───────┬────────5
sessions. ├─Inservice──┤ ├─ATi───┤ ├─TTi───┤
└─Outservice─┘ └─NOAti─┘ └─NOTti─┘
In an SNA environment, a terminal is the CICS
representation of an SNA logical unit with which CICS can be 5──┬────────────┬──┬──────────┬────────────────5
├─PUrge──────┤ ├─ACquired─┤
in communication. (SNA environment means that CICS is ├─Forcepurge─┤ ├─COldacq──┤
using VTAM or ACF/TCAM GSA as the access method for └─CAncel─────┘ └─RELeased─┘
communication with SNA logical units.)
5──┬──────────┬──5%
├─CReate───┤
This logical unit can be: └─NOCreate─┘
A physical terminal (such as a 3277)
A function of a cluster controller (such as a 3790 Type 2 Options
batch function)
(value)
An intersystem communication (ISC) or interregion
A terminal identifier (1-4 characters) as specified in an
communication (IRC) session that has been generated
installed terminal definition.
by the CEDA transaction.
If the terminal name is, for example, S201, this option is
If you are familiar with network names, you may prefer to use coded thus:
the command that uses these names. See “CEMT SET
CEMT SET TERMINAL(S2ð1)
NETNAME” on page 190.
ACquired (vtam only)
The message “TEMP OUT SERVICE” can be displayed if CICS is in session with the logical unit represented by
recovery is in progress for the terminal. The ”TEMP OUT the terminal.
SERVICE” indicator is reset by simply refreshing the screen,
or by overtyping the “INS” field with “INS” or “OUT”. If “TEMP ALl
OUT SERVICE” continues to be displayed, the cause of the Any changes you request are made to all resources of
indicator should be investigated. the specified type that you are authorized to access.
ATi (vtam only)

The terminal is available for use by transactions that are
initiated automatically from within CICS or, if the terminal
Type CEMT SET TERMINAL (the minimum abbreviation is is an ISC session, by transactions that are using this
CEMT S TE) with (value), CLASS(value), or ALL. You get session as an alternative facility to communicate with
a display that lists the current status, similar to that another system.
obtained by CEMT INQUIRE TERMINAL. You can then
tab to the highlighted or blank fields and overtype them AUtopageable (vtam only)
with the required values. Pages after the first in a series are to be written to the
terminal automatically.
Type CEMT SET TERMINAL (CEMT S TE) with (value),
CLASS(value), or ALL, followed by one or more attribute CAncel
settings that you wish to change. For example, cemt s AIDs queuing for the specified terminal are canceled.
te(value) i cr specifies that a named terminal is AIDs representing scheduled and allocated requests
available for use (inservice) and that it can be acquired waiting in the local CICS system for the specified
automatically by ATI transactions (create). terminal are canceled. However, TD AIDs with an
associated triggered task already started are not
Typing ? at the beginning of either the first or second line canceled.
When a canceled scheduled request is found to have a
immediately.
precursor in a remote CICS system, this remote AID is
canceled asynchronously. Message DFHTF0100 is
written to CSMT to indicate how many AIDs have been
deleted for the terminal and how many remain.
An ‘AIDS CANCELED’ message appears on the CEMT
panel whenever AIDs are deleted using the CANCEL
option of the CEMT SET TERMINAL command.

CEMT SET TERMINAL
CLass(value) OUTSERVICE also causes it to be released and the

The 1-or 2-character suffix of a terminal list table (TLT). operator to be signed off, either immediately or when the
current transaction has terminated.
COldacq (vtam only)
This is a special form of ACQUIRED, where no In an LU6.1 ISC session the connection is set
resynchronization is required. If the previous session OUTSERVICE if there are no allocatable sessions left.
abended, the use of COLDACQ overrides CICS integrity To set an IRC session OUTSERVICE, you must set the
control. This could lead to integrity problems. Also, you connection to the MRO partner OUTSERVICE.
should check the CSMT log for an activity keypoint after
the restart of a session following a CICS failure. If there PAgeable (vtam only)
is no activity keypoint, you should issue COLDACQ Pages after the first in a series are to be written to the
again after the next emergency restart. terminal only if you request them to be.
CReate (vtam only) PRiority(value) (vtam only)

If the terminal is not in session, CICS is to acquire it if it specifies the priority of a terminal relative to other
is needed to satisfy an ATI request. terminals. The priority of a task is the sum of the
transaction priority, the terminal priority, and the operator
Forcepurge priority. Priority has no meaning for terminals that are
Any transaction running with this terminal is immediately ISC sessions being used as alternative facilities. The
terminated abnormally. Data integrity is not guaranteed. value must be in the range 0–255, where 255 is the
In some extreme cases (for example, if an error occurs highest priority.
during backout processing), CICS might terminate
abnormally. PUrge
Any transaction running with this terminal is purged only
Inservice if system and data integrity can be maintained.
The terminal is available for use. For VTAM, INSERVICE
means that the terminal can be ACQUIRED. RELeased (vtam only)
CICS is not in session with the logical unit represented
NOAti (vtam only) by the terminal. Setting a terminal RELEASED causes
The terminal is not available for use by transactions that the session to be terminated. Running transactions are
are initiated automatically from within CICS or, if the allowed to finish unless PURGE or FORCEPURGE is
terminal is an ISC session, by transactions that are also specified.
using this session as an alternative facility to
communicate with another system. TTi (vtam only)
This terminal can be used by transactions.
Note: A terminal cannot be defined with both NOATI
and NOTTI.
NOCreate (vtam only)

If the terminal is not in session, CICS is not to acquire it
to satisfy an ATI request. A session must be started by,
for example, a logon request or a CEMT SET
TERMINAL ACQUIRED command before the ATI
request can be satisfied.
If NOCREATE is set for an LU6.1 ISC session and there
are no allocatable sessions left, the connection is placed
OUTSERVICE.
NOTti (vtam only)

This terminal cannot be used by transactions that are
initiated from this terminal.
Note: A terminal cannot be defined with both NOATI
and NOTTI.
Outservice
The terminal is not available for use. Setting a terminal
OUTSERVICE means that the terminal can no longer be
used by transactions. If PURGE or FORCEPURGE is
also specified, any transaction using the terminal is
terminated abnormally. If PURGE or FORCEPURGE is
not specified, the transaction is allowed to terminate
normally, but no further transactions are allowed to use
the terminal. For VTAM, setting a terminal

CEMT SET TRANSACTION
CEMT SET TRANSACTION from being shipped to a remote region. When a

task is attached for the requested transaction,
Function: Change some of the attributes of a selected CICS checks that the transaction is enabled in
transaction. the remote region.
Enabled
The transaction is available for use.
Type CEMT SET TRANSACTION (the minimum abbreviation NOTpurgeable
is CEMT S TRANS) with (value), CLASS(value), or ALL. The transaction cannot be purged.
You get a display that lists the current status, similar to PRIority(value)
that obtained by CEMT INQUIRE TRANSACTION. You specifies the priority of a transaction relative to other
can then tab to the highlighted or blank fields and transactions. When a transaction is running as a CICS
overtype them with the required values. task, the priority of a task is the sum of the transaction
Type CEMT SET TRANSACTION (CEMT S TRANS) followed by priority, the terminal priority, and the operator priority.
one or more attribute settings that you wish to change. The “value” must be in the range 0–255, where 255 is
For example, cemt s trans(value) e pu specifies that a the highest priority.
named transaction is available for use (enabled) and is
PUrgeable
system-purgeable.
The transaction is system-purgeable. This operand
Typing ? at the beginning of either the first or second line relates to the SPURGE parameter on the transaction
gives a syntax prompt. Resetting the values takes effect resource definition and indicates that CICS can purge
immediately. the transaction in a deadlock time-out situation. See the
CICS Resource Definition Guide for information about
the SPURGE and DTIMEOUT parameters on a
55──CEMT Set TRAnsaction──┬─(value)──────┬─────5 transaction resource definition.
└─ALl──────────┘ TClass(value)
5──┬─────────────────┬──┬───────────────┬──────5 specifies the 8-character transaction class name to
└─PRIority(value)─┘ └─TClass(value)─┘ which the transaction belongs. If the transaction does
not belong to a class, DFHTCL00 is returned. The
5──┬──────────┬──┬──────────────┬──5%
├─Enabled──┤ ├─PUrgeable────┤ abbreviation for TCLASS is Tcl. To remove a transaction
└─Disabled─┘ └─NOTpurgeable─┘ from its TCLASS, the Tcl field should be set to
DFHTCL00. A series of blanks can be inserted, in which
case, DFHTCL00 is returned. An added or changed
Options TClass must be defined.
(value)
specifies a transaction identifier (1-4 characters). Only
transactions that have been defined in the CICS system
definition (CSD) file and installed on the running CICS
system are accessible through CEMT.
ALl
to access.
CLass(value)
specifies the 2-character suffix of a transaction list table
(XLT).
Disabled
The transaction is not available for use. Transactions
that have identifiers beginning with “C” cannot be
disabled because these are reserved for use by CICS.
When the CEMT SET TRANSACTION DISABLED
command is used, existing transactions run to
completion before being DISABLED.
Note: If a transaction is disabled, this does not prevent
a START command which names this transaction

CEMT SET TRDUMPCODE
CEMT SET TRDUMPCODE Local

A system dump request is not to be sent to other MVS
Function: Change the status of a transaction dump. images in the sysplex which are running XCF/MRO
connected CICS regions related to the CICS region on
Description: Using the SET function, you can change which the dump is initiated.
entries in the transaction dump table to request a transaction Note: A related CICS region is one in which the unit of
dump. You can also set the maximum number of dumps that work identifiers, in the form of APPC tokens, of
can be taken. See the CICS Problem Determination Guide one or more tasks match those in the CICS
for information on using dumps. region that issued the dump request.
Syntax: Press the Clear key to clear the screen. There are Maximum(value)
two ways of commencing this transaction: specifies the largest number of dump calls for this dump
code that result in dumps being taken. The range is
Type CEMT SET TRDUMPCODE (the minimum abbreviation is
0–999, though a value of 999 means ‘no limit’.
CEMT S TRD) with (value) or ALL. You get a display that
lists the current status, similar to that obtained by CEMT NOSHutdown
INQUIRE TRDUMPCODE. You can then tab to the The CICS system is not to shut down.
highlighted or blank fields and overtype them with the
required values. NOSYsdump
A system dump is not to be taken.
Type CEMT SET TRDUMPCODE (CEMT S TRD) followed by one
or more attribute settings that you wish to change. For NOTrandump
example, cemt s trd(value) t sh specifies that a A transaction dump is not to be taken.
transaction dump is to be taken for the named
RELated
transaction dump code and that the CICS system is to
A system dump request is to be sent to MVS images in
shut down after the occurrence of an error
the sysplex which are running XCF/MRO connected
corresponding to this dump code.
CICS regions related to the CICS region on which the
Typing ? at the beginning of either the first or second line dump is initiated.
gives a syntax prompt. Resetting the values takes effect Note: A related CICS region is one in which the unit of
immediately. work identifiers, in the form of APPC tokens, of
55──CEMT Set TRDumpcode──┬─(value)─┬───────────5
└─ALl─────┘ REMove
5──┬────────────┬──┬───────────┬───────────────5 This code is to be removed from the dump code table.
├─Trandump───┤ ├─SYsdump───┤
└─NOTrandump─┘ └─NOSYsdump─┘ RESet
5──┬────────────┬──┬─────────┬─────────────────5 The current count of dump calls for this dump code is to
├─SHutdown───┤ ├─RELated─┤ be reset to zero.
└─NOSHutdown─┘ └─Local───┘
SHutdown
5──┬────────────────┬──┬────────┬──5% The CICS system is to shut down after the occurrence of
└─Maximum(value)─┘ ├─RESet──┤
├─REMove─┤ an error corresponding to this dump code.
└─ADd────┘
SYsdump
A system dump is to be taken.
Options Trandump
A transaction dump is to be taken.
(value)
specifies a 4-byte transaction dump code. See the CICS
Messages and Codes manual for a list of transaction
dump codes.
ADd
The specified transaction dump code is to be added to
the dump code table.
ALl
to access.

CEMT SET TSQUEUE
| CEMT SET TSQUEUE | TSQUEUE(data-value)

| specifies the 16-character identifier of the TS queue.
| Function: Delete a temporary storage queue (TS queue).
| This section applies also to the alternative command, CEMT

| SET TSQNAME. Use either to delete temporary storage
| queues (TS queues) with names up to 8 characters long.
| Use SET TSQNAME to delete temporary storage queues (TS
| queues) with names up to 16 characters long.
| Description: The SET TSQUEUE command enables you

| to delete a temporary storage queue (TS queue).
| The LASTUSEDINT option may be used to ensure that the

| queue to be deleted has not been referenced since a
| previous INQUIRE was issued. It may also be used to delete
| queues which have not been referenced within a given
| interval.
| Syntax
|
| ┌─ALl─────┐
| 55──CEMT Set TSqueue──┼─────────┼──────────────5
| └─(value)─┘
| 5──┬─────────────────┬─────────────────────────5
| ├─SYSID(value)────┤
| └─POOLNAME(value)─┘
| 5──┬────────────────────┬──────────────────────5
| └─LAstusedint(value)─┘
| 5──┬─Action(value)─┬──5%
| └─DELETE────────┘
| Options
| (value)
| specifies the identifier of the TS queue
| ALl
| specifies that any changes you request are made to all
| resources of the specified type that you are authorized
| to access.
| ACTION(value)
| specifies the action to be taken on the queue. The
| values are:
| DELETE
| the queue is to be deleted.
| LASTUSEDINT
| if this option is specified, the queue is only deleted if its
| last used interval is greater or equal to the value
| specified.
| POOLNAME(data-value)
| specifies an 8-character pool name.
| SYSID(data-value)
| specifies a 4-character shared sysid.

CEMT SET UOW CEMT SET UOWLINK
CEMT SET UOW CEMT SET UOWLINK

Function: Commit or back out a shunted unit of work. Function: Delete a link to a unit of work that was created
by a connection that has since been discarded.
Description: The SET UOW command enables you to
commit, back out, or force a unit of work that has been | UOWLINKS associated with RRS can be deleted when RRS
shunted during the transaction’s in-doubt period. | has cold started.
Syntax Description: The association between a unit of work and

a connection is known as a UOW-link. You can use the
INQUIRE UOWLINK command to browse all the UOW-links
55──CEMT Set UOW(value)──┬─(value)─┬───────────5 currently in the system. Some of the UOW-links may have
└─ALl─────┘ been created by connections that have since been discarded.
5──┬─COMmit──┬──5% If so, you may be able to use the SET UOWLINK command
├─Backout─┤ to delete them. (For information about when it is safe to
└─Force───┘
delete UOW-links, see the CICS Intercommunication Guide.)
Syntax
Options
(value)
55──CEMT Set UOWlink(value)──┬─(value)─┬───────5
specifies the 16-character identifier of the UOW to be └─ALl─────┘
committed, backed out, or forced.
5──Delete──5%
ALl
resources of the specified type that you are authorized Options
to access.
(value)
Backout specifies the 4-character identifier of the
Attempt to force syncpoint backout processing, as UOW-connection dependency (the UOW-link) to which
specified for this UOW. this command applies.
COMmit ALl
Attempt to force syncpoint commit processing, as specifies that any changes you request are made to all
specified for this UOW. resources of the specified type that you are authorized
to access.
Force
Attempt to force the UOW to backout or commit, as Delete
specified on the ACTION option of the TRANSACTION specifies that the UOW-link is to be deleted.
resource definition.
Note that all these values are valid only for UOWs that have
been shunted in-doubt. For information about the in-doubt
attributes of TRANSACTION definitions, see the CICS

CEMT SET VTAM
CEMT SET VTAM and then closes the terminal sessions tidily.
FORCECLOSE cancels any task and closes the VTAM
Function: Open or close the VTAM ACB, set the ACB, terminating all sessions immediately.
persistent session delay interval (PSDI), or deregister CICS Immclose
from membership of a generic resource. The connection between CICS and VTAM is to be
terminated immediately. Any transactions using
VTAM-connected terminals are terminated abnormally,
and all such terminals are lost to CICS.
Type CEMT SET VTAM (the minimum abbreviation is CEMT
The difference between IMMCLOSE and FORCECLOSE
S VT). You get a display that lists the current status,
is that IMMCLOSE cancels any task at a VTAM terminal
similar to that obtained by CEMT INQUIRE VTAM. You
and then closes the terminal sessions tidily.
can then tab to the highlighted or blank fields and
FORCECLOSE cancels any task and closes the VTAM
ACB, terminating all sessions immediately.
Type CEMT SET VTAM (CEMT S VT) followed by one or
more attribute settings that you wish to change. For Open
example, cemt s vt o specifies that the connection The connection between CICS and VTAM is established.
between CICS and VTAM is established. With ACF/VTAM, this refers to the opening of the
ACF/VTAM ACB through which ACF/VTAM
Typing ? at the beginning of either the first or second line communicates with CICS.
gives a syntax prompt. Resetting the values takes effect A CEMT SET VTAM OPEN command will fail with a
immediately. STILL CLOSING message if the command is issued
while a previous predatory takeover is still being
processed. No attempt is made to open the VTAM ACB,
55──CEMT Set Vtam──┬─Open───────┬──────────────5
├─Closed─────┤ because it is still being closed as a result of the
├─Immclose───┤ predatory takeover. After the predatory takeover
└─Forceclose─┘ completes, the CEMT SET VTAM OPEN command will
5──┬─────────────────────┬─────────────────────5 work as normal. The failure is notified by a
└─Psdinterval(hhmmss)─┘ RESP=INVREQ and RESP2=14 condition.
5──┬──────────────┬──5% If CICS is using VTAM multi-node persistent sessions,
└─Deregistered─┘ and VTAM has been restarted after an abend, opening
the VTAM ACB causes CICS to restore the persistent
sessions that VTAM has retained. However, CICS does
Options not restore APPC synclevel 2 sessions, which are
Closed unbound.
The connection between CICS and VTAM is to terminate Psdinterval(hhmmss)
normally; that is, transactions are allowed to complete specifies the persistent session delay interval, expressed
and terminals are released normally. in the form hhmmss. It specifies if and for how long
Deregistered sessions are held in recovery-pending state after CICS
specifies that CICS is to be removed from the VTAM fails. The permitted range is 000000 to 235959 inclusive.
generic resource that it is currently a member of. If you 000000 If CICS fails, sessions are terminated.
deregister a region from membership of a generic
resource, you should end any affinities that it owns—see Hhmmss If CICS fails, sessions are held in
the PERFORM ENDAFFINITY command. recovery-pending state by VTAM for up to
the interval specified.
Generic resources are described in the CICS
Intercommunication Guide. Table 7 on page 211 shows possible CEMT error
Forceclose messages resulting from unsuccessful attempts to set
The connection is terminated immediately, and all the persistent session delay interval.
terminal connections using the VTAM ACB (access
method control block), together with the transactions
associated with them, are terminated abnormally. If
transactions do not terminate because of their state at
the time FORCECLOSE was issued, it is necessary to
issue CEMT SET TASK(nn) PURGE or FORCEPURGE
before the ACB can be reopened.
The difference between IMMCLOSE and FORCECLOSE
is that IMMCLOSE cancels any task at a VTAM terminal

CEMT SET WEB
Table 7. CEMT error messages for attempts to set the | CEMT SET WEB
persistent session delay interval
| Function: Open or close CICS internal sockets support,
Message RESP/RESP2
| change Web garbage collection settings, or change Web
INVALID PSDINT RESP=INVREQ, RESP2=4 | 3270 terminal timeout settings.
NOT WITH XRF RESP=INVREQ, RESP2=8
SETLOGON RESP=INVREQ, RESP2=9
FAILURE | two ways of commencing this transaction:
BACK LEVEL RESP=INVREQ, RESP2=10 | Type CEMT SET WEB (the minimum abbreviation is CEMT S
VTAM | W). You get a display that lists the current status, similar
| to that obtained by CEMT INQUIRE WEB. You can then
ACB CLOSED RESP=INVREQ, RESP2=12
| tab to the highlighted or blank fields and overtype them
RECOVERY All other cases of INVREQ | with the required values.
ERROR
| Type CEMT SET WEB (CEMT S W) followed by one or more
| attribute settings that you wish to change. For example,
| cemt s w g specifies that you want to change the
| GARBAGEINT option.

| gives a syntax prompt. Resetting the values takes effect
| immediately.
|
| 55──CEMT Set Web──┬───────────────────┬────────5
| └─Garbageint(value)─┘
| 5──┬───────────────────┬──5%
| └─Timeoutint(value)─┘
| Displayed fields
| GARBAGEINT
| is the interval at which the Web garbage collection task
| runs to clean up Web 3270 state data for which the
| terminal timeout interval has expired.
| TIMEOUTINT
| is the period of time after which inactive Web 3270
| sessions are eligible for garbage collection.

CEMT SET WEB

CEOT—terminal status
Chapter 12. CEOT—terminal status

The CEOT command allows you to inquire about the status Net(netname)
of your own terminal, and to change some of its values. You displays the name by which this terminal is known to
cannot use CEOT to inquire about or change the values of VTAM.
any other terminal.
Pag
You can start CEOT from 3270 family display devices, or See ‘PAGEABLE’ in the Command Options below.
from equivalent terminals, or from the operating system The paging status can be modified by overtyping.
console.
Pri(nnn)
Press the Clear key to clear the screen. There are two ways displays the priority of your terminal relative to other
of using this transaction: in inquiry mode and in set mode. terminals, and is a number in the range 0–255.
Ter(xxxx)
displays the 4-character identifier of your terminal.
CEOT in inquiry mode
Tra(ceot)
Type CEOT. You get the following display: displays the transaction that is running on your terminal.
This is always CEOT.
Tti
à STATUS: RESULTS - OVERTYPE TO MODIFY
ð The terminal is available for use by transactions initiated
Ter(S2ð8) Tra(CEOT) Pri(ððð) Pag Ins Ati Tti
Net(IGKS2ð8 ) Acq
from this terminal. You cannot change the TTI setting by
CEOT SYNTAX:
< PAgeable | AUtopageable > overtyping it with blanks.
< ATi | NOAti >
< TTi | NOTti >
CEOT in set mode
Figure 141. CEOT transaction: initial screen Type CEOT followed by one or more of the following attributes:
The top half of the screen shows the current status of your
terminal. The bottom half of the screen shows the syntax of 55──CEOT──┬──────────────┬──┬───────┬──────────5
├─PAgeable─────┤ ├─ATi───┤
the CEOT command. └─AUtopageable─┘ └─NOAti─┘
Note: NET, ACQ, and CRE are not displayed for non-VTAM 5──┬───────┬──5%
terminals. ├─TTi───┤
└─NOTti─┘
The status items are displayed in the following sequence.
Note: If an item has a “negative” value—for example,
ATi
NOATI—that value will be replaced by a blank space.
Your terminal is available for use by transactions that
Acq are automatically initiated from within CICS or, if the
CICS is in session with the logical unit represented by terminal is an ISC session, by transactions that are
this terminal. You cannot overtype this value. using this session as an alternate facility to communicate
with another system.
Aut
See ‘AUTOPAGEABLE’ in the Command Options below. AUtopageable
Pages after the first in a series are written to the
The paging status can be modified by overtyping.
terminal automatically. This option should never be used
ATi with a display device.
See ‘ATI’ in the Command Options below.
NOAti
Cre Your terminal is not available for use by transactions that
This terminal can be acquired automatically by ATI are automatically initiated from within CICS or, if the
transactions. You cannot overtype this value. terminal is an ISC session, by transactions that are
using this session as an alternate facility to communicate
Ins with another system.
Your terminal is INSERVICE. You cannot overtype this
value.

CEOT—terminal status
NOTti
This terminal cannot be used by transactions that are
initiated from this terminal. Setting NOTTI is valid only
for sequential devices.
PAgeable
Pages after the first in a series are written to the
terminal on request from the operator.
TTi
This terminal can be used by transactions.
Typing ? at the beginning of the first line gives a syntax

prompt. Resetting the values takes effect immediately.
If you do not want to view the current status of your terminal

(as displayed in the top half of the CEOT screen), you can
change the paging status and the ATI status by using the
CEOT syntax displayed in the bottom half of the screen. So,
for example, if you simply want to make your terminal
PAGEABLE, type CEOT PAGEABLE on the command line of
your display and press the Enter key.
Notes:
1. You can use CEOT with the routing transaction (CRTE).
A user can inquire only about his or her own
terminal, and cannot change any of the attributes.
The attributes returned are those of the remote
terminal TCTTE in the application-owning
region(AOR).
You must cancel the CRTE transaction by typing
CANCEL on the command line.
2. Using CEOT in the TOR:
When a terminal is defined as unshippable, and
CEOT is used to change the status of the terminal,
the changes are not reflected in a remote terminal
built in an AOR as a result of a transaction routing
request. The status of the remote terminal is
determined by the remote definition of the terminal
in the AOR.
Even when a terminal is defined as shippable, a
status change made in the TOR, using CEOT, is not
reflected in an existing remote terminal definition in
the AOR. A remote terminal in the AOR is created
from a shippable definition the first time it is required
in the AOR for running a program. The status of the
remote terminal returned is its current status in the
TOR. Any later updates are not passed on to the
remote terminal.
3. If you make an invalid request, CICS lists the keyword
options and waits for a valid keyword entry.

CESF—sign off
Chapter 13. CESF—sign off

Use the CESF transaction to sign off from the CICS system. NOTTI Terminal transaction initiation is not allowed, and
your terminal is placed in RECEIVE status so
This transaction: that, the next time a connection is made, it can
Writes the signoff message to your terminal receive messages.
Logs the message on the transient data destination DISCREQ=YES is an operand of the TYPETERM definition
CSCS associated with the terminal, and means that CICS is to
Logs any error message on the transient data honor a disconnect request. If DISCREQ=NO, a disconnect
destination CSMT. request (for example, a CESF LOGOFF request) is not
honored.
If you are using CESF to disconnect a terminal and security
is active, a message will still be sent to the log if the signoff If a CESF GOODNIGHT is given when there are outstanding
fails. However, this will not stop the terminal being automatic transaction initiation (ATI) requests, the ATI
disconnected if it is a preset terminal or if the terminal is not requests are actioned and the session is reacquired
signed on. irrespective of the RDO options.
You cannot use CESF on:

Fixed-format terminals (such as the 3608, the 3614, and
the 3653)
Numeric-only terminals.
For these devices, you must code your own transaction using
the EXEC CICS SIGNOFF command. For programming
information about this command, see the CICS Application
Programming Reference manual.
The syntax of the CESF transaction is as follows:
55──CESF──┬───────────┬──5%
├─GOODNIGHT─┤
└─LOGOFF────┘
If you simply type CESF by itself, you are signed off the
CICS system. Your terminal can still start transactions
without you having to request them, and messages can be
sent to it. You can sign on again at that terminal at any time.
The effects of typing CESF with the GOODNIGHT value or

the LOGOFF value depend on the access method in use, as
shown in Table 8:
Table 8. Effect of CESF LOGOFF and GOODNIGHT with

different access methods
VTAM Otherwise
DISCREQ=YES
CESF TTI TTI
CESF LOGOFF Disc, TTI TTI
CESF Disc, TTI NOTTI
GOODNIGHT
where:
Disc The terminal is disconnected.
TTI Terminal transaction initiation is allowed.

CESF—sign off

CESN—sign on
Chapter 14. CESN—sign on

By default, intending users of CICS see the CICS
“good-morning” panel displayed when they logon to CICS as
IBM 3270 family display devices
a VTAM application (see Figure 142).
Clear the screen, and type CESN on the command line of
the screen. Press ENTER. You get the following display:
à \\\\\\\ \\\\\\\ \\\\\\\ \\\\\\\ \\ \\\\\\\\\ \\\\\\\ \\\\\

ð
\\\\\\\\\ \\\\\\\ \\\\\\\\\ \\\\\\\\\ \\\ \\\\\\\\\ \\\\\\\\\ \\\\\\\
\\\\\\\\\
\\\ \\
\\\\\
\\\
\\\\\\\\\
\\\ \\
\\\\\\\\\
\\\ \\
\\\
\\\
\\\\\\\\\
\\\
\\\\\\\\\
\\\ \\
\\\\\\\\\
\\\ \\\
à Sign on for CICS Transaction Server APPLID=CICSA1ðð
ð
\\\ \\\ \\\ \\\\\\\\ \\\ \\\\\\\ \\\\\\\\ \\\\\\\\\
\\\ \\\ \\\ \\\\\\\\ \\\ \\\\\\\ \\\\\\\\ \\\\\\\\\ . . . . . . This is where the good morning message appears. . . . . . .
\\\ \\\ \\\ \\\\\\\ \\\ \\\\\\\ \\\\\\\ \\\\\\\\\ . . . . . . It can be up to four lines in depth to contain the. . . . .
\\\ \\\ \\\ \\\ \\\ \\\ \\\ \\\ \\\ \\\ \\\ \\\ \\\ . . . . . . maximum message length of 246 characters (that is, three. .
\\\\\\\\\ \\\\\\\ \\\\\\\\\ \\\\\\\\\ \\\ \\\\\\\\\ \\\\\\\\\ \\\ \\\ . . . . . . full lines and six characters on the fourth line) . . . . .
\\\\\\\\ \\\\\\\ \\\\\\\\ \\\\\\\\ \\ \\\\\\\\\ \\\\\\\\ \\\ \\\
\\\\\\ \\\\\\ \\\\\\ \\\\\\ \ \\\\\\\\ \\\\\\ \\ \\
á ñ Type your userid and password, then press ENTER:
Userid . . . . ________ Groupid . . . ________
Figure 142. The CICS good-morning panel Password . . . ________
Language . . . ___
This panel is displayed by the CICS-supplied transaction, New Password . . . ________
CSGM. Instead of using CSGM, you can specify your own

transaction panel on the GMTRAN system initialization
parameter. DFHCE352ð Please type your userid.
F3=Exit
Users may either press the CLEAR key and type the CICS
á ñ
sign-on transaction id, CESN or, if CESN is specified as the Figure 143. CESN transaction: initial screen
good-morning transaction, CICS displays the sign-on panel
shown in Figure 143. The panel for 40 x 12 size screens is shown below. There is
no space for the release number or the good morning
The user ID specified for this transaction is used in error message.
messages and so on, to identify the user.
Notes:
1. If you sign on at a terminal that is already signed on,
à Sign on for CICS Transaction Server APPLID=CICSA1ðð
ð
Userid . . . . ________
CSSN signs off the previous operator. This does not Groupid . . . . ________
Password . . . . ________
happen, however, unless you complete the CESN panel Language . . . . ___
New Password . . ________
before pressing ENTER. For further information, see
“Signing off with CESN” on page 218.
2. For numeric-only devices or for the IBM 2741
DFHCE352ð Please type your userid.
Communication Terminal, use the signon procedure F3=Exit
described in “Non-3270 family terminal” on page 218. á ñ

3. RACF recognizes only uppercase alphabetic characters.
Figure 144. 40 x 12 screen
Userids and passwords specified in the CESN
transaction are only translated to uppercase if the Enter your user ID. This may be up to 8 characters in length.
UCTRAN(YES) attribute is specified in the PROFILE
resource definition or TYPETERM resource definition,
otherwise data is passed to RACF as entered. See the
CICS Resource Definition Guide for information on
defining PROFILE and TYPETERM.
4. Autoinstall of BMS maps is not carried out within the
CESN transaction. When CESN tries to send out any
BMS map that is not installed, CESN will send out the
English BMS map.
5. This dialog will not prompt you for a new password
unless your old password has expired. If you wish to
change your password before it has expired, you must
use another method, such as signing on at a CICS
terminal rather than a console.

CESN—sign on
violation via message ICH408I before CICS prompts for

Non-3270 family terminal the password.
A user can also sign on by providing all the user information USERID=uuuuuuuu
along with the transaction id, as follows: is your user ID (up to 8 characters).
| 55──CESN USERID=uuuuuuuu──CESN────────────────5
Signing off with CESN
| 5──USERID=uuuuuuuu──┬───────────────────┬──────5
└─,GROUPID=gggggggg─┘ When a user starts the CESN transaction, CICS verifies
5──┬───────────────┬──┬──────────────┬─────────5 userids and password by calling RACF. If the terminal user
└─,LANGUAGE=lll─┘ └─,PS=pppppppp─┘ sign-on is valid, the CICS user domain keeps track of the
5──┬─────────────────┬──5% signed-on user. Thereafter, CICS uses the information about
└─,NEWPS=password─┘ the user when calling RACF to make authorization checks. If
Note: a user was signed on before the call to RACF, this signed-on
1 Do not use blanks between parameters in the user is signed off by CICS whether the returns from RACF
comma-separated list. are valid or invalid.
If users enter the CESN transaction when they are already

This style of input can be used on video display terminals, signed on, the transaction may or may not sign them off. For
but is especially useful for sequential terminals and devices example, a user is not signed off by entering CESN, and
not belonging to the IBM 3270 family of terminals. then pressing F3 when the signon panel is displayed.
In CICS Transaction Server for OS/390, CESN signs off any

Command options signed-on user only when a new signon attempt is made. A
signed-on user is signed off when a userid is entered on the
GROUPID=gggggggg
signon panel and the ENTER key is pressed. Alternatively,
| is your group userid (up to 8 characters). If this
the signed-on user is signed off if the CESN transaction
| parameter is specified, it may be propagated to remote
identifier is entered with operands (for example
| systems along with the userid (refer to the section on
USERID=userid), and the ENTER key is pressed.
| 'Implementing LU6.2 Security / Information about remote
| users' in the CICS RACF Security Guide). Unsuccessful sign-on and sign-off errors cause DFHCEnnnn
LANGUAGE=lll messages to be issued.
enables you to choose a national language (from those
RACF OIDCARD users can use CESN to sign on if the card
that are available at your installation) for terminal
reader supports the DFHOPID attention identifier (AID). If it
directed messages. “lll”, the national language identifier,
does not, you will need to write your own sign-on program
is a standard, three-character IBM code. If the language
using the EXEC CICS SIGNON command. For programming
identifier is omitted, CICS examines the following in this
information see the CICS Application Programming
order:
Reference.
1. Language specified for the user in the signon table
2. Language specified in the installed terminal
definition for the terminal at which the signon occurs
3. Language specified on the NATLANG system
initialization parameter.
If you enter a code other than the range of IBM codes,

you get the following message:
DFHCE3537 Language is invalid. Please retype.
NEWPS=password
“password” is your new password (up to 8 characters). A
‘password’ value that consist entirely of space characters
will not be interpreted as a password update request.
The user will not be prompted for verification.
PS=pppppppp
is your password (up to 8 characters). If the password is
required but omitted, then RACF will report a security

CEST—supervisory terminal
Chapter 15. CEST—supervisory terminal

Use CEST to invoke a subset of the master terminal (CEMT)
transaction. The CEST INQ|SET commands allows you to
inquire about and alter some of the values of lines,
netnames, tasks, and terminals.
CEST can be invoked from 3270 family display devices, or

from equivalent terminals, or from the operating system
console.
All of the CEST commands require the SUPRID keyword to

be specified. SUPRID identifies the supervisor invoking the
transaction, and its value is the 1-or 2-character suffix of a
terminal list table (TLT). For information about the SUPRID
keyword, see the CICS Resource Definition Guide.
For example, CEST INQ TERMINAL SUPRID(AL) displays

the status of all the terminals in the DFHTLTA1 table. Values
can be changed by overtyping the display or by using CEST
SET commands. Apart from the requirement that SUPRID
has to be specified, the syntax of the commands and the
meaning of the values is exactly as described in CEMT
INQUIRE|SET LINE, NETNAME, TASK, and TERMINAL.

CEST—supervisory terminal

CETR—trace control
Chapter 16. CETR—trace control

Use CETR to control CICS tracing activity.
Component trace options
Start the transaction by typing CETR on the command line of
your display, as follows: The “Component Trace Options” display is produced by
pressing PF4 on the main CETR display. You get the
CETR following display, with the values of your own system in each
Press the ENTER key. of the fields.
You get the following display, with the values of your own
system in each of the fields. à ð
CETR Component Trace Options CI41 IYAHZCCV
Over-type where required and press ENTER. PAGE 1 OF 3

Component Standard Special
-------- ------------------------------- -------------------------------
à CETR CICS/ESA Trace Control Facility CI41 IYAHZCCV
ð |
AP
BA
1
1
1-2
1-2
BF 1 1
Type in your choices. BM 1 1
BR 1 1-2
Item Choice Possible choices CP 1 1-2
DC 1 1
Internal Trace Status ===> STARTED STArted, STOpped DD 1 1
Internal Trace Table Size ===> 16 K 16K - 1ð48576K DI 1 1
DM 1 1-2
Auxiliary Trace Status ===> STOPPED STArted, STOpped, Paused DS 1 1-2
Auxiliary Trace Dataset ===> B A, B DU 1 1-2
Auxiliary Switch Status ===> NO NO, NExt, All EI 1 1
| EM 1 1-2
GTF Trace Status ===> STOPPED STArted, STOpped FC 1 1-2
GC 1 1-2
Master System Trace Flag ===> ON ON, OFf IC 1 1
Master User Trace Flag ===> ON ON, OFf
PF: 1=Help 3=Quit 7=Back 8=Forward 9=Messages ENTER=Change
When finished, press ENTER.
á ñ
PF1=Help 3=Quit 4=Components 5=Ter/Trn 9=Error List Figure 146. CETR transaction: component trace options screen
á ñ
PF7 and PF8 can be used to scroll backward and forward
Figure 145. CETR transaction: initial screen through the list of components. PF9 gives the error message
list.
Any of the input fields can be overtyped with the new values
that you require. When you press ENTER, CETR issues the The trace levels for a particular component are represented
necessary commands to set the new values. If there are any by two values. One gives the active level of tracing for
errors, PF9 can be pressed to display the error messages. If standard tracing; the other gives the level for special tracing.
there is only one short error message, it appears near the From the list of components, you can set the active level of
bottom of this display. tracing for standard and/or special tracing for each individual
component. See the CICS Problem Determination Guide for
The following table shows the relationships between the an explanation of standard and special tracing, and of tracing
auxiliary trace status, trace flag, and trace data set. levels.
Table 9. The meanings of auxiliary trace status values The values are in the range 1 through 32 for most
components. In practice, you will normally want to use an
Auxiliary tracing Auxiliary trace Auxiliary trace
status flag data set
active level of ‘1’ for any component, and you do this by
overtyping (if necessary) the displayed value under the
Started On Open relevant heading for the required component.
Paused Off Open
In certain circumstances, if you have referred a problem to
Stopped Off Closed
the IBM System Support Center staff, they may ask you to
get a level ‘2’ trace. You will need to specify both level 1 and
Two other main functions of CETR are: 2 to get all of the trace points that are needed.
1. Setting the component trace options (press PF4)
You can specify a range of tracing levels—normally levels ‘1’
2. Setting the transaction and terminal trace options (press and ‘2’. You do this by overtyping the displayed value with
PF5). ‘1-2’ or ‘1,2’.
For information about the use of the various CETR options Alternatively, you can type ‘ALL’ in upper or lower case
as an aid to problem determination, see the CICS Problem under the relevant heading. Similarly, you can type ‘OFF’ to
Determination Guide. turn off the tracing for a particular component under either
the ‘special’ or ‘standard’ heading.

The equal sign “=” can be used, when changing several Note: The SZ component can be used only if the Front End
fields, to indicate that a particular field should be changed to Programming Interface feature (FEPI) is installed. For
the same value as the one above. information, see the CICS Front End Programming
Interface User's Guide.
The complete list of components is:
Note: If you use CETR to turn on tracing for a particular
Component Title component, CICS does not save modifications to the
AP Application domain
component trace flags across any kind of CICS
| BA CICS business application manager for BTS restart.
BF* Built-in function support
BM* BMS
BR 3270 Bridge Transaction and terminal-related trace
CP* Common Programming Interface
DC* Dump macro-compatibility
options
DD Directory manager domain
| DH Document handling domain The “Transaction and Terminal Trace” display is produced by
DI* Data interchange pressing PF5 on the main CETR display. It can be used to
DM Domain manager domain set STANDARD, SPECIAL, or SUPPRESSED tracing for
DS Dispatcher domain particular CICS tasks. This is done by setting the appropriate
DU Dump domain value for the transaction ID used to start the task, or for the
EI* Exec interface terminal from which the task is to be run. Note that
| EM Event manager domain for BTS
SUPPRESSED cannot be set for terminals, only for
FC* File control
GC Global catalog domain
transaction IDs. The required terminal can also be specified
IC* Interval control by using its netname.
IS* Intersystems communication and MRO
KC* Task control macro-compatibility Setting SPECIAL tracing for a particular transaction means
KE Kernel that the SPECIAL flags for each component (as defined on
LC Local catalog domain the “Component Trace Options” display) is used to decide
LD Loader domain whether a particular trace entry is to be made at any given
LG Log manager domain point in the process of the task.
LM Lock manager domain
ME Message domain The display layout is as follows:
MN Monitoring domain
NQ Enqueue manager domain
PA Parameter manager domain
PC* Program control à CETR Transaction and Terminal Trace CI41 IYAHZCCV
ð
PG Program manager domain Type in your choices.
RI Resource manager interface (RMI) Item Choice Possible choices
RM Recovery manager domain
Transaction ID ===> Any valid 4 character ID
| RX Recoverable EXCI domain Transaction Status ===> STandard, SPecial, SUppressed
SC* Storage control macro-compatibility Terminal ID ===> Any valid Terminal ID

Netname ===> Any valid Netname
| SH Scheduler services domain for BTS Terminal Status ===> STandard, SPecial
Terminal VTAM Exit Trace ===> ON, OFf
| SO Sockets domain Terminal ZCP Trace ===> ON, OFf
SM Storage manager domain VTAM Exit override ===> NONE All, System, None
SP* Syncpoint
ST Statistics domain When finished, press ENTER.
SZ Front End Programming Interface

TC* Terminal control PF1=Help 3=Quit 6=Cancel Exits 9=Error List
TD* Transient data
TI Timer domain
á ñ
TR Trace domain
TS Temporary storage domain Figure 147. CETR transaction: transaction and terminal trace screen
UE* User exit control
US User domain A common way of using this display is to set the terminal
| WB Web interface trace status for a particular terminal to SPECIAL, to have all
XM Transaction manager of the STANDARD component trace flags as level-1 only,
XS Security manager domain and the SPECIAL component trace flags as level-1 and
level-2. In this way, all tasks run from the SPECIAL terminal
Components marked * are subcomponents of the AP have level-1 and level-2 tracing. All other tasks have level-1
domain, and the trace entries for these components are tracing only.
produced with a trace point ID of AP nnnn.
For example, you can use SPECIAL tracing to trace a single
For information about the use of trace for problem transaction. You can do this by setting the “master system
determination, and for information about the format of trace trace flag” OFF on the main CETR display. This turns
entries, see the CICS Problem Determination Guide.

STANDARD tracing OFF. (STANDARD tracing can also be

turned off by coding SYSTR=OFF at system initialization.) à CETR Help: CICS Trace control facility
ð
You can then press PF4 for the “components trace options” (2) DESCRIPTION OF FIELDS.
screen, shown in Figure 146 on page 221, where you select The values that can be set from the main panel are:-
the levels of tracing for the required components under the Internal Trace Status - Whether tracing to the main storage trace
table is required.
heading “Special”. Finally, on the “transaction and terminal Internal Trace Table Size - The size of the main storage trace table.
Auxiliary Trace Status - Whether tracing to the current auxiliary trace
trace” screen, shown in Figure 147 on page 222, specify the Auxiliary Trace Dataset -
data set is required.
The current data set. A = DFHAUXT, B = DFHBUXT.
transaction ID and a transaction status of SPECIAL. Auxiliary Switch Status - Whether a switch to the alternate extent is
required at next or all end-of-extents.
GTF Trace Status - Whether CICS is writing its trace data to GTF.
Note that GTF must have been started to MVS.
This display can also be used to enable VTAM exit tracing Master System Trace Flag - This flag must be on if CICS system-requested
entries are to be written for STANDARD tracing
and ZCP trace for specified terminal IDs or netnames. For Master User Trace Flag -
tasks.
This flag must be on if user-requested trace
example, to set VTAM exit tracing in an AOR, enter the entries are to be produced.
applid of the TOR as Netname and enter ON for the PF 3=End 7=Back 8=Next ENTER=End
Terminal VTAM Exit Trace. á ñ
There are also fields that allow enabling of all nonterminal Figure 150. CETR transaction: HELP panel (3)
VTAM exits, and PF6 can be used to cancel all exit tracing.
à ð
HELP panels CETR Help: CICS Trace control facility
(3) FUNCTION KEY USE ON THE MAIN PANEL.

If you press the help key (PF1), the following panels are Key Name Function
displayed: ENTER Change Execute any changes.

PF1 Help Display this help information.
PF3 Quit Terminate the transaction.
PF4 Components Display or set STANDARD or SPECIAL trace levels
for individual CICS components.
PF5 Ter/Trn Query or set current trace status for terminal
à CETR Help: CICS Trace control facility
ð PF9 Messages
or transaction.
Display any messages created, these can be
warning (informative) messages, or errors.
FUNCTION OF THE MAIN PANEL.
This panel displays the current state of CICS Internal, Auxiliary

and GTF trace and the settings of the master system and user trace
flags. The current values are obtained from the system on initial
entry and subsequently every time ENTER or a PF key is pressed.
The values can be altered by over-typing and pressing ENTER. PF 3=End 7=Back ENTER=End
The APPLID of the CICS system being queried is displayed in the top á ñ
right corner of the screen.
Figure 151. CETR transaction: HELP panel (4)

Further help information follows:
1. Data entry and alteration.

2. Description of fields.
3. Function key use on the main panel. HELP panels for components
PF 3=End 8=Next ENTER=End
If you press the help key (PF1) while viewing the component
á ñ trace options screen, the following panels are displayed:
à CETR Help: CICS Component Trace

ð
à CETR Help: CICS Trace control facility
ð FUNCTION OF THE COMPONENT TRACE PANEL
The component trace panel is used to inquire and set the STANDARD and
SPECIAL trace levels for the individual components of the CICS system.
(1) DATA ENTRY AND ALTERATION.
Every component of CICS has a number of trace points. Associated with
This is achieved by simply over-typing the existing data, and then each is a trace level. These levels are numbers from one to thirty-two.
pressing ENTER. For the trace entry associated with the trace point to be made, the
associated level must be active (except for exception traces).
Abbreviations may be used, provided they are not ambiguous. The minimum
possible abbreviations are listed in capitals to the right hand side of Each CICS task is either a STANDARD tracing task or a SPECIAL tracing
the input fields. For example STO may be entered for STOPPED, but ST task. This distinction is made at task attach time when the STANDARD or
would not be allowed as it could mean STARTED or STOPPED. SPECIAL attributes of the terminal id and transaction id are examined.
These can be set on the Terminal and Transaction Trace panel of CETR.
Erased or blank fields will redisplay the current level settings as
known to CICS. These will be the levels current when ENTER was last Further help information follows:
pressed. They may have been changed from the previously displayed 1. Data entry and alteration 1
values by other activity in the system. 2. Data entry and alteration 2
3. Meanings of Component abbreviations.
All input will be validated when ENTER is pressed, and no internal 4. Function key use on the component trace panels.
settings will be made until all errors have been removed.
PF 3=End 8=Next ENTER=End
PF 3=End 7=Back 8=Next ENTER=End

á ñ
á ñ Figure 152. CETR transaction: Component trace HELP panel (1)
Chapter 16. Trace control CETR 223


ð à CETR Help: CICS Component Trace
ð
(1) DATA ENTRY AND ALTERATION 1 (4) MEANINGS OF COMPONENT ABBREVIATIONS.
From this panel detailed tracing levels can be set for each component.
Each level is specified by a number between one and three, the TR . . . Trace domain
presence of the number indicates that the level is set, the omission TS . . . Temporary storage
of a number indicates that the level is not set. UE . . . User exit interface
US . . . User domain
Multiple consecutive levels are displayed as xx-yy, where xx is the | WB . . . Web interface
lower of the consecutive values, and yy is the higher. For example, XM . . . Transaction manager
if 1-3 was displayed, then trace levels 1,2 and 3 would all be set. XS . . . Security domain
There is more than one page of components. Function keys PF7 and PF8
can be used in the usual way to switch pages. The page may only be
switched when the displayed page contains no errors.
Changes to the level settings are automatically validated when the

current page is changed, but these levels are only set within CICS when
ENTER is pressed. Until this time it is possible to quit from the
program (PF3) without altering internal values.
á ñ
Figure 153. CETR transaction: Component trace HELP panel (2) á ñ

Figure 156. CETR transaction: Component trace HELP panel (5)
ð
(2) DATA ENTRY AND ALTERATION 2
The level settings may be changed by simply over-typing the existing

ð
data and then pressing ENTER.
(5) FUNCTION KEY USE ON THE COMPONENT TRACE PANELS.
To set a single level enter the number. To set consecutive levels
enter the first and last levels separated by a hyphen. Key Name Function
Erased or blank fields will redisplay the current level settings as ENTER Change Execute any Changes.
known to CICS. These will be the levels set when ENTER was last pressed. PF1 Help Display this help information.
PF3 Quit Return to main Trace Control panel.
All levels may be set by entering ALL and none by entering OFF. PF7 Backward Scroll backward one page.
PF8 Forward Scroll forward one page.
To provide identical level settings for more than one component: PF9 Messages Display any messages created,
- type the setting(s) for the first component, do not press ENTER. these can be warning
- type = in fields where you want this setting duplicated. (informative) messages, or errors.
NOTE: Although levels up to 32 may be set for most components, only

levels 1,2 and 3 are currently used.
á ñ
PF 3=End 7=Back ENTER=End
Figure 154. CETR transaction: Component trace HELP panel (3) á ñ

ð
(3) MEANINGS OF COMPONENT ABBREVIATIONS.
AP . . . Application domain LD . . . Loader domain

BF . . . Built-in function LG . . . Log manager domain
BM . . . Basic Mapping Support LM . . . Lock manager
CP . . . CPI-C interface ME . . . Message domain
DC . . . Dump compatibility layer MN . . . Monitoring domain
DD . . . Directory manager NQ . . . Enqueue Manager
DI . . . Batch data interchange PA . . . Parameter manager domain
DM . . . Domain manager domain PC . . . Program control
DS . . . Dispatcher domain PG . . . Program manager domain
DU . . . Dump domain RI . . . RMI
EI . . . Exec interface RM . . . Recovery Manager
FC . . . File control SC . . . Storage control
GC . . . Global Catalog domain SM . . . Storage Manager domain
IC . . . Interval control ST . . . Statistics domain
IS . . . ISC SZ . . . Front End Prog Interface
KC . . . Task control TC . . . Terminal control
KE . . . Kernel TD . . . Transient data
LC . . . Local Catalog domain TI . . . Timer domain
á ñ

HELP panels for terminal and transaction

trace
à CETR Help: CICS Terminal and Transaction Trace
ð
(2) ZCP TRACE
If you press the help key (PF1) while viewing the terminal ZCP trace is the activate scan trace facility. Turning it on
for a particular terminal means that the activate scan routine
and transaction trace screen, the following panels are of the terminal control program (DFHZCP) will start to monitor
the activate scan queue for the Terminal Control Table Terminal
Entry (TCTTE) for that terminal.
displayed:
When the TCTTE is found, indicating that there is activity on the
terminal, a trace entry is made for the activate scan ZCP routine.

ð
FUNCTION OF THE TERMINAL AND TRANSACTION PANEL.
This panel has two main functions.
(1) To allow STANDARD/SPECIAL tracing to be set for tasks to be run from

particular terminals or with particular transaction ids. It is also PF 3=End 7=Back 8=Next ENTER=End
possible to suppress tracing for particular transaction ids.
STANDARD tracing tasks use the STANDARD component flags.
SPECIAL tracing tasks use the SPECIAL component flags.
á ñ
See the help information for the component panel for more detail.
(2) To allow the setting of VTAM EXIT and ZCP tracing. Figure 160. CETR transaction: Terminal and transaction HELP
The current settings will be displayed if transaction id, terminal id panel (3)
or netname are specified without other values.
Further help information follows:

1. VTAM EXIT trace.
2. ZCP trace.
PF 3=End
3. Function key use on the terminal and transaction panel.
8=Next ENTER=End
ð
á ñ (3) FUNCTION KEY USE ON THE TERMINAL AND TRANSACTION PANEL.
Key Name Function
ENTER Change Execute any Changes.

Figure 158. CETR transaction: Terminal and transaction HELP PF1 Help Display this help information.
PF3 Quit Return to main Trace Control panel.
panel (1) PF6 Cancel Cancel all exit tracing. This turns off
VTAM EXIT tracing for all terminals and
for all the non-terminal EXITs.
PF9 Messages Display any messages created.

ð
(1) VTAM EXIT trace.
CICS VTAM EXIT tracing consists of entries on GTF made by the CICS
supplied VTAM exits that run asynchronously with the rest of CICS.
The exits that are related directly to a particular terminal have their
tracing activated by specifying the terminal id and/or netname and PF 3=End 7=Back ENTER=End
setting ON in the Terminal VTAM Exit Trace field.
There are also non-terminal related exits for which tracing is enabled by
á ñ
specifying SYSTEM in the VTAM Exit override field. A setting of ALL in
the exit override field will turn on exit tracing for all non-terminal
exits, and for all terminal exits for all terminals. Figure 161. CETR transaction: Terminal and transaction HELP
NOTES: panel (4)
(a) Setting trace for any terminal related exit will also turn on trace of
all non-terminal related exits.
(b) CICS GTF tracing need not be STARTED (main panel) to use this facility.
(c) An unknown netname is assumed to be an autoinstall terminal.
(d) Pressing PF6 cancels all tracing from all exits.
(e) Connection name in the termid field causes setting of all sessions.
á ñ
Figure 159. CETR transaction: Terminal and transaction HELP
panel (2)
Chapter 16. Trace control CETR 225


CIND—in-doubt testing tool
Chapter 17. CIND—in-doubt testing tool

Use CIND to: Note: You cannot use CIND on internal CICS system
transactions. If you change a system transaction so
Test the effect of in-doubt failures on application
that it is defined in transaction class DFHTCIND,
programs
CIND detects that it is to be used with a CICS system
Produce shunted units of work (UOWs) to test programs task, and issues message DFHIN1014 to CSMT. The
that use SPI commands to inquire on, and change the system task continues to run and CIND does not
characteristics of, shunted UOWs cause it to fail in-doubt when it reaches syncpoint.
Unshunt UOWs that have been shunted using CIND.
Note: For a description of the concepts involved in the
synchronization of distributed applications, including Running the CIND in-doubt tool
in-doubt periods and shunted UOWs, see the CICS 1. Change the transaction class of the transactions you
Intercommunication Guide. want to go in-doubt to DFHTCIND. (You can do this
using CEMT or CEDA.)
CIND can operate in a standalone system; it provides a way
of changing the UOW so that it is distributed, and of causing 2. Type CIND ON. This activates the tool and enables a
a failure during syncpoint processing in the in-doubt window. task-related user exit for task start. You should get the
following message:
It can be used to cause a failure in syncpoint processing as DFHIN1ðð1 date time applid termid userid.
follows: The in-doubt tool is now active for
CIND changes the UOW to be distributed by adding DFHTCIND tranclass transactions.
itself to the UOW as the syncpoint initiator and For every transaction that is started, the task-related
coordinator. This has the effect of simulating a link to a user exit inquires whether it is in transaction class
remote CICS system that has assumed the syncpoint DFHTCIND. If it is, the task-related user exit issues a
coordinator role and that has sent a syncpoint call to the CICS recovery manager to add a link to
PREPARE request to CICS. This in turn forces CICS to CIND, acting as a CICS coordinator system called
assume the role of a syncpoint subordinate. Being a DFHINDSP.
syncpoint subordinate means that during the two-phase
3. Run your transactions. If the transactions update
commit syncpoint protocol, CICS itself becomes in-doubt
recoverable resources and the TRANSACTION resource
as to the outcome of the UOW. While CICS is in-doubt,
definition specifies the INDOUBT attribute WAIT(YES),
CIND simulates a link failure to the syncpoint
they fail in-doubt. The transaction abends with abend
coordinator.
code ASP1, and the UOW is shunted. You can use the
If the TRANSACTION resource definition specifies CEMT INQUIRE UOW SHUNTED command to display
WAIT(YES), the failure in the in-doubt window causes the shunted UOWs.
CICS to shunt the UOW.
A transaction that updates non-recoverable resources, or
If the TRANSACTION resource definition specifies that issues only READ requests abends with abend code
WAIT(NO), a forced decision is taken to commit or back ASPR. However, the UOW is not shunted, because it is
out the UOW, as defined by the TRANSACTION read-only, so no syncpoint resynchronization is required
ACTION option. In this case, the UOW is not shunted, with remote coordinator DFHINDSP.
but is forced to back out or commit without consulting
4. Type CIND OFF. This disables the task-related user exit
the coordinator of the distributed UOW.
and stops any further invocations of your transactions
You can also use CIND to shunt a UOW that is genuinely going in-doubt. You should get the following message:
distributed across multiple CICS systems. It must be DFHIN1ðð4 date time applid termid userid.
activated on the CICS system where the syncpoint is The in-doubt tool is no longer active for
initiated, so that it can assume the role of syncpoint initiator DFHTCIND tranclass transactions.
and coordinator before any other CICS systems try to do so. 5. Type CIND RESYNC COMMIT or CIND RESYNC
In particular, CIND should not be activated for CICS mirror BACKOUT. This simulates a coordinator CICS system
transactions unless the mirror can be guaranteed to be the reconnecting to your CICS system. In this case, the
syncpoint initiator (that is, a mirror running a server coordinator is DFHINDSP. You should get the following
transaction that has been DPLed to specifying message:
SYNCONRETURN).
DFHIN1ðð7 date time applid termid userid.
When active, CIND forces all transactions defined to be in a Initiation of resynchronization for units of work
awaiting coordinator DFHINDSP is now complete.
new transaction class, DFHTCIND, to fail in-doubt when they
reach syncpoint.

CIND—in-doubt testing tool
The CICS recovery manager domain unshunts all Setting a single transaction in-doubt
UOWs that were previously shunted because of the tool.
The commit or backout specifies what happened in the If you want a single transaction to go in-doubt regardless of
dummy coordinator DFHINDSP, and hence what the its transaction class, an application can link to program
CICS recovery manager domain instructs its DFHINDAP. (No commarea is required in this case.) This
subordinates to do when the unshunt takes place. causes that single transaction to go in-doubt without the
For each UOW unshunted, message DFHIN1012 is sent need to type CIND ON. This single transaction can be
to CSMT detailing the UOW status as defined by resynchronized by typing CIND RESYNC COMMIT, and so
coordinator DFHINDSP, and the UOW status held by the on, as described in “Running the CIND in-doubt tool” on
CICS recovery manager. Both states should be the page 227. DFHINDAP works by enabling the in-doubt
same. task-related user exit if necessary and then issuing an API
call to the in-doubt task-related user exit to add the dummy
You can use the CIND RESYNC COMMIT command or coordinator. This has the advantage of allowing a test
the CIND RESYNC BACKOUT command to simulate application to decide it wants to force in-doubt dynamically,
what happens when UOWs are not synchronized. For after it has started. Hence a UOW, other than the first one in
example, a transaction may be run with CIND activated the transaction can be forced in-doubt.
and with a TRANSACTION resource definition that
specifies the INDOUBT attributes WAIT(NO) and
WAITACTION(COMMIT). In this case, the UOW is not
shunted but is forced to commit. The CICS recovery
Resource definitions
manager domain keeps a record of the UOW in order to The required resource definitions for CIND are provided in
resynchronize with the coordinator. CEMT shows the group DFHINDT, which is a member of group list DFHLIST.
UOW in committed status waiting for the return of the
coordinator. If a CIND RESYNC BACKOUT command is
issued at this point, the DFHIN1012 message output to
CSMT shows the UOW to be out of sync, as does
Messages
message DFHRM0111 output by CICS recovery
The in-doubt tool outputs audit trail DFHINxxxx messages to
manager domain.
CSMT at the following times:
When CIND is activated using CIND ON
Inquiring on the status of CIND
When CIND is deactivated using CIND OFF
Type CIND INQUIRE This returns the current status of CIND When a resync is initiated using CIND RESYNC
with one of the following messages: COMMIT or CIND RESYNC BACKOUT
DFHIN1ðð3 date time applid. The in-doubt tool For each UOW acted upon, when:
is active for DFHTCIND tranclass transactions.
– CIND adds itself as coordinator to the UOW
DFHIN1ðð6 date time applid. The in-doubt tool is – CIND simulates losing the link to the coordinator
not active.
system and the UOW is shunted
– CIND simulates losing the link to the coordinator,
Running the in-doubt tool using an EXEC but the UOW is not shunted
CICS LINK command – CIND causes resynchronization of a UOW.
Instead of running the in-doubt tool using a terminal and the
Each message shows the transaction ID, the task number,
CIND transaction, you can use the EXEC CICS LINK
and the UOW identifier.
command to link to the in-doubt tool from an application
passing a commarea; for example:
EXEC CICS LINK PROGRAM('DFHINDT') COMMAREA(COMM)
where COMM is a data-area that contains the commands to
pass to DFHINDT. COMM should contain one of:
' ON '
' OFF '
' RESYNC COMMIT '
' RESYNC BACKOUT '

CMAC—messages and codes display
Chapter 18. CMAC—messages and codes display

Use CMAC to give you individual message information as Explanation
provided in the CICS Messages and Codes manual. An explanation of the cause of the message.
To use the CMAC transaction: System action

The actions the system is taking.
Add the DFHCMAC group on the CICS system definition
(CSD) file to your initialization list (DFHLIST) User response
What actions you can or cannot take.
Add the data set name of the CICS messages file to the
definition of the DFHCMACD file within the DFHCMAC Destination
group. Where to see the message. This can be the console, the
end-user terminal, or a transient data queue.
For information about how to carry out these actions, see the
CICS Resource Definition Guide manual. Module
The name of the module reporting the error.
Notes:
For example, to display information about message
1. This transaction is not valid for the MVS console.
DFH5130, which does not have a component ID, type:
2. The information is available only in English.
CMAC 513ð
You start the transaction by typing one of the following:
You get the following display:
1. CMAC
2. CMAC abcd where ‘abcd’ is the abend code.
3. CMAC xxxx where ‘xxxx’ is the message number only.
à DFH513ð UNABLE TO LOCATE MODULE DFHCICS. PRIMARY
ð
CSD NOT INITIALIZED.
EXPLANATION: The DFHCICS module is missing from the library.
4. CMAC yyxxxx where ‘yy’ is the component id and ‘xxxx’ SYSTEM ACTION: Processing of the INITIALIZE command is
terminated.
is the message number. USER RESPONSE: Ensure that the DFHCICS module is present in
the library.
DESTINATION: SYSPRINT
5. CMAC DFHxxxx where ‘xxxx’ is the message number. MODULE(S): DFHCSDUP
F3=CANCEL
6. CMAC DFHyyxxxx where ‘yy’ is the component id and

‘xxxx’ is the message number.
If you use method 1, you get the display shown in á ñ

Figure 162.
Figure 163. CMAC transaction: 1st example screen
To display the message CE3528, type a component ID of CE

à DFHCMCð1 Display On-line Messages and Codes
ð and a message number of 3528. You get the following
Type the required message identifier, then press Enter.
display:
Component ID ===> (for example, TC for Terminal Control

FC for File Control, etc.)
This field is required for Messages in the
form DFHxxyyyy, Where xx is the Component ID.
à DFHCE3528 Signon failed during SECLABEL checking.
ð
Message Number => (for example, 1ð6ð, 5718, or Abend Code
such as ASRA, etc.) EXPLANATION: The signon request has failed because the
external security manager (ESM) detected a critical error.
SYSTEM ACTION: The signon transaction terminates.
USER RESPONSE: Refer to message DFHSNð1ð8 on the CSCS log

for the information and actions necessary to resolve this
problem.
DESTINATION: Terminal End User

F3=Exit to CICS
MODULE(S): DFHSNP
á ñ
Figure 162. CMAC transaction: initial screen F3=CANCEL
You tell CICS which message you want by typing the á ñ

component ID and the message number. If the message
does not have a component ID, leave that field blank. Figure 164. CMAC transaction: 2nd example screen
The display then gives information under the headings:

CMAC—messages and codes display
If you use methods 2 through 6 (listed above), the initial

screen is bypassed and you move directly to the message
information screen.

CMSG—message switching
Chapter 19. CMSG—message switching

Use CMSG to send messages from your terminal to one or After entering CMSG, you must include at least the message
more destinations. text, a destination (ROUTE, or OPCLASS, or both), and the
option SEND (which you can abbreviate to S). For example:
The destination may be:
CMSG 'GOOD MORNING',R=ALL,S
Another terminal
sends the message ‘GOOD MORNING’ to all terminals.
Another terminal, but only when a specified operator is
signed on at that terminal If all is well, your message is sent, and the response
Another terminal, but only when the operator signed on MESSAGE HAS BEEN ROUTED
at that terminal is in a specified class is returned to your terminal.
Another operator (CICS locates the operator, if currently
signed on, and sends the message to that operator’s This response is received for the normal completion of a
terminal) message-switching transaction. It means that the message
has been successfully routed to its destination but does not
All terminals reflect any delivery status.
All terminals with operators signed on in specified
classes You can use backspace characters in your input.
Any combination of these destinations. New-line characters (or carriage returns on a hard-copy
terminal) that are not part of the message are changed to
You can specify that the message is to be sent at some commas, unless they appear at the beginning or end of the
future time. If the message cannot be sent, your terminal is input, in which case they are deleted. In this way, you can
notified. use NL characters as option separators, instead of commas.
For example, on a display device, you could enter:
In addition, standard routing lists can be provided using the
terminal list table (TLT), which can include terminal and CMSG R=(Tðð1,Tðð2)#
operator identifiers. Multiple routing lists can be specified at T=15ðð#
'THE TIME IS 15ðð HOURS'#
the time the message is entered, and individual destinations
S@
can be deleted from, or added to, the lists at this time.
where the ENTER key.
CICS message switching is provided by a service program
invoked by a user-defined transaction identifier that must be You can enter the options, except SEND and CANCEL (one
defined to CICS. This transaction identifier can be CMSG or of which must be entered last), in any order after CMSG and
any user-defined 4-character transaction identifier. CMSG is one or more spaces. You can abbreviate every option,
the transaction identifier assumed throughout this book. except CANCEL, to a single character, and you can include
one or more options in a single input. If you specify two or
You can extend message switching to include predefined
more options, you must follow each by a comma, except the
messages and even complete message-switching transaction
last, which must be followed by a space or by an end-of-data
input formats.
(EOD) condition indicating the end of your input. Any data
The terminals from which message switching is initiated, and following a space in the same input is ignored.
all terminals of message destinations, must support BMS.
To mark the end of a single input:
Routed messages can be directed to a terminal, including the Press the ENTER key on display devices such as the
transaction terminal, that supports partitions. However, such IBM 3270
messages reset the terminal to “base” state.
Press carriage return for hardcopy terminals such as the
IBM 2741.
Sending a message To maintain the conversation with a terminal, the status of all
inputs, except the final input which includes the SEND
To send a message to another terminal or terminals, enter option, is saved in a single temporary-storage record.
the transaction identifier, CMSG, followed by the applicable
options, as shown in the syntax diagram on page A message-switching transaction remains conversational until
“Command syntax” on page 234. ended. This means that all input (even other transaction
identifiers) is passed to the message-switching program. You
Full details of the options are given under “CMSG command must end a message-switching transaction (possibly involving
options” on page 234. multiple inputs) before you can start a different transaction.

Canceling a message there are no spaces between the transaction identifier, the C,
or the following data.)
You can cancel your current message-switching transaction
by entering: For example, enter:
CANCEL as the last 6 characters of your input. You get CMSG R=(T4ð,T41)
the response: and you receive:
R OK CONTINUE INPUT,
TERMINATED BY OPERATOR. T=15ðð
RT OK CONTINUE INPUT
CMSG as your first 4 characters, followed by end-of-data 'THERE WILL BE ....... AT THE
(EOD). You get the response: RT OK CONTINUE MSG
NO INPUT - REENTER. MAIN NIO;FOMH PM VS;OGPTMOS SBR, CANCEL (see Note)
TERMINATED BY OPERATOR
CMSGx as your first 5 characters, where x is any
CMSGCMAIN BUILDING ON CALIFORNIA AVENUE
character other than a space or a C. You get the RT OK CONTINUE MSG
response: IN ROOM 4ð7',SEND
SPACE MUST FOLLOW TRANSID. MRTS OK MESSAGE HAS BEEN ROUTED
CMSG as your first 4 characters followed by a space Note: You can cancel and reenter instead of trying to
and EOD. This starts a new message-switching correct the input. This terminates the entire
transaction. You get the response: transaction. To save the previously entered input,
CONTINUE INPUT. enter CMSGC to restart at the previously saved
status point and continue the message.
The first three examples in this list terminate the
conversation and allow you to enter other transactions. Your terminal is free between a message-switching response
and the next input, and if it is in TRANSCEIVE status, an
automatically initiated task can be started on your terminal
Message-switching continuation before you can continue the message-switching transaction.
The message-switching transaction appears to be Upon completion of this new task, even if it required a
conversational. Internally, a new task is created to process response from you, the message-switching transaction
each message switching input. continues as if nothing had intervened. However, if you
receive a response indicating that the intervening task has
If a task requires more information to complete the issued a RETURN, you must enter the transaction identifier
transaction, the current status of the transaction is saved in followed by C to force continuation of the previous
temporary storage, a response is sent to your terminal, and message-switching transaction.
the task terminates with a requirement that the next task
started be a message-switching task.
Message delivery
The saving of status replaces any previously saved status for
any message-switching transaction from that terminal. You can deliver a message to a destination if the following
conditions are met:
If a message-switching transaction completes successfully, or
The specified delivery time has been reached
you have canceled it, an appropriate response is sent to your
The terminal is INSERVICE, and either:
terminal, the status of the transaction is not saved, and the
– The opid of the operator signed-on matches the
task terminates with no transaction restart specified. The
requested opid if specified in the ROUTE option
saved status is always used by a message-switching task to
continue a conversational input from your terminal. You can or
recall the saved status by entering the transaction identifier – The class of the operator signed-on matches any
to which you have added C (for example CMSGC). You can class specified by the OPCLASS option.
include additional input, but it must follow CMSGC with no
intervening spaces. The processing and paging status of a terminal, which also
affects delivery of eligible messages, is initially specified on
This method is useful because you can enter CANCEL to the CEDA DEFINE TYPETERM command. You can change
bypass errors in the current input and yet not allow the the status using the CEMT, CEST, and CEOT transactions.
conversation to continue. You can then enter, for example
CMSGC and then enter EOD, which puts the terminal in the When the processing status is RECEIVE or TRANSCEIVE, a
conversation that prevailed at the time of the most recent message is sent automatically to the terminal when no
input that has not been canceled or has not resulted in a transaction is attached to it.
message being routed. At this point you could also add an
option if desired, for example CMSGCT=1030. (Note that

When the processing status is TRANSACTION, you must the message) are interpreted as NL characters (there is no
request message delivery by entering a paging command, corresponding key on 3270 family display devices) and
see Chapter 22, “CSPG—page retrieval” on page 253. cause correct positioning of the message on all other
terminals.
A message is formed into one or more “pages”, the size of
which is predefined for a destination by the system
programmer. The terminal processing status determines the IBM 3767 Communication Terminal
delivery of the first or only page of a message. Succeeding
The keyboard/printer unit of the 3767 is eligible for entering
pages, if any, are sent according to the paging status of the
and receiving messages.
terminal as defined by the system programmer.
When the terminal is in PAGE status, you must request Sequential terminal
succeeding pages through a paging command.
On a sequential (BSAM) terminal, the CMSG
When the terminal is in AUTOPAGE status, the complete message-switching facility remains conversational until a
message is printed. message-switching transaction is completed or canceled.
Variable conditions requiring a response, such as operators
not being signed on, can be handled easily from an
Subsystems and terminal systems interactive terminal. These conditions, however, cannot
always be anticipated, and the message-switching task
With the exception of any specific details relating to the continues reading input and issuing error messages until a
ROUTE option (see page 237), all other information on the valid response is received. It is possible that an entire
use of the following subsystems in message switching is sequential input stream could be consumed in such a
given in the appropriate IBM subsystem guides: process. You are advised to ensure that a CMSG CANCEL
IBM 3600 Finance Communication System (VTAM), record appears in the sequential input following each
SC33-0233 message-switching transaction that could possibly require an
IBM 3650 Retail Store System, SC33-0234 unanticipated reply. This is strongly recommended following
IBM 3770 Data Communication System, SC33-0235 the final message-switching transaction.
IBM 3790 Communication System, SC33-0236.
IBM 3270 display devices

The responses to 3270 family display devices are designed
to fit on a single 40-character line of a Model 1 display. To
provide more space for the response, the indicators that
precede the response do not have the spaces between them
that appear on non-3270 terminals.
Responses to the 3270 family display devices do not erase

what is displayed on the screen and are displayed in the last
40 character positions of the line.
After a message-switching transaction has been started, you

can press the CLEAR key if you want to continue from an
empty screen. A CLEAR/CANCEL OR CONT xxxxx response
is displayed, where xxxxx is either INPUT, ROUTE, or MSG.
You can continue the transaction or, if you press the CLEAR
key a second consecutive time, you can cancel the
transaction. A better method of erasing the screen is to press
the ERASE INPUT key, because this does not cause an
interaction with the processor.
Because positions on the screen that are not keyed are not
received, you can position and display data on the screen in
various ways. For example, you can start each option on a
new line of the display screen. You must include a comma
between consecutive options. Also, if you want to start a new
line within the message text you should enter a field mark
character to indicate the end of the current line. All field mark
characters within a message (including the first character of
Chapter 19. Message switching CMSG 233

Command syntax
┌──
──────────────┐
55──CMSG──┬──────┬──'message'──┬─────────────────────────────────────────────────┬───6┬────────────┬┴───────5
└─MSG=─┘ │ ┌──
───────────────┐ │ └─,OPCLASS=n─┘
└─,ROUTE=──┬──6─Termid──/opid─┴──────────────────┬─┘
├─ALL────────────────────────────────┤
│ ┌──
───────────┐ ┌───────────────────┐ │
└──6─.termlist─┴───6─,±termid──/opid─┴─┘
5──┬─────────────┬──┬─────────────────┬──┬───────────────────────┬──┬─────────────┬────────────────────────5
└─,TIME=value─┘ ├─,DATE=value─────┤ └─,ERRTERM=─┬─Termid─┬──┘ └─,ID=(title)─┘
└─,FULLDATE=value─┘ └─ORIG───┘
5──┬────────────────────┬──┬───────────────────────┬──┬─,SEND───┬──5%
└─,HEADING=─┬─YES─┬──┘ └─,PROTECT=─┬─YES────┬──┘ └─,CANCEL─┘
└─NO──┘ ├─NO─────┤
└─Prefix─┘
The fourth form allows you to specify a number of days

CMSG command options from today. For example, a value of DATE=+3 (or D=+3)
means that the message is to be transmitted 3 days
The message-switching options are listed below. Except for
from today. The number must be in the range 0–4.
CANCEL, you can specify the first letter of each option
| DATE=+d entries are not accepted when the system1
instead of the entire option.
| time is between 2330 and 0030, (to avoid confusion at
CANCEL | or near midnight). If you use this form of the command
specifies that the current input is to be ignored and | within 30 minutes of midnight, the following error
institutes a non-conversational status between the | message is issued:
terminal and the message-switching transaction. +DATE INVLD FROM 233ð to ðð3ð
CANCEL must be the last 6 characters of the input.
CANCEL is also effective within a message. You can also specify a time for message delivery using
the TIME= option, which is described on page 238. The
DATE=value effects of TIME= and DATE= together are as follows:
The date on which you want your message to be
delivered. It can be specified in any of the following If you specify neither a time nor a date, the
forms: message is transmitted as soon as the receiving
terminal is free.
yy.ddd year (00–99) and day (001–366).
If you specify a time but no date, the message is
mm/dd/yy month (01–12), day (01–31), and year transmitted at the specified time today. For example,
(00–99). if the time now is 09.00 and you specify
mm/dd month (01–12) and day (01–31). TIME=0930, or TIME=+30, the message is
transmitted at 09.30 today.
+d number of days (0–4).
If you specify a date but no time, the message is
| The first three of these forms provide ways of specifying | transmitted at the current system1 time on the
| absolute dates, with the year (where used) in a 2-digit specified date. For example, if the time now is 10.30
| format. For example, if the current system1 date is in the and you specify DATE=+2, the message is
| year 1997, January 31 1997 could be specified as transmitted at 10.30 in two days’ time.
| 97.031, 01/31/97, or 01/31. In this last case, the year of If you specify both a date and a time, the message
| the current system1 date is assumed to be the year for is transmitted at the specified time on the specified
| delivery of the message. date. For example, if you specify DATE=07/29/98
| (If DATFORM=DDMMYY was specified in the CICS and TIME=1130, the message is transmitted at
| system initialization parameters, enter the second and 11.30 on 07/29/98.
| third of these as dd/mm/yy or dd/mm).
| If you want to specify an absolute date with the year

| in a 4-digit format, then use the FULLDATE
| parameter.
| 1 References to "system date", "system time", "system year" and so on mean the date time or year as would be returned by EXEC CICS
| ASKTIME.

Notes: | FULLDATE=value
| The FULLDATE option is similar to the DATE option, but
1. In all cases, the delivery time that you request must
| it requires a four-digit year to be entered. It specifies the
be less than 100 hours from the beginning of the
| date on which you want your message to be delivered. It
current day. This means that the delivery time can
| can be specified in any of the following forms:
never be later than 03.59 on the fourth day from the
current day. | yyyy.ddd year (0000–9999) and day (001–366).
| 2. When processing date options entered in the form | mm/dd/yyyy month (01–12), day (01–31), and year
| yy.ddd, mm/dd/yy and dd/mm/yy, CMSG operates a | (0000–9999).
| 'sliding 50 year window' to establish whether the
| mm/dd month (01–12) and day (01–31).
| year is in this century, the previous century or the
| next century. The two digit year is initially assumed | +d number of days (0–4).
| to be in the same century as the current date. If this
| assumed year is more than 50 years in the past or | The first three of these forms provide ways of specifying
| more than 50 years ahead, it is adjusted | absolute dates, with the year (where used) in a 4-digit
| accordingly. For example, if todays date is the 31st | format. For example, if the current system1 date is in the
| December 1997, the following DATE options are | year 1997, December 31 1997 could be specified as
| handled as follows: | 1997.365, 12/31/1997 or 12/31. In this last case, the
| year of the current system1 date is assumed to be the
| DATE=99.001 is initially assumed to be the
| year for delivery of the message.
| year 1999. Since it is within 50 years of the
| system1 year, the year 1999 is determined to be | (If DATFORM=DDMMYY was specified in the CICS
| the delivery date for the message. | system initialization parameters, enter the second and
| DATE=00.001 is initially assumed to be the | third of these as dd/mm/yyyy or dd/mm).
| year 1900. Since this year is more than 50 | The fourth form allows you to specify a number of days
| years ago, the delivery date is established as | from today. For example, a value of FULLDATE=+3 (or
| the year 2000. | F=+3) means that the message is to be transmitted 3
| In both of these examples above, the delivery date | days from today. The number must be in the range 0–4.
| is not accepted and the message 'DATE TOO FAR | FULLDATE=+d entries are not accepted when the
| IN FUTURE' is displayed. | system1 time is between 2330 and 0030, (to avoid
| confusion at or near midnight). If you use this form of the
| Note that the FULLDATE operand allows a four digit
| command within 30 minutes of midnight, the following
| year to be specified, and removes any possible
| error message is issued:
| ambiguity when using the DATE operand.
| +DATE INVLD FROM 233ð to ðð3ð
ERRTERM
| You can also specify a time for message delivery using
“termid” is the identifier of the terminal to which
| the TIME= option, which is described on page 238. The
notification is to be sent if the message is purged
| effects of TIME= and FULLDATE= together are as
because it is undeliverable.
| follows:
ORIG is a way of specifying the identifier of the
originating terminal. | If you specify neither a time nor a date, the
| message is transmitted as soon as the receiving
Note: A message is considered undeliverable to a | terminal is free.
destination if it cannot be delivered within a
specified interval after the requested delivery | If you specify a time but no date, the message is
time. This interval is specified by the system | transmitted at the specified time today. For example,
programmer. If no interval is specified, no action | if the time now is 09.00 and you specify
is taken for undelivered messages, and the | TIME=0930, or TIME=+30, the message is
ERRTERM option has no effect. | transmitted at 09.30 today.
If PRGDLAY is specified in the system initialization table | If you specify a date but no time, the message is
(DFHSIT), the transient data destination CSMT is | transmitted at the current system1 time on the
notified of the number of undeliverable messages purged | specified date. For example, if the time now is 10.30
for a terminal. In addition, if ERRTERM is entered, the | and you specify FULLDATE=+2, the message is
specified terminal is notified of the message number, title | transmitted at 10.30 in two days’ time.
identifier, and destination of the message. | If you specify both a date and a time, the message
| is transmitted at the specified time on the specified
| 1 References to "system date", "system time", "system year" and so on mean the date time or year as would be returned by EXEC CICS
| ASKTIME.

| date. For example, if you specify New-line (NL) characters within the message are kept.
| FULLDATE=07/29/1998 and TIME=1130, the (If the first character is a new-line character, it is
| message is transmitted at 11.30 on 07/29/1998. deleted.) This allows the operator to enter M=' and then
carriage return (CR) or the equivalent of CR, to begin
| Note: In all cases, the delivery time that you request
entering the message text at the left margin. The first
| must be less than 100 hours from the beginning
CR is deleted. Additional CRs may be entered if blank
| of the current day. This means that the delivery
lines are desired at the top of the transmitted message.
| time can never be later than 03.59 on the fourth
| day from the current system1 date. Note: If the HEADING option is specified, these blank
lines appear between the heading (time, date,
HEADING and originator’s terminal identifier) and the
specifies heading information. You can use H or message.
HEADING in place of HEADING=YES.
With NL processing, the delivered message is positioned
YES at the left margin. If an unformatted message, or a line
Specifies that the current time, date, and within a formatted message, exceeds the line width
identifier of the originating terminal is to precede defined for the receiving terminal, sentences are split
the message text. between words for any line exceeded.
NO OPCLASS
causes a previous heading request to be ignored. One or more numbers, each of which can be in the
range 1–24, that define the operator classes that must
ID=(title)
be signed on before a message can be delivered. If
title specifies the title (maximum length 62 characters) to
more than one number is specified, the list must be
be associated with the message.
enclosed within parentheses. For example,
See Chapter 22, “CSPG—page retrieval” on page 253 OPCLASS=(8,2) causes the message to be sent to all
for commands to request a display of the titles of all terminals that currently have an operator of class 8 or 2
messages queued for immediate delivery to that signed on, and to all terminals that have that operator
terminal. security value specified in their installed definitions. If
OPCLASS=1 is specified, the message is routed to all
MSG=message
terminals that are in service, regardless of whether an
“message” is the text of the message to be sent. The
operator is signed on or not.
keyword MSG and the equal sign are optional. You must
enclose the text within single quotation marks. A single If ROUTE is specified as well, the message is routed to
quotation mark to be included as part of the message all requested destinations, but is not eligible for delivery
must be represented by a pair of single quotation marks. to a terminal unless the class of the operator signed on
The message may be continued across multiple matches one of the numbers specified by OPCLASS.
consecutive inputs. However, if a ROUTE destination is qualified by an
operator identifier, OPCLASS is ignored for that
If the ending single quotation mark is omitted, the entire
destination. For more information about how ROUTE=
input is treated as part of the message and a request to
and OPCLASS= are used together, see the description
continue the message is sent to the terminal. The entire
of the ROUTE option.
transaction may be canceled, or alternatively, options
previously entered for this transaction may be saved by PROTECT
entering a single quotation mark followed by a comma to specifies message recovery for a CICS emergency
terminate the MSG option. The correct message can restart. You can use P or PROTECT in place of
then be reentered; the previous incorrect message being PROTECT=YES.
ignored.
YES
A single quotation mark at the end of data in a MSG
Specifies that $$ is to be prefixed to the
option means either the end of the MSG option, or the
temporary storage data identifier of the stored
first of a pair of single quotation marks indicating that a
message.
single quotation mark is to be included as part of the
message. NO
Specifies that a previous protect request is to be
In this situation, the response to the terminal is:
ignored. This is done by using the default prefix
CONTINUE INPUT OR MSG of **. The same method is used to omit the
If the first character of the next input is a single option altogether.
quotation mark, it is treated as the second of a pair of prefix
single quotation marks and the message is continued. Specifies a 1-or 2-character prefix to be used for
Any character other than a single quotation mark causes the temporary-storage data identifier of the stored
the message to be complete, and that character is message. If a single character only is specified, a
treated as the first character of a new option.

$ is provided as the second character. (For first) with the operator identifier PJ currently signed
example, PROTECT=T causes a prefix of T$.) on. If no such terminal is found, the sending
operator is notified. The operator identifier that you
If this option is omitted, a default prefix of ** is used. ** specify must not contain any of the following
is also the default for user application programs issuing characters:
BMS message requests where no protection is specified
, comma
(REQID option omitted).
) right parenthesis
A temporary-storage table (TST) entry is needed for
each prefix specified in the PROTECT option so that space.
message recovery is effective for that prefix.
Termid/opid
ROUTE is a terminal identifier qualified by an operator
specifies the destinations to receive the message. For identifier to restrict the message delivery to the
routing messages to 3600, 3770 (batch), or 3790 (batch) specified operator at the terminal location. For
terminals, see “Examples of 3600 and 3770 batch example, ROUTE=(LA04,OL/LBS,SF2) routes the
destinations” on page 240. message to terminals LA04 and SF2. The message
is routed to terminal OL only if the operator whose
Termid
identifier is LBS is signed on at that terminal.
is the identifier or identifiers of the terminals to
which the message is to be routed. For example, ROUTE=(T001,T001/OP1,/OP1) causes the same
ROUTE=(LA04,OL,SF2) routes the message to the message to be delivered three times to the same
three terminals with the identifiers LA04, OL, and destination if the operator OP1 is signed on at T001.
SF2. If routing is performed to several terminals of
ALL
the same device and map suffixes, CICS processes
causes the message to be broadcast to all
the message identically for all of them and the most
terminals.
restricting page size prevailing is used.
There is a variable limit on the number of terminals
The length of the terminal identifier specified in a
to which a message can be sent. This limit depends
message-switching transaction must be in the range
on a combination of factors. Significant factors are
1–4 characters, and must not contain any of the
the types of terminal in use, the number of each
following characters:
type, and the length of message sent. The CMSG
/ slash transaction is abended with an abend code of
ABMC if the limit is exceeded.
, comma
Note: If a CMSG ROUTE=ALL is issued to a large
) right parenthesis
number of terminals, a task for each terminal
( left parenthesis is initiated up to the MAXTASK value.
Because the tasks are single threaded, they
+ plus sign
are suspended and can give rise to an SOS
− minus sign condition. For guidance about avoiding this,
* asterisk see the CICS Performance Guide.
blank. .termlist
is a 1-or 2-character terminal list table (TLT) suffix
Note: A single message can be delivered more
preceded by a period. For example, .H3 identifies
than once to the same terminal. For
the terminal list table DFHTLTH3. A maximum of 10
example, the instruction
terminal lists can be specified, and the terminal lists
ROUTE=(T001,T001) causes two
that you specify are merged together. The entries in
transmissions of a single message to
the terminal lists contain terminal identifiers, or
terminal T001. If the destination terminal is
operator identifiers, or both. Duplicate entries within
in TRANSCEIVE status, the message
a single TLT are kept, though entries that are
appears consecutively at the terminal. If the
duplicated among the lists are deleted. (Entries are
terminal is in TRANSACTION status, the
considered duplicate if each has the same terminal
operator must request delivery of the
identifier and operator identifier.)
message.
Here are two examples that show the effects of
/opid merging TLTs that contain duplicate entries. For
is a 1-to 3-character operator identifier preceded by these examples, assume that terminal list table
a slash. The message is routed to the first terminal DFHTLTL1 contains T001 twice, and that
at which an operator with that identifier is currently DFHTLTL2 contains T001 and T001/OP1.
signed on. For example, ROUTE=/PJ routes the
message to the first terminal found (and only the

If you specify ROUTE=(.L1,.L2), all entries from ROUTE=(.L1,.L2,−T001,+T001/OP1); the −T001

DFHTLTL1 are included as destinations. causes all entries from the TLTs that refer to
Duplicate entries within DFHTLTL1 are kept. All T001 (including the T001/OP1 entry in
entries from DFHTLTL2 are checked for DFHTLTL2) to be deleted. The +T001/OP1
duplicates against the entries in the previously entry is then added and becomes the only
specified DFHTLTL1 and, if a duplicate is resulting destination. There is no duplicate
found, it is not repeated. because it has just been deleted.
The resulting destination list is T001, T001, A ROUTE option may be divided across multiple
T001/OP1. consecutive inputs. However, if it refers to a TLT, it
The order in which you specify the TLTs is must be completed in the same input in which it was
significant. If you specify R=(.L2,.L1), the started. An individual ROUTE parameter
DFHTLTL2 entries T001 and T001/OP1 are (termid/opid) may not be split across two inputs.
included in the destination list. However, the When both ROUTE and OPCLASS are specified
two entries for T001 in DFHTLTL1 are not together, OPCLASS further restricts the message
included because T001 is already in DFHTLT2. transmission. For example,
In this case, the resulting destination list is ROUTE=(LA04/PJL,/MGK,OL), OPCLASS=4 routes
T001, T001/OP1. the message to terminal LA04 if the operator whose
identifier is PJL is signed on. The message is also
(±termid/opid,...)
sent to the first terminal with the operator whose
A +termid/opid adds the specified destination (if not
identifier is MGK signed on. An operator whose
a duplicate) to the destinations contained in the
class is 4 must be signed on to OL before the
requested TLT. A −termid/opid deletes the specified
message can be routed there. Note that the
destination from the requested TLT. A −termid,
OPCLASS value is acted on only when no operator
without an opid, deletes all destinations of that
identifier is specified.
terminal (with or without operator identifier) resulting
from the requested TLT. + or −termid/opid SEND
parameters affect only those entries that result from specifies that all of the options have been entered and
requested TLTs, and have no effect on other + or − that the message is to be routed. SEND is the final
termid/opid parameters in the same request. All TLT option and must be followed by a space or an
suffixes must be entered before any + or − end-of-data.
parameters.
TIME=value
Here are some examples that show the effects of
“value” is the time at which you want the message to be
specifying both TLTs that contain duplicate entries
delivered. You can specify the time in one of the
and ± entries. For these examples, assume that
following four ways:
terminal list table DFHTLTL1 contains T001 twice,
and that DFHTLTL2 contains T001 and T001/OP1. hhmm where “hhmm” is an absolute time in the range
0001–2400. For example, TIME=1145 causes the
ROUTE=(.L1,.L2,+T001) has the same effect as
message to be transmitted at 11.45 am. The
R=(.L1,.L2). The entry +T001 is not added,
minutes value must be less than 60.
because it is a duplicate of an entry from
DFHTLTL1. The resulting destination is T001, +hhmm where “hhmm” is the number of hours and
T001, T001/OP1. minutes from the current time. The minutes value
must be less than 60. For example, TIME=+0720
ROUTE=(.L1,.L2,+T001/OP1,−T001) does not
means that the message is to be transmitted in 7
add +T001/OP1 because it is a duplicate of an
hours and 20 minutes from now. A value of
entry in DFHTLTL2. The −T001 causes all
TIME=+2400 means the same as DATE=+1.
entries from TLTs that refer to T001 (regardless
of whether they are qualified by an operator +mm where “mm” is the number of minutes from the
identifier) to be deleted. The message ALL current time. This value must be in the range
ROUTE ENTRIES DELETED is issued. 0–99. So, for example, a value of TIME=+75
causes the message to be transmitted 1 hour
If DFHTLTL2 did not contain the entry
and 15 minutes from now. The values TIME=+90
T001/OP1, the +T001/OP1 instruction would
and TIME=+0130 both cause the message to be
cause that entry to be added to the destination
transmitted in 90 minutes time.
list. The −T001 instruction would not then delete
the T001/OP1 entry from the list, because the +m where “m” is the number of minutes from the
effects of the + and − instructions are not current time. This value must be in the range
cumulative: they act in isolation on the original 0–9. So, for example, a value of TIME=+5
concatenated TLTs. causes the message to be transmitted 5 minutes
from now.

If you specify a delivery time on the current day that falls

within the past hour, it is interpreted as a request for 55──ROUTE=─────────────────────────────────────5
immediate delivery. An earlier time than that is ┌──
─────────────────────┐
considered already passed and is treated as an error. 5──┬──6─Termid──\ldc──/opid─┴─────────┬──5%
The following message is issued: ├─ALL──\ldc───────────────────────┤
│ ┌──
─────────────────┐ │
TIME ALREADY PASSED └──6─.termlist──\ldc─┴──┤ Idloop ├─┘
Note that, if the current time is 00.15, T=2345 is Idloop:
interpreted as 23.45 today because there has been a ┌──
─────────────────────────┐
change of date. The message is not therefore ├───6┬───────────────────────┬┴──┤
transmitted immediately. └─,±termid──\ldc──/opid─┘
Logical unit destinations where:
This section describes the use of the CMSG transaction to *ldc

send messages to logical units. For details of message is a 2-character LDC mnemonic preceded by an asterisk
handling within CICS subsystems, and of the use of the (*) that qualifies the destinations. The *ldc parameter
message-switching transaction at subsystem terminals, see may qualify an LU identifier (termid), a general broadcast
the appropriate CICS/OS/VS subsystem guide. (ALL), or a terminal list table specification (.termlist).
The *ldc parameter applies only to LUs, not to any
Each logical unit in a CICS-SNA network is identified by a start-stop or BSC terminals.
single terminal identifier and, if the logical unit is capable of Different LDC mnemonics may be included in one
receiving message text, messages may be routed to it in the ROUTE option specification; however, all destinations for
same way as they are routed to non-SNA terminals. Routing one message must indicate the same device type.
by operator identifier may also be employed if the logical unit
supports operator signon, and SNA and non-SNA Termid*ldc
destinations may be specified in the same ROUTE option. associates an LDC mnemonic with an LU
identification.
The destination for a message sent to a logical unit can be a
display or printer device, or it can be a data set or an ALL*ldc
application program in a subsystem controller. To the is a general broadcast to all terminals with the same
message sender, the destination behaves like a “terminal”, LDC mnemonic qualifying all LUs.
and any necessary formatting is performed by the CMSG Termlist*ldc
transaction or within the subsystem controller itself. .termlist*ldc
qualifies all entries in this terminal list table with the
Logical device codes specified LDC mnemonic. This overrides any LDC
specified within the terminal list table. This LDC
Some types of logical unit (LU) can be used to get access to specification does not apply to start-stop or BSC
more than one resource within a subsystem. For example, terminals.
data sent to a 3601 LU may be intended for an IBM 3604 Note: This qualification of a TLT occurs before any
Keyboard Display, an IBM 3618 Administrative Line Printer, succeeding TLTs or +/− entries are
or some other element of the IBM 3600 Finance processed, see example 9 in “Examples of
Communication System. The facility provided by CICS to 3600 and 3770 batch destinations” on
permit destination selection within LUs of this type is the page 240.
logical device code (LDC).
+termid*ldc/opid
The LUs that support destination selection by LDC are: adds a destination, if not a complete duplicate to
3601 LU any contained in the requested TLTs.
3770 batch LU −termid*ldc/opid
3770 batch data interchange LU deletes duplicate destinations resulting from the
3790 batch data interchange LU. requested TLTs. A −termid*ldc, without an opid,
deletes all destinations of that termid*ldc (with or
For the user of the message-switching transaction, the LDC
without operator identifiers) resulting from the
is a 2-character mnemonic code whose meaning is defined
requested TLTs. A −termid/opid, without an LDC
by the CICS installation. It may be used to qualify an LU
mnemonic, deletes all destinations of that
destination by including it in the ROUTE option in the syntax
termid/opid (with or without LDC mnemonics)
diagram that follows:
resulting from the requested TLTs.

If a destination is specified by /opid without termid, it Note: The default LDC mnemonic for T363 must
becomes termid/opid, in which termid is the identifier of the indicate the same device type as LDC mnemonic
first terminal or LU to which an operator with that identifier is DS.
currently signed on. If no such terminal or LU is found, the
3. R=ALL*LP
destination is not valid and the operator is notified.
Route message to all terminals (3600, 3770 batch and
interactive logical units, start-stop, and BSC) with all
Examples of 3600 and 3770 batch 3600 destinations qualified by mnemonic LP. LP is
destinations ignored for start-stop and BSC destinations.
These examples assume the following: 4. R=.L3

Use the terminal list table DFHTLTL3 for message
Terminal identifiers T36n and T37n are 3600 logical destinations. (This is the same as example 2, plus
units and 3770 batch logical units respectively; all others T362*DS/OP2 and T372*P1/OP2.)
are start-stop or BSC terminals.
5. R=(.L3,−T362*DS/OP2,−T372*P1/OP2)
LDC mnemonics DS and LP have been defined for the
This is the same as example 4, but deletes
system and T361, T362, and T363 during resource
T362*DS/OP2 and T372*P1/OP2, so is the same result
definition.
as example 2.
LDC mnemonic P1 has been defined for the system and
T371, T372, and T373 during resource definition. 6. R=(.L3,−T362*DS)
This is the same as example 4, but deletes all entries for
You can also use the TYPETERM LDCLIST attribute of T362*DS (with or without opids). The result is T361*DS,
RDO to define these mnemonics instead of the DFHTCT T363, all T37n terminals, and T40.
TYPE=TERMINAL macro shown.
7. R=(.L3,−T362)
Terminal list table DFHTLTL3 contains entries for:
This is the same as example 6. −T362 deletes all entries
T361*DS for T362.
T362*DS/OP1
T362*DS/OP2 8. R=.L4*LP
T363 LDC mnemonic LP qualifies (overrides) all entries in
T371*P1 DFHTLTL4. Resulting destinations are:
T372*P1/OP1 T361\LP T362\LP/OP1 T362\LP/OP2 T363\LP T4ð\LP
T372*P1/OP2 Note: The LP mnemonic has no effect on the start-stop
T373 or BSC terminal T40.
T40.
9. R=(.L4*LP,−T362*DS)
Terminal list table DFHTLTL4 contains entries for:
The −T362*DS causes no action, because the TLT
T361*DS destinations are qualified by LDC mnemonic LP before
T362*DS/OP1 the additions or deletes are processed, thus causing no
T362*DS/OP2 matching entry to delete.
T363
T40. 10. R=(.L4,+T363*LP)
Cause error message ‘INVALID LDC AT T363*LP’ to be
1. R=T361*DS generated. LDC mnemonic LP has a different device
Route message to terminal identifier T361 qualified by type from LDC mnemonic DS (first 3600 destination
LDC mnemonic DS. encountered is T361*DS). All 3600 destinations for one
message must indicate the same device type. All 3770
2. R=(T361*DS,T362*DS/OP1,T363,T371*P1,
batch logical unit destinations for one message must
T372*P1/OP1,T373,T40)
indicate the same device type.
Route message to:
11. R=/OP2
T361 and T362 qualified by LDC mnemonic DS
Route message to the first terminal or logical unit found
T363, using the default LDC
in the CICS terminal definition with operator identifier
T371 and T372 qualified by LDC mnemonic P1
OP2 currently signed on. If OP2 is signed on to T362,
T373 console keyboard/printer
the resulting destination is T362/OP2 with the default
T40, which is a start-stop or BSC terminal.
LDC mnemonic for logical unit T362. The default is DS
T362 and T372 require that an operator with because it is the first LDC mnemonic defined for T362.
identification OP1 be signed on before the message can The resulting destination is T362*DS/OP2.
be sent.

Note: If an option is entered, the error message is

Message-switching responses repeated unless a new ROUTE option is entered
before SEND. If the incorrect entry is changed or
Every input from the terminal receives a response. Most
deleted by responding with a space or
responses are preceded by indicators where the letters
termid/opid, the message is routed unless other
before OK represent the first character of each of the CMSG
errors are still present. These errors are
options (except CANCEL) as follows:
indicated by another message. If an option is
D DATE entered, it signifies normal entry mode in which
E ERRTERM multiple options can be entered requiring another
H HEADING SEND option to end the input.
I ID
M MSG The following is a list of all possible responses from the
O OPCLASS message-switching program (DFHMSP). Because of
P PROTECT device-dependent considerations, all responses are limited to
R ROUTE
25 characters plus the indicators.
S SEND
T TIME ALL ROUTE ENTRIES DELETED
These indicators identify the options that have been A space entered in reply to a incorrect destination
processed and that are currently in effect. message caused the remaining destinations to be
deleted, leaving no destinations to which to route the
Errors may occur because of: message. This condition forces a return to normal option
mode, and a ROUTE option must be reentered to
Syntax (for example, misspelled option, unbalanced
provide the message destinations.
parentheses, terminal identifier more than 4 characters,
invalid option separator, and message and destination CANCELED - TEMP STRG ERR N
not provided). N has a value in the range 1–4.
Specification (for example, the specified terminal has not
N=1. An error occurred on a temporary storage (TS)
been defined to CICS).
request.
Operation (for example, operator not currently signed on
N=2. An error occurred on a temporary storage (TS)
to the system).
request. A possible cause of this response, not
related to a TS problem, is a request for a TS
Syntax errors within an option cause it to be rejected by the
record that does not exist. This can happen if:
message-switching routine. To correct a known error, reenter
the option before typing the SEND keyword. – The transaction identifier is entered followed by
a C. This extended transaction identifier
Syntax errors cause no data to be processed in that input (CMSGC) normally requests a continuation of a
beyond the detected error. All following data must be message-switching transaction, but no previous
reentered to be included. status information exists for this terminal. See
“Message-switching continuation” on page 232.
A specification or operation error message may be written to
the terminal with an indicator that shows that the option in Note: A CICS cold start of temporary storage
question has been processed and is still in effect. Two causes the loss of any status saved
possible error messages are: from a previous CICS process.
1. M OK TERMID GT 4 CHAR AT T004A – The transaction identifier is entered in

lowercase on a 3270 family display device that
This message has been issued because the terminal
is defined as a dual case keyboard, and for
identifier is greater than 4 characters. The absence of
which no previous message-switching
the R indicator preceding the message shows that
transaction status exists.
ROUTE is not currently in effect and that the message
must be reentered. Note: The transaction identifier in the terminal
input/output area (TIOA) is not
2. MRHS OK INVLD TERMINL ID T004
translated. To correct this problem,
This message has been issued because the specified enter the transaction identifier in
terminal is not known to CICS. The R indicator shows uppercase.
that ROUTE is still in effect. Operator action as a result
N=2 also occurs when transaction routing is being
of this type of message is either:
used and indicates that the transaction identifier
A space (entry deleted) used to initiate the task is different to that specified
Termid/opid specifying a termid, or operator in the CICS system definition.
identifier, or both (entry changed)
N=3. An error (most likely caused by TS) occurred
Any option (the route option or another option may
on a DFHBMS TYPE=TEXTBLD request.
be entered).

N=4. An error (most likely caused by TS) occurred CONTINUE ROUTE OPERAND
on a DFHBMS TYPE=PAGEOUT request. The ROUTE option was being processed in the previous
input and a space or an EOD was found. Continue the
CLEAR/CANCL or cont input|route|msg
ROUTE option.
An operator on a 3270 family display device pressed the
CLEAR key and the message states continue (CONT): DATE ALREADY PASSED
A delivery date before the current day is invalid.
INPUT
The last option in the previous input is complete. DATE INVALID AT xxxxxxxx
Enter an option to continue. DATE must be in one of the following forms:
ROUTE yy.ddd year (ðð–99) and day (ðð1–366)

The last option in the previous input is ROUTE and mm/dd month (ð1–12) and day (ð1–31)
mm/dd/yy month (ð1–12), day (ð1–31),
a closing parenthesis cannot be found. Continue
and year (ðð–99)
entering ROUTE destinations.
D=+d day (ð–4)
MSG
DATE NOT xx/xx at xxxxx
The last option in the previous input is MSG, and a
DATE must start with 2 digits followed by a slash (for
single quotation mark to end the message cannot
month), or a period (for year). This message is issued if
be found, or a single quotation mark is found as the
the third character of DATE is not a slash or a period.
last character of the input, and might be the first of
a pair of single quotation marks. If the previous Notes:
input does not end with a single quotation mark,
1. September 5, for example, must be specified as
continue entering the message. If the previous input
09/05 and not as 9/5.
ends with a single quotation mark, enter another
single quotation mark to continue the message 2. The date must be valid, not 06/31 for example.
(which causes a single quotation mark to be
DATE TOO FAR IN FUTURE
included), or enter any option that causes the
Future delivery may not be specified after 0359 hours on
message to be considered complete.
the fourth day from the current day. The error is either:
Note: If the operator replies by again pressing the
CLEAR key (two consecutive times) it has 1. D=+n, where n is greater than 4, or
the same effect as entering CANCEL for the 2. DATE specified explicitly as being after the fourth
last 6 characters of the input. day from the current day, or
3. A condition of DATE and TIME that exceeds the
CONTINUE INPUT stated limit.
A SEND option has not been processed, and a ROUTE
or MSG option was not being continued. Continue by If conditions 1 or 2 occur, the DATE option is not in
entering any option. effect (the D status indicator is not present). If condition
CONTINUE INPUT OR MSG 3 occurs, both the DATE and TIME options are currently
The previous input ended with a single quotation mark in effect (the D and T status indicators precede the
with the MSG option being processed. This single message), and one or both of them must be changed to
quotation mark could specify the end of the MSG option a valid delivery time or the error occurs again.
or could be the first character of a pair of single ERRTERM INVALID AT xxxxx
quotation marks (signifying that a single quotation mark An ERRTERM must be 1–4 characters.
was to be included within the message).
ERRTERM INVLD/UNSUPP xxxx
If the next input starts with a single quotation mark, the
A terminal identifier specified for the ERRTERM option
message is continued with a single quotation mark
does not have an entry specified in the CICS terminal
included in the message. A nonpaired single quotation
definition, or it is for a terminal type not supported by
mark is required to end the MSG option.
BMS, and is therefore invalid. Valid replies by the
If the next input starts with any character other than a operator to this are:
single quotation mark, it is treated as the beginning of a
new option and the MSG option is considered complete. 1. A terminal identifier or ORIG in the same format as
a normal ERRTERM destination (without entering
CONTINUE MSG the option ERRTERM or E). The message is routed
The previous input ended with the MSG option being following this input unless the new ERRTERM
processed, but no single quotation mark ended the specified is invalid. In this case, the message is
entered text. Continue the message. repeated.
2. A space as the first character (followed by an EOB
or comments). This causes the entire ERRTERM

specification to be eliminated. The message is destination (without entering the option ROUTE= or
routed following this input. R=) that replaces the invalid destination.
3. Any option that causes a return to normal option 2. A space as the first character, which causes the
processing mode. If another ERRTERM option is invalid destination to be deleted.
not entered to correct this condition, the same error
3. Any option that causes a return to normal option
message is repeated after SEND has been
processing mode. If another ROUTE option is not
reentered.
entered, the same condition exists after the SEND
option is reentered.
HEADNG NOT YES/NO AT xxxx
A HEADING option may only be specified as follows:
Note: 1 and 2 cause the message to be routed if the
HEADING resulting destinations are valid; otherwise,
HEADING=YES another error message is issued.
HEADING=NO
H LDC NOT 2 CHARS AT xxxxx
H=YES The LDC mnemonic that follows the * in the ROUTE
H=NO destination must be 2 characters.
ID OPERAND GT 62 CHARS MESSAGE HAS BEEN ROUTED
An ID option must be from 1–62 characters in length, A SEND option has been processed and the message
and enclosed within parentheses. has been routed to its destinations. This is the normal
completion of a message-switching transaction.
ID OPERAND MISSING
The ID option requires the identifier to be enclosed MSG NOT SENT - NO RECEIVER
within parentheses. This condition is caused by an OPCLASS option
specified without a ROUTE option and no operators, with
ID PARAM MISSING OR NO )
the specified operator class, or classes, currently
The ID option must be from 1–62 characters in length
signed-on to terminal types supported by BMS. To
and enclosed within parentheses.
correct this situation, a new destination must be entered
INVALID LDC AT xxxxxxxx by the ROUTE option, or OPCLASS option, or both.
The LDC mnemonic is not valid for the logical unit, or a
NEED OPCLASS OR ROUTE
previous entry contained an LDC mnemonic that
The SEND option was entered without specifying any
indicated a different device type.
destinations for the message. To correct this situation, a
Note: A missing LDC mnemonic can cause this destination must be entered by the ROUTE option, or
message if the default mnemonic for that station OPCLASS option, or both.
indicates a different device type than a previously
indicated mnemonic (specified or defaulted). NO INPUT - REENTER
A transaction identifier was entered followed by
INVALID OPND AT xxxxx end-of-data (EOD), or the number of backspace
An option xxxxx is invalid (possibly caused by a keying characters entered caused the deletion of all the data
error). No data beyond this point was processed. The (including the position following the transaction
status indicators represent the options that are in effect. identification, if present). If the input does not start with
the transaction identifier, the terminal remains in
INVALID TBL SFX AT xxxxx
conversation. Otherwise, it is not in conversation.
A terminal list table suffix must be 1 or 2 characters
preceded by a period. NO MESSAGE PROVIDED
The SEND option was entered without specifying the
INVLD OPERATR ID AT xxxxx
message. To correct the situation, provide the message.
An operator identifier must be 1, 2, or 3 characters
preceded by a slash. NO MSG STRT QUOT AT xxxxx
A MSG parameter must be enclosed within single
INVLD SEPARATOR AT xxxxx
quotation marks. A single quotation mark must follow an
The end of an option must be followed by a space, a
M or MESSAGE.
comma (except for SEND), a carriage return (new-line
character), or end of data (EOD). NO TRMID FOR LDC AT xxxxx
The destination started with an asterisk *. A logical unit
INVLD TERMINL ID xxxx
identification must precede the LDC mnemonic.
There is no entry in the CICS terminal definition for the
terminal identifier specified for a ROUTE destination. NO TERM LIST TBL-xx
The valid operator reply is one of the following: An entry for a terminal list table with suffix xx
(DFHTLTxx) was not found in the CICS system
1. A terminal identifier, or operator identifier, or both, in
definition.
the same format as a normal termid/opid ROUTE

OPCLASS NOT 1-24 AT xxxxx SPACE MUST FOLLOW TRANSID

An OPCLASS parameter must be in the range 1–24. One or more spaces must follow the transaction
identifier before the first option can start. (The character
OPERATORS NOT SIGNDON nnn
C causes a continuation from the last input preceding a
The ROUTE option specified operator identifications
normal completion or a cancelation.)
without terminal identifiers (that is, ROUTE=/opid). nnn
operator identifications are not currently signed on. TERMID GT 4 CHAR AT xxxxx
A terminal identifier must be 1–4 characters.
The valid reply to this is to enter one of the following:
TERMID NOT +/− at xxxxx
1. A space as the first character, which deletes the
All TLT suffixes must be specified before any individual
nnn destinations.
destination (which must be preceded by a + or −) may
2. The character D (or any other character) which be entered. A ROUTE option that specifies a TLT suffix
causes each of the nnn destinations to be may not be continued on a succeeding input. If a
individually displayed through the message OPRTR ROUTE option includes more than one parameter, it
ID NOT SIGNDON. must be enclosed in parentheses.
3. Any option that causes a return to normal option
processing mode. If no further ROUTE options are
The operator entered CANCEL as the last 6 characters
entered, this same condition exists if an operator
of the previous input, or pressed the CLEAR key twice in
does not sign on before the SEND option is
succession on an IBM 3275 (or 3277) display station.
reentered.
The previous input is canceled and the terminal is not in
Note: This message is only issued if nnn is greater conversational mode with CICS message switching.
than 5; otherwise, each destination is individually
TIME ALREADY PASSED
displayed. Reply 1 causes the message to be
A delivery time for the current day, more than one hour
routed if the resulting destinations are valid;
before the current time is considered already passed
otherwise, another error message is issued.
and is invalid.
OPRTR ID NOT SIGNDON /xxx If the message is for immediate delivery, enter T=+0, to
An operator with identifier xxx, specified as a destination replace the TIME option that is still in effect.
(entered either by the terminal operator or included as
If the message is for delivery at the specified time on a
an entry in a TLT whose suffix was specified), is not
future day, enter the appropriate DATE option. The
currently signed on to any terminal controlled by CICS.
specified time is still in effect.
If the message is for delivery at a different time, reenter
The valid reply to this is to enter one of the following:
the TIME option.
A terminal identifier, or operator identifier, or both in
TIME INVALID AT xxxxx
the same format as a normal termid/opid ROUTE
TIME must be one of the following:
destination (without entering the option ROUTE or
R), which replaces this /xxx destination. hhmm 0001–2400 (mm<60)
A space as the first character, which causes the +hhmm 0000–2400 (mm<60)
/xxx destination to be deleted.
+mm 00–99
Any option that causes a return to normal option
+m 0–9
processing mode. If no further ROUTE options are
entered, this same condition exists if an operator where hh=hours and mm=minutes.
with identifier xxx does not sign on by the time the
SEND option is reentered. TIME NOT 4 CHARS AT xxxxx
A TIME parameter must be a 4-digit number if it is not
Note: The first two replies cause the message to be preceded by +.
routed if the resulting destinations are valid,
otherwise, another error message is issued. TOO MANY TBL SFX AT xxxxx
A maximum of 10 TLT suffixes may be specified.
PROTECT OPND NOT 1-2 CHAR
The PREFIX option of the PROTECT option must not UNBALANCD PARENS AT xxxxx
specify more than 2 characters. A ROUTE or OPCLASS option started with a
parenthesis but did not have one at the end, or ended
ROUTE INVALID AT xxxxx with a parenthesis but did not have one at the beginning.
A field separator entered before the first ROUTE xxxxx represents the characters near the relevant end of
parameter, or 2 consecutive field separators were found. the option.
Reenter a valid ROUTE option.

UNSUP OPRT TRMNL xxxxxxxx 6. CMSG ‘FRED - WHAT IS CURRENT STOCK ON P/N
An operator identifier without a terminal identifier was 4837-LP4# BPK’,R=BLD3,H,S
specified as a ROUTE destination; however that This routes a message to BLD3 asking Fred a
operator is signed on to a terminal that is a type not question and including the requestor’s initials
supported by BMS and is, therefore, an invalid (operator identifier). A heading is included so
destination. that Fred also knows the originating termid.
The valid reply to this is the same as for the message 7. CMSG ‘PNO 4837-LP4, QTY 26?’,R=/BPK,H,S
OPRTR ID NOT SIGNDON. This shows Fred’s answer routed to the terminal
at which operator identifier BPK is currently
UNSUP TERMINAL xxxxxxxx
signed on.
A terminal identifier, specified as a ROUTE destination,
is for a terminal type not supported by BMS and is, 8. CMSG ‘BRID KADDER ARRIVING 3:15 PST. PLEASE
therefore, an invalid destination. MAKE RESERVATION# M. KRN’,R=PADC,H,S
This makes a request for a reservation for a Mr
The valid reply to this is the same as for the message
Kadder.
INVLD TERMINL ID.
9. CMSG ‘SHUTDOWN IN 5 MINUTES’,R=ALL,T=1655,S
ZERO LENGTH MSG AT '' This sends the shutdown message to all
A message must have at least one character enclosed in terminals.
single quotation marks. A single quotation mark to be
Note: Examples 1, 2, 3, and 9 are possible candidates for
included as part of a message must be entered as two
inclusion in a sequential (BSAM) terminal input
separate single quotation mark characters. A message
stream during startup.
must start with a single quotation mark and may be
followed immediately by pairs of single quotation marks.
+DATE INVLD 2330 TO 0030

A DATE=+ option is invalid from 30 minutes before to 30
minutes after midnight.
Examples of complete message-switching

transactions
Here are some typical examples of the CMSG transaction.
In all of the examples,

1. CMSG R=ALL,‘GOOD MORNING#TODAY IS FRIDAY
FEB 1’,S
This sends a good morning message to all
terminals.
2. CMSG ‘GOOD MORNING’,R=.G1,T=0900,S
This routes a good morning message to be
delivered at 0900 hours to all destinations
contained in DFHTLTG1. (Locations in Eastern
time zone.)
3. CMSG ‘GOOD MORNING’,R=(.G2,+CHI4),T=1000,S
This message is for delivery at 10.00 hours to
terminals in Central time zone (DFHTLTG2).
Also included as a destination is termid CHI4,
which was recently added but not yet included in
the TLT.
4. CMSG ‘SUPERVISORS’ ‘MEETING IN 5
MINUTES’,O=(4,7),S
This routes the message to all supervisors who
are assigned operator class 4 or 7 and are
currently signed on to CICS.
5. CMSG R=ALL,‘NEW PRICE MODEL 402 - $28.70’,S
This sends the price of the new model to all
terminals.


CRTE—remote transactions
Chapter 20. CRTE—remote transactions

Use CRTE to run transactions that reside on a remote CEOS and CEOT with CRTE, and you cannot use PA or PF
system. keys to invoke transactions under CRTE.
Transaction routing in a multiregion operation (MRO) You end a routing session by entering CANCEL. If you have
environment or for intersystem communication (ISC) is signed on to the remote system, the CANCEL request
usually achieved by making entries in the PCT. The entries automatically signs you off.
define the transaction as remote, and name the system on
which it is to be processed. Entering the transaction code When a routing session has ended, you get the message:
then causes CICS to route the requests to the named ROUTING SESSION TO SYSTEM system-id HAS BEEN TERMINATED
system.
Notes:
The CRTE transaction provides you with another way of
1. If you use CRTE to route transactions through more than
running a transaction on a remote system. Use CRTE, rather
one system, then, to end the routing session, you must
than making special PCT entries, for infrequently-used
press CANCEL the same number of times as you
transactions or when using transactions such as CEMT
entered CRTE.
which reside on all systems. You must use CRTE when EDF
is used to test a transaction running on a remote system. 2. While a terminal is in a routing session with another
However, because the session has to be established and system (that is, during the period between entering
canceled explicitly, additional signon operations may be CRTE and CANCEL) the terminal cannot receive
required. CRTE can be invoked from a 3270 terminal, but not messages delivered by automatic transaction initiation
on LU6.1 links. (ATI).
3. The message cannot be delivered immediately if a
The syntax of the routing transaction is:
transaction:
Runs on a remote system using CRTE
55──CRTE──SYSID=sysid──┬────────────────┬──5%
└─,TRPROF=trprof─┘ Builds a message using BMS paging
Sends the message using a BMS SEND PAGE
command
where
Does not specify either RETAIN or RELEASE.
Sysid
It is delivered when the routing session ends, but only if
is the name of the system that is to process the
the terminal was in TRANSCEIVE status when the
transaction. This sysid is the same as the 4-character
routing session commenced. Alternatively, you can
CONNECTION specified, either by using RDO (resource
retrieve the message (while still routed) using BMS
definition online), or the 4-character SYSIDNT specified
paging commands.
in the DFHTCT TYPE=SYSTEM definition of the remote
system. 4. There are some restrictions on the use of CRTE with
BMS chaining of messages:
Trprof
is the 8-character name of the profile to be used for the You cannot use CRTE as a chained transaction
session that carries the intersystem flows, if that session without losing the logical message from which
uses VTAM. If VTAM is used and ‘trprof’ is not entered, CRTE was to be chained.
the default profile DFHCICSS is used. You cannot use chaining within a routing session
without purging the logical message currently
The routing transaction verifies that the specified remote attached to the terminal.
system is known and is available. If it is, a message is
displayed confirming that a routing session to the required You cannot route transactions back to any system in
system has been started. the chain.
When you have received this message, you can clear the
screen and enter the transaction identifier for the transaction
that is to be run on the remote system. In fact, you can use
the terminal as if it were connected directly to the remote
system, although you might be asked to sign on to the
remote system before being allowed to run any transactions.
The transactions that you can invoke include
pseudoconversational transactions, BMS paging transactions,
and even CRTE itself. However, you cannot use transactions

CRTE—remote transactions

CSFE—terminal and system test
Chapter 21. CSFE—terminal and system test

Use CSFE to diagnose terminal problems and software
problems. This transaction is mainly intended to be used by
System spooling interface trace
system programmers and IBM field engineers.
You can use CSFE to request additional trace and diagnostic
Use this transaction to: facilities for the system spooling interface.
Test your terminal

55──CSFE spoolfe=──┬─ON──┬──5%
Activate the system spooling interface trace └─OFF─┘
Activate the terminal builder trace
Activate any of the following: storage freeze, the storage OFF
violation trap, and the global trap/trace program exit switches off the system spooling interface trace and the
routine. diagnostic facility.
For each of these activities, successful completion of the ON
CSFE transaction gives you the following message: specifies that additional trace entries of system type are
DFHFE33ð1 Transaction complete provided for the system spooling interface.
For information about the use of this transaction, see the SPOOLFE
CICS Problem Determination Guide. is the system spooling interface trace and diagnostic
facility.
Terminal test
Terminal builder trace
You can use CSFE to test your terminal, but only if it is one
of the terminals supported by CICS. You can use the CSFE transaction to activate and deactivate
the terminal builder trace.
You cannot use CSFE to test the following:
IBM 2780 Data Transmission terminals 55──CSFE zcqtrace──┬─=termid──────┬──5%
IBM 3600 Finance Communication System terminals ├─,AUTOINSTALL─┤
└─,OFF─────────┘
IBM 3614 Consumer Transaction Facility terminals
IBM 3735 Programmable Buffered terminals
,AUTOINSTALL
Output-only printers (for example, printers of the IBM Switches tracing on for autoinstalled terminals.
3270 Information Display System).
,OFF
You start the transaction by entering CSFE on the command Switches tracing off for individual and autoinstalled
line of the screen, as follows: terminals.
CSFE =termid
Press the ENTER key. You get the following display: Switches tracing on for the terminal or connection
identified by termid.
DFHFE33ð4 Enter PRINT for character set, END to
terminate. All other data will be echoed.
END
When you type END on the command line of the screen,
the test ends.
PRINT
When you enter PRINT, all characters printable or
capable of display at the terminal are sent to your
terminal.
Any other input is returned to your terminal (that is, it is

echoed), unless it is of the form of one of the other CSFE
requests.

Debug functions 55──CSFE debug──┬─,CHKSTSK=─┬─CURRENT─┬──┬──5%

│ └─NONE────┘ │
Storage freeze, the storage violation trap and the global └─,CHKSTRM=─┬─CURRENT─┬──┘
trap/trace exit are all debugging functions that are controlled └─NONE────┘
by the CSFE transaction. These functions are described in
the following sections.
CURRENT
Specifies that validity checks are to be performed on the
Storage freeze user storage (not the CICS storage) for the current task
whenever the trace program is entered. Validity checks
You can use CSFE DEBUG to freeze storage that is are to be performed for the currently active task, as
normally freed during the processing of a transaction. The follows:
frozen storage is not freed until the end of the transaction.
This freezing of storage can help you in the subsequent Validity checking of the storage chain for the task
diagnosis of problems that may have occurred during Validity checking of the addresses and storage
processing. accounting areas for all storage areas on the
transaction storage chain.
55──CSFE debug──┬─,TRANID=xxxx─┬───────────────5
└─,TASKREQ=yyy─┘ For information on the CSFE options and their actions,
see the CICS Problem Determination Guide.
5──┬───────────────────┬──5%
│ ┌─OFF─┐ │ NONE
└─,STGFRZ=─┴─ON──┴──┘ deactivates the user storage checking function.
CHKSTRM={CURRENT|NONE}
You must code the options in the order shown in the syntax The terminal subpools, above and below the line, are to
display above. be checked for the CURRENT task or for NONE (no
tasks).
STGFRZ= ON or off
specifies that you want the storage freeze function to be
set on or off. If you omit this option, storage freeze is
set to OFF by default. To improve efficiency, storage
freeze should be switched OFF when not required.
TASKREQ=yyy
This is an alternative method of identifying the
transaction. “yyy” is the PA or PF key definition on a
3270 display device which identifies the transaction for
which storage freeze is to apply. For example,
TASKREQ=PA1.
TRANID=xxxx
Identifies the transaction for which storage freeze is to
apply.
Storage violation trap

Use CSFE DEBUG to activate and deactivate the storage
violation trap, which is in the trace program (DFHTRP), the
exec interface program (DFHEIP), and the resource manager
interface program (DFHERM).
This trap lets you verify the user storage associated with the
currently active task. The storage violation trap is entered
before the trace program returns to its caller after making a
trace entry.
When a storage violation is detected by the trap, an

exception trace entry is made, a CICS system dump is
produced (if dumping has not been disabled), and the
storage violation trap is switched off.

Global trap/trace program exit and global

kernel exit
You can use CSFE DEBUG with the TRAP or GTRAP
operand to activate and deactivate the global trap/trace
program exit routine or the global kernel exit routine
respectively.
These exits are intended to be used only under the guidance

of IBM support personnel.
55──CSFE DEBUG──┬─,TRAP=─┬─ON──┬───┬──5%
│ └─OFF─┘ │
└─,GTRAP=─┬─ON──┬──┘
└─OFF─┘
TRAP={ON|OFF}
The global trap/trace program exit routine is to be
activated or deactivated.
GTRAP={ON|OFF}
The global kernel exit routine is to be activated or
deactivated. On each domain call and return, and each
subroutine call and return, the kernel invokes the global
kernel exit routine, if it is activated.
TRAP= ON or off
specifies that the global/trap exit routine is to be
activated or deactivated.
Chapter 21. Terminal and system test CSFE 251


CSPG—page retrieval
Chapter 22. CSPG—page retrieval

Some transactions, especially those performed on screens,
produce a response that is too large to be displayed or 55──CSPG──Getpage──┬───┬──B──┬──────┬──────────5
└─A─┘ ├─\ldc─┤
printed at one time. The whole response is held on direct └─\ALL─┘
access storage, and only the first portion (called a page) is
displayed. You can manipulate these pages, through basic 5──┬─────────┬──5%
└─,hhhhhh─┘
mapping support (BMS), using the CSPG page retrieval
transaction. You can use paging to view all pages of the
response, in any order. All the pages produced by a Getpage
transaction make up a logical message. This is the user-defined identification code for the
retrieval transaction, and is 1–7 characters long. This
A page retrieval session begins when you enter the first page
code is defined by the PGRET system initialization
retrieval command, or when the first page is presented by
parameter. For convenience, make the code as short as
automatic transaction initiation (ATI). During the session,
possible; for example, P/.
CICS passes commands directly to BMS terminal paging,
without following the normal transaction identification A You can ignore this option unless chaining is being
procedure. used. It is the level, within a chain of logical messages,
of the logical message to be retrieved. You must
When using BMS for IBM 3780 Communication Terminal enclose it in parentheses. It can be one of the following:
transactions, switch off the SPACE COMPRESS EXPAND
(standard feature), TRNSPCY (special feature), and the n message is at level n
INHIBIT IRS (special feature) switches. +n message is n levels forward
Pages to be manipulated with paging commands must have -n message is n levels backward
been created by BMS, which must be active in the system to P previous level backward
service the commands. Paging commands enable you to:
C current level (the default)
Retrieve a page.
N next level forward
Display information about logical messages queued for
your terminal. L last level.
Chain a logical message, that is, retain the previous For more information on levels of messages, see
logical message on direct access storage while you “Message chaining” on page 255.
enter a new transaction.
B Defines the next operation to be performed on the
Purge a logical message, that is, erase it from direct
logical message at the current level, or at the level
access storage; a paging session must be ended by
specified by the a option It can be one of the following:
purging the message.
Copy a page to another terminal. n page n
+n page n pages forward
You select the above functions by entering a unique
identification code for each function. This code is 1–7 -n page n pages backward
characters long, and is defined by the PGRET, PGCHAIN, P previous page
PGPURGE, and PGCOPY system initialization parameters.
C redisplay current page (after clearing the screen)
Do not use codes that are the same as the leading N next page
characters of any transaction defined in the PCT.
L last page
A for an autopaging (that is, hard copy) terminal
Retrieve a page that is temporarily in paging mode: return the
terminal to autopaging mode and output all
The page retrieval command allows you to retrieve a remaining pages.
specified page. If partitions are in use, the page retrieval This is discussed further under “Status of
command refers to the partition in which it has been entered hardcopy terminal” on page 257.
(see “Inquiring on the status of CIND” on page 228).
X enter data that is not recognized as a paging
command.
This is discussed further under “Single keystroke
retrieval (SKR)” on page 254.

*ldc If you omit *ldc, and the application program in the logical
Is the LDC for the device to which you want to send the device does not provide a default, BMS selects the first page
message. (See Page retrieval for logical devices.) destined for a logical device that is currently in PAGE status.
The application program in the logical unit should provide a
*ALL
default LDC, because pages may be delivered to logical
A special case of *ldc.
devices other than those you originally specified.
Hhhhhh
In either case, if your request is the first request for a page
Is the 6-digit hexadecimal identifier of an undelivered
from a logical message, all pages (within the logical
logical message to be retrieved. You would normally
message) destined for logical devices currently in
determine this identifier by entering a page query
AUTOPAGE status are delivered after the first or specified
command (see “Display information about logical
page is delivered to a device in PAGE status.
messages” on page 255).
If you do not specify an identifier, the oldest message is The getpageA command supports an *ldc specification for
retrieved. After a paging session has started, you can nonrouted messages created for a 3601 logical unit. The
omit hhhhhh because all subsequent pages are from the various forms of getpageA are interpreted as follows:
current message.
getpageA*ALL-resets to autopaging and delivers all
pages for the logical devices that have autopage
In the following examples, P/ is the page retrieval transaction
specified in the terminal definition, but that were
identifier:
temporarily placed in page status by the CICS
P/7 Retrieve page 7 of this message. application programmer.
P/N Retrieve next page (following the one being getpageA*ldc-resets the specified logical device to
displayed) of this message. autopage and delivers the pages for that *ldc. The
P/(N)9 Retrieve page 9 of the next message (of several that command is similar to getpageA*ALL, except that it
have been chained). operates only for the specified logical device.
getpageA-resets to autopaging and delivers the
Single keystroke retrieval (SKR) remaining pages for the logical device for which pages
are currently being displayed.
If you use a 3270 display device under BTAM or VTAM, you
| can use PA or PF keys, as defined in the SKRxxxx system
Page retrieval and partitions
| initialization parameter, to enter page retrieval commands,
and greatly reduce the number of keystrokes necessary in a The page retrieval commands, including any PA and PF keys
page retrieval session. used in single keystroke retrieval, refer to the partition in
which they are entered. For example, P/N means ‘retrieve
After the session has ended, the PA and PF keys can again
the next page for this partition’. The partition in which the last
be used for initiating transactions in the usual way. The CICS
paging command is entered is the current partition. A paging
System Definition Guide gives further information on this command for a partitioned message entered on a
topic.
nonpartitioned screen (that is, after CLEAR) refers to the
current partition.
Page retrieval for logical devices
After a transition from base (unpartitioned) state to
Your application program can send messages to a partitioned state, or a change of partition set (that is, the
communication system such as the IBM 3600. Your initial page display, a page display following CLEAR, or
application program can also send different pages to each of following a change in the level of page chaining), the current
the logical devices within the system. These pages must be page is displayed in each partition. The current page is
grouped as a single logical message, held in storage. initially the first page for that partition. It is updated by page
retrieval commands.
Each part of a logical message is accompanied by a logical
device code (LDC) that identifies its destination. When
retrieving the pages for a logical device, you must specify the
LDC for that device. However, you do not need to do this if
the user-written program in the logical device controller
provides a default LDC mnemonic.
If you specify the page number and *ldc, delivery begins with
the specified page for that logical device. If the logical device
is in AUTOPAGE status, all pages for that logical device,
starting with the requested page, are written. If the logical
device is in PAGE status, only the specified page is written.

P/2 The second page of message is displayed.

Display information about logical
C/CEMT INQ TIM CEMT data is displayed.
messages
P/2 The second page of message is
This command displays the message identifiers and titles of redisplayed.
logical messages queued for this terminal.
If the new transaction uses BMS in PAGING mode, and
getpageQ
RETAIN or RELEASE is specified in the SEND PAGE
Getpage command in the application program, the output is chained to
The user-defined identification code for the retrieval existing output, and a new level of chaining is created.
transaction, and is 1–7 characters long. The PGRET
system initialization parameter defines this code. If RELEASE is specified, this chaining process can be
repeated indefinitely. However, chaining requests must
Q (Query). The identifiers of all logical messages destined always be made while viewing pages at the highest level of
for this terminal are displayed. If the message is security chaining. Otherwise, messages at levels higher than the
protected (that is, if it has been routed to a specific current level is automatically purged (if OPERPURGE has
operator ID or operator class), its identifier is displayed not been specified in the application program SEND PAGE
only if the operator ID or class for the operator signed on command), or you are asked to purge them. If RETAIN is
matches that in the message. The identifier consists of a specified, no further chaining (in either TERMINAL or
6-digit hexadecimal number, a 2-character PAGING mode) can be performed until the second logical
temporary-storage prefix, and optionally, a title. The message has been terminated. Further chaining requests are
6-digit hexadecimal number can be used as the hhhhhh rejected.
option in the page retrieval command (see “Retrieve a
page” on page 253) to retrieve pages for this display. If neither RETAIN nor RELEASE is specified, the output from
the second transaction is queued as a new message for the
terminal, and is not received until all earlier messages have
Message chaining been terminated. It is thus not chained to the current
message.
Usually, when you have viewed the output pages from a
transaction, there is no need to retain the pages. However, If you enter data that is not a paging command during a
you might want to initiate a new transaction and still retain message chaining session, all pages on levels higher than
the old pages, so that you can view them again after you the current level are deleted, if no message in the chain has
have displayed output from the new transaction. This is been built using OPERPURGE=YES in the SEND PAGE
called message chaining and can be done using the command.
following command:
An example of the use of message chaining under BMS in
PAGING mode is a search of a personnel file for people who
speak French. Your initial inquiry might turn up three names.
55──CSPG──Messchnyyyy──┬────────────┬──5% Without terminating the page containing the names, you can
└─Parameters─┘ examine the records of each of the three people named. The
chaining transaction could be used to read a record, without
erasing the three names.
Messchn
The installation-defined message-chaining transaction This would create output at the second level of chaining (the
identification code (for example, C/), as defined in the output from the original transaction being first-level output).
PGCHAIN system initialization parameter. When you finish viewing a person’s record, you enter a
paging command to terminate the current level, see
Yyyy “Message termination” on page 256. The message
The identifier of a transaction that produces data to be displaying the person’s record would be purged, and the
added to the message chain. original page, containing the three names, redisplayed.
Parameters Assuming that the message chaining transaction identifier is
The parameters, if any, required by transaction yyyy. C/, enter:
LANG DEPT=J34,FRENCH
If the new transaction uses terminal control, or BMS in
TERMINAL mode, its output is displayed immediately. When Receive:
the new transaction terminates, anything else you enter is BERESFORD, J.A. 1ð43
interpreted as a paging command for the first message. For LEVY, A.R. 7121
example: WALTON, J. 8143
TRAN The transaction invokes an application
To find out more about Beresford, enter:
program that produces multiple pages of
output. The first page is displayed.
Chapter 22. Page retrieval CSPG 255

C/PREC 1ð43 example), view the summary page (level one) and then enter
C/PREC 3642; the new transaction becomes level two and
This finds the personnel record for employee number 1043. all other chained messages below that are erased (assuming
PREC is the identifier of a user-written transaction for that they have been built using a SEND PAGE command
examining personnel records. Receive: with the OPERPURGE option omitted).
NAME - BERESFORD, JERRY A.
EMPLOYEE NO - 1ð43 Messages involving different partition layouts (different
(and so on) partition sets, including unpartitioned) may be chained. The
current page in each partition is redisplayed on a change of
To go back to the list of names, enter:
message level.
T/C
T/ is the user-defined transaction identifier that terminates the
message at the current level of chaining (see Message Message termination
termination).
You can erase a logical message using the message
Receive: terminate command. If the logical message is security
BERESFORD, J.A. 1ð43 protected, it is terminated only if your identification or class
LEVY, A.R. 7121 matches that in the message. After an erase, the last
WALTON, J. 8143 message still in the chain is displayed. The format of the
message terminate command is as follows:
You can now examine Levy’s record.
You can also chain a series of messages together and use

55──CSPG──Msgterm──┬─A─┬──┬─────────┬──5%
paging commands to view the series simultaneously. Using ├─B─┤ └─,hhhhhh─┘
the previous example, you can have the summary page as ├─C─┤
your base message (first level) and each of the personnel ├─H─┤
records as subsequent chain levels. Assume you are └─R─┘
currently displaying the summary:
Enter: Msgterm
A user-defined transaction identifier (1–7 characters) for
C/PREC 1ð43
the message termination transaction (for example T/) as
Receive: defined in the PGPURGE system initialization parameter.
NAME - BERESFORD... A Terminates all logical messages destined for and being
Enter: displayed on that terminal (including routed messages
not yet displayed). The following message is received
C/PREC 7121
when termination has been completed:
Receive:
DFHTP4122 Requested purge completed successfully
NAME - LEVY...
B Terminates the logical message being displayed on that
Enter:
terminal and all logical messages chained to it. This
C/PREC 8143 does not include routed messages. Whenever you have
Receive: finished with all the output from a transaction, you
should terminate the base message by entering a
NAME - WALTON... command of the form msgtermB. If the message has
been built using a SEND PAGE command with the
There are now four levels of logical messages at the
OPERPURGE option omitted, you can terminate the
terminal. You can now page back and forth between the
paging session by entering data other than a paging
personnel records. Enter:
command.
P/(2)1
C Terminates the current (level) logical message and any
Receive:
messages chained below it.
NAME - BERESFORD...
H Terminates all logical messages chained to the base
Enter: logical message being displayed on that terminal. The
P/(L)1 page of the base message that was most recently
Receive: displayed is redisplayed at the terminal.
NAME - WALTON... R Terminates all logical messages queued for immediate

delivery (routed) to the terminal. The page that was
You can chain a new transaction only while you are viewing being displayed at the terminal is redisplayed.
the last logical level. If you have four levels (as in the above

Hhhhhh This condition exists until either of the following occurs:

The 6-digit hexadecimal identifier of a specific,
1. You enter P/A (reset terminal to autopaging status),
undelivered logical message to be erased. (This
indicating that all subsequent pages are to be displayed
identifier would have been determined using a page
without further intervention.
query command.) If the message specified is
security-protected, the operator should have a security 2. You enter T/C (terminate current message). All pages
code that matches the one in the message. from that logical message are purged, and the terminal
is again put into autopaging status.
If a message identifier (hhhhhh) is not specified in the
termination request and there is no message currently P/ is the paging transaction identifier, and T/ is the terminate
displayed, the oldest message is automatically retrieved. transaction identifier.
Copying pages Routed pages displayed at terminal

You can send a copy of the page being displayed, as it You can use the message-switching transaction to direct
appeared when initially transmitted, to another terminal output to a terminal or terminals other than your own. For
(normally hardcopy). more information on message switching, see Chapter 19,
“CMSG—message switching” on page 231. When a terminal
You do this by entering the page-copy transaction identifier to which you have directed a message is in TRANSCEIVE
and the identifier of the terminal that is to receive the copy, status, and is not involved with a transaction, and is not
as follows: displaying pages, CICS displays the first page of that
msgcopytttt message.
Msgcopy However, if the terminal is in TRANSACTION status, you can

The copy transaction identifier (1–7 characters), for display the first page only of a waiting message by entering
example D/, as defined in the PGCOPY system CSPG, CSPG P/1, or just P/1. Here, you are using P/ as a
initialization parameter. paging command. If no page is waiting, you get the following
message:
Tttt
DFHTP41ð4 A paging request has been received but
The identifier of the terminal to which the page is to be
there are no pages for display
copied.
You get the message:

DFHTP4124 Page copied from terminal tttt
(message number msgno)
Field and character attributes in the copied page that are not
supported by the target terminal are ignored. The copied
page is reformatted if it does not fit on the target terminal.
Field and character attributes are discarded in the
reformatting. If partitions are in use, the page copy command
copies the displayed page for the partition in which the copy
command is entered.
Status of hardcopy terminal

A hardcopy terminal that is not defined as a paging terminal
(one that displays pages when you request them) is an
autopaging terminal (one that displays all pages without your
intervention). An autopaging terminal may be temporarily
designated as a paging terminal by the user’s application
program using the NOAUTOPAGE option of the SEND
PAGE command. If this is done at the time the first page is
to be displayed on the terminal, the terminal is temporarily
treated as a paging terminal for the duration of the message.
Chapter 22. Page retrieval CSPG 257


CWTO—write to console operator
Chapter 23. CWTO—write to console operator

Use CWTO to send messages to the console operator.
Start the transaction by entering CWTO, optionally followed

by the text of your message, on the command line of the
screen, as follows:
55──CWTO──Message──5%
Press the ENTER key. If the transaction runs successfully,

your message is sent to the console, and you get the normal
completion response:
MESSAGE HAS BEEN SENT
If you enter CWTO with no message text, you are prompted for
your message as follows:
ENTER MESSAGE
You can cancel the CWTO transaction by entering CANCEL

as the last 6 characters of your message. The transaction is
terminated and you get the following response:
The following are some general points about the format of
your messages:
If your message exceeds the line length of the console,
it is divided between words into more than one line.
Each part of a divided message is prefixed by your
identifier and by that of the originating terminal.
New-line (NL) characters within your message are kept,
although any leading NL character is deleted.
You can include blank lines at the top of your
transmitted message by pressing ENTER (or using
carriage returns) the required number of times.
You can enter any number of backspace characters for
deletion. If you enter only blank characters, or if you
delete all of the data by entering too many deletion
characters, you get the following message:
NO INPUT - REENTER

CWTO—write to console operator

DSNC—write to console operator
Chapter 24. DSNC—CICS DB2 transaction DSNC

The DSNC transaction can be used to perform the following:
Enter DB2 commands from a CICS terminal.
Cause threads to be terminated when they are released
(DSNC DISCONNECT).
Display information about transactions using the CICS
DB2 interface, and display statistics (DSNC DISPLAY).
Modify the unsolicited message destinations, and modify
the number of active threads used by a DB2ENTRY, the
pool, or for commands (DSNC MODIFY).
Shut down the CICS DB2 interface (DSNC STOP).
Start the CICS DB2 interface (DSNC STRT).
For more information about the CICS DB2 transaction,

DSNC, see the CICS DB2 Guide.

DSNC—write to console operator

Appendix
Appendix. List of CICS transactions

The following table lists all the transactions that are supplied Tranid Program Group Description
with CICS, except for those that are part of CICS sample CEOT* DFHEOTP DFHOPER Terminal status
programs. CESC* DFHCESC DFHSIGN Terminal timeout
CESD DFHCESD DFHSDAP Shutdown assist
The transactions that have operator interfaces, and which are CESF* DFHSFP DFHSIGN Sign off
therefore described in this manual, are marked by an asterisk CESN* DFHSNP DFHSIGN Sign on
(*). The remainder therefore have no operator interface. CEST* DFHESTP DFHOPER Supervisory terminal
CETR* DFHCETRA DFHOPER Trace
Tranid is the transaction identifier. Program indicates the CEX2 DFHDB2EX2 DFHDB2 CICS DB2 attachment
program (if there is one) that is specified in the supplied facility service transaction
| CFCL DFHFCDL - CFDT Load
transaction definition, and Group indicates the supplied
| CFOR DFHFCQT - RLS Quiesce
resource-definition group that contains the transaction | CFQS DFHFCQT - RLS Quiesce
definition. For general information on resource definition and | CFSL DFHDTLX - Shared DT load
the CICS groups, see the CICS Resource Definition Guide. CFTS DFHZATS DFHSPI Remote mass flag
CGRP - - Persistent sessions (See
Tranid Program Group Description note)
CAFB CAFB1 DFHAUGRP Transaction Affinities Utility CHLP DFHCMAC DFHCMAC Alias for CMAC
data saver CIND* DFHINDT DFHINDT CICS in-doubt testing tool
CAFF CAUCAFF1 DFHAUGRP Transaction Affinities Utility | CIOD DFHIIOPA DFHIIOP Default CICS IIOP interface
controller | started by CIOR
CATA DFHZATA DFHSPI Autoinstall terminal | CIOF DFHIIOPA DFHIIOP CICS Generic factory
CATD DFHZATD DFHSPI Delete autoinstalled terminal | started by CIOR
CATR DFHZATR DFHSPI Restart autoinstalled | CIOR DFHIIOP DFHIIOP CICS IIOP interface started
terminal | by SO_Domain
| CBAM* DFHECBAM DFHOPER BTS browser CITS DFHZATS DFHSPI Remote install
CBRC* DFHBRCP DFHCOMP5 IMS DBRC interface | CLQ2 DFHLUP DFHISC OUTBOUND RESYNC FOR
| CCIN DFHZCN1 DFHCLNT CICS Client | APPC AND MRO
CDBC* DFHDBME DFHDBCTL DBCTL connect/disconnect | CLR1 DFHZLS1 DFHISCT Inbound CNOS for APPC
CDBD DFHDBDI DFHDBCTL DBCTL disable | parallel sessions
CDBF DFHD2CM3 DFHDB2 CICS DB2 attachment | connections
facility shutdown force | CLR2 DFHLUP DFHISC INBOUND RESYNC FOR
transaction | MRO
CDBI* DFHDBIQ DFHDBCTL DBCTL inquiry CLS1 DFHZLS1 DFHISC LU services model
CDBM* DFHDBMP DFHDBCTL DBCTL issue commands CLS2 DFHLUP DFHISC LU services model
CDBN DFHDBCON DFHDBCTL DBCTL issue commands CLS3 DFHCLS3 DFHISC LU services model
CDBO DFHDBCT DFHDBCTL DBCTL control CLS4 DFHCLS4 DFHISC LU services model
CDBQ DFHD2CM2 DFHDB2 CICS DB2 attachment CMPX DFHMXP DFHISC Local queuing shipper
facility shutdown quiesce CMSG* DFHMSP DFHMSWIT Message switching
transaction CMTS DFHZATS DFHSPI Remote mass delete
CDBT DFHDBDSC DFHDBCTL DBCTL disconnection COVR DFHZCOVR - CICS open VTAM retry
| CDFS DFHDFST DFHISC Dynamic routing of a CPLT - - PLT programs
| delayed CPMI DFHMIRS DFHISC Synchronization level 1
| non-terminal-related START mirror
| request | CQPI DFHCLS5 DFHISC Connection Queisce
CDTS DFHZATS DFHSPI | Architected transaction
CEBR* DFHEDFBR DFHEDF Temporary-storage browse | (inbound)
CEBT* — — Master terminal, alternate | CQPO DFHCLS5 DFHISC Connection Queisce
CICS | Architected transaction
CECI* DFHECIP DFHINTER Command level interpreter | (outbound)
CECS* DFHECSP DFHINTER Command level interpreter CQRY DFHQRY DFHSTAND ATI query support
CEDA* DFHEDAP DFHSPI Resource definition online CRMD DFHZATMD DFHSPI Remote terminal delete
(RDO) CRMF DFHZATMF DFHSPI Remote terminal flag for
CEDB* DFHEDAP DFHSPI Resource definition online delete
(RDO) | CRPA DFHRPAS DFHRPC ONC RPC-supplied
CEDC* DFHEDAP DFHSPI Resource definition online | transaction
(RDO) | CRPC DFHRPC00 DFHRPC ONC RPC-supplied
CEDF* DFHEDFP DFHEDF Execution diagnostic facility | transaction
| CEDX* DFHEDFP DFHEDF Execution diagnostic facility | CRPM DFHRPHS DFHRPC ONC RPC-supplied
CEGN DFHCEGN DFHSIGN Good night transaction stub | transaction
CEHP DFHCHS DFHISC CICS/VM request handler ONC
CEHS DFHCHS DFHISC CICS/VM request handler RPC-supplied
CEMT* DFHEMTP DFHOPER Master terminal transaction

Appendix
Tranid Program Group Description Tranid Program Group Description

CRSQ DFHCRQ DFHISC ATI purge | CWXN DFHWBXN DFHWEB CICS Web Attach
CRSR DFHCRS DFHISC Remote scheduler | Transaction
CRSY DFHRMSY DFHRMI Resource manager CXCU DFHCXCU DFHSTAND XRF catchup transaction
resynchronization CXRE DFHZXRE DFHSTAND Autoconnect processing
CRTE* DFHRTE DFHISC Transaction routing CXRT DFHCRT DFHISC Transaction routing relay
CRTX - DFHISC Dynamic transaction routing DSNC* DFHD2CM1 DFHDB2 CICS DB2 attachment
transaction definition facility transaction
CSAC DFHACP DFHSTAND Abnormal condition
CSCY DFHCPY DFHVTAMP 3270 print support Note: Transactions CGRP, CSSY, CSTP, and CSXM are
CSFE* DFHFEP DFHFE Terminal test, trace, storage transaction names that are used by some CICS
| CSFR DFHFCRD - RLS cleanup tasks.
CSFU DFHFCU DFHOPCLS File open utility
CSGM DFHGMM DFHVTAM “Good-morning” signon
CSGX DFHDLG DFHCOMP5 Global command processor
| CSHA - - Scheduler services
| CSHQ - - Scheduler services
| CSHR DFHMIRS DFHISC SCHEDULER SERVICES
| REMOTE ROUTING
| CSJC DFHJCBSP DFHCOMP3 Journal control bootstrap
CSKP DFHAKP DFHCOMP5 Activity keypoint
CSLG DFHZRLG DFHCOMP5 Log committed output
messages
CSMI DFHMIRS DFHISC Mirror transaction
CSM1 DFHMIRS DFHISC SYSMSG model
CSM2 DFHMIRS DFHISC Scheduler model
CSM3 DFHMIRS DFHISC Queue model
CSM5 DFHMIRS DFHISC DL/I model
CSNC DFHCRNP DFHISC IRC connection manager
CSNE DFHZNAC DFHVTAM VTAM node abnormal
| CSOL DFHSOL - TCPIP listener
CSPG* DFHTPR DFHBMS Terminal paging
CSPK DFHPRK DFHVTAMP 3270 print support
CSPP DFHP3270 DFHHARDC 3270 print support
CSPQ DFHTPQ DFHBMS Terminal page cleanup
CSPS DFHTPS DFHBMS Terminal page scheduling
CSQC DFHLGQC DFHLGQC CICS quiesce after system
log failure
CSRK DFHRKB DFHVTAMP 3270 print support
CSRS DFHZRSP DFHRSEND 3614 message
resynchronization
| CSSC DFHCSSC DFHCOMPx Sign off inactive terminal
CSSF DFHRTC DFHISC CRTE cancel remote
transaction
CSSX DFHDLS DFHCOMP5 Status exit procedure
CSSY — — (See note)
CSTE DFHTACP DFHSTAND Terminal abnormal
CSTP — — (See note)
CSXM — — (See note)
CSZI DFHSZRMP DFHFEPI Front end programming
interface (FEPI), only active
if FEPI installed.
| CTIN DFHZCT1 DFHCLNT CICS Client
| CTSD DFHTSDQ - Temporary storage delete
CVMI DFHMIRS DFHISC Synchronization level 1
mirror
| CWBA DFHWBA DFHWEB CICS Web Interface Alias
| Transaction
| CWBC DFHWBC00 DFHWEB CICS Web Interface
| Connection Manager
| Transaction
| CWBG DFHWBGB DFHWEB CICS Web Interface
| Garbage Collection
| Transaction
| CWBM DFHWBM DFHWEB CICS Web Interface Server
| Controller Transaction
CWTO* DFHCWTO DFHCONS Write to console operator

Index
ACQUIRED (continued)
Special Characters CEMT INQUIRE TERMINAL 132
? and CEMT 45 CEMT SET CONNECTION 163
(VALUE) CEMT SET MODENAME 187
CEMT INQUIRE JMODEL 92 CEMT SET NETNAME 190
CEMT INQUIRE JOURNALNAME 93 CEMT SET TERMINAL 204
CEMT SET PROCESSTYPE 192 acquiring VTAM terminals 190, 204
* and CEMT 47 ACTION
*ALL CEMT INQUIRE DSNAME 75
CSPG 254 CEMT INQUIRE SYDUMPCODE 115
*LDC CEMT INQUIRE TRDUMPCODE 136
CMSG 239 CEMT SET TSQUEUE 208
−TERMID*LDC/OPID ACTIVE
CMSG 239 CEMT INQUIRE ENQ 81
+ in CEMT syntax 47 CEMT INQUIRE MODENAME 96
+ in scrolling under CEMT 48 CEMT INQUIRE SYSTEM 118, 119
+HHMM CEMT INQUIRE TCLASS 123
CMSG 244 CEMT INQUIRE UOW 144
+M CEMT INQUIRE UOWENQ 150
CMSG 244 ACTIVITY
+MM CEMT INQUIRE TASK 120
CMSG 244 CEMT SET PROCESSTYPE 191
+TERMID*LDC/OPID ACTIVITYID
CMSG 239 CEMT INQUIRE TASK 120
ACTOPENTCBS
CEMT INQUIRE SYSTEM 116
A ADD
abbreviation of keywords
CEMT INQUIRE SYDUMPCODE 115
CEMT transaction 46
CEMT INQUIRE TRDUMPCODE 136
abbreviations for keywords 2
CEMT SET SYDUMPCODE 196
ABEND
CEMT SET TRDUMPCODE 207
CEMT INQUIRE DB2CONN 64, 66
ADDABLE
CEMT INQUIRE DB2ENTRY 68
CEMT INQUIRE FILE 86
CEMT SET DB2CONN 169
CEMT SET FILE 181
CEMT SET DB2ENTRY 173
ADDREXECENQ
access method control block (ACB) 153, 210
CEMT INQUIRE ENQ 81
ACCESSMETHOD
CEMT INQUIRE UOWENQ 150
CEMT INQUIRE CONNECTION 59
ADDSTATUS
CEMT INQUIRE DSNAME 75
AFFINITY
ACCOUNTREC
CEMT INQUIRE DB2CONN 63
AFTER
CEMT INQUIRE DB2ENTRY 67
CEDA 36
AGE
CEMT INQUIRE UOW 143
ACQ
AGING
CEOT 213
ACQSTATUS
CEMT SET SYSTEM 198
CEMT INQUIRE MODENAME 96
AKP
ACQUIRED
CEMT SET SYSTEM 198
CEMT INQUIRE NETNAME 101

ALL ALL ROUTE ENTRIES DELETED
CEBT INQUIRE AUXTRACE 21 CMSG 241
CEBT SET AUXTRACE 27 ALL*LDC
CEDA 36 CMSG 239
CEMT INQUIRE AUTINSTMODEL 53 ANY
CEMT INQUIRE AUXTRACE 56 CEMT INQUIRE PROGRAM 107
CEMT INQUIRE CONNECTION 58 CEMT INQUIRE TRANSACTION 135
CEMT INQUIRE DB2CONN 63 APPC
CEMT INQUIRE DB2ENTRY 67 CEMT INQUIRE CONNECTION 60
CEMT INQUIRE DB2TRAN 70 CEMT INQUIRE UOWLINK 152
CEMT INQUIRE DSNAME 74 APPENDCRLF
CEMT INQUIRE FILE 85 CEMT INQUIRE DOCTEMPLATE 71
CEMT INQUIRE JMODEL 92 AS
CEMT INQUIRE JOURNALNAME 93 CEDA 36
CEMT INQUIRE MODENAME 95 ASSEMBLER
CEMT INQUIRE NETNAME 99 CEMT INQUIRE PROGRAM 108
CEMT INQUIRE PARTNER 102 ATI
CEMT INQUIRE PROCESSTYPE 103 CEMT INQUIRE NETNAME 99
CEMT INQUIRE PROFILE 105 CEMT INQUIRE TERMINAL 130
CEMT INQUIRE PROGRAM 106 CEMT SET NETNAME 190
CEMT INQUIRE STREAMNAME 113 CEMT SET TERMINAL 204
CEMT INQUIRE SYDUMPCODE 114 CEOT 213
CEMT INQUIRE TASK 120 ATI (automatic transaction initiation) 128, 203
CEMT INQUIRE TCLASS 123 ATISTATUS
CEMT INQUIRE TDQUEUE 126 CEMT INQUIRE NETNAME 99
CEMT INQUIRE TERMINAL 129 CEMT INQUIRE TERMINAL 130
CEMT INQUIRE TRANSACTION 133 AUDITLEVEL
CEMT INQUIRE TRDUMPCODE 136 CEMT INQUIRE PROCESSTYPE 104
CEMT INQUIRE TSMODEL 138 AUDITLOG
CEMT INQUIRE TSPOOL 139 CEMT INQUIRE PROCESSTYPE 104
CEMT INQUIRE TSQUEUE 141 AUT
CEMT INQUIRE UOW 143 CEOT 213
CEMT INQUIRE UOWLINK 151 AUTHID
CEMT PERFORM STATISTICS 159 CEMT INQUIRE DB2CONN 63
CEMT SET AUXTRACE 162 CEMT INQUIRE DB2ENTRY 68
CEMT SET CONNECTION 163 CEMT SET DB2CONN 168
CEMT SET DSNAME 177 CEMT SET DB2ENTRY 172
CEMT SET FILE 181 AUTHTYPE
CEMT SET JOURNALNAME 186 CEMT INQUIRE DB2CONN 63
CEMT SET MODENAME 187 CEMT INQUIRE DB2ENTRY 68
CEMT SET NETNAME 190 CEMT SET DB2CONN 168
CEMT SET PROCESSTYPE 192 CEMT SET DB2ENTRY 172
CEMT SET PROGRAM 192 AUTINSTMODEL
CEMT SET SYDUMPCODE 196 CEMT DISCARD 51
CEMT SET TASK 200 CEMT transaction 53
CEMT SET TCLASS 201 AUTOACTIVE
CEMT SET TDQUEUE 203 CEMT INQUIRE SYSTEM 118
CEMT SET TERMINAL 204 CEMT SET SYSTEM 198
CEMT SET TRANSACTION 206 AUTOINACTIVE
CEMT SET TRDUMPCODE 207 CEMT INQUIRE SYSTEM 118
CEMT SET TSQUEUE 208 CEMT SET SYSTEM 198
CEMT SET UOW 209 AUTOINSTALL
CEMT SET UOWLINK 209 CEMT INQUIRE AUTOINSTALL 54
CMSG 237 CEMT PERFORM STATISTICS 159
general statement 46 CEMT SET transaction 161
CEMT transaction 54

AUTOINSTALL (continued) BACKUPTYPE
CSFE ZCQTRACE 249 CEMT INQUIRE DSNAME 76
AUTOMATIC BASE
CEBT SET TAKEOVER 30 CEMT INQUIRE DSNAME 76
automatic transaction initiation (ATI) 128, 203 BASEDSNAME
AUTOPAGEABLE CEMT INQUIRE DSNAME 78
CEMT INQUIRE NETNAME 100 basic mapping support (BMS)
CEMT INQUIRE TERMINAL 131 logical message 255
CEMT SET NETNAME 190 page retrieval 253
CEMT SET TERMINAL 204 paging commands 253
CEOT 213 BDAM
autopaging terminal 257 CEMT INQUIRE DSNAME 75
AUTOSWITCH CEMT INQUIRE FILE 86
CEBT INQUIRE DUMP 22 BEFORE
CEBT SET DUMP 28 CEDA 36
CEMT INQUIRE DUMPDS 79 BELOW
CEMT SET DUMPDS 179 CEMT INQUIRE PROGRAM 107
AUXILIARY CEMT INQUIRE TRANSACTION 135
CEBT INQUIRE AUXTRACE 21 blank fields in a display 48
CEMT INQUIRE AUXTRACE 56 BMS (basic mapping support) 253
CEMT INQUIRE TSMODEL 138 BMS paging
CEMT INQUIRE TSQUEUE 141 copy command 257
auxiliary trace 221 display routed pages 257
CEBT 21 logical message 256
CEBT SET 27 status of hardcopy terminal 257
CEMT 55 BREXIT
CEMT SET 162 CEMT INQUIRE TRANSACTION 133
AUXTRACE BRIDGE
CEBT 21 CEMT INQUIRE TASK 120
CEBT SET transaction 27 BROWSE
CEMT SET transaction 162 CEMT INQUIRE FILE 86
CEMT transaction 55 CEMT SET FILE 181
AVAILABILITY BROWSESTATUS
CEMT INQUIRE DSNAME 77 CEMT INQUIRE FILE 86
AVAILABLE BSAM terminals 233
CEMT INQUIRE CONNECTION 60 BTS browser transaction 9
CEMT SET DSNAME 177 C
CEMT SET MODENAME 188 C
CEMT INQUIRE PROGRAM 108
CACHE
B CEMT INQUIRE UOWDSNFAIL 146
BACKLOG CAFB transaction 263
CEMT SET TCPIPSERVICE 202 CAFF transaction 263
BACKOUT CANCEL
CEMT INQUIRE CONNECTION 62 CEMT INQUIRE CONNECTION 61
CEMT INQUIRE DSNAME 78 CEMT SET CONNECTION 163
CEMT INQUIRE TASK 121 CEMT SET TERMINAL 204
CEMT INQUIRE TRANSACTION 134 CMSG 234
CEMT INQUIRE UOW 144 CANCELED - TEMP STRG ERR N
CEMT SET CONNECTION 163 CMSG 241
CEMT SET DSNAME 177 canceling a message 232
CEMT SET UOW 209 canceling a transaction 1, 232, 233, 236, 259
BACKUPNONBWO CATA transaction 263
CEMT INQUIRE UOWDSNFAIL 146
Index 267
CATD transaction 263 CEMT INQUIRE DOCTEMPLATE (continued)
CATR transaction 263 DOCTEMPLATE 72
CAUSE NAME 72
CEMT INQUIRE UOWDSNFAIL 146 TEMPLATENAME 72
CAVM (CICS availability manager) 25 TEMPLATETYPE 72
CBAM transaction 9, 263 TYPE 72
CBRC transaction 263 CEMT INQUIRE DOCTEMPLATE definition
CCIN transaction 263 DDNAME 72
CDATAKEY CEMT transaction 263
CEMT INQUIRE TRANSACTION 135 ? character 45
CDBC transaction 11, 263 * symbol 47
CDBD transaction 263 + in CEMT syntax 47
CDBF transaction 263 + in scrolling 48
CDBI transaction 13, 263 abbreviation of keywords 46
CDBM transaction 15, 263 AUTINSTMODEL 53
CDBN transaction 263 AUTOINSTALL 54, 161
CDBO transaction 263 AUXTRACE 55, 162
CDBQ transaction 263 blank fields in a display 48
CDBT transaction 263 CEMT as a prompter 45
CDFS transaction 263 CEMT on the command line 45
CDSASIZE CFDTPOOL 57
CEMT INQUIRE DSAS 73 CONNECTION 58, 163
CDTS transaction 263 DB2CONN 63, 167
CEBR transaction 19, 263 DB2ENTRY 171
CEBT transaction 263 DB2TRAN 70, 174
AUXTRACE 21, 27 DBENTRY 67
CICS availability manager (CAVM) 25 DELETSHIPPED 70, 175
DUMP 22, 28 DISCARD 49, 50
GTFTRACE 23, 28 DOCTEMPLATE 71
INQ|SET 21 DSAS 72, 176
INTTRACE 23, 29 DSNAME 74, 176
PERFORM 25 DUMP 156
request formats 21 DUMPDS 79, 179
SHUTDOWN 25 ENDAFFINITY 156
SNAP 26 ENQ 80
SURVEILLANCE 24, 29 ENQMODEL 82
TAKEOVER 24, 26, 30 ENQQUEUE 179
XRF complex 21 EXCI 83
CECI transaction 31, 263 Family of resources 47
CECS transaction 32, 263 FILE 85, 180
CEDA transaction 33, 263 generic names 47
security checking 38 generic resource identifiers 47
CEDB transaction 33, 263 GTFTRACE 89, 184
CEDC transaction 33, 263 INQUIRE 45
CEDF INTTRACE 90, 184
CEMT INQUIRE PROGRAM 107 invoking from an application program 49
CEMT SET PROGRAM 193 IRBATCH 90
CEDF transaction 41, 263 IRC 91, 185
CEDFSTATUS JMODEL 92
CEMT INQUIRE PROGRAM 107 JOURNALNAME 93, 186
CEDX transaction 263 LINE 94, 186
CEGN transaction 263 MODENAME 95, 187
CEHP transaction 263 MONITOR 97, 188
CEHS transaction 263 NETNAME 99, 190
CEMT INQUIRE DOCTEMPLATE overtyping a display 47
APPENDCRLF 71 PARTNER 102

CEMT transaction (continued) CFDTPOOL (continued)
PERFORM 155 CEMT transaction 57
PROCESSTYPE 103, 191 CFOR transaction 263
PROFILE 105 CFQS transaction 263
PROGRAM 105, 192 CFSL transaction 263
program function (PF) keys 46 CFTABLE
question mark preceding CEMT 45 CEMT INQUIRE FILE 88
QUEUE 194 CEMT INQUIRE UOWLINK 152
request formats 45 CEMT SET FILE 181
REQUESTMODEL 110 CFTS transaction 263
RESET 157 CGROUP
RRMS 110 CEMT INQUIRE DB2CONN 64
scrolling a display 48 CEMT SET DB2CONN 168
SECURITY 157 CGRP transaction 263
security checking 49 chaining a message
SET 45 CSPG transaction 255
SHUTDOWN 158 partitions 5
SNAP 156 checking user storage 250
STATISTICS 111, 159, 194 CHKSTRM
STREAMNAME 113 CSFE DEBUG 250
SYDUMPCODE 114, 196 CHLP transaction 263
SYSTEM 116, 198 CICS availability manager (CAVM) 25
tab key 48 CICS DB2 transaction (DSNC) 261
TASK 119, 200 CICS releases, CSD compatibility across 37
TCLASS 123, 201 CICSTABLE
TCPIP 124, 201 CEMT INQUIRE FILE 88
TCPIPSERVICE 124, 202 CEMT SET FILE 181
TDQUEUE 126, 203 CICSTELEVEL
TERMINAL 129, 204 CEMT INQUIRE SYSTEM 116
TRANSACTION 133, 206 CID
TRDUMPCODE 136, 207 CEMT INQUIRE NETNAME 100
TSMODEL 138 CEMT INQUIRE TERMINAL 130
TSPOOL 139 CIND transaction 227, 263
TSQNAME 140 CIOD transaction 263
TSQUEUE 140, 208 CIOF transaction 263
UOW 142, 209 CIOR transaction 263
UOWDSNFAIL 145 CITS transaction 263
UOWENQ 148 CKOPEN
UOWLINK 151, 209 CEMT INQUIRE TASK 122
VTAM 153, 210 CLASS
WEB 154, 211 CEMT INQUIRE PROGRAM 106
without keywords 46 CEMT INQUIRE TERMINAL 129
CEOT transaction 213, 263 CEMT INQUIRE TRANSACTION 133
CESC transaction 263 CEMT SET PROGRAM 193
CESD transaction 263 CEMT SET TERMINAL 205
CESF transaction 215, 263 CEMT SET TRANSACTION 206
CESN transaction 217, 263 general statement 47
CEST transaction 219, 263 class tasks, CEMT requests 123, 201
CETR transaction 221, 263 CLEAR key
CEX2 transaction 263 when invoking transaction 1
CEXECKEY when used with partitions 4
CEMT INQUIRE PROGRAM 108 CLEAR PARTITION key 4
CFCL transaction 263 CLEAR/CANCL or CONT INPUT/ROUTE/MSG
CFDTPOOL CMSG 242
CEMT INQUIRE CFDTPOOL 57 CLOSED
CEMT SET FILE 181 CEBT INQUIRE DUMP 22
Index 269
CLOSED (continued) COMAUTHID
CEBT SET DUMP 28 CEMT INQUIRE DB2CONN 64
CEMT INQUIRE DUMPDS 79 CEMT SET DB2CONN 168
CEMT INQUIRE FILE 88 COMAUTHTYPE
CEMT INQUIRE IRC 91 CEMT INQUIRE DB2CONN 64
CEMT INQUIRE MODENAME 96 COMMAND
CEMT INQUIRE RRMS 110 CEBT SET TAKEOVER 30
CEMT INQUIRE TDQUEUE 127 command interpreter transaction (CECI) 31
CEMT INQUIRE VTAM 153 command syntax checker (CECS) 32
CEMT SET DUMPDS 179 commands
CEMT SET FILE 181 CEBT INQ|SET 21
CEMT SET IRC 185 CEBT PERFORM 25
CEMT SET MODENAME 188 CEMT DISCARD 50
CEMT SET TDQUEUE 203 CEMT INQUIRE 53
CEMT SET VTAM 210 CEMT PERFORM 155
CLQ2 transaction 263 CEMT SET 160
CLR1 transaction 263 paging 253
CLR2 transaction 263 COMMIT
CLS1 transaction 263 CEMT INQUIRE CONNECTION 62
CLS2 transaction 263 CEMT INQUIRE DSNAME 78
CLS3 transaction 263 CEMT INQUIRE TASK 121
CLS4 transaction 263 CEMT INQUIRE TRANSACTION 134
CMAC transaction 229 CEMT INQUIRE UOW 144
CMDPROT CEMT SET CONNECTION 164
CEMT INQUIRE SYSTEM 116 CEMT SET DSNAME 177
CMDPROTECT CEMT SET UOW 209
CEMT INQUIRE SYSTEM 116 COMMITFAIL
CMPX transaction 263 CEMT INQUIRE UOWDSNFAIL 146
CMSG transaction 231, 263 communicating with CICS 1
CANCEL 234 compatibility, CSD, across CICS releases 37
DATE 234 COMPLETE
ERRTERM 235 CEMT INQUIRE CONNECTION 60
FULLDATE 235 component trace options 221
HEADING 236 COMTHREADLIM
ID 236 CEMT INQUIRE DB2CONN 64
logical unit destination 239 CEMT SET DB2CONN 169
MSG 236 COMTHREADS
OPCLASS 236 CEMT INQUIRE DB2CONN 64
options 234 CONCURRENCY
program (DFHMSP) 241 CEMT INQUIRE PROGRAM 107
PROTECT 236 CONNECING
ROUTE 237 CEMT INQUIRE DB2CONN 65
SEND 238 CONNECT
syntax 234 CEMT INQUIRE DB2CONN 66
TIME 238 CEMT SET DB2CONN 170
CMTS transaction 263 CONNECTED
COBOL CEMT INQUIRE DB2CONN 65
CEMT INQUIRE PROGRAM 108 CEMT INQUIRE TSPOOL 140
codes, display 229 CEMT SET DB2CONN 169
COLD CONNECTERROR
CEMT INQUIRE UOWLINK 152 CEMT INQUIRE DB2CONN 64
COLDACQ CEMT SET DB2CONN 169
CEMT INQUIRE NETNAME 101 CONNECTION
CEMT INQUIRE TERMINAL 132 CEDA 36
CEMT SET NETNAME 190 CEMT DISCARD 51
CEMT SET TERMINAL 205 CEMT INQUIRE CONNECTION 59

CONNECTION (continued) CQPO transaction 263
CEMT INQUIRE MODENAME 96 CQRY transaction 263
CEMT INQUIRE UOW 144 CRE
CEMT INQUIRE UOWDSNFAIL 146 CEOT 213
CEMT INQUIRE UOWLINK 152 CREATE
CEMT PERFORM STATISTICS 159 CEMT INQUIRE NETNAME 100
CEMT SET CONNECTION 163 CEMT INQUIRE TERMINAL 131
CEMT SET MODENAME 188 CEMT SET NETNAME 190
CONNECTST CEMT SET TERMINAL 205
CEMT INQUIRE DB2CONN 65 CREATESESS
CEMT SET DB2CONN 169 CEMT INQUIRE NETNAME 100
CONNSTATUS CEMT INQUIRE TERMINAL 130
CEMT INQUIRE CONNECTION 59 CRMD transaction 263
CEMT INQUIRE TSPOOL 140 CRMF transaction 263
CONSOLE CRPA transaction 263
CEMT INQUIRE TERMINAL 130 CRPC transaction 263
console as a CICS terminal 5 CRPM transaction 263
console operator, write to 259 CRSQ transaction 264
console support, multiple 5 CRSR transaction 264
CONSOLES CRSY transaction 264
CEMT INQUIRE AUTOINSTALL 54 CRTE transaction 247, 264
CEMT SET AUTOINSTALL 161 CRTX transaction 264
CONTENTION CSAC transaction 264
CEMT SET FILE 181 CSCY transaction 264
CONTINUE INPUT CSD compatibility across CICS releases 37
CMSG 242 CSFE transaction 249, 264
CONTINUE INPUT OR MSG CSFR transaction 264
CMSG 242 CSFU transaction 264
CONTINUE MSG CSGM transaction 264
CMSG 242 CSGX transaction 264
CONTINUE ROUTE OPERAND CSHA transaction 264
CMSG 242 CSHQ transaction 264
CONVERSE CSHR transaction 264
CEMT INQUIRE MONITOR 97 CSIGN
CEMT SET MONITOR 189 CEMT INQUIRE DB2CONN 64
CONVERSEST CEMT SET DB2CONN 168
CEMT INQUIRE MONITOR 97 CSJC transaction 264
COORDINATOR CSKP transaction 264
CEMT INQUIRE UOWLINK 152 CSLG transaction 264
COPID CSM1 transaction 264
CEMT INQUIRE DB2CONN 64 CSM2 transaction 264
CEMT SET DB2CONN 169 CSM3 transaction 264
option of DSNCRCT macro 169 CSM5 transaction 264
COPY command 257 CSMI transaction 264
copying pages CSNC transaction 264
CSPG 257 CSNE transaction 264
partitions 5 CSOL transaction 264
COPYSTATUS CSPG transaction 253, 264
CEMT INQUIRE PROGRAM 107 CSPK transaction 264
COVR transaction 263 CSPP transaction 264
CPLT transaction 263 CSPQ transaction 264
CPMI transaction 263 CSPS transaction 264
CQP CSQC transaction 264
CEMT INQUIRE CONNECTION 60 CSRK transaction 264
CQPI transaction 263 CSRS transaction 264
Index 271
CSSC transaction 264
CSSF transaction 264 D
CSSX transaction 264 D
CSSY transaction 264 CEMT INQUIRE TASK 122
CSTE transaction 264 DAE
CSTP transaction 264 CEMT INQUIRE SYDUMPCODE 115
CSXM transaction 264 CEMT SET SYDUMPCODE 196
CSZI transaction 264 DAEOPTION
CTERM CEMT INQUIRE SYDUMPCODE 115
CEMT INQUIRE DB2CONN 64 data sets
CEMT SET DB2CONN 169 CEMT requests 85
CTERM option CEMT SET requests 180
DSNCRCT macro 169 database control (DBCTL)
CTIN transaction 264 connection to 11
CTLGALL disconnection from 11
CEMT INQUIRE SYSTEM 117 database control inquiry transaction (CDBI) 13
CEMT SET SYSTEM 198 database control interface transaction (CDBM) 15
CTLGMODIFY database control menu transaction (CDBC) 11
CEMT INQUIRE SYSTEM 117 DATABUFFERS
CEMT SET SYSTEM 198 CEMT INQUIRE TDQUEUE 128
CTLGNONE DATALOC
CEMT INQUIRE SYSTEM 117 CEMT INQUIRE PROGRAM 107
CEMT SET SYSTEM 198 DATASET
CTSD transaction 264 CEMT INQUIRE ENQ 81
CTX CEMT INQUIRE UOW 144
CEMT INQUIRE DB2CONN 64 CEMT INQUIRE UOWDSNFAIL 146
CEMT SET DB2CONN 169 CEMT INQUIRE UOWENQ 150
CURAUXDS DATASETFULL
CEMT INQUIRE AUXTRACE 56 CEMT INQUIRE UOWDSNFAIL 146
CURRENT DATE
CEMT INQUIRE SYDUMPCODE 115 CMSG 234
CEMT INQUIRE TRDUMPCODE 136 DATE ALREADY PASSED
CSFE 250 CMSG 242
CURRENT(A|B) DATE INVALID AT XXXXXXXX
CEBT INQUIRE AUXTRACE 21 CMSG 242
CURRENTDDS DATE NOT XX/XX AT XXXXX
CEBT INQUIRE DUMP 22 CMSG 242
CEMT INQUIRE DUMPDS 79 date resetting 157
CURREQS DATE TOO FAR IN FUTURE
CEMT INQUIRE AUTOINSTALL 54 CMSG 242
CUSERID DATFORM, system initialization parameter 4
CEMT INQUIRE DB2CONN 64 DB2
CEMT SET DB2CONN 169 CEMT PERFORM STATISTICS 159
CVMI transaction 264 DB2 definitions
CWBA transaction 264 connection
CWBC transaction 264 CEMT INQUIRE DB2CONN command 63
CWBG transaction 264 CEMT SET DB2CONN command 167
CWBM transaction 264 entry
CWTO transaction 259, 264 CEMT INQUIRE DB2ENTRY command 67
CWXN transaction 264 CEMT SET DB2ENTRY command 171
CXCU transaction 264 transaction
CXRE transaction 264 CEMT INQUIRE DB2TRAN command 70
CXRT transaction 264 CEMT SET DB2TRAN command 174
DB2CONN
CEDA 36
CEMT DISCARD 51

DB2CONN (continued) DEST
CEMT INQUIRE DB2CONN 63 CEMT INQUIRE TASK 121
CEMT INQUIRE SYSTEM 116 destinations, multiple 231
CEMT SET transaction 167 DFHCICSP 2
CEMT transaction 63 DFLTUSER
DB2ENTRY CEMT INQUIRE SYSTEM 116
CEDA 36 DISABLED
CEMT DISCARD 51 CEMT INQUIRE DB2ENTRY 68
CEMT INQUIRE DB2ENTRY 67 CEMT INQUIRE ENQMODEL 83
CEMT INQUIRE DB2TRAN 70 CEMT INQUIRE FILE 87
CEMT SET DB2TRAN 174 CEMT INQUIRE JOURNALNAME 93
CEMT SET transaction 171 CEMT INQUIRE PROGRAM 109
CEMT transaction 67 CEMT INQUIRE TDQUEUE 127
DB2ID CEMT INQUIRE TRANSACTION 135
CEMT INQUIRE DB2CONN 65 CEMT SET DB2ENTRY 173
CEMT SET DB2CONN 169 CEMT SET ENQMODEL 179
DB2PLAN CEMT SET FILE 181
CEMT INQUIRE TASK 121 CEMT SET JOURNALNAME 186
DB2RELEASE CEMT SET PROCESSTYPE 192
CEMT INQUIRE DB2CONN 65 CEMT SET PROGRAM 193
DB2TRAN CEMT SET TDQUEUE 203
CEDA 36 CEMT SET TRANSACTION 206
CEMT DISCARD 51 DISABLEDACT
CEMT INQUIRE DB2TRAN 70 CEMT INQUIRE DB2ENTRY 68
CEMT SET transaction 174 CEMT SET DB2ENTRY 173
CEMT transaction 70 DISABLING
DBCTL (database control) 11 CEMT INQUIRE DB2ENTRY 69
DBCTL system identifier (DBCTLID) 12 DISCONNING
DBCTLID 12 CEMT INQUIRE DB2CONN 65
DDNAME DISPATCHABLE
CEMT INQUIRE DOCTEMPLATE 72 CEMT INQUIRE TASK 122
CEMT INQUIRE TDQUEUE 128 DISPATCHER
DEADLOCK CEMT PERFORM STATISTICS 159
CEMT INQUIRE UOWDSNFAIL 147 display logical message (BMS) 255
DEBUG display routed pages 257
CSFE 250 display transaction 229
DEL DISPOSITION
CEMT INQUIRE DELETSHIPPED 70 CEMT INQUIRE FILE 86
DELETE CEMT INQUIRE TDQUEUE 126
CEMT INQUIRE FILE 86 DOCTEMPLATE
CEMT SET FILE 181 CEDA 36
CEMT SET TSQUEUE 208 CEMT DISCARD 51
CEMT SET UOWLINK 209 CEMT INQUIRE DOCTEMPLATE 72
DELETESTATUS CEMT transaction 71
CEMT INQUIRE FILE 86 DPLSUBSET
DELETSHIPPED CEMT INQUIRE PROGRAM 108
CEMT SET transaction 175 CEMT SET PROGRAM 193
CEMT transaction 155 DROLLBACK
DELETSHIPPED command CEMT INQUIRE DB2CONN 65
CEMT transaction 70 CEMT INQUIRE DB2ENTRY 68
DELEXITERROR DS
CEMT INQUIRE UOWDSNFAIL 147 CEMT INQUIRE TASK 122
DEREGISTERED DSALIMIT
CEMT INQUIRE VTAM 153 CEMT INQUIRE DSAS 72
CEMT SET VTAM 210 CEMT INQUIRE SYSTEM 116
CEMT SET DSAS 176
Index 273
DSALIMIT (continued)
CEMT SET SYSTEM 199 E
DSAS ECDSASIZE
CEMT INQUIRE transaction 72 CEMT INQUIRE DSAS 73
CEMT SET transaction 176 EDF (execution diagnostic facility) 41, 247
DSNAME EDSALIMIT
CEMT INQUIRE DSNAME 75 CEMT INQUIRE DSAS 73
CEMT INQUIRE FILE 86 CEMT INQUIRE SYSTEM 117
CEMT INQUIRE TDQUEUE 128 CEMT SET DSAS 176
CEMT INQUIRE UOWDSNFAIL 146 CEMT SET SYSTEM 199
CEMT SET FILE 181 EMPTYREQ
CEMT SET transaction 176 CEMT INQUIRE FILE 86
CEMT transaction 74 CEMT SET FILE 182
DSNC transaction 261, 264 EMPTYSTATUS
DSNC transactions CEMT INQUIRE FILE 86
DISCONNECT 261 ENABLED
DISPLAY 261 CEMT INQUIRE DB2ENTRY 68
MODIFY 261 CEMT INQUIRE ENQMODEL 83
STOP 261 CEMT INQUIRE FILE 87
STRT 261 CEMT INQUIRE JOURNALNAME 93
DSRTPROGRAM CEMT INQUIRE PROGRAM 109
CEMT SET SYSTEM 199 CEMT INQUIRE TDQUEUE 127
DTRPROGRAM CEMT INQUIRE TRANSACTION 135
CEMT INQUIRE SYSTEM 116, 117 CEMT SET DB2ENTRY 173
CEMT SET SYSTEM 199 CEMT SET ENQMODEL 179
DUMMY CEMT SET FILE 182
CEMT INQUIRE JMODEL 92 CEMT SET JOURNALNAME 186
CEMT INQUIRE JOURNALNAME 94 CEMT SET PROCESSTYPE 192
DUMP CEMT SET PROGRAM 193
CEBT 22 CEMT SET TDQUEUE 203
CEBT INQUIRE DUMP 22 CEMT SET TRANSACTION 206
CEBT PERFORM SHUTDOWN 25 ENABLESTATUS
CEBT PERFORM TAKEOVER 26 CEMT INQUIRE AUTOINSTALL 54
CEBT SET transaction 28 CEMT INQUIRE DB2ENTRY 68
CEMT PERFORM DUMP 156 CEMT INQUIRE FILE 87
CEMT PERFORM SHUTDOWN 158 CEMT INQUIRE PROCESSTYPE 104
CEMT transaction 156 CEMT INQUIRE TDQUEUE 127
DUMPDS CEMT SET DB2ENTRY 173
CEMT INQUIRE DUMPDS 79 END
CEMT SET transaction 179 CSFE 249
CEMT transaction 79 ENDAFFINITY
DUMPSCOPE CEMT INQUIRE CONNECTION 59
CEMT INQUIRE SYDUMPCODE 115 CEMT SET CONNECTION 164
CEMT INQUIRE TRDUMPCODE 137 ENDOFDAY
DURATION CEMT INQUIRE STATISTICS 111
CEMT INQUIRE ENQ 81 CEMT SET STATISTICS 194
CEMT INQUIRE UOWENQ 149 ENQ
DYNAMIC CEMT transaction 80
CEMT INQUIRE DSNAME 77 ENQFAILS
CEMT INQUIRE PROGRAM 107 CEMT INQUIRE ENQ 81
DYNAMSTATUS CEMT INQUIRE UOWENQ 149
CEMT INQUIRE PROGRAM 107 ENQMODEL
CEDA 36
CEMT DISCARD 51
CEMT INQUIRE ENQMODEL 82
CEMT transaction 82

ENQNAME EXTRA
CEMT INQUIRE ENQMODEL 82 CEMT INQUIRE TDQUEUE 128
ENQQUEUE
CEMT SET transaction 179
ENQSCOPE F
CEMT INQUIRE ENQ 81 FACILITY
CEMT INQUIRE ENQMODEL 82 CEMT INQUIRE TASK 120
CEMT INQUIRE UOWENQ 149 FACILITYLIKE
ENQUEUE CEMT INQUIRE TRANSACTION 133
CEMT PERFORM STATISTICS 159 FAILED
EQUAL CEMT INQUIRE CONNECTION 60
CEMT INQUIRE DB2CONN 65 CEMT INQUIRE JOURNALNAME 93
CEMT INQUIRE DB2ENTRY 69 CEMT INQUIRE STREAMNAME 113
CEMT SET DB2CONN 170 FAILEDBKOUT
CEMT SET DB2ENTRY 173 CEMT INQUIRE UOWDSNFAIL 147
ERDSASIZE Family of resources 47
CEMT INQUIRE DSAS 73 FCANCEL
error message in partition 5 CEMT INQUIRE CONNECTION 61
errors in message switching 241 CEMT SET CONNECTION 164
ERRTERM FENODE
CMSG 235 CEMT DISCARD 51
ERRTERM INVALID AT XXXXX FEPI
CMSG 242 CEMT PERFORM STATISTICS 159
ERRTERM INVLD/UNSUPP XXXX FEPI, Front End Programming Interface ix
CMSG 242 FEPOOL
ESDSASIZE CEMT DISCARD 51
CEMT INQUIRE DSAS 73 FEPROPSET
EUDSASIZE CEMT DISCARD 51
CEMT INQUIRE DSAS 73 FETARGET
EVENT CEMT DISCARD 51
CEMT INQUIRE MONITOR 97 FILE
CEMT SET MONITOR 189 CEDA 36
EVENTCLASS CEMT DISCARD 51
CEMT INQUIRE MONITOR 97 CEMT INQUIRE ENQ 81
EXCEPT CEMT INQUIRE FILE 87
CEMT INQUIRE MONITOR 97 CEMT INQUIRE PROCESSTYPE 104
CEMT SET MONITOR 189 CEMT INQUIRE UOWENQ 150
EXCEPTCLASS CEMT PERFORM STATISTICS 159
CEMT INQUIRE MONITOR 97 CEMT SET transaction 180
EXCI CEMT transaction 85
CEMT INQUIRE CONNECTION 60 FILECOUNT
CEMT INQUIRE EXCI 84 CEMT INQUIRE DSNAME 76
CEMT INQUIRE transaction 83 fixed-format terminals 215
EXCLSTATUS FLUSH
CEMT INQUIRE FILE 87 CEMT INQUIRE JOURNALNAME 93
EXCLUSIVE CEMT SET JOURNALNAME 186
CEMT INQUIRE FILE 87 FORCE
CEMT SET FILE 182 CEMT INQUIRE SYSTEM 117
EXECENQ CEMT INQUIRE UOW 144
CEMT INQUIRE ENQ 81 CEMT SET DSNAME 177
CEMT INQUIRE UOWENQ 150 CEMT SET SYSTEM 199
EXECKEY CEMT SET UOW 209
CEMT INQUIRE PROGRAM 108 FORCECLOSE
execution diagnostic facility (EDF) 41 CEMT INQUIRE FILE 88
EXECUTIONSET CEMT INQUIRE VTAM 153
CEMT INQUIRE PROGRAM 108 CEMT SET FILE 182
Index 275
FORCECLOSE (continued) GMT
CEMT SET VTAM 210 CEMT INQUIRE MONITOR 98
FORCEDISABLED GRNAME
CEMT SET DB2ENTRY 173 CEMT INQUIRE CONNECTION 60
FORCENOTCONNECTED CEMT INQUIRE VTAM 153
CEMT SET DB2CONN 169 GROUP
FORCEPURGE CEDA 37
CEMT INQUIRE CONNECTION 61 CEMT INQUIRE DB2ENTRY 68
CEMT INQUIRE NETNAME 101 CEMT SET DB2CONN 168
CEMT INQUIRE TASK 121 CEMT SET DB2ENTRY 172
CEMT INQUIRE TERMINAL 131 group identifier 218
CEMT SET CONNECTION 164 GROUPID
CEMT SET LINE 186 CESN 218
CEMT SET NETNAME 190 GRSTATUS
CEMT SET TASK 200 CEMT INQUIRE VTAM 153
CEMT SET TERMINAL 205 GTF trace 221
FORCEQR GTFTRACE
CEMT INQUIRE SYSTEM 117 CEBT INQUIRE GTFTRACE 23
CEMT SET SYSTEM 199 CEBT INQUIRE transaction 23
FORCEUOW CEBT SET transaction 28
CEMT INQUIRE CONNECTION 62 CEMT INQUIRE GTFTRACE 89
CEMT SET CONNECTION 164 CEMT INQUIRE transaction 89
FREEING CEMT SET transaction 184
CEMT INQUIRE CONNECTION 60 GTRAP
FREQUENCY CSFE DEBUG 251
CEMT INQUIRE MONITOR 97
CEMT SET MONITOR 189
FRLOG H
CEMT INQUIRE DSNAME 77 hardcopy terminal 257
Front End Programming Interface (FEPI) ix HBACKOUT
FTYPE CEMT INQUIRE UOW 144
CEMT INQUIRE TASK 120 HCOMMIT
FULL CEMT INQUIRE UOW 144
CEMT SET PROCESSTYPE 191 HEADING
FULLAPI CMSG 236
CEMT INQUIRE PROGRAM 108 HEADNG NOT YES/NO AT XXXX
CEMT SET PROGRAM 193 CMSG 243
FULLDATE hexadecimal values 48
CMSG 235 HHHHHH
FWDRECOVABLE CSPG 254, 257
CEMT INQUIRE DSNAME 76 HHMM
FWDRECOVLSN CMSG 238, 244
CEMT INQUIRE DSNAME 78 HHMMSS
CEMT INQUIRE VTAM 154
CEMT SET VTAM 210
G HIGH
GARBAGEINT CEMT INQUIRE DB2CONN 65
CEMT INQUIRE WEB 154 CEMT INQUIRE DB2ENTRY 69
CEMT SET WEB 211 CEMT SET DB2CONN 170
generic names 47 CEMT SET DB2ENTRY 173
generic resource identifiers 47 HTIME
GETPAGE CEMT INQUIRE TASK 121
CSPG 253, 255 HTYPE
global kernel exit routines 251 CEMT INQUIRE TASK 121
global trap/trace program exit routine 251 HVALUE
CEMT INQUIRE TASK 121

inquire about a resource 45
I INQUIRE keyword, CEMT 45
ID INS
CMSG 236 CEOT 213
ID OPERAND GT 62 CHARS INSERVICE
CMSG 243 CEMT INQUIRE CONNECTION 62
ID OPERAND MISSING CEMT INQUIRE LINE 95
CMSG 243 CEMT INQUIRE NETNAME 101
ID PARAM MISSING OR NO ) CEMT INQUIRE TERMINAL 131
CMSG 243 CEMT SET CONNECTION 164
IDENTIFIER CEMT SET LINE 186
CEMT INQUIRE TASK 121 CEMT SET NETNAME 190
identifiers CEMT SET TERMINAL 205
resource, lists of 47 interface to master terminal, programmable 49
identifying terminals 3 INTERNAL
IDLE CEMT INQUIRE TASK 122
CEMT INQUIRE DELETSHIPPED 70 interregion communication (IRC) 91, 185
CEMT SET DELETSHIPPED 175 INTERVAL
IMMCLOSE CEMT INQUIRE DELETSHIPPED 71
CEMT INQUIRE IRC 91 CEMT INQUIRE STATISTICS 111
CEMT INQUIRE VTAM 153 CEMT SET DELETSHIPPED 175
CEMT SET IRC 185 CEMT SET STATISTICS 195
CEMT SET VTAM 210 INTRA
IMMEDIATE CEMT INQUIRE TDQUEUE 128
CEBT PERFORM SHUTDOWN 25 INTTRACE
CEMT PERFORM SHUTDOWN 158 CEBT INQUIRE INTTRACE 23
IMMQUIESCED CEBT INQUIRE transaction 23
CEMT INQUIRE DSNAME 78 CEBT SET transaction 29
CEMT SET DSNAME 177 CEMT INQUIRE INTTRACE 90
INACTIVE CEMT INQUIRE transaction 90
CEMT INQUIRE SYSTEM 118, 119 CEMT SET transaction 184
INDEXRECFULL INVALID
CEMT INQUIRE UOWDSNFAIL 147 CEMT INQUIRE DSNAME 76
INDIRECT INVALID LDC AT XXXXXXXX
CEMT INQUIRE CONNECTION 59 CMSG 243
CEMT INQUIRE TDQUEUE 128 INVALID OPND AT XXXXX
INDOUBT CMSG 243
CEMT INQUIRE TASK 121 INVALID TBL SFX AT XXXXX
CEMT INQUIRE TDQUEUE 127 CMSG 243
CEMT INQUIRE TRANSACTION 134 INVLD OPERATR ID AT XXXXX
CEMT INQUIRE UOW 144 CMSG 243
CEMT INQUIRE UOWDSNFAIL 147 INVLD SEPARATOR AT XXXXX
INDOUBTMINS CMSG 243
CEMT INQUIRE TASK 121 INVLD TERMINL ID XXXX
CEMT INQUIRE TRANSACTION 134 CMSG 243
INDOUBTWAIT invoking a transaction 1
CEMT INQUIRE TASK 121 invoking CEMT from an application program 49
CEMT INQUIRE TDQUEUE 128 IOERROR
CEMT INQUIRE TRANSACTION 134 CEMT INQUIRE UOWDSNFAIL 147
INFLIGHT IOTYPE
CEMT INQUIRE UOW 144 CEMT INQUIRE TDQUEUE 127
Information Display System 233 IRBATCH
INPUT CEMT INQUIRE transaction 90
CEMT INQUIRE TDQUEUE 127 IRC
CMSG 242 CEMT INQUIRE CONNECTION 59
CEMT INQUIRE IRC 91
Index 277
IRC (continued) LCKSTRUCFULL
CEMT INQUIRE transaction 91 CEMT INQUIRE UOWDSNFAIL 147
CEMT INQUIRE UOWLINK 151 LDC (logical device code) 239
CEMT SET transaction 185 LDC NOT 2 CHARS AT XXXXX
IRC (interregion communication) CMSG 243
CEMT INQUIRE transaction 91 LE/370 108
CEMT SET transaction 185 LE370
ISOLATE CEMT INQUIRE PROGRAM 108
CEMT INQUIRE TRANSACTION 134 LENGTH
ISOLATEST CEMT INQUIRE PROGRAM 108
CEMT INQUIRE TRANSACTION 134 CEMT INQUIRE TSQUEUE 141
LINE
CEMT INQUIRE transaction 94
J CEMT SET transaction 186
JAVA LINE(VALUE)
CEMT INQUIRE PROGRAM 108 CEMT INQUIRE LINE 95
JMODEL LINK
CEMT DISCARD 51 CEMT INQUIRE UOW 143
CEMT transaction 92 CEMT INQUIRE UOWLINK 151
JMODEL(VALUE) LIST
CEMT INQUIRE JMODEL 92 CEDA 37
JOURNALMODEL Lists
CEDA 37 of resource identifiers 47
JOURNALNAME LOAD
CEMT DISCARD 51 CEMT INQUIRE FILE 87
CEMT INQUIRE JMODEL 92 CEMT SET FILE 182
CEMT PERFORM STATISTICS 159 LOADTYPE
CEMT transaction 93 CEMT INQUIRE FILE 87
JOURNALNAME(VALUE) LOCAL
CEMT INQUIRE JOURNALNAME 93 CEMT INQUIRE MONITOR 98
JVM CEMT INQUIRE NETNAME 100
CEMT SET PROGRAM 193 CEMT INQUIRE SYDUMPCODE 115
JVMCLASS CEMT INQUIRE TERMINAL 131
CEMT INQUIRE PROGRAM 108 CEMT INQUIRE TRDUMPCODE 137
CEMT SET PROGRAM 193 CEMT SET SYDUMPCODE 196
JVMDEBUG CEMT SET TRDUMPCODE 207
CEMT INQUIRE PROGRAM 108 LOCATION
CEMT INQUIRE TSMODEL 138
CEMT INQUIRE TSQUEUE 141
K LOCKING
kernel exit routines, global 251
CEMT SET FILE 182
key, tab 48
LOGDEFER
KEYLENGTH
CEMT SET SYSTEM 199
CEMT SET FILE 182
logical device code (LDC) 239
keyword, minimum abbreviation 2
logical unit destination 239
LOSTLOCKS
L LOW
LANGUAGE
CEMT INQUIRE PROGRAM 108 CEMT INQUIRE DB2CONN 65
CESN 218 CEMT INQUIRE DB2ENTRY 69
Language Environment/370 108 CEMT SET DB2CONN 170
LASTUSEDINT CEMT SET DB2ENTRY 173
CEMT INQUIRE TSQUEUE 141 LSRPOOL
CEMT SET TSQUEUE 208 CEDA 37
CEMT PERFORM STATISTICS 159

LTPNAME message-switching (continued)
CEMT INQUIRE PARTNER 103 examples 245
LU61 message-switching response
CEMT INQUIRE CONNECTION 61 indicator 241
CEMT INQUIRE UOWLINK 152 response 241
message-switching transaction
multiple destinations 231
M saved status 232
MAIN subsystems 233
CEMT INQUIRE TSMODEL 138 terminal systems 233
CEMT INQUIRE TSQUEUE 142 transaction CMSG 231
MANUAL messages
CEBT SET TAKEOVER 30 +DATE INVLD 2330 to 0030 245
MAPSET ALL ROUTE ENTRIES DELETED 241
CEDA 37 CANCELED - TEMP STRG ERR N 241
CEMT INQUIRE PROGRAM 108 canceling 232
master terminal operator chaining 255
duties 4 chaining in partition 5
restriction 4 CLEAR/CANCL or CONT INPUT/ROUTE/MSG 242
transaction, CEBT 21 CONTINUE INPUT 242
transaction, CEMT 45 CONTINUE INPUT OR MSG 242
types of terminal 4 CONTINUE MSG 242
master terminal, programmable interface to 49 CONTINUE ROUTE OPERAND 242
MAXACTIVE DATE ALREADY PASSED 242
CEMT INQUIRE TCLASS 123 DATE INVALID AT xxxxxxxx 242
CEMT SET TCLASS 201 DATE NOT xx/xx AT xxxxx 242
MAXIMUM DATE TOO FAR IN FUTURE 242
CEMT INQUIRE AUTOINSTALL 54 delivery 232
CEMT INQUIRE MODENAME 96 displaying 255
CEMT INQUIRE SYDUMPCODE 115 ERRTERM INVALID AT xxxxx 242
CEMT INQUIRE TRDUMPCODE 137 ERRTERM INVLD/UNSUPP xxxx 242
CEMT SET SYDUMPCODE 196 HEADNG NOT YES/NO AT xxxx 243
CEMT SET TRDUMPCODE 207 ID OPERAND GT 62 CHARS 243
MAXITEMLEN ID PARAM MISSING OR NO ) 243
CEMT INQUIRE TSQUEUE 142 INVALID LDC AT xxxxxxxx 243
MAXNUMRECS INVALID OPND AT xxxxx 243
CEMT INQUIRE FILE 87 INVALID TBL SFX AT xxxxx 243
CEMT SET FILE 182 INVLD OPERATR ID AT xxxxx 243
MAXOPENTCBS INVLD SEPARATOR AT xxxxx 243
CEMT INQUIRE SYSTEM 117 INVLD TERMINL ID xxxx 243
CEMT SET SYSTEM 199 IO OPERAND GT 62 CHARS 243
MAXREQS LDC NOT 2 CHARS AT xxxxx 243
CEMT SET AUTOINSTALL 161 MESSAGE HAS BEEN ROUTED 243
MAXTASKS MESSAGE HAS BEEN SENT 259
CEMT INQUIRE SYSTEM 117 MSG NOT SENT- NO RECEIVER 243
CEMT SET SYSTEM 199 NEED OPCLASS OR ROUTE 243
MEMBER NO INPUT - REENTER 243
CEMT INQUIRE TDQUEUE 127 NO MESSAGE PROVIDED 243
MEMBERNAME NO MSG STRT QUOT AT xxxxx 243
CEMT INQUIRE CONNECTION 60 NO TERM LIST TBL- xx 243
MESSAGE HAS BEEN ROUTED NO TRMID FOR LDC AT xxxxx 243
CMSG 243 OPCLASS NOT 1-24 AT xxxxx 243
message-switching OPERATORS NOT SIGNDON NNN 244
continuation 232 OPRTR ID NOT SIGNDON /xxx 244
displaying at terminal 255 PROTECT OPND NOT 1-2 CHAR 244
errors 241 purging 5
Index 279
messages (continued) MSGQUEUE2 (continued)
ROUTE INVALID AT xxxxx 244 CEMT SET DB2CONN 169
sending 231 MSGQUEUE3
SPACE MUST FOLLOW TRANSID 244 CEMT INQUIRE DB2CONN 65
TERMID GT 4 CHAR AT xxxxx 244 CEMT SET DB2CONN 169
TERMID NOT +/− AT xxxxx 244 MSGTERM
TERMINATED BY OPERATOR 244, 259 CSPG 256
terminating in partition 5 multiple console support 5
termination 256 multiple destinations, message switching 231
TIME ALREADY PASSED 244 multiregion operation (MRO) 247
TIME INVALID AT xxxxx 244 MVS
TIME NOT 4 CHARS AT xxxxx 244 CEMT INQUIRE JMODEL 92
TOO MANY TBL SFX AT xxxxx 244 CEMT INQUIRE JOURNALNAME 94
UNBALANCD PARENS AT xxxxx 244
UNSUP OPRT TRMNL xxxxxxxx 244
UNSUP TERMINAL xxxxxxxx 245 N
ZERO LENGTH MSG AT '' 245 N906D
messages and codes, display 229 CEMT INQUIRE DB2CONN 66
MESSCHN NAME
CSPG 255 CEMT INQUIRE DOCTEMPLATE 72
MINITEMLEN NAMEIND
CEMT INQUIRE TSQUEUE 142 CEMT INQUIRE TDQUEUE 127
MM/DD NATLANG, system initialization parameter 218
CMSG 234, 235 NATURE
MM/DD/YY CEMT INQUIRE NETNAME 100
CMSG 234 CEMT INQUIRE TERMINAL 131
MM/DD/YYYY NEED OPCLASS OR ROUTE
CMSG 235 CMSG 243
MOD NEGPOLL
CEMT INQUIRE TDQUEUE 126 CEMT INQUIRE LINE 95
MODENAME CEMT SET LINE 186
CEMT INQUIRE MODENAME 96 NET
CEMT INQUIRE transaction 95 CEOT 213
CEMT SET transaction 187 NETID
MODENAME, CEMT requests 187 CEMT PERFORM ENDAFFINITY 156
MODIFY command 6 NETNAME
MONITOR CEMT INQUIRE CONNECTION 60
CEMT INQUIRE MONITOR 97 CEMT INQUIRE NETNAME 100
CEMT INQUIRE transaction 97 CEMT INQUIRE PARTNER 103
CEMT PERFORM STATISTICS 159 CEMT INQUIRE TERMINAL 131
CEMT SET transaction 188 CEMT INQUIRE transaction 99
MRO (multiregion operation) 247 CEMT INQUIRE UOW 143
MROBATCH CEMT INQUIRE UOWDSNFAIL 146
CEMT INQUIRE SYSTEM 117 CEMT PERFORM ENDAFFINITY 156
CEMT SET SYSTEM 199 CEMT SET transaction 190
MSG NETUOWID
CMSG 236, 242 CEMT INQUIRE ENQ 81
MSG NOT SENT - NO RECEIVER CEMT INQUIRE UOW 143
CMSG 243 CEMT INQUIRE UOWENQ 149
MSGCOPY CEMT INQUIRE UOWLINK 151
CSPG 257 NETWORK
MSGQUEUE1 CEMT INQUIRE PARTNER 103
CEMT INQUIRE DB2CONN 65 networks
CEMT SET DB2CONN 169 CEMT INQUIRE transaction 99
MSGQUEUE2 CEMT SET transaction 190

NEWCOPY NOCREATE (continued)
CEMT INQUIRE PROGRAM 107 CEMT SET NETNAME 190
CEMT SET PROGRAM 193 CEMT SET TERMINAL 205
NEWPS NODAE
CESN 218 CEMT INQUIRE SYDUMPCODE 115
NEXT CEMT SET SYDUMPCODE 197
CEBT INQUIRE AUXTRACE 21 NODEBUG
CEBT SET AUXTRACE 27 CEMT SET PROGRAM 193
CEMT INQUIRE AUXTRACE 56 NODELETE
CEMT SET AUXTRACE 162 CEMT INQUIRE FILE 86
NEXTTIME CEMT SET FILE 182
CEMT INQUIRE STATISTICS 111, 112 NOEMPTYREQ
CEMT SET STATISTICS 194 CEMT INQUIRE FILE 87
NO CEMT SET FILE 182
CMSG 236 NOEVENT
NO INPUT - REENTER CEMT INQUIRE MONITOR 97
CMSG 243 CEMT SET MONITOR 189
NO MESSAGE PROVIDED NOEXCEPT
CMSG 243 CEMT INQUIRE MONITOR 97
NO MSG STRT QUOT AT XXXXX CEMT SET MONITOR 189
CMSG 243 NOEXCLUSIVE
NO TERM LIST TBL-XX CEMT INQUIRE FILE 87
CMSG 243 CEMT SET FILE 182
NO TRMID FOR LDC AT XXXXX NOFORCE
CMSG 243 CEMT INQUIRE SYSTEM 117
NOADDABLE CEMT SET SYSTEM 199
CEMT INQUIRE FILE 86 NOISOLATE
CEMT SET FILE 182 CEMT INQUIRE TRANSACTION 134
NOATI NOLOAD
CEMT INQUIRE NETNAME 99 CEMT INQUIRE FILE 87
CEMT INQUIRE TERMINAL 130 CEMT SET FILE 183
CEMT SET NETNAME 190 NOLOSTLOCKS
CEMT SET TERMINAL 205 CEMT INQUIRE DSNAME 77
CEOT 213 NONE
NOAUTOSWITCH CEMT INQUIRE DB2CONN 63
CEBT INQUIRE DUMP 22 CEMT INQUIRE DB2ENTRY 68
CEBT SET DUMP 28 CEMT SET DB2CONN 167
CEMT INQUIRE DUMPDS 79 CEMT SET DB2ENTRY 172
CEMT SET DUMPDS 179 CSFE 250
NOBROWSE NONTERMREL
CEMT INQUIRE FILE 86 CEMT INQUIRE DB2CONN 65
CEMT SET FILE 182 CEMT SET DB2CONN 169
NOCEDF NOPERF
CEMT INQUIRE PROGRAM 107 CEMT INQUIRE MONITOR 98
CEMT SET PROGRAM 193 CEMT SET MONITOR 189
NOCMDPROT NOREAD
CEMT INQUIRE SYSTEM 116 CEMT INQUIRE FILE 88
NOCONNECT CEMT SET FILE 183
CEMT INQUIRE DB2CONN 66 NORECOVDATA
CEMT SET DB2CONN 170 CEMT INQUIRE CONNECTION 61
NOCONVERSE CEMT SET CONNECTION 164
CEMT INQUIRE MONITOR 97 NOREENTPROTECT
CEMT SET MONITOR 189 CEMT INQUIRE SYSTEM 118
NOCREATE NORELEASE
CEMT INQUIRE NETNAME 100 CEMT INQUIRE DB2CONN 65
CEMT INQUIRE TERMINAL 131 CEMT SET DB2CONN 169
Index 281
NORESTART NOTREQUIRED
CEMT PERFORM SHUTDOWN 158 CEMT INQUIRE PROGRAM 107
NORETAINED NOTRLS
CEMT INQUIRE DSNAME 77 CEMT INQUIRE FILE 88
NOROLLBACK CEMT INQUIRE UOWDSNFAIL 148
CEMT INQUIRE DB2CONN 65 CEMT SET FILE 183
CEMT INQUIRE DB2ENTRY 68 NOTROUTABLE
NOSDTRAN CEMT INQUIRE TRANSACTION 135
CEMT PERFORM SHUTDOWN 158 NOTSOS
NOSECURITY CEMT INQUIRE DSAS 72, 73
CEMT INQUIRE TSMODEL 138 CEMT INQUIRE SYSTEM 118
NOSHUTDOWN NOTSUPPORTED
CEMT INQUIRE SYDUMPCODE 115 CEMT INQUIRE CONNECTION 60
CEMT INQUIRE TRDUMPCODE 137 NOTTABLE
CEMT SET SYDUMPCODE 197 CEMT INQUIRE FILE 88
CEMT SET TRDUMPCODE 207 CEMT SET FILE 183
NOSWITCH NOTTI
CEBT INQUIRE AUXTRACE 21 CEMT INQUIRE NETNAME 102
CEBT SET AUXTRACE 27 CEMT INQUIRE TERMINAL 132
CEMT INQUIRE AUXTRACE 56 CEMT SET NETNAME 191
CEMT SET AUXTRACE 162 CEMT SET TERMINAL 205
NOSYNCPOINT CEOT 214
CEMT INQUIRE MONITOR 98 NOTWAIT
CEMT SET MONITOR 189 CEMT INQUIRE DB2CONN 66
NOSYSDUMP CEMT INQUIRE DB2ENTRY 69
CEMT INQUIRE SYDUMPCODE 115 CEMT SET DB2CONN 170
CEMT INQUIRE TRDUMPCODE 137 CEMT SET DB2ENTRY 173
CEMT SET SYDUMPCODE 197 NOUPDATE
CEMT SET SYSTEM 199 CEMT INQUIRE FILE 89
CEMT SET TRDUMPCODE 207 CEMT SET FILE 183
NOSYSLOG NOWAIT
CEMT INQUIRE STREAMNAME 113 CEMT INQUIRE TASK 121
NOTAPPLIC CEMT INQUIRE TDQUEUE 128
CEMT INQUIRE DSNAME 77 CEMT INQUIRE TRANSACTION 134
CEMT INQUIRE UOWDSNFAIL 147 NRS
notation, syntax 2 CEMT INQUIRE CONNECTION 61
NOTCONNECTED NUMBER
CEMT INQUIRE DB2CONN 65 CEMT INQUIRE LINE 95
CEMT SET DB2CONN 169 CEMT SET LINE 187
NOTDEFINED NUMITEMS
CEMT INQUIRE PROGRAM 108 CEMT INQUIRE TSQUEUE 142
NOTDYNAMIC
CEMT INQUIRE PROGRAM 108
NOTPENDING O
CEMT INQUIRE CONNECTION 60 OBJECT
CEMT SET CONNECTION 165 CEMT INQUIRE DSNAME 76
NOTPURGEABLE OBTAINING
CEMT INQUIRE TRANSACTION 134 CEMT INQUIRE CONNECTION 60
CEMT SET TRANSACTION 206 OFF
NOTRANDUMP CEBT SET SURVEILLANCE 29
CEMT INQUIRE TRDUMPCODE 137 CEDF 41
CEMT SET TRDUMPCODE 207 CEDX 43
NOTRECOVABLE CEMT INQUIRE MONITOR 98
CEMT INQUIRE DSNAME 76 CEMT INQUIRE STATISTICS 112
CEMT INQUIRE TSMODEL 138 CEMT SET MONITOR 189
CEMT INQUIRE TSQUEUE 142 CEMT SET PROCESSTYPE 191

OFF (continued) OPERATORS NOT SIGNDON NNN
CEMT SET STATISTICS 195 CMSG 244
CSFE SPOOLFE 249 OPID
CSFE ZCQTRACE 249 CEMT INQUIRE DB2CONN 64
OK CEMT INQUIRE DB2ENTRY 68
CEMT INQUIRE STREAMNAME 113 CEMT SET DB2CONN 168
CEMT INQUIRE UOWLINK 152 CEMT SET DB2ENTRY 173
OLD CMSG 237
CEMT INQUIRE FILE 86 OPRTR ID NOT SIGNDON /XXX
CEMT INQUIRE TDQUEUE 126 CMSG 244
CEMT SET FILE 183 OSLEVEL
OMGINTERFACE option CEMT INQUIRE SYSTEM 117
CEMT INQUIRE REQUESTMODEL command 110 OUTPUT
OMGMODULE option CEMT INQUIRE TDQUEUE 127
CEMT INQUIRE REQUESTMODEL command 110 OUTSERVICE
OMGOPERATION option CEMT INQUIRE CONNECTION 62
CEMT INQUIRE REQUESTMODEL command 110 CEMT INQUIRE LINE 95
ON CEMT INQUIRE NETNAME 101
CEBT SET SURVEILLANCE 29 CEMT INQUIRE TERMINAL 132
CEDF 41 CEMT SET CONNECTION 165
CEDX 43 CEMT SET LINE 187
CEMT INQUIRE MONITOR 98 CEMT SET NETNAME 191
CEMT INQUIRE STATISTICS 112 CEMT SET TERMINAL 205
CEMT SET MONITOR 189 overtyping a display 47
CEMT SET STATISTICS 195 OWNER
CSFE SPOOLFE 249 CEMT INQUIRE ENQ 81
OPCLASS CEMT INQUIRE UOWENQ 149
CMSG 236
OPCLASS NOT 1-24 AT XXXXX
CMSG 244 P
OPEN PA1 print key 5
CEBT INQUIRE DUMP 22 PAG
CEBT SET DUMP 28 CEOT 213
CEMT INQUIRE DUMPDS 79 page copying 5, 257
CEMT INQUIRE FILE 88 page retrieval
CEMT INQUIRE IRC 91 and partitions 5, 254
CEMT INQUIRE RRMS 110 logical device 254
CEMT INQUIRE TDQUEUE 127 session 253
CEMT INQUIRE VTAM 153 single keystroke 254
CEMT SET DUMPDS 179 transaction, CSPG 253
CEMT SET FILE 183 page retrieval function
CEMT SET IRC 185 new PROFILE definition, DFHCICSP 2
CEMT SET TDQUEUE 203 PAGEABLE
CEMT SET VTAM 210 CEMT INQUIRE NETNAME 100
OPENERROR CEMT INQUIRE TERMINAL 131
CEMT INQUIRE UOWDSNFAIL 147 CEMT SET NETNAME 191
OPENSTATUS CEMT SET TERMINAL 205
CEMT INQUIRE DUMPDS 79 CEOT 214
CEMT INQUIRE FILE 88 PAGESTATUS
CEMT INQUIRE TDQUEUE 127 CEMT INQUIRE NETNAME 100
CEMT INQUIRE VTAM 153 CEMT INQUIRE TERMINAL 131
OPENSTATUS(VALUE) paging command 253
CEMT INQUIRE IRC 91 PARAMETERS
operating system console as a terminal 5 CSPG 255
operator security 3 partitions 254
Index 283
partitions, BMS 4 plus sign in scrolling under CEMT 48
PARTITIONSET POOL
CEDA 37 CEMT SET DB2ENTRY 173
CEMT INQUIRE PROGRAM 109 POOLNAME
PARTNER CEMT INQUIRE TSMODEL 138
CEDA 37 CEMT INQUIRE TSQUEUE 141
CEMT DISCARD 51 CEMT SET TSQUEUE 208
CEMT INQUIRE PARTNER 103 positional fields 47
CEMT INQUIRE transaction 102 PREFIX
PATH CEMT INQUIRE TSMODEL 138
CEMT INQUIRE DSNAME 76 CMSG 236
PAUSE PRFILE
CEBT INQUIRE AUXTRACE 21 CEMT INQUIRE TRANSACTION 134
CEBT SET AUXTRACE 27 PRGDLAY, system initialization parameter 235
CEMT INQUIRE AUXTRACE 56 PRI
CEMT SET AUXTRACE 162 CEOT 213
PENDING PRINT
CEMT INQUIRE CONNECTION 60 CSFE 249
PENDSTATUS print (PA1) key 5
CEMT INQUIRE CONNECTION 60 PRIORITY
PERF CEMT INQUIRE DB2CONN 65
CEMT INQUIRE MONITOR 98 CEMT INQUIRE DB2ENTRY 69
CEMT SET MONITOR 189 CEMT INQUIRE NETNAME 100
PERFCLASS CEMT INQUIRE TASK 121
CEMT INQUIRE MONITOR 98 CEMT INQUIRE TERMINAL 131
PERFORM, CEBT CEMT INQUIRE TRANSACTION 134
SHUTDOWN 25 CEMT SET DB2CONN 170
SNAP 26 CEMT SET DB2ENTRY 173
TAKEOVER 26 CEMT SET NETNAME 191
PERFORM, CEMT CEMT SET TASK 200
RESET 157 CEMT SET TERMINAL 205
SECURITY 157 CEMT SET TRANSACTION 206
SHUTDOWN 158 PRIVATE
STATISTICS 159 CEMT INQUIRE PROGRAM 109
PF (program function) key 46 CEMT SET PROGRAM 193
PGCHAIN, system initialization parameter 253, 255 PROCESS
PGCOPY, system initialization parameter 253, 257 CEMT INQUIRE TASK 121
PGPURGE, system initialization parameter 253, 256 CEMT SET PROCESSTYPE 191
PGRET, system initialization parameter 253, 255 PROCESSTYPE
PHASEIN CEDA 37
CEMT INQUIRE PROGRAM 107 CEMT DISCARD 52
CEMT SET PROGRAM 193 CEMT INQUIRE TASK 121
PLAN CEMT INQUIRE transaction 103
CEMT INQUIRE DB2CONN 65 CEMT SET transaction 191
CEMT INQUIRE DB2ENTRY 69 PROFILE
CEMT SET DB2CONN 169 CEDA 37
CEMT SET DB2ENTRY 173 CEMT DISCARD 52
PLANEXITNAME CEMT INQUIRE PARTNER 103
CEMT INQUIRE DB2CONN 65 CEMT INQUIRE PROFILE 105
CEMT INQUIRE DB2ENTRY 69 CEMT INQUIRE transaction 105
CEMT SET DB2CONN 170 profile, rebuild 157
CEMT SET DB2ENTRY 173 PROGAUTO
PLi CEMT PERFORM STATISTICS 159
CEMT INQUIRE PROGRAM 108 PROGAUTOCTLG
PLT CEMT INQUIRE SYSTEM 117
CEMT PERFORM SHUTDOWN 158 CEMT SET SYSTEM 198

PROGAUTOEXIT PURGECYCLES
CEMT INQUIRE SYSTEM 117 CEMT INQUIRE DB2CONN 65
CEMT SET SYSTEM 199 CEMT SET DB2CONN 170
PROGAUTOINST PURGETHRESH
CEMT INQUIRE SYSTEM 117 CEMT INQUIRE TCLASS 123
CEMT SET SYSTEM 198 CEMT SET TCLASS 201
PROGRAM PURGETYPE
CEDA 37 CEMT INQUIRE CONNECTION 61
CEMT DISCARD 52 CEMT INQUIRE NETNAME 101
CEMT INQUIRE AUTOINSTALL 55 CEMT INQUIRE TASK 121
CEMT INQUIRE PROGRAM 108 CEMT INQUIRE TERMINAL 131
CEMT INQUIRE transaction 105, 134
CEMT PERFORM STATISTICS 159
CEMT SET AUTOINSTALL 161 Q
CEMT SET PROGRAM 192 Q
CEMT SET transaction 192 CSPG 255
program function (PF) key 46 QD
programmable interface to master terminal 49 CEMT INQUIRE TASK 122
PROGTYPE QLEN
CEMT INQUIRE PROGRAM 108 CEMT INQUIRE ENQ 81
PROTECT CEMT INQUIRE UOWENQ 149
CMSG 236 QR
PROTECT OPND NOT 1-2 CHAR CEMT INQUIRE TASK 122
CMSG 244 QUALIFIER
PROTECTNUM CEMT INQUIRE ENQ 81
CEMT INQUIRE DB2ENTRY 69 CEMT INQUIRE UOWENQ 149
CEMT SET DB2ENTRY 173 QUASIRENT
PROTOCOL CEMT INQUIRE PROGRAM 107
CEMT INQUIRE CONNECTION 60 question mark preceding CEMT 45
CEMT INQUIRE UOWLINK 151 QUEUE
PS CEMT INQUIRE TDQUEUE 127
CESN 218 CEMT SET transaction 194
PSDINTERVAL QUEUED
CEMT INQUIRE VTAM 153 CEMT INQUIRE TCLASS 123
CEMT SET VTAM 210 queues, CEMT requests 126, 194, 201, 203
pseudo-display fields 47 QUIESCED
PTHREADS CEMT INQUIRE DSNAME 78
CEMT INQUIRE DB2ENTRY 69 CEMT SET DSNAME 177
PURGE QUIESCESTATE
CEMT INQUIRE CONNECTION 61 CEMT INQUIRE DSNAME 78
CEMT INQUIRE NETNAME 101
CEMT INQUIRE TASK 121
CEMT INQUIRE TERMINAL 131
R
RACF resource profile 157
CEMT SET CONNECTION 165
RCONNECTION
CEMT SET LINE 187
CEMT SET NETNAME 191
RDBACK
CEMT SET TASK 200
CEMT INQUIRE TDQUEUE 127
CEMT SET TERMINAL 205
RDO (resource definition online) 33
PURGEABILITY
RDSASIZE
CEMT INQUIRE TRANSACTION 134
CEMT INQUIRE DSAS 73
PURGEABLE
READ
CEMT INQUIRE TRANSACTION 134
CEMT SET TRANSACTION 206
CEMT SET FILE 183
PURGECYCLEM
READBACK
CEMT INQUIRE TDQUEUE 127
Index 285
READSTATUS RELEASED
CEMT INQUIRE FILE 88 CEMT INQUIRE CONNECTION 59
REASON CEMT INQUIRE NETNAME 101
CEMT INQUIRE UOWDSNFAIL 146 CEMT INQUIRE TERMINAL 132
REBUILD CEMT SET CONNECTION 166
CEMT PERFORM SECURITY 157 CEMT SET NETNAME 191
rebuild resource profiles 157 CEMT SET TERMINAL 205
RECONNECT REMLOSTLOCKS
CEMT INQUIRE DB2CONN 66 CEMT INQUIRE DSNAME 77
CEMT SET DB2CONN 170 REMOTE
RECORD CEMT INQUIRE FILE 86
CEMT INQUIRE STATISTICS 112 CEMT INQUIRE TDQUEUE 128
CEMT PERFORM STATISTICS 159 REMOTEPREFIX
RECORDING CEMT INQUIRE TSMODEL 138
CEMT INQUIRE STATISTICS 112 REMOTESYSTEM
RECORDNOW CEMT INQUIRE CONNECTION 61
CEMT SET STATISTICS 195 CEMT INQUIRE NETNAME 101
RECORDSIZE CEMT INQUIRE PROGRAM 109
CEMT INQUIRE FILE 88 CEMT INQUIRE TERMINAL 131
CEMT SET FILE 183 CEMT INQUIRE TSMODEL 138
RECOVDATA REMOVE
CEMT INQUIRE CONNECTION 61 CEMT INQUIRE DSNAME 75
RECOVERABLE CEMT INQUIRE SYDUMPCODE 115
CEMT INQUIRE DSNAME 76 CEMT INQUIRE TRDUMPCODE 136
CEMT INQUIRE TSMODEL 138 CEMT SET DSNAME 178
CEMT INQUIRE TSQUEUE 142 CEMT SET SYDUMPCODE 197
RECOVERED CEMT SET TRDUMPCODE 207
CEMT INQUIRE DSNAME 75 REPLY command 6
CEMT SET DSNAME 177 REQUESTMODEL
RECOVERLOCKS CEDA 37
CEMT INQUIRE DSNAME 77 CEMT DISCARD 52
RECOVERY CEMT transaction 110
CEMT PERFORM STATISTICS 159 REQUIRED
RECOVSTATUS CEMT INQUIRE PROGRAM 107
CEMT INQUIRE CONNECTION 61 RESCOUNT
CEMT INQUIRE DSNAME 76 CEMT INQUIRE PROGRAM 109
CEMT INQUIRE TSMODEL 138 RESET
CEMT INQUIRE TSQUEUE 142 CEMT INQUIRE JOURNALNAME 93
REENTPROTECT CEMT INQUIRE STATISTICS 112
CEMT INQUIRE SYSTEM 118 CEMT INQUIRE SYDUMPCODE 115
REGISTERED CEMT INQUIRE TRDUMPCODE 136
CEMT INQUIRE VTAM 153 CEMT PERFORM RESET 157
REJECT CEMT SET JOURNALNAME 186
CEMT INQUIRE TDQUEUE 127 CEMT SET SYDUMPCODE 197
RELATED CEMT SET TRDUMPCODE 207
CEMT INQUIRE SYDUMPCODE 115 RESETLOCKS
CEMT INQUIRE TRDUMPCODE 137 CEMT INQUIRE DSNAME 75
CEMT SET SYDUMPCODE 197 CEMT SET DSNAME 178
CEMT SET TRDUMPCODE 207 RESETNOW
RELATION CEMT PERFORM STATISTICS 160
CEMT INQUIRE ENQ 81 CEMT SET STATISTICS 195
CEMT INQUIRE UOWENQ 149 RESOURCE
RELEASE CEMT INQUIRE ENQ 81
CEMT INQUIRE DB2CONN 65 CEMT INQUIRE UOWENQ 150
CEMT INQUIRE SYSTEM 118 resource definition online transaction, CEDA 33

resource definitions ROUTE
profile, DFHCICSP 2 CMSG 237, 242
resource groups ROUTE INVALID AT XXXXX
Subdefining 47 CMSG 244
resource identifiers routed pages 257
lists of 47 routing transaction, CRTE 247
RESYNC ROUTSTATUS
CEMT INQUIRE CONNECTION 62 CEMT INQUIRE TRANSACTION 134
CEMT SET CONNECTION 166 RRCOMMITFAIL
RESYNCSTATUS CEMT INQUIRE UOWDSNFAIL 147
CEMT INQUIRE UOWLINK 152 RRINDOUBT
RETAINED CEMT INQUIRE UOWDSNFAIL 147
CEMT INQUIRE DSNAME 77 RRMS
CEMT INQUIRE ENQ 81 CEMT INQUIRE transaction 110
CEMT INQUIRE UOWENQ 150 CEMT INQUIRE UOW 144
RETLOCKS CEMT INQUIRE UOWLINK 152
CEMT INQUIRE DSNAME 77 RSESSION
retrieve a page 5, 253 CEMT INQUIRE NETNAME 100
RETRY CEMT INQUIRE TERMINAL 131
CEMT INQUIRE DSNAME 76 RTERMINAL
CEMT SET DSNAME 178 CEMT INQUIRE NETNAME 100
RLEN CEMT INQUIRE TERMINAL 131
CEMT INQUIRE ENQ 81 RUNAWAY
CEMT INQUIRE UOWENQ 150 CEMT INQUIRE SYSTEM 118
RLS CEMT SET SYSTEM 199
CEMT INQUIRE FILE 88 RUNNING
CEMT SET FILE 183 RUNSTATUS
RLSACCESS CEMT INQUIRE TASK 122
CEMT INQUIRE FILE 88 RUNTIME
CEMT INQUIRE UOWDSNFAIL 148 CEMT INQUIRE PROGRAM 109
RLSGONE
CEMT INQUIRE UOWDSNFAIL 147
RLSSERVER S
CEMT INQUIRE UOW 144 S
RMI saved status, message switching 232
CEMT INQUIRE UOWLINK 152 SCANDELAY
RMIQFY CEMT INQUIRE SYSTEM 118
CEMT INQUIRE UOWLINK 152 CEMT SET SYSTEM 199
RNAME scrolling a display 48
CEMT INQUIRE CONNECTION 62 SD
CEMT INQUIRE NETNAME 101 CEMT INQUIRE TASK 122
CEMT INQUIRE TERMINAL 131 SDSASIZE
RNETNAME CEMT INQUIRE DSAS 73
CEMT INQUIRE CONNECTION 62 SDTRAN
CEMT INQUIRE NETNAME 101 CEMT INQUIRE SYSTEM 118
CEMT INQUIRE TERMINAL 131 CEMT PERFORM SHUTDOWN 158
ROLE SECURITY 157
CEMT INQUIRE UOWLINK 152 CEMT INQUIRE DB2CONN 65
ROLLBACK CEMT INQUIRE TSMODEL 138
CEMT INQUIRE DB2CONN 65 security checking 38, 49
CEMT INQUIRE DB2ENTRY 68 security, operator 3
ROUTABLE SECURITY(REBUILD)
CEMT INQUIRE TRANSACTION 135 CEMT SET DB2CONN 170
Index 287
SECURITYST single keystroke retrieval (SKR) 254
CEMT INQUIRE TSMODEL 138 SKR (single keystroke retrieval) 254
SEND SKRxxxx, system initialization parameter 254
CMSG 238 SMF
sequential terminal 233 CEMT INQUIRE JMODEL 92
SERVSTATUS CEMT INQUIRE JOURNALNAME 94
CEMT INQUIRE CONNECTION 62 SNAP
CEMT INQUIRE NETNAME 101 CEMT PERFORM DUMP 156
CEMT INQUIRE TERMINAL 131 CEMT transaction 156
SESSION SNAP command
CEMT INQUIRE NETNAME 100 CEBT transaction 26
CEMT INQUIRE TERMINAL 131 SOS
SESSIONID CEMT INQUIRE DSAS 72, 73
CEDF 41 CEMT INQUIRE SYSTEM 118
SESSIONS SOSABOVE
CEDA 37 CEMT INQUIRE DSAS 73
SHARE CEMT INQUIRE SYSTEM 118
CEMT INQUIRE FILE 86 SOSBELOW
CEMT SET FILE 183 CEMT INQUIRE DSAS 73
SHARED CEMT INQUIRE SYSTEM 118
CEMT INQUIRE PROGRAM 109 SOSSTATUS
CEMT SET PROGRAM 193 CEMT INQUIRE DSAS 72
SHARESTATUS CEMT INQUIRE SYSTEM 118
CEMT INQUIRE PROGRAM 109 SPACE MUST FOLLOW TRANSID
shipped terminal definitions CMSG 244
deletion of SPOOLFE
CEMT INQUIRE DELETSHIPPED command 70 CSFE 249
CEMT PERFORM DELETSHIPPED command 155 spooling interface trace 249
CEMT SET DELETSHIPPED command 175 SQLCODE
SHR CEMT INQUIRE DB2CONN 64
CEMT INQUIRE TDQUEUE 126 CEMT INQUIRE DB2ENTRY 68
SHUNTED CEMT SET DB2CONN 169
CEMT INQUIRE UOW 145 CEMT SET DB2ENTRY 173
SHUTDOWN STANDBYMODE
CEMT INQUIRE SYDUMPCODE 115 CEMT SET DB2CONN 170
CEMT INQUIRE TRDUMPCODE 137 STANDYBYMODE
CEMT SET SYDUMPCODE 197 CEMT INQUIRE DB2CONN 66
CEMT SET TRDUMPCODE 207 START
shutdown, CICS CEBT INQUIRE AUXTRACE 21
CEBT 25 CEBT INQUIRE GTFTRACE 23
CEMT 158 CEBT INQUIRE INTTRACE 23
SHUTOPTION CEBT SET AUXTRACE 27
CEMT INQUIRE SYDUMPCODE 115 CEBT SET GTFTRACE 28
CEMT INQUIRE TRDUMPCODE 137 CEBT SET INTTRACE 29
SIGN CEMT INQUIRE AUXTRACE 56
CEMT INQUIRE DB2ENTRY 68 CEMT INQUIRE GTFTRACE 89
CEMT SET DB2CONN 168 CEMT INQUIRE INTTRACE 90
CEMT SET DB2ENTRY 172 CEMT SET AUXTRACE 162
sign-off, CESF CEMT SET GTFTRACE 184
fixed-format terminal 215 CEMT SET INTTRACE 184
SIGNID STARTCODE
CEMT INQUIRE DB2CONN 63, 65 CEMT INQUIRE TASK 122
CEMT SET DB2CONN 170 STARTING
signon, CESN CEMT INQUIRE UOWLINK 152
3270 screen 217 starting a transaction 1
non-3270 screen 218

STATE Subdefining
CEMT INQUIRE ENQ 81 resource groups 47
CEMT INQUIRE UOWENQ 150 SUBORDINATE
STATIC CEMT INQUIRE UOWLINK 152
CEMT INQUIRE DSNAME 76 subsystem message-switching 233
STATISTICS SUBSYSTEMID
CEMT INQUIRE STATISTICS 112 CEMT INQUIRE MONITOR 98
CEMT INQUIRE transaction 111 supervisory terminal operator
CEMT PERFORM 159 duties 3
CEMT SET transaction 194 identifying terminals 3
STATS SUPRID option 3
CEMT PERFORM STATISTICS 160 transaction CEST 219
STATSQUEUE SURVEILLANCE
CEMT INQUIRE DB2CONN 66 CEBT transaction 24, 29
CEMT SET DB2CONN 170 SUSPENDED
STATUS CEMT INQUIRE TASK 122
CEMT INQUIRE AUXTRACE 56 SWITCH
CEMT INQUIRE JOURNALNAME 93 CEBT INQUIRE AUXTRACE 22
CEMT INQUIRE MONITOR 98 CEBT INQUIRE DUMP 22
CEMT INQUIRE PROGRAM 109 CEBT SET AUXTRACE 27
CEMT INQUIRE STREAMNAME 113 CEBT SET DUMP 28
CEMT INQUIRE TRANSACTION 135 CEMT INQUIRE AUXTRACE 56
CEMT SET TCPIP 201 CEMT INQUIRE DUMPDS 79
CEMT SET TCPIPSERVICE 202 CEMT SET AUXTRACE 162
hardcopy terminal 257 CEMT SET DUMPDS 179
indicator 241 SWITCHACTION
STGFRZ CEMT INQUIRE AUXTRACE 56
CSFE 250 SWITCHSTATUS
STOP CEMT INQUIRE AUXTRACE 56
CEBT INQUIRE AUXTRACE 22 CEMT INQUIRE DUMPDS 79
CEBT SET AUXTRACE 27 SYDUMPCODE
CEBT SET GTFTRACE 28 CEMT INQUIRE SYDUMPCODE 115
CEBT SET INTTRACE 29 CEMT SET transaction 196
CEMT INQUIRE AUXTRACE 56 CEMT transaction 114
CEMT SET AUXTRACE 162 SYNCPOINT
CEMT SET GTFTRACE 184 CEMT INQUIRE MONITOR 98
CEMT SET INTTRACE 184 CEMT SET MONITOR 189
STOPPED SYNCPOINTST
CEBT INQUIRE GTFTRACE 23 CEMT INQUIRE MONITOR 98
CEBT INQUIRE INTTRACE 23 syntax notation 2
CEMT INQUIRE GTFTRACE 89 SYSDUMP
CEMT INQUIRE INTTRACE 90 CEMT INQUIRE SYDUMPCODE 115
STORAGE CEMT INQUIRE TRDUMPCODE 137
CEMT PERFORM STATISTICS 160 CEMT PERFORM STATISTICS 160
storage freeze, CSFE 250 CEMT SET SYDUMPCODE 197
storage subpool 250 CEMT SET SYSTEM 199
storage violation trap 250 CEMT SET TRDUMPCODE 207
STOREPROTECT SYSDUMPING
CEMT INQUIRE SYSTEM 118 CEMT INQUIRE SYDUMPCODE 115
STREAMNAME CEMT INQUIRE TRDUMPCODE 137
CEMT INQUIRE JMODEL 92 SYSID
CEMT INQUIRE STREAMNAME 113 CEDF 41
CEMT PERFORM STATISTICS 160 CEMT INQUIRE TSQUEUE 141
CEMT transaction 113 CEMT INQUIRE UOW 143
STREAMNAME(VALUE) CEMT INQUIRE UOWDSNFAIL 148
CEMT INQUIRE JOURNALNAME 94 CEMT INQUIRE UOWLINK 152
Index 289
SYSID (continued) TCBLIMIT
CEMT SET TSQUEUE 208 CEMT INQUIRE DB2CONN 66
CRTE transaction 247 CEMT SET DB2CONN 170
SYSLOG TCBs
CEMT INQUIRE STREAMNAME 113 CEMT INQUIRE DB2CONN 66
SYSTEM TCLASS
CEMT INQUIRE transaction 116 CEMT DISCARD 52
CEMT SET transaction 198 CEMT INQUIRE TASK 120
system spooling interface trace 249 CEMT INQUIRE TCLASS 123
SYSTEMLOG CEMT INQUIRE transaction 123, 135
CEMT INQUIRE STREAMNAME 113 CEMT PERFORM STATISTICS 160
CEMT SET transaction 201, 206
TCP/IP services, CEMT requests 124
T TCPIP
tab key 48 CEMT INQUIRE transaction 124
TABLE CEMT SET transaction 201
CEMT INQUIRE FILE 88 TCPIP, CEMT requests 202
TABLEMGR TCpipservice
CEMT PERFORM STATISTICS 160 CEDA 37
TABLENAME CEMT DISCARD 52
CEMT INQUIRE FILE 88 CEMT INQUIRE transaction 124
CEMT SET FILE 183 CEMT PERFORM STATISTICS 160
TAKEOVER CEMT SET transaction 202
CEBT 24 TDQ
CEBT transaction 26, 30 CEMT INQUIRE ENQ 82
CEMT PERFORM SHUTDOWN 158 CEMT INQUIRE UOWENQ 150
TASK TDQUEUE
CEMT INQUIRE DB2CONN 63 CEDA 37
CEMT INQUIRE DB2ENTRY 67 CEMT DISCARD 52
CEMT INQUIRE EXCI 84 CEMT INQUIRE TDQUEUE 127
CEMT INQUIRE NETNAME 101 CEMT INQUIRE transaction 126
CEMT INQUIRE TASK 121, 122 CEMT PERFORM STATISTICS 160
CEMT INQUIRE TERMINAL 132 CEMT SET transaction 203
CEMT SET DB2CONN 167 TEMPLATENAME
CEMT SET DB2ENTRY 172 CEMT INQUIRE DOCTEMPLATE 72
CEMT SET transaction 200 TEMPLATETYPE
task associated trap 250 CEMT INQUIRE DOCTEMPLATE 72
TASK command temporary storage browse transaction, CEBR 19
CEMT INQUIRE transaction 119 TER
TASKDATAKEY CEOT 213
CEMT INQUIRE TRANSACTION 135 TERM
TASKDATALOC CEMT INQUIRE DB2CONN 64
CEMT INQUIRE TRANSACTION 135 CEMT INQUIRE DB2ENTRY 68
TASKID CEMT INQUIRE TASK 121
CEMT INQUIRE ENQ 81 CEMT SET DB2CONN 168
CEMT INQUIRE UOW 143 CEMT SET DB2ENTRY 173
CEMT INQUIRE UOWENQ 150 TERMID
TASKREQ CEDF 41
CSFE 250 CEMT INQUIRE TDQUEUE 127
tasks CEMT INQUIRE UOW 144
CEMT INQUIRE requests 119 CMSG 237
CEMT SET requests 200 CSFE ZCQTRACE 249
TCAM devices TERMID GT 4 CHAR AT XXXXX
Neg(poll) 95 CMSG 244
TCB TERMID NOT +/− AT xxxxx
CEMT INQUIRE TASK 122 CMSG 244

TERMID/OPID THREADS (continued)
CMSG 237 CEMT INQUIRE DB2ENTRY 69
TERMID*LDC THREADSAFE
CMSG 239 CEMT INQUIRE PROGRAM 107
TERMINAL THREADWAIT
CEDA 37 CEMT INQUIRE DB2CONN 66
CEMT DISCARD 52 CEMT INQUIRE DB2ENTRY 69
CEMT INQUIRE NETNAME 101 CEMT SET DB2CONN 170
CEMT INQUIRE TERMINAL 132 CEMT SET DB2ENTRY 173
CEMT INQUIRE transaction 129 TIME
CEMT PERFORM STATISTICS 160 CEMT INQUIRE MONITOR 98
CEMT SET transaction 204 CEMT INQUIRE SYSTEM 119
terminal and system test transaction, CSFE 249 CEMT SET SYSTEM 200
terminal builder trace 249 CMSG 238
terminal list table (TLT) 3 TIME ALREADY PASSED
terminal operator CMSG 244
duties 3 TIME INVALID AT XXXXX
master 4 CMSG 244
paging 253 TIME NOT 4 CHARS AT XXXXX
supervisory 3 CMSG 244
transactions 2 time-of-day resetting 157
write to console operator (CWTO) 259 TIMEOUTINT
terminals CEMT INQUIRE WEB 154
3270 displays 233 CEMT SET WEB 211
3767 keyboard/printer 233 TITLE
autopaging 257 CEMT PERFORM DUMP 156
CEMT INQUIRE requests 129 TLT (terminal list table) 3
CEMT SET requests 204 TO
console as a CICS terminal 5 CEDA 37
fixed-format 215 CEMT INQUIRE TASK 122
identifying 3 TOO MANY TBL SFX AT XXXXX
message-switching transaction 233 CMSG 244
paging 5, 253 TP
sequential 233 CEMT INQUIRE TASK 122
status 213 TPNAME
test 249 CEMT INQUIRE PARTNER 103
terminate a logical message 5, 256 TPOOL
TERMINATED BY OPERATOR CEMT INQUIRE DB2ENTRY 69
CMSG 244 CEMT SET DB2ENTRY 173
TERMLIST TRA
CMSG 237 CEOT 213
TERMLIST*LDC trace control transaction 221
CMSG 239 trace program exit routine 251
TERMSTATUS TRANCLASS
CEMT INQUIRE NETNAME 101 CEDA 37
CEMT INQUIRE TERMINAL 132 TRANDUMP
testing a terminal 249 CEMT INQUIRE TRDUMPCODE 137
THREADERROR CEMT SET TRDUMPCODE 207
CEMT INQUIRE DB2CONN 66 TRANDUMPING
THREADLIMIT CEMT INQUIRE TRDUMPCODE 137
CEMT INQUIRE DB2CONN 66 TRANID
CEMT INQUIRE DB2ENTRY 69 CEDX 43
CEMT SET DB2CONN 170 CEMT INQUIRE TASK 122
CEMT SET DB2ENTRY 173 CEMT INQUIRE TDQUEUE 127
THREADS CSFE 250
Index 291
TRANISOLATE TRANSID option
CEMT INQUIRE SYSTEM 119 CEMT INQUIRE REQUESTMODEL command 110
TRANSACTION TRAP
CEDA 37 CSFE DEBUG 251
CEMT DISCARD 52 trap program exit routine 251
CEMT INQUIRE NETNAME 101 traps
CEMT INQUIRE TERMINAL 132 storage violation 250
CEMT INQUIRE transaction 133, 135 task associated 250
CEMT PERFORM STATISTICS 160 TRDUMP
CEMT SET transaction 206 CEMT PERFORM STATISTICS 160
transaction routing, CRTE 247 TRDUMPCODE
transaction, BTS browser 9 CEMT INQUIRE transaction 136
transaction, in-doubt test tool 227 CEMT INQUIRE TRDUMPCODE 137
transaction, trace control 221 CEMT SET transaction 207
transactions TRIGGERLEVEL
all (list) 263 CEMT INQUIRE TDQUEUE 128
canceling 1 CEMT SET TDQUEUE 203
CBAM 9 TRPROF
CEBT 21 CEMT INQUIRE TRANSACTION 135
CECI 31 CRTE transaction 247
CECS 31, 32 TSMODEL
CEDA 33 CEDA 37
CEDB 33 CEMT DISCARD 52
CEDC 33 CEMT INQUIRE transaction 138
CEDF 41 CEMT INQUIRE TSMODEL 139
CEMT 45 TSO console as a CICS terminal 7
CEOT 213 TSPOOL
CESN 217 CEMT INQUIRE transaction 139
CEST 219 CEMT INQUIRE TSPOOL 140
CMSG 231 TSQ
CRTE 247 CEMT INQUIRE ENQ 82
CSFE 249 CEMT INQUIRE UOWENQ 150
CSPG 253 TSQNAME
CWTO 259 CEMT INQUIRE transaction 140
DSNC 261 TSQUEUE
identification codes 3 CEMT INQUIRE transaction 140
initiating from console 6 CEMT INQUIRE TSQUEUE 142
invocation of 1 CEMT PERFORM STATISTICS 160
security key 3 CEMT SET transaction 208
transactions with operator interface 263 CEMT SET TSQUEUE 208
transactions with operator interface TTI
CBAM 9 CEMT INQUIRE NETNAME 101
CDBC 11 CEMT INQUIRE TERMINAL 132
CDBI 13 CEMT SET NETNAME 191
CDBM 15 CEMT SET TERMINAL 205
CESF 215 CEOT 213, 214
CETR 221 TTISTATUS
CMAC 229 CEMT INQUIRE NETNAME 101
TRANSID CEMT INQUIRE TERMINAL 132
CEMT INQUIRE DB2TRAN 70 TTTT
CEMT INQUIRE ENQ 81 CSPG 257
CEMT INQUIRE TSQUEUE 142 TWAIT
CEMT INQUIRE UOW 144 CEMT INQUIRE DB2CONN 66
CEMT INQUIRE UOWENQ 150 CEMT INQUIRE DB2ENTRY 69
CEMT SET DB2TRAN 174 CEMT SET DB2CONN 170

TX UNQUIESCED (continued)
CEMT INQUIRE DB2CONN 64 CEMT SET DSNAME 178
CEMT INQUIRE DB2ENTRY 68 UNREGISTERED
CEMT SET DB2CONN 168 CEMT INQUIRE VTAM 153
CEMT SET DB2ENTRY 173 UNSUP OPRT TRMNL XXXXXXXX
TXID CMSG 245
CEMT INQUIRE DB2CONN 63 UNSUP TERMINAL XXXXXXXX
CEMT INQUIRE DB2ENTRY 67 CMSG 245
CEMT SET DB2CONN 167 UOW
CEMT SET DB2ENTRY 172 CEMT INQUIRE DB2CONN 63
TYPE CEMT INQUIRE DB2ENTRY 67
CEMT INQUIRE ENQ 81 CEMT INQUIRE ENQ 82
CEMT INQUIRE JMODEL 92 CEMT INQUIRE TASK 122
CEMT INQUIRE JOURNALNAME 94 CEMT INQUIRE UOW 144
CEMT INQUIRE TDQUEUE 128 CEMT INQUIRE UOWDSNFAIL 148
CEMT INQUIRE UOWENQ 150 CEMT INQUIRE UOWENQ 150
CEMT INQUIRE UOWLINK 152 CEMT INQUIRE UOWLINK 152
TYPE attribute CEMT SET DB2CONN 167
CEMT INQUIRE DOCTEMPLATE 72 CEMT SET transaction 209
TYPETERM CEMT transaction 142
CEDA 37 UOWACTION
U UOWDSNFAIL
U CEMT INQUIRE transaction 145
CEMT INQUIRE TASK 122 CEMT INQUIRE UOWDSNFAIL 148
UDATAKEY UOWENQ
CEMT INQUIRE TRANSACTION 135 CEMT transaction 148
UDSASIZE UOWLINK
CEMT INQUIRE DSAS 73 CEMT INQUIRE transaction 151
UEXECKEY CEMT INQUIRE UOWLINK 152
CEMT INQUIRE PROGRAM 108 CEMT SET transaction 209
UKOPEN UOWSTATE
CEMT INQUIRE TASK 122 CEMT INQUIRE UOW 144
UNATTEMPTED UPDATE
CEMT INQUIRE CONNECTION 60 CEMT INQUIRE FILE 89
UNAVAILABLE CEMT SET FILE 183
CEMT INQUIRE DSNAME 77 UPDATEMODEL
CEMT INQUIRE UOWLINK 152 INQUIRE FILE command 89
CEMT INQUIRE VTAM 153 UPDATESTATUS
CEMT SET DSNAME 178 CEMT INQUIRE FILE 89
UNBALANCD PARENS AT XXXXX uppercase input to transactions 2
CMSG 244 URID
UNCONNECTED CEMT INQUIRE EXCI 84
CEMT INQUIRE TSPOOL 140 CEMT INQUIRE UOWLINK 152
CEMT INQUIRE UOWLINK 152 URM
UNDEFINED CEMT SET TCPIPSERVICE 202
CEMT INQUIRE UOWDSNFAIL 146 USECOUNT
UNDETERMINED CEMT INQUIRE PROGRAM 109
CEMT INQUIRE DSNAME 76 CEMT INQUIRE STREAMNAME 113
UNENABLED user storage, checking 250
CEMT INQUIRE FILE 87 USERID
UNKNOWN CEMT INQUIRE DB2CONN 64
CEMT INQUIRE UOWLINK 152 CEMT INQUIRE DB2ENTRY 68
UNQUIESCED CEMT INQUIRE NETNAME 102
CEMT INQUIRE DSNAME 78 CEMT INQUIRE TASK 122
Index 293
USERID (continued) value (continued)
CEMT INQUIRE TDQUEUE 128 CEMT SET UOW 209
CEMT INQUIRE TERMINAL 132 CEMT SET UOWLINK 209
CEMT INQUIRE UOW 144 values
CEMT SET DB2CONN 168 hexadecimal 48
CEMT SET DB2ENTRY 173 VSAM
CESN 218 CEMT INQUIRE DSNAME 75
USERTABLE CEMT INQUIRE FILE 86
CEMT INQUIRE FILE 88 VTAM
CEMT SET FILE 183 CEMT INQUIRE CONNECTION 59
CEMT INQUIRE transaction 153
CEMT INQUIRE VTAM 154
V CEMT PERFORM STATISTICS 160
VALID CEMT SET transaction 210
CEMT INQUIRE DSNAME 76 VTAM ACB (access control block) 153, 210
VALIDITY VTAM terminals, acquiring 190, 204
value
CEMT INQUIRE CONNECTION 58 W
CEMT INQUIRE DSNAME 74 WAIT
CEMT INQUIRE FILE 85 CEMT INQUIRE TASK 121
CEMT INQUIRE MODENAME 95 CEMT INQUIRE TDQUEUE 128
CEMT INQUIRE NETNAME 99 CEMT INQUIRE TRANSACTION 134
CEMT INQUIRE PARTNER 102 WAITCAUSE
CEMT INQUIRE PROFILE 105 CEMT INQUIRE UOW 144
CEMT INQUIRE PROGRAM 106 WAITCOMMIT
CEMT INQUIRE STREAMNAME 113 CEMT INQUIRE UOW 144
CEMT INQUIRE SYDUMPCODE 114 WAITER
CEMT INQUIRE TASK 120 CEMT INQUIRE ENQ 81
CEMT INQUIRE TCLASS 123 CEMT INQUIRE UOWENQ 149
CEMT INQUIRE TDQUEUE 126 WAITFORGET
CEMT INQUIRE TERMINAL 129 CEMT INQUIRE UOW 144
CEMT INQUIRE TRANSACTION 133 WAITING
CEMT INQUIRE TRDUMPCODE 136 CEMT INQUIRE ENQMODEL 83
CEMT INQUIRE TSMODEL 138 CEMT INQUIRE UOW 144
CEMT INQUIRE TSPOOL 139 WAITRMI
CEMT INQUIRE TSQUEUE 141 CEMT INQUIRE UOW 144
CEMT INQUIRE UOW 143 WAITSTATE
CEMT INQUIRE UOWLINK 151 CEMT INQUIRE UOW 144
CEMT SET CONNECTION 163 Web support 211
CEMT SET DSNAME 177 CEMT INQUIRE transaction 154
CEMT SET ENQMODEL 179 CEMT SET transaction 211
CEMT SET FILE 181 Web support inquiry 154
CEMT SET JOURNALNAME 186 write to console operator (CWTO) 259
CEMT SET LINE 186
CEMT SET MODENAME 187
CEMT SET NETNAME 190 X
CEMT SET PROGRAM 192 XCF
CEMT SET SYDUMPCODE 196 CEMT INQUIRE CONNECTION 59
CEMT SET TASK 200 XLNSTATUS
CEMT SET TCLASS 201 CEMT INQUIRE CONNECTION 62
CEMT SET TDQUEUE 203 XLT
CEMT SET TERMINAL 204 CEMT PERFORM SHUTDOWN 158
CEMT SET TRANSACTION 206 XM
CEMT SET TRDUMPCODE 207 CEMT INQUIRE CONNECTION 59
CEMT SET TSQUEUE 208

XNOTDONE
XOK
XRF and the CEBT transaction 21
Y
YES
CMSG 236
YY.DDD
CMSG 234
YYYY
CSPG 255
YYYY.DDD
CMSG 235
Z
ZERO LENGTH MSG AT ''
CMSG 245
Index 295
Sending your comments to IBM
If you especially like or dislike anything about this book, please use one of the methods listed below to send your comments to
IBM.
Feel free to comment on what you regard as specific errors or omissions, and on the accuracy, organization, subject matter, or
completeness of this book.
Please limit your comments to the information in this book and the way in which the information is presented.
To request additional publications, or to ask questions or make comments about the functions of IBM products or systems, you
should talk to your IBM representative or to your IBM authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it
believes appropriate, without incurring any obligation to you.
You can send your comments to IBM in any of the following ways:
By mail, to this address:
Information Development Department (MP095)
IBM United Kingdom Laboratories
Hursley Park
WINCHESTER,
Hampshire
SO21 2JN
United Kingdom
By fax:
– From outside the U.K., after your international access code use 44–1962–870229
– From within the U.K., use 01962–870229
Electronically, use the appropriate network ID:
– IBM Mail Exchange: GBIBM2Q9 at IBMMAIL
– IBMLink: HURSLEY(IDRCF)
– Internet: idrcf@hursley.ibm.com
Whichever you use, ensure that you include:

The publication number and title
The topic to which your comment applies
Your name and address/telephone number/fax number/network ID.

IBM 
Program Number: 5655-147
Printed in the United States of America

on recycled paper containing 10%
recovered post-consumer fiber.
SC33-1686-ð2
Spine information:
IBM CICS TS for OS/390 CICS Supplied Transactions Release 3

CICS Supplied Transaction

Uploaded by

Copyright:

Available Formats

CICS Supplied Transaction

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CICS Supplied Transaction

Uploaded by

Copyright:

Available Formats

CICS Transaction Server for OS/390 IBM

CICS Supplied Transactions

Third edition (March 1999)

IBM United Kingdom Laboratories, Information Development,

Chapter 1. Transactions supplied by CICS . . . . . . . . . . . . . . . . . . . . . . . 1

| Chapter 2. CBAM—BTS browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 3. CDBC—database control menu . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 4. CDBI—database control inquiry . . . . . . . . . . . . . . . . . . . . . 13

Chapter 5. CDBM—database control interface . . . . . . . . . . . . . . . . . . . . 15

Chapter 6. CEBR—temporary storage browse . . . . . . . . . . . . . . . . . . . . 19

Chapter 7. CEBT—master terminal (alternate CICS) . . . . . . . . . . . . . . . . . 21

 Copyright IBM Corp. 1982, 1999 iii

Chapter 8. CECI—command-level interpreter . . . . . . . . . . . . . . . . . . . . 31

Chapter 9. CEDA—resource definition online . . . . . . . . . . . . . . . . . . . . 33

Chapter 10. CEDF & CEDX — the execution diagnostic facility . . . . . . . . . . 41

Chapter 11. CEMT—master terminal . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 12. CEOT—terminal status . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Chapter 13. CESF—sign off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Chapter 14. CESN—sign on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Chapter 15. CEST—supervisory terminal . . . . . . . . . . . . . . . . . . . . . . . 219

Chapter 16. CETR—trace control . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Chapter 17. CIND—in-doubt testing tool . . . . . . . . . . . . . . . . . . . . . . . 227

Chapter 18. CMAC—messages and codes display . . . . . . . . . . . . . . . . . 229

Chapter 19. CMSG—message switching . . . . . . . . . . . . . . . . . . . . . . . 231

Chapter 20. CRTE—remote transactions . . . . . . . . . . . . . . . . . . . . . . . 247

iv CICS Supplied Transactions

Chapter 22. CSPG—page retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Chapter 23. CWTO—write to console operator . . . . . . . . . . . . . . . . . . . 259

Chapter 24. DSNC—CICS DB2 transaction DSNC . . . . . . . . . . . . . . . . . . 261

Appendix. List of CICS transactions . . . . . . . . . . . . . . . . . . . . . . . . . 263

Sending your comments to IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

IBM Director of Licensing

IBM World Trade Asia Corporation

 Copyright IBM Corp. 1982, 1999 vii

viii CICS Supplied Transactions

What this book is about

Who should read this book

What you need to know to understand this book

How to use this book

Transaction CICS book

Front end programming interface

 Copyright IBM Corp. 1982, 1999 ix

x CICS Supplied Transactions

CICS Transaction Server for OS/390

CICS books for CICS Transaction Server for OS/390

 Copyright IBM Corp. 1982, 1999 xi

Other CICS books

Books from related libraries

Determining if a publication is current

xii CICS Supplied Transactions

| Changes for this edition

 Copyright IBM Corp. 1982, 1999 xv

Changes for the CICS/ESA 4.1 edition

For CICS/ESA 4.1, the following changes have been made:

xvi CICS Supplied Transactions

Chapter 1. Transactions supplied by CICS

Function Name Page How to start or stop a transaction

If you use an IBM 3270 system display or similar display

 Copyright IBM Corp. 1982, 1999 1

Syntax notation and conventions used in Uppercase input to transactions

Type the identifier, CDBC, on the command line of your