IBM SC33-1686-02 User Manual

Download

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.

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 CDBC CDBI CEBR CECI CECS CEDA CEDF CETR CRTE CSFE DSNC

CICS Business Transaction Services CICS IMS Database Control Guide CICS IMS Database Control Guide CICS Application Programming Guide CICS Application Programming Guide CICS Application Programming Guide CICS Resource Definition Guide CICS Application Programming Guide CICS Problem Determination Guide CICS RACF Security Guide CICS Problem Determination Guide 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 CICS Transaction Server for OS/390 Release Guide CICS Transaction Server for OS/390 Migration Guide CICS Transaction Server for OS/390 Installation Guide CICS Transaction Server for OS/390 Program Directory CICS Transaction Server for OS/390 Licensed Program Specification

CICS books for CICS Transaction Server for OS/390

General

CICS Master Index CICS User's Handbook CICS Transaction Server for OS/390 Glossary

Administration

CICS System Definition Guide CICS Customization Guide CICS Resource Definition Guide CICS Operations and Utilities Guide CICS Supplied Transactions

Programming

CICS Application Programming Guide CICS Application Programming Reference CICS System Programming Reference CICS Front End Programming Interface User's Guide CICS C++ OO Class Libraries CICS Distributed Transaction Programming Guide CICS Business Transaction Services

Diagnosis

CICS Problem Determination Guide CICS Messages and Codes CICS Diagnosis Reference CICS Data Areas CICS Trace Entries CICS Supplementary Data Areas

Communication

CICS Intercommunication Guide CICS Family: Interproduct Communication CICS Family: Communicating from CICS on System/390 CICS External Interfaces Guide CICS Internet Guide

Special topics

CICS Recovery and Restart Guide CICS Performance Guide CICS IMS Database Control Guide CICS RACF Security Guide CICS Shared Data Tables Guide CICS Transaction Affinities Utility Guide CICS DB2 Guide

GC33-1789 GC34-5352 GC34-5353 GC33-1681 GI10-2506 GC33-1707

SC33-1704 SX33-6104

(softcopy only) GC33-1705

SC33-1682 SC33-1683 SC33-1684 SC33-1685 SC33-1686

SC33-1687 SC33-1688 SC33-1689 SC33-1692 SC34-5455 SC33-1691 SC34-5268

GC33-1693 GC33-1694 LY33-6088 LY33-6089 SC34-5446 LY33-6090

SC33-1695 SC33-0824 SC33-1697 SC33-1944 SC34-5445

SC33-1698 SC33-1699 SC33-1700 SC33-1701 SC33-1702 SC33-1777 SC33-1939

 Copyright IBM Corp. 1982, 1999

CICSPlex SM books for CICS Transaction Server for OS/390

General

CICSPlex SM Master Index CICSPlex SM Concepts and Planning CICSPlex SM User Interface Guide CICSPlex SM View Commands Reference Summary

Administration and Management

CICSPlex SM Administration CICSPlex SM Operations Views Reference CICSPlex SM Monitor Views Reference CICSPlex SM Managing Workloads CICSPlex SM Managing Resource Usage CICSPlex SM Managing Business Applications

Programming

CICSPlex SM Application Programming Guide CICSPlex SM Application Programming Reference

Diagnosis

CICSPlex SM Resource Tables Reference CICSPlex SM Messages and Codes CICSPlex SM Problem Determination

Other CICS books

CICS Application Programming Primer (VS COBOL II) CICS Application Migration Aid Guide CICS Family: API Structure CICS Family: Client/Server Programming CICS Family: General Information CICS 4.1 Sample Applications Guide CICS/ESA 3.3 XRF Guide

SC33-1812 GC33-0786 SC33-0788 SX33-6099

SC34-5401 SC33-0789 SC34-5402 SC33-1807 SC33-1808 SC33-1809

SC34-5457 SC34-5458

SC33-1220 GC33-0790 GC33-0791

SC33-0674 SC33-0768 SC33-1007 SC33-1435 GC33-0155 SC33-1173 SC33-0661

If you have any questions about the CICS Transaction Server for OS/390 library, see

Transaction Server for OS/390: Planning for Installation

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



Resource Access Control Facility (RACF): Security Administrator’s Guide



IMS Utilities Reference manual



IMS Messages and Codes manual



IMS System Administration Guide



IMS Operations Guide



An Introduction to the IBM 3270 Information Display System



Systems Network Architecture—LU6.2 Reference: Peer Protocols



MVS/DFP 3.2 System Programming Reference



OS/390 MVS Diagnosis: Tools and Service Aids



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.

CICS

which discusses both hardcopy and

, GC28-1781

, SC28-1340

, SC26-4284

, SC26-4290

, SC26-4278

, SC26-4287

, GA27-2739

, SC31-6808

manual, SC26-4567

, SY28-1085

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

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.

CD-ROM, SK2T-0730-xx. Each reissue of

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

| also added to CEMT are the following: | – INQUIRE CFDTPOOL

| 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 (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.

CICS-Supplied Transactions

Changes for the CICS/ESA 4.1 edition

This edition is based on the CICS/ESA 3.3 (SC33-0669-02).

CICS-Supplied Transactions

manual

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 tables, programs, and internal services. This book deals with those transactions that are supplied by CICS and which, in addition, have an operator interface.

CICS transactions have identification codes that start with “C” and are 4 characters long; for example, CEMT.

The following table shows the transactions that are described in this book. For a more complete list of CICS transactions, including those that do not have an operator interface, see the Appendix, “List of CICS transactions” on page 263.

Function Name Page

| CICS business transaction

| CBAM| 9 | services (BTS) browser

Command-level interpreter CECI,

CECS Database control inquiry CDBI 13 Database control interface CDBM 15 Database control menu CDBC 11 Execution diagnostic facility CEDF 41

CEDX 41 In-doubt testing tool CIND 227 Master terminal CEMT 45 Master terminal (alternate CICS) CEBT 21 Messages and codes display CMAC 229 Message switching CMSG 231 Page retrieval CSPG 253 Remote transactions CRTE 247 Resource definition online (RDO)

Sign off CESF 215 Sign on CESN 217 Supervisory terminal CEST 219 Temporary-storage browse CEBR 19 Terminal status CEOT 213 Trace control CETR 221 Terminal and system test CSFE 249 Write to console operator CWTO 259

CEDA,

CEDB,

CEDC

In general, you start a CICS transaction by entering its transaction identifier (for example, CEMT). The transaction identifier is used by CICS to identify the programs that handle the specified transactions, and to establish a task to process them.

Upgrading CICS transactions

You may wish to apply a CICS-supplied upgrade, but are using modified versions of one or more CICS-supplied transactions or of the CICS-supplied calling programs that handle CICS-supplied transactions. After you have first copied them to differently named groups, you must replace these private versions from the upgraded CICS-supplied version and modify them afresh to ensure that the necessary upgrade changes are carried out. Failure to do this can lead to unpredictable results.

How to start or stop a transaction

You start a CICS transaction by pressing the CLEAR key to clear the screen, and entering the transaction identifier, either by itself or followed by data, on the command line of the screen. The command line is a single line, usually at the top of the screen.

You can type the transaction identifier by itself and follow the prompts until a complete transaction command is built up, or you can type the complete transaction command on the command line. If you do not enter enough information, or if the information you enter is wrong, you are prompted to complete or correct your input.

For example, in the following transaction, CEMT is the transaction identifier and the additional data is INQUIRE PROGRAM(PROG1).

CEMT INQUIRE PROGRAM(PROG1)

When the transaction starts, it processes the additional data. At the completion of this transaction, you get the following message:

STATUS: SESSION ENDED

After a transaction has completed, press the CLEAR key to clear the screen in readiness for the next transaction. You can cancel any request by typing CANCEL on the command line.

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

introduction

Syntax notation and conventions used in this book

Each command has a syntax box to show you what options there are.

You interpret the syntax by following the arrows from left to right. The conventions are:

Symbol Action

─ ──┬ ┬─A─ ──── ├┤─B─ └┘─C─

┌ ┐───────



─ ─── ├┤─B─ └┘─C─

─ ──┬ ┬─── ──── ├┤─A─ ├┤─B─ └┘─C─

┌ ┐─────── ─ ─── ├┤─A─ ├┤─B─ └┘─C─

┌┐─A─ ─ ──┼ ┼─── ──── └┘─B─

──┤ Name ├──

Name:

├─ ──A ──┬ ┬─── ───┤ └┘─B─

Punctuation and uppercase characters

Lowercase characters

┴┬┬─A─ ──



┴┬┬─── ──

A set of alternatives—one of which you

must

code.

A set of alternatives—one of which you

must

code. You

one of them, in any sequence.

A set of alternatives—one of which you

may

code.

A set of alternatives — any number (including none) of which you may code once, in any sequence.

Alternatives where A is the default.

Use with the named section in place of its name.

Code exactly as shown.

Code your own text, as appropriate (for example, name).

may

code more than

Minimum abbreviation of keywords

In general, the CICS transactions accept as few characters of a keyword as needed to identify it within the request. For example, in a CEMT INQUIRE TASK command, you could use TASK, TAS, or TA to uniquely identify TASK. T alone, however, could be confused with TCLASS, TERMINAL, TRACE, or TRANSACTION.

In the syntax displays on your screen (unless your terminal is uppercase only), and in most cases in this book, the minimum permitted abbreviation is given in uppercase characters, the remainder in lowercase.

Uppercase input to transactions

In general, most CICS-supplied transactions accept only uppercase input. If UCTRAN=YES has been specified in the terminal definition, all lowercase characters, even those enclosed within single quotation marks, are translated to uppercase.

If you have to specify UCTRAN=NO for your terminal, you have to ensure that the group specified for your terminal refers to a profile that will carry out uppercase translation.

CICS provides a PROFILE definition, DFHCICSP, in the DFHSTAND group in the CICS system definition (CSD) file. This profile is identical to DFHCICST except that it specifies UCTRAN(YES) instead of UCTRAN(NO).

The new profile is used by the CICS-supplied page retrieval transaction, CSPG. The new profile, together with changes in the task-attach routine and the page retrieval program, enables CICS to perform uppercase translation at the transaction level for BMS paging.

This allows users of terminals that are defined with uppercase translation switched off to use the page retrieval function without having to enter paging commands in upper case. Assigning a new profile for CSPG means that all data entered on the retrieval command (defined by the PGRET system initialization parameter) and the purge command (defined by the PGPURGE system initialization parameter) is translated to uppercase.

If a user’s terminal is defined with UCTRAN(YES), the new profile has no effect because all terminal input is translated to uppercase anyway.

Terminal operators

A CICS system makes provision for the following classes of operators:

terminal operator

 A

routine transactions that cause application programs to be processed. You can use a small selection of CICS transactions. For example, you can inquire about, or change, the status of your own terminal.

supervisory terminal operator

 A

duties of a terminal operator, in addition to supervising other operators within a functional group. Your operator security code gives you access to the supervisory terminal transaction, CEST, with which you can monitor and control some of the system resources used by your group.

master terminal operator

 A

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.

who can use a terminal to perform

who can perform all the

who can monitor and control

2 CICS Supplied Transactions

introduction

| $ (the dollar symbol) | In the character sets given in this book, the dollar symbol ($)

| is used as a national currency symbol and is assumed to be | assigned the EBCDIC code point X'5B'. In some countries a | different currency symbol, for example the pound symbol (£), | or the yen symbol (¥), is assigned the same EBCDIC code | point. In these countries, the appropriate currency symbol | should be used instead of the dollar symbol.

Operator security

The transactions you can initiate are defined by your profile in the external security manager (ESM) database, which is normally provided when you sign on using the CESN transaction.

Generally, the master terminal operator has access to all CICS-supplied transactions, the supervisory terminal operator has access to a subset, and the terminal operator has access to very few transactions.

The system programmer is responsible for allocating operator security codes to restrict the use of particular transactions. For more information, see the relevant system administration guide for the ESM you are using. For example, if you are using RACF, see the

(RACF): Security Administrator’s Guide

Resource Access Control Facility

Your responsibilities can be thought of as a subset of those of the master terminal operator, and you should be aware of those functions that are not available to the terminals under your supervision. You also should be aware of, and understand, the procedure for changing the status of each terminal.

You should know the identifiers of all terminals and operators 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 SUPRID and CLASS(value) keywords of the CEST transaction.

When you use the CEST command for in a TLT, you have to specify the SUPRID keyword followed by the 2-character identifier of that TLT.

A subset of those terminals can be grouped together as a

class

, and can be defined as such in a different TLT. (For

information about defining the TLT itself, see the

Resource Definition Guide

means of the CLASS(value) keyword of the CEST SET TERMINAL command, where ‘value’ is the suffix that identifies the TLT in which the class of terminals has been defined.

Alternatively, you can name one or more terminals in the CEST SET TERMINAL(value) command itself.

.) You can specify that class by

all

terminals defined

CICS

Terminal operator

To operate the system, you normally first sign on to the system and, as a minimum, enter your user ID and your password.

During signon, the information you enter is used by CICS to establish priorities and your ESM profile for the transactions that you may want to use later. When you have signed on, you have access to those transactions defined in your ESM profile.

After you have signed on, you can enter only specific transaction identifiers. Be aware of error messages that might be generated by the transactions you start, and the corrective action that you must take. In addition to error messages, be aware of other messages that CICS might transmit to your terminal.

You need to know the terminal identifiers of other terminals with which you want to communicate.

Supervisory terminal operator

A supervisory terminal operator is the supervisor of any part of the system for which group control is desired. You are 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.

If you frequently want to restrict a CEST command to a subset of your terminals, and have defined another TLT identifying that subset, you then have to use the CEST SET TERMINAL SUPRID(value) keyword to refer to the “main” TLT, followed by the CLASS(value) keyword to refer to the specific TLT containing the subset.

So, for example, if you have defined terminals S202, S203, S204, and S205 in DFHTLTAB and you want to issue a CEST command that sets you issue the following command:

CEST SET TERMINAL SUPRID(AB) OUTSERVICE

If, on the other hand, you want to restrict your command(s) to terminals S202 and S204, for example, you could define these two terminals in another TLT—DFHTLTCD, say—and issue the following command:

CEST SET TERMINAL SUPRID(AB) CLASS(CD) OUTSERVICE

Alternatively, of course, you could issue the following command:

CEST SET TERMINAL(S22,S24) SUPRID(AB) OUTSERVICE

Unless otherwise stated, the information in this book about the supervisory terminal and the CEST transaction applies only to a single CICS system, regardless of whether it is connected to another CICS system through ISC or MRO.

all

those terminals out of service,

Chapter 1. Transactions supplied by CICS 3

introduction

Master terminal operator

The master terminal operator controls system components using the master terminal transaction, CEMT. With this transaction, the master terminal operator can dynamically change the system control parameters.

Although the transaction can be started at any valid IBM 3270 family display device or equivalent terminal, or from the operating system console, its use is intended to be limited to a person known as the transaction from the operating system console is described in “The system console as a CICS terminal” on page 5.

The control permitted through CEMT allows you, the master terminal operator, to improve performance by changing the system control parameters in the day-to-day operation of the system. In addition to system control, you have prime responsibility for administering the terminal facilities of the system.

By using the routing transaction (CRTE), you can also be a master terminal operator for multiple connected CICS systems.

As the master terminal operator, you can access all terminal and supervisory terminal transactions. In addition, however, you must be familiar with all the procedures associated exclusively with the master terminal. You must be aware of which terminals and operators can access CICS at any given time, and of the identifiers by which they are known to CICS.

master terminal operator

. Starting a

When the system has satisfactorily completed its response to a command, the time and date are printed or displayed at your terminal, as follows:

TIME=hh.mm.ss DATE=mm.dd.yy

where time is in hours, minutes, and seconds, and date is in months, days, and years, or in the form specified by the DATFORM system initialization parameter. For brevity this final message has been deleted from all examples in the remainder of the book.

Unless otherwise stated, the information about the master terminal and its transactions given in this book applies only to a single CICS system, regardless of whether it is connected to another CICS system through ISC or MRO.

MRO and ISC support

Multiregion operation (MRO) and intersystem communication (ISC) allow the sharing of resources between more than one CICS region. Thus a user at a terminal assigned to one CICS region can run transactions in connected regions, and can access resources—files, for example—in other regions.

It is also possible for a transaction running in one region to communicate with a transaction running in another region, thus sharing the processing workload.

Except for experiencing longer response times, you should not be aware that MRO or ISC processes are being used.

For example, when inquiring about terminals, you can specify a class of terminals or a list of terminals. A class of terminals is specified by the CLASS(value) keyword, where ‘value’ is the 1-or 2-character suffix of the related terminal list table (DFHTLTxx). A list of terminals is specified by a series of terminal identifiers following the CEMT SET TERMINAL(t1,t2,...,) command, where t1, t2, are terminal identifiers. See “List of resource identifiers” on page 47 for more information.

For MRO and LUTYPE6.1 connections, you must know the identifier of each parallel session, and specify this identifier when operating on the session.

For LUTYPE6.2 (APPC) connections, you must know the modename of each set of parallel sessions, and specify this modename when operating on the modegroup.

Your use of the master terminal transaction is restricted by entries in the signon table and in the installed transaction definitions. These entries are the responsibility of the system programmer.

During long periods of continuous operation, you can, at intervals, read out and reset the statistics counters. The volume of activity in your system determines how often you should do this.

BMS partitions

When you use display devices that support BMS partitions, make sure that you understand:

 How to use the SCROLL, PARTITION JUMP, CLEAR,

and CLEAR PARTITION keys

 The concept of the active partition  The meanings of the partition-related indicator symbols

that can appear on a display screen.

For information about BMS partitions, see the

Application Programming Guide

CICS

CLEAR key

The CLEAR key clears all partitions from the display, and sets the terminal to ‘base’ state. The next BMS output request recreates the partitions (but does not restore their contents), using the application partition set.

The CLEAR and CLEAR PARTITION keys cannot be used interchangeably when an existing CICS transaction is run in a single explicit partition.

4 CICS Supplied Transactions

introduction

Partitions and the execution diagnostic facility

The execution diagnostic facility (EDF), invoked by CEDF, is not available in single-screen mode on a terminal in partitioned state. EDF must be used in dual-screen mode for debugging application programs that use partitions.

Partitions and the command interpreter

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 restored after the screen has been partitioned.

PA1 print key

The PA1 print key is not supported from a terminal in partitioned state.

Routing and multiple partitions

Routed messages can be directed to a terminal, including the transaction terminal, which supports partitions. However, such messages reset the terminal to ‘base’ state.

Terminal paging

is redisplayed in each partition in the following circumstances:

 For the initial display when the BMS paging program is

first invoked

 Following erasure of the terminal partition set caused by

pressing the CLEAR key

 Following page retrieval for a different page-chaining

level

 Following page purge for a different page-chaining level.

Copying pages

BMS page copy operates on a partition basis (not a screen or partition set basis). BMS page copy copies a page from a partition to any terminal in ‘base’ state. You cannot copy a page from a partition to another partition on the same or another terminal.

Message termination

When you terminate a message, the entire logical message (that is, all pages in all partitions) is purged, irrespective of the partition in which you entered the purge command.

The response to a page query request is displayed on a cleared, unpartitioned screen.

When a BMS logical message is saved in CICS temporary storage, CICS also saves the application partition set. This partition set is loaded onto the target terminal before any pages are delivered. CICS builds a separate page for each partition, and overflow occurs on a partition basis.

Page retrieval

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 in that partition. If single-keystroke retrieval is used, the retrieval command applies to the partition containing the cursor when the PF key is pressed. The first page for a partition is displayed initially in the viewport.

Message chaining

CICS retains a current partition for each level of page chaining. This is initially the default partition for that partition set. Page-retrieval commands entered on a cleared screen, or page-retrieval commands for a chaining level other than the one being displayed, refer to the current partition for the target chaining level. The current partition is reset to the partition in which the last terminal-operator command was entered.

CICS retains the current page for each partition in the partition set. This is initially the first page. The current page

Error messages

Most error messages relating to invalid paging commands are displayed with an erase or write in the partition in which 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 screen.

The system console as a CICS terminal

Console support makes it possible for a terminal to be both an operating system console and a CICS master terminal.

If multiple console support (MCS) is in use, you can define each console to CICS as a separate terminal, and all consoles can communicate with CICS simultaneously.

You can use any operating system console as a CICS terminal if it has been specified as such on the CONSOLE keyword of the CEDA DEFINE TERMINAL command. If this has not been done, you get the following message when you try to use the console:

DFHAC215 This console has not been defined to CICS.

and your input is ignored. All consoles that have been defined as CICS terminals can

use automatic transaction initiation (ATI), and can receive

Chapter 1. Transactions supplied by CICS 5

introduction

messages from other terminals and consoles, as well as from CICS transactions.

In a system that has consoles and VTAM terminals, a console can remain active when CICS and VTAM are disconnected from each other. You can use the console to make or break the CICS-VTAM connection without CICS being terminated.

Use the MODIFY and REPLY commands to start the CICS-supplied transactions from an operating system console.

In addition to the MODIFY and REPLY commands, the system programmer should consider use of the CONTROL, DISPLAY, START, and VARY commands when preparing console operator procedures. For information on these commands and other system details, see the

System Commands

manual.

OS/390 MVS

Rules for console entry

Commands typed at a console are translated to uppercase, except for characters enclosed within single quotation marks (''), which remain unchanged. The occurrence of a literal single quotation mark must be indicated by a pair of single quotation marks (''), for example:

'Please phone Mr O''Neill'. If UCTRAN=YES has been specified in the terminal

definition, all lowercase characters, even those enclosed within single quotation marks, are translated to uppercase.

MODIFY command

You start a CICS transaction from a console by using the MODIFY command, as follows:

MODIFY ident,datastring

You can abbreviate the MODIFY command to F.

ident can be any of the following:

 The name of the job used to start CICS, when it is

started by a job stream.

 The name of the procedure used to start CICS, when it

is started by an MVS START command, for example:

START procedure_name

where “procedure_name” is the ident value.

 The task identifier that was used to qualify the procedure

name, for example:

START procedure_name.taskid

where “taskid” is the ident value. This is likely to be used where the same procedure is started more than once.

datastring is a string of data, starting with a CICS transaction identifier.

For example, to start transaction CEBT on the CICSA system from the console, type:

MODIFY CICSA,CEBT PERFORM TAKEOVER

You can type more than one MODIFY command at a 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

6 CICS Supplied Transactions

introduction

where nn is the number of the prompt to which you are replying, and datastring is your reply.

If a transaction is purged while it is awaiting a reply from the operator, the reply is canceled.

You should note that messages to the console can become interspersed with messages from the operating system and from other regions, making them difficult to read. In extreme cases, parts of lengthy messages can ‘scroll off’ the console screen before they have been read.

Example of a conversation using CONVERSE

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.

Time sharing option (TSO) consoles

A TSO session can be used to input CICS commands. This has several advantages:

 It removes the MVS limitation of 99 consoles.  It supports additional device types, such as the IBM

3290.

 It supports remote operation.

The console ID is 4 bytes, only one of which is used for locally connected consoles. TSO and JES3 consoles use all 4 bytes. In addition, each console in a sysplex has an 8-byte name.

.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.

Chapter 1. Transactions supplied by CICS 7

introduction

8 CICS Supplied Transactions

CBAM—BTS browser

Chapter 2. CBAM—BTS browser

CICS Business Transaction Services

 Copyright IBM Corp. 1982, 1999 9

CBAM—BTS browser

10 CICS Supplied Transactions

CDBC—database control menu

Chapter 3. CDBC—database control menu

Use CDBC to connect CICS to DBCTL, or to disconnect CICS from DBCTL. CDBC is applicable only to CICS systems using the IMS/ESA Database Control (DBCTL) interface. For detailed guidance on using the CDBC transaction with databases controlled by DBCTL, see the

CICS IMS Database Control Guide

You can start CDBC from any terminal, from a card

| reader/line printer (CRLP) or DASD sequential terminal, or | from the operating system console.

There are two ways of commencing this transaction:

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

display, followed by the required keyword, which can be either:

CDBC CONnect [SUFfix(startup)]

where startup is a two-digit startup table suffix, or:

CDBC DISconnect [IMMediate]

 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:2

Select one of the following:

1 Connection

Option Selection ==>

Status of the Interface: DFHDB829I DBCTL not connected to CICS.

DBCTL ID:

PF1 = Help 2 = Refresh 3 = End

Figure 1. CDBC transaction: initial screen

2 ORDERLY disconnection 3 IMMEDIATE disconnection

Startup Table Suffix ==>  DBCTL ID Override ==>

CICS APPLID: IYAHZCD2

Startup Table Suffix:

You should get the following message:

DFHDB827D DBCTL Connection requested. Press PF5

to confirm.

If you want to proceed with the CICS-DBCTL connection, press PF5 as requested on the display. The “status” line of the display is then updated. (You can find out the current status of the connection at any time by pressing PF2, which refreshes the display.)

This 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. The DBCTL identifier is available only when the connection has been made. You can also see the suffix of the startup table for this connection.

The following display shows you the effect of asking for option 1:

à ð

CDBC CICS-DBCTL CONNECTION/DISCONNECTION 93.259 13:33:59

Select one of the following:

1 Connection

Option Selection ==> 1

DFHDB827D Connection to DBCTL requested. Press PF5 to confirm.

Status of the Interface: DFHDB829I DBCTL not connected to CICS.

DBCTL ID:

PF1 = Help 2 = Refresh 3 = End

2 ORDERLY disconnection 3 IMMEDIATE disconnection

Startup Table Suffix ==>  DBCTL ID Override ==>

CICS APPLID: IYAHZCD2

Startup Table Suffix:

Figure 2. CDBC transaction: option 1 screen

Disconnecting CICS from DBCTL

As you can see from this display, you can select a CICS-DBCTL connection, an orderly disconnection, or an immediate disconnection.

To disconnect CICS from DBCTL, you can:

1. Type

CDBC DISConnect [IMMediate]

Connecting CICS to DBCTL

You can connect CICS to DBCTL by:

1. Typing CDBC CONnect [SUFFIX(xx)], or

2. Typing ‘1’ in the Option Selection field indicated by ==>.

2. Choose either option 2 or option 3 of the CDBC panel.

Option 2 gives you an orderly disconnection. An orderly disconnection allows all existing CICS-DBCTL tasks to be 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.

 Copyright IBM Corp. 1982, 1999 11

The following display shows you the effect of asking for option 2:

à ð

CDBC CICS-DBCTL CONNECTION/DISCONNECTION 93.259 13:39:2

Select one of the following:

1 Connection

Option Selection ==> 2

DFHDB829D DBCTL orderly disconnection requested. Press PF5 to confirm.

Status of the Interface: DFHDB8293I DBCTL connected and ready.

PF1 = Help 2 = Refresh 3 = End

2 ORDERLY disconnection 3 IMMEDIATE disconnection

Startup Table Suffix ==>  DBCTL ID Override ==>

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.

CDBC—database control menu

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

Database Control Guide

CICS IMS

The HELP panel

If you press the help key (PF1), the following panel is displayed:

à ð

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

STARTUP TABLE SUFFIX Suffix used when CICS was connected to DBCTL.

HELP : CICS-DBCTL CONNECTION/DISCONNECTION

CICS system is communicating.

PRESS ENTER TO RETURN TO SELECTION SCREEN

Figure 4. CDBC transaction: the HELP panel

12 CICS Supplied Transactions

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 (and 3270-like) terminals or from the operating system console.

For detailed information about the CICS-DBCTL interface and guidance on using the CDBI transaction with databases controlled by DBCTL, see the

Guide

CICS IMS Database Control

Start the transaction by typing the identifier, CDBI, on the command line of your display, and press the ENTER key. You get the following display:

à ð

CDBI CICS-DBCTL INTERFACE INQUIRY 91.184 11:23:5

Status : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.

DBCTL ID : SYS1

CICS APPLID: DBDCCICS

The HELP panel

If you press the help key (PF1), you get the following display:

à ð

The CICS-DBCTL interface inquiry screen shows:

STATUS OF THE INTERFACE The status can be:

DFHDB829I DBCTL not connected to CICS. DFHDB8291I DBCTL connect phase 1 in progress. DFHDB8292I DBCTL connect phase 2 in progress. DFHDB8293I DBCTL connected and ready. DFHDB8294I DBCTL orderly disconnect in progress. DFHDB8295I DBCTL immediate disconnect in progress. 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

You can press PF2 to update (refresh) the information shown on screen.

Figure 6. CDBI transaction: the HELP panel

HELP : CICS-DBCTL INTERFACE INQUIRY

PRESS ENTER TO RETURN TO INQUIRY SCREEN

PF1 = Help 2 = Refresh 3 = End

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:

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.

 Copyright IBM Corp. 1982, 1999 13

CDBI–database control inquiry

14 CICS Supplied Transactions

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 CICS systems using the IMS/ESA Database Control (DBCTL) interface.

| CDBM also provides a means of maintaining a command file | which stores commands. You may store commands for any | reason, but repeated re-use is likely to be a frequent | purpose. These stored commands may include more | databases than the operator transaction panel has space for.

To use CDBM you must:

1. Have a DBCTL system running IMS/ESA 5.1 or later | 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 | interface to operate.

3. Generate and add to the DBCTL system, a PSB named

DFHDBMP.

Syntax

 The syntax of the CDBM transaction is:

CDBM /DBCTL operator command

where / is the default command recognition character (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

with the default CRC. The CRC is present only for syntax checking reasons; it does not 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 CDBM - it can only be sent to the one currently connected to CICS. This DBCTL may have its own CRC value which is different from the default one of /. This does not matter to CDBM however, because the / character is used only for syntax checking, and the command is presented to the connected DBCTL without a CRC, using the AIB interface.

| You can enter a DBCTL command, for example: | CDBM /DISPLAY DB DEPT

| or a group command, for example: | CDBM /GROUP SAMPLE STO

| in this way.

 You can also start the transaction by typing the identifier,

CDBM, on the command line of your display, as follows:

CDBM

Press the ENTER key. You get the panel shown in Figure 7.

à ð

CDBM CICS-DBCTL Operator Transaction 98.135 13:24:2

Type IMS command. ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________

For /DBDUMP or /DBRECOVER commands

Choose one. 1 1. Do not force end of volume

Press enter to display responses.

CICS APPLID DBDCCICS DBCTL ID SYS3

2. Force end of volume

| F1=Help F2=Maintenance F3=Exit F5=Refresh F12=Cancel

Figure 7. CICS-DBCTL operator transaction

| On this panel you can enter a DBCTL command, for | example:

| /DISPLAY DB ALL | or a group command, for example:

| /GROUP SAMPLE STA | An example of the use of a /GROUP command from the

| CICS-DBCTL Operator Transaction screen is shown in | Figure 8.

à ð

CDBM CICS-DBCTL Operator Transaction 98.135 13:24:2

Type IMS command.

____________________________________________________________ ____________________________________________________________ ____________________________________________________________

For /DBDUMP or /DBRECOVER commands

Choose one. 1 1. Do not force end of volume

Press enter to display responses.

CICS APPLID DBDCCICS DBCTL ID SYS3

F1=Help F2=Maintenance F3=Exit F5=Refresh F12=Cancel

Figure 8. CICS-DBCTL operator transaction panel showing a GROUP command

| Note: The group command

/GROUP SAMPLE STA___________________________________________

2. Force end of volume

SAMPLE STA

referred to in this

| panel can be found in the “DFHDBFK - The CDBM | GROUP command file” on page 16.

| Responses to commands issued using CDBM are returned in

a screen like the one shown in Figure 9 on page 16, which shows the first of a number of screens issued in response to a /DISPLAY DB ALL command.

 Copyright IBM Corp. 1982, 1999 15

CDBM–database control interface

à ð

CDBM CICS-DBCTL IMS Responses Screen 1 Responses 1 to 18 More: +

DATABASE TYPE TOTAL UNUSED TOTAL UNUSED ACC CONDITIONS ACCUNTDB UP STOPPED, NOTOPEN, NOTINIT ADMIDX1 UP STOPPED, NOTOPEN, NOTINIT ADMOBJ1 UP STOPPED, NOTOPEN, NOTINIT ADMOBJ2 UP STOPPED, NOTOPEN, NOTINIT ADMOBJ3 UP STOPPED, NOTOPEN, NOTINIT ADMSYSDF UP STOPPED, NOTOPEN, NOTINIT BE1CHKPT DL/I UP NOTOPEN BE1PARTA UP STOPPED, NOTOPEN, NOTINIT BE1PARTB UP STOPPED, NOTOPEN, NOTINIT BE1PARTC UP STOPPED, NOTOPEN, NOTINIT BE1PARTS UP STOPPED, NOTOPEN, NOTINIT BE2ORDER DL/I UP NOTOPEN BE2ORDRX DL/I UP NOTOPEN BE2PARTS DL/I UP NOTOPEN BE2PCUST DL/I UP NOTOPEN BE3ORDER DL/I UP NOTOPEN BE3ORDRX DL/I UP NOTOPEN More...

F1=Help F3=Exit F4=Top F6=Bottom F7=Bkwd F8=Fwd F9=Retrieve F12=Cancel

Figure 9. CICS-DBCTL IMS responses

DFHDBFK - The CDBM GROUP command

file

| Before you can use the /GROUP command CDBM requires a | file in which all your predefined commands can be stored. | This file, DFHDBFK, is the CDBM GROUP command file. It | is a VSAM KSDS.

| The DFHDBFK file is not required until you first attempt to | use the /GROUP command.

| Sample JCL to enable you to define this file and optionally to | place some of your group definitions within it is provided in | the

CICS System Definition Guide

. The example given there | also shows you how to batch load this file if you want to do | so.

| You may load many definitions in this way, or load none. You | may use whatever means you prefer to define this file and | and to maintain its content. One method of maintainting the | content once the file is defined is provided by CDBM which | offers a Maintenance function for the DFHDBFK file.

| To use the the /GROUP command functions of the CDBM | transaction, add the data set name of the group command | file to the definition of the DFHDBFK file within the | DFHDBCTL group. For information about how to do this, see | the

CICS Resource Definition Guide

manual.

| 2| 10| IMS

| a 10-character field containing | Command

| any of the IMS command verbs | that are valid for CDBM (see the | |

CICS IMS Database Control Guide

for details). Leading or

| embedded blanks are not | allowed, but trailing blanks are | acceptable.

| 3| 1406| IMS

| Up to 1406 characters of | Command

| parameters appropriate to the | parameters

| chosen IMS command verb. | (This will often consist of lists of | databases.)

The MAINTENANCE panel for DFHDBFK

| | If you press the Maintenance key (PF2) on the main CDBM

| panel, you get the panel shown in Figure 10 on page 17.

Record layout in the CDBM GROUP

| command file | Each record in the DFHDBFK file may be up to 1428

| characters long, as follows:

16 CICS Supplied Transactions

CDBM–database control interface

|à|

| CDBM CICS/DBCTL COMMAND GROUP MAINTENANCE

| _ ACTION A add B browse D delete R read U update

| ____________ GROUP __________ IMS COMMAND

| > <

| > < | F1=Help F3=Exit F12=Cancel

|á| |

Figure 10. CICS-DBCTL Group Maintenance panel

| Input fields | The input fields are:

|  Action |  Group |  IMS Command |  IMS Command parameters

| (between the > < marks). | Group, IMS Command and IMS Command parameters are

| described in the section “Record layout in the CDBM | GROUP command file” on page 16

| The Action field will accept one of the following: | A Add

| Add a new record to the DFHDBFK file. If the key | already exists, the Add fails.

| D Delete | Delete a record from the DFHDBFK file. A Delete must

| 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 | 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.

| A lock is released by exiting the CDBM maintenance | panel, or by your next CDBM Maintenance action | (whether that is the Update or Delete you had | contemplated, or something different entirely).

| U Update | Update a record in the DFHDBFK file. An Update must

| be immediately preceded by a Read to lock the required | record.

| You cannot update the key fields (GROUP and IMS | COMMAND).

| Note: Use Add to create a new key.

Key

| Note: In the descriptions above, | characters at the beginning of each record in the | DFHDBFK file (namely the GROUP and IMS | COMMAND).

refers to the 22

The CICS-DBCTL interface

For detailed information about the CICS-DBCTL interface and guidance on using the CDBM transaction with databases controlled using DBCTL, see the

Guide

CICS IMS Database Control

| B Browse | Displays the contents of the command file, record by

| record. Specify any key (or none) to indicate where you | want the browse to start. Each time you press ENTER, | Browse moves on to the next record. At the end of the | 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

The HELP panels

| If you press the help key (PF1) from the CICS-DBCTL | Operator Transaction panel, you get the panel shown in

Figure 11 on page 18.

à ð

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

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.

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

command and press enter to display responses.

1. Do not force end of volume

2. Force end of volume

| 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.

CDBM–database control interface

| F3=Exit F12=Cancel |á|

Figure 12. CICS-DBCTL Maintenance help panel

18 CICS Supplied Transactions

CEBR—temporary storage browse

Chapter 6. CEBR—temporary storage browse

Use the CEBR transaction to browse temporary storage queues and to delete them.

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

invoking CEBR without a queue name or from an EDF session at terminal S21A is shown in Figure 14.

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

 Copyright IBM Corp. 1982, 1999 19

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

Application Programming Guide

CICS

CEBR—temporary storage browse

The HELP panel

If you press the help key (PF1), the following panel is displayed:

à ð

These commands are available to you (abbreviations in UPPER CASE): Find /string/ - Keyword optional. Final delimiter optional if

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

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.

string has no blanks. Any other delimiter is OK.

(name may be in hex - e.g., X'C134')

20 CICS Supplied Transactions

CEBT INQUIRE AUXTRACE

Chapter 7. CEBT—master terminal (alternate CICS)

Use CEBT to control an alternate CICS system in an extended recovery facility (XRF) environment. For information about XRF, see the

You can start this transaction only at the operating system console. Starting a transaction at the system console is described in “The system console as a CICS terminal” on page 5.

CICS/ESA 3.3 XRF Guide

Minimum abbreviation of keywords

The CEBT command accepts as few characters of a keyword as needed to uniquely identify it within the request. An exception to this rule is the SHUTDOWN keyword, for which the minimum abbreviation is SHUT.

In the syntax displays on your screen and in this book, the minimum permitted abbreviation is given in uppercase characters, and the rest of the keyword in lowercase characters.

CEBT INQUIRE and SET commands

The CEBT INQUIRE and SET commands allow you to query or set:

 Auxiliary trace (CEBT INQUIRE|SET AUXTRACE)  The dump data set (CEBT INQUIRE|SET DUMP)  GTF tracing (CEBT INQUIRE|SET GTFTRACE)  Internal tracing (CEBT INQUIRE|SET INTTRACE)  Surveillance or ‘tracking’ of the active CICS system by

the alternate CICS system (CEBT INQUIRE|SET SURVEILLANCE)

 Takeover from the active CICS system by the alternate

CICS system (CEBT INQUIRE|SET TAKEOVER).

Descriptions follow of the CEBT INQUIRE and SET commands in alphabetic order of the name of the resource.

CEBT INQUIRE AUXTRACE

Function: Return information about the status of auxiliary

trace.

Description: Auxiliary trace entries are made to a pair of

CICS-controlled BSAM data sets, ‘A’ and ‘B’. CEBT 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).

For background information about auxiliary tracing, see the

CICS Problem Determination Guide

Input: Press the Clear key and type CEBT INQUIRE

AUXTRACE (the minimum abbreviation is CEBT I AUX).

To change various attributes, use the CEBT SET AUXTRACE command.

─ ──CEBT Inquire Auxtrace ─

Displayed fields

All

Automatic switching occurs as necessary until the end of this CICS session without the need for operator intervention.

Auxiliary

identifies this panel as relating to auxiliary trace.

Current(A|B)

displays a 1-character identifier of the current auxiliary data set, which can be ‘A’ or ‘B’. This value is blank if there is no auxiliary trace data set.

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.

 Copyright IBM Corp. 1982, 1999 21

CEBT INQUIRE DUMP

Stop

Auxiliary tracing has stopped.

Switch

displays the information that an immediate switch is being made from the current auxiliary trace data set to the alternate trace data set.

CEBT INQUIRE DUMP

Function: Retrieve information about the CICS dump data

sets.

Description: CEBT INQUIRE DUMP tells you which dump

data set (A or B) is currently open. For general information about dumps, see the

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.

─ ──CEBT Inquire Dump ─

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.

CICS Problem

Currentdds(

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

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.

value

)

appears blank.

22 CICS Supplied Transactions

CEBT INQUIRE GTFTRACE  CEBT INQUIRE INTTRACE

CEBT INQUIRE GTFTRACE

Function: Show the GTF status. Description: CEBT INQUIRE GTFTRACE tells you

whether CICS tracing to the MVS Generalized Tracing Facility (GTF) is started or stopped.

This command is intended for use at terminals that do not support the CETR full-screen tracing transaction.

For information about GTF tracing, see the

Determination Guide

and the

CICS Performance Guide

Input: Press the Clear key and type CEBT INQUIRE

GTFTRACE (the minimum abbreviation is CEBT I G).

To change various attributes, use the CEBT SET GTFTRACE command.

─ ──CEBT Inquire Gtftrace ─

Displayed fields

Gtftrace

indicates that this panel relates to a GTFTRACE inquiry.

Start

CICS tracing to the MVS Generalized Tracing Facility (GTF) is in progress.

CICS Problem

CEBT INQUIRE INTTRACE

Function: Show the status of CICS internal tracing. Description: CEBT INQUIRE INTTRACE tells you

whether CICS internal tracing is in progress. This command is intended for use at terminals that do not

support the full-screen tracing transaction CETR.

Input: Press the Clear key and type CEBT INQUIRE

INTTRACE (the minimum abbreviation is CEBT I IN).

To change various attributes, use the CEBT SET INTTRACE command.

─ ──CEBT Inquire Inttrace ─

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.

Stopped

CICS tracing to the MVS Generalized Tracing Facility (GTF) is not in progress.

Chapter 7. Master terminal (alternate CICS) CEBT 23

CEBT INQUIRE SURVEILLANCE  CEBT INQUIRE TAKEOVER

CEBT INQUIRE SURVEILLANCE

Function: Display whether surveillance (or tracking) of the

active CICS system by the alternate CICS system is ON or OFF.

Input: Press the Clear key and type CEBT INQUIRE

SURVEILLANCE (the minimum abbreviation is CEBT I SU).

To change various attributes, use the CEBT SET SURVEILLANCE command.

─ ──CEBT Inquire Surveillance ─

For more information about surveillance, see the

3.3 XRF Guide

CICS/ESA

CEBT INQUIRE TAKEOVER

Function: Display whether any takeover from the active

CICS system by the alternate CICS system is to be automatic, manual, or command-driven.

Input: Press the Clear key and type CEBT INQUIRE

TAKEOVER (the minimum abbreviation is CEBT I T).

To change various attributes, use the CEBT SET TAKEOVER command.

24 CICS Supplied Transactions

CEBT PERFORM commands  CEBT PERFORM SHUTDOWN

CEBT PERFORM commands

The CEBT PERFORM commands allow you to:

 Shut down the alternate CICS system (CEBT PERFORM

SHUTDOWN)

 Request a dump of the alternate CICS and continue

processing (CEBT PERFORM SNAP)

 Cause the alternate CICS to take over from the active

CICS (CEBT PERFORM TAKEOVER).

Descriptions follow of the CEBT PERFORM commands in alphabetic order.

CEBT PERFORM SHUTDOWN

Function: Shut down the alternate CICS system in an

XRF complex.

Description: If you enter CEBT PERFORM SHUTDOWN,

all active system tasks are allowed to finish, and the alternate CICS system signs off normally from the CICS availability manager (CAVM) data set.

─ ──CEBT Perform SHutdown ──Dump ──Immediate ─

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.

Chapter 7. Master terminal (alternate CICS) CEBT 25

CEBT PERFORM SNAP  CEBT PERFORM TAKEOVER

CEBT PERFORM SNAP

Function: Cause a “snapshot” dump of the alternate CICS

system to be taken while CICS continues to run. All CEBT PERFORM SNAP requests result in an SDUMP on

an MVS SYS1.DUMPnn data set. The use of CEBT PERFORM SNAP prevents all other tasks

from running on the alternate system, and could delay takeover or recovery after takeover.

Syntax

─ ──CEBT Perform SNap ─

CEBT PERFORM TAKEOVER

Function: The CEBT PERFORM TAKEOVER command

initiates a takeover by the alternate CICS system, causing the active CICS system to sign off abnormally.

Syntax

─ ──CEBT Perform Takeover ──Dump ─

Options

Dump

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.

26 CICS Supplied Transactions

CEBT SET AUXTRACE

Function: Change auxiliary tracing options. Description: 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 about using traces, see the

Determination Guide

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.

─ ──CEBT Set Auxtrace ──┬ ┬─────── ────────────── ├┤─STArt─ ├┤─Pause─ └┘─STOp──

─ ──┬ ┬────────── ──SWitch ─ ├ ┤─NOswitch─ ├ ┤─NExt───── └ ┘─All──────

CICS Problem

STArt

CICS is to start auxiliary tracing and open the auxiliary trace data set if it is currently closed.

STOp

CICS is to stop auxiliary tracing and close the auxiliary trace data set. A subsequent START request causes new trace entries to be written at the start of the data set, thereby overwriting the trace entries that were written before the STOP request.

SWitch

specifies that an immediate switch from the current auxiliary trace data set is to be made to the alternate trace data set.

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.

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.

Chapter 7. Master terminal (alternate CICS) CEBT 27

CEBT SET DUMP  CEBT SET GTFTRACE

CEBT SET DUMP

Function: Change the attributes of a CICS dump data set. Description: Using CEBT SET DUMP, you can open or

close the active CICS dump data set, and specify whether or not the automatic switch to the inactive dump data set is to occur when the active dump data set is full. 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 about using dumps, see the

Determination Guide

Syntax: Press the Clear key to clear the screen. There are

two ways of commencing this transaction:

 Type CEBT SET DUMP (the minimum abbreviation is CEBT

SDU). You get a display that lists the current status,

similar to that obtained by CEBT INQUIRE DUMP. You can then tab to the highlighted or blank fields and overtype them with the required values.

 Type CEBT SET DUMP (CEBT S DU) followed by one or

more attribute settings that you wish to change. For example, CEBT S DU A will cause an automatic switch to the inactive dump data set if ‘noautoswitch’ was previously specified.

─ ──CEBT Set Dump ──┬ ┬──────── ───────────────── ├┤─Open─── ├┤─CLosed─ └┘─Switch─

─ ──┬ ┬────────────── ─ ├ ┤─Autoswitch─── └ ┘─Noautoswitch─

CICS Problem

CEBT SET GTFTRACE

Function: Change the status of GTF tracing Description: CEBT SET GTFTRACE allows you to switch

CICS tracing to the MVS Generalized Tracing Facility (GTF) on and off.

This command is intended for use at terminals that do not support the CETR full-screen tracing transaction.

For information about using GTF tracing, see the

Problem Determination Guide

Syntax: Press the Clear key to clear the screen. There are

two ways of commencing this transaction:

 Type CEBT SET GTFTRACE (the minimum abbreviation is

CEBT S G). You get a display that lists the current status,

similar to that obtained by CEBT INQUIRE GTFTRACE. You can then tab to the highlighted or blank fields and overtype them with the required values.

 Type CEBT SET GTFTRACE (CEBT S G) followed by one or

more attribute settings that you wish to change. For example, CEBT S G STO will stop GTF tracing if it is already running.

─ ──CEBT Set Gtftrace ──┬ ┬─────── ─ ├┤─STArt─ └┘─STOp──

Options

STArt

CICS tracing to the MVS Generalized Tracing Facility (GTF) is started.

CICS

Options

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.

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

The currently active dump data set is to become inactive, and the currently inactive data set is to become active.

STOp

CICS tracing to the MVS Generalized Tracing Facility (GTF) is stopped.

28 CICS Supplied Transactions

CEBT SET INTTRACE  CEBT SET SURVEILLANCE

CEBT SET INTTRACE

Function: Switch CICS internal tracing on or off. Description: This command is intended for use at

terminals that do not support the full-screen tracing transaction CETR.

Syntax: Press the Clear key to clear the screen. There are

two ways of commencing this transaction:

 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 INTTRACE. You can then tab to the highlighted or blank fields and overtype them with the required values.

 Type CEBT SET INTTRACE (CEBT S IN) followed by one or

more attribute settings that you wish to change. For example, CEBT S IN STO will stop internal tracing if it is already running.

─ ──CEbt Set Inttrace ──┬ ┬─────── ─ ├┤─STArt─ └┘─STOp──

CEBT SET SURVEILLANCE

Function: Set surveillance (or tracking) of the active CICS

by the alternate CICS on or off.

Syntax

─ ──CEBT Set Surveillance ──┬ ┬───── ─ ├┤─OFf─ └┘─ON──

Options

OFf

Surveillance of the active CICS system by the alternate CICS is to be stopped.

Surveillance of the active CICS system by the alternate CICS is to be started.

For more information about surveillance, see the

CICS/ESA 3.3 XRF Guide

Options

STArt

CICS internal tracing is started.

STOp

CICS internal tracing is stopped.

Chapter 7. Master terminal (alternate CICS) CEBT 29

CEBT SET TAKEOVER

Function: Set takeover from the active CICS system by

the alternate CICS system to be automatic, manual, or command-driven.

Syntax: Press the Clear key to clear the screen. There are

two ways of commencing this transaction:

 Type CEBT SET TAKEOVER (the minimum abbreviation is

CEBT S T). You get a display that lists the current status,

similar to that obtained by CEBT INQUIRE TAKEOVER. You can then tab to the highlighted or blank fields and overtype them with the required values.

 Type CEBT SET TAKEOVER (CEBT S T) followed by one or

more attribute settings that you wish to change. For example, CEBT S T M changes takeover to a manual operation if it was previously specified to be automatic.

─ ──CEBT Set Takeover ──┬ ┬─────────── ─ ├┤─Automatic─ ├┤─Command─── └┘─Manual────

Options

The HELP panel

If you press the help key (PF1), the following panel is displayed:

à ð

GENERAL HELP INFORMATION

Enter command on the first line and press ENTER (after returning from HELP). Options can be abbreviated to the minimum to make them unique. ? before command gives COMMAND SYNTAX CHECK and prevents execution. To modify results, position cursor using TAB key, overtype and press ENTER. ? at start of results line gives SYNTAX OF SET COMMAND.

PF KEY HELP INFORMATION

PF1 HELP HELP INFORMATION PF2 UNDEFINED

PF3 END END SESSION PF4 UNDEFINED PF5 UNDEFINED PF6 UNDEFINED

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 15. CEBT transaction: the HELP panel

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

command options.

tells you more about these

30 CICS Supplied Transactions

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 syntax, and modify it if necessary. In most cases, you can also process the command.

For programming information on each EXEC CICS command, see the manual or the

CICS Application Programming Reference

CICS System Programming Reference

manual. For details of how to use the CECI transaction, see the

Application Programming Guide

, which includes an example

CICS

of a complete session with CECI. Start the transaction by entering CECI on the command line

of the screen, as follows:

CECI

Press ENTER. You get a list of all EXEC CICS commands.

à ð

STATUS: ENTER ONE OF THE FOLLOWING

ABend DISAble ISsue RELease SUspend

ACquire DISCard Journal RESEtbr SYncpoint

ADdress DUmp LInk RESYnc Trace ALlocate ENAble LOad RETRieve Unlock ASKtime ENDbr Monitor RETUrn Verify

ASSign ENQ PErform REWrite WAIT

BIf ENTer POInt ROute WAITCics BUild EXtract POP SENd WRITE

CAncel FEpi POSt SET WRITEQ CHange FOrmattime PURge SIGNOFf Xctl

COLlect FREE PUSh SIGNON CONNect FREEMain Query SPOOLClose CONVerse GDs READ SPOOLOpen DELAy GEtmain READNext SPOOLRead

DELETE Handle READPrev SPOOLWrite DELETEQ IGnore READQ START

DEQ INquire RECeive STARTBr

PF 1 HELP 2 HEX 3 END 4 EIB 5 VAR 6 USER 9 MSG

Figure 16. CECI transaction: initial screen

Note: RECEIVE and SEND cannot be used on

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 syntax for that command. For example, Figure 17 shows the screen displayed for the EXEC CICS RETRIEVE command.

à ð

RETR STATUS: ABOUT TO EXECUTE COMMAND NAME= EXEC CICS RETRieve

< Set() | Into() > < Length() > < RTRansid() > < RTErmid() > < Queue() > < Wait >

PF 1 HELP 2 HEX 3 END 4 EIB 5 VAR 6 USER 7 SBH 8 SFH 9 MSG 1 SB 11 SF

Figure 17. CECI transaction: RETRieve command screen

Alternatively, you can enter CECI together with the name of the command in which you are interested, and bypass the full list of commands; for example:

CECI asktime

In both cases, you can generally go on to check the syntax of the command, change it if necessary, and then process the command.

Many CICS system programming commands use CVDA values, and CECI shows numeric equivalents for these. See the

CICS System Programming Reference

manual for programming information, including a “translation” of these numeric values to their alphabetic values.

The HELP panel

If you press the help key (PF1), the following panel is displayed:

à ð

GENERAL HELP INFORMATION

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

 Copyright IBM Corp. 1982, 1999 31

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

CECI/CECS—command-level interpreter

For information how to use the CECI and CECS transactions, see the

CICS Application Programming Guide

32 CICS Supplied Transactions

CEDA—resource definition online

Chapter 9. CEDA—resource definition online

Use CEDA to define resources to your CICS system while the system is running. With CEDA, you can update both the CICS system definition (CSD) file and the running CICS system.

Start the transaction by entering CEDA on the command line of the screen. Press ENTER. You get the following screen (Figure 19), which shows the options available within CEDA.

à ð

ENTER ONE OF THE FOLLOWING

ADd ALter APpend CHeck COpy DEFine DELete DIsplay Expand Install Lock Move REMove REName UNlock USerdefine View

SYSID=CI41 APPLID=IYAHZCCV

PF 1 HELP 3 END 6 CRSR 9 MSG 12 CNCL

Figure 19. CEDA transaction: initial screen

CEDA provides the following functions: ADd Adds a group name to a list, and creates a new

list if the list did not already exist.

ALter Changes some of the attributes of an existing

resource definition.

APpend Copies a list to another list. CHeck Checks that the resource definitions within a

group or list are consistent with one another.

COpy Copies one or more resource definitions. DEFine Creates a new resource definition on the CSD

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.

REName Renames a resource definition. UNlock Removes a lock on a group or list which was

previously put there by a CEDA LOCK command.

USerdefine Instead of using CICS-supplied default values

with the DEFINE command, you can set your own defaults and use the USERDEFINE command to create a new resource definition on the CSD file.

View Lets you look at the resource definition

attributes.

This section briefly describes each of these functions and their syntax. For guidance on how to use CEDA, see the

CICS Resource Definition Guide

If you enter DEF on the command line and press ENTER, you get the screen shown in Figure 20 which lists the resources:

à ð

DEF

ENTER ONE OF THE FOLLOWING

| Connection TCpipservice

DB2Conn TDqueue DB2Entry TErminal DB2Tran TRANClass

| DOctemplate TRANSaction

| Enqmodel TSmodel

File TYpeterm Journalmodel Lsrpool Mapset PARTItionset PARTNer

| PROCesstype

PROFile PROGram

| Requestmodel

Sessions

SYSID=JOHN APPLID=I

PF 1 HELP 3 END 6 CRSR 9 MSG 1

Figure 20. CEDA transaction: DEFINE screen

 Copyright IBM Corp. 1982, 1999 33

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

CEDA—resource definition online

Figure 21. CEDA transaction: INSTALL screen

Command syntax

34 CICS Supplied Transactions

CEDA—resource definition online

─ ──CEDA ─────────────────────────────────────────────────────────────────── ─ ──┬ ┬─ADD─ ──GROUP(groupname1)──LIST(name)──┬ ┬──────────────────── ──── ─

││├┤──AFTER(groupname2)─

││└┘──BEFORE(groupname3) ├ ┤─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 ├─── ├ ┤─DELETE─ ──┬ ┬─ALL────────── ──GROUP(name)──┬ ┬──────── ─────────────

││└┘─┤ Resource ├─ └ ┘─REMOVE─ ├ ┤ ─DISPLAY─ ──┬ ┬──LIST(name)──┬ ┬───────────── ────────────── ────────

││││└┘──GROUP(name) │ │└┘──GROUP(name)──┬ ┬────────────── ──┬ ┬──────── │ │├┤─ALL────────── └ ┘─RENAME─

││└┘─┤ Resource ├─ ├ ┤ ─EXPAND─ ──┬ ┬──LIST(name)──┬ ┬───────────── ────────────── ─────────

││└┘─┤ Resource ├─ ├ ┤─INSTALL─ ──┬ ┬────────────── ──┬ ┬──GROUP(name) ────────────────────

││├┤─ALL────────── └ ┘──LIST(name)─

││└┘─┤ Resource ├─ ├ ┤─LOCK─ ──┬ ┬──GROUP(name) ─────────────────────────────────────────

││└┘──LIST(name)─ │ │┌┐─ALL────────── ├ ┤ ─MOVE─ ──┼ ┼────────────── ──┬ ┬─────────── ──┬ ┬───────── ──┬ ┬────────

││└┘─┤ Resource ├─ └ ┘─┤ Route ├─ ├ ┤─REPLACE─ └ ┘─REMOVE─ │ │└┘─MERGE─── ├ ┤─REMOVE─ ──GROUP(name)──LIST(name) ─────────────────────────────── ├ ┤ ─RENAME─ ──┬ ┬────────────── ──┬ ┬─────────── ──┬ ┬──────── ───────────

││├┤─ALL────────── └ ┘─┤ Route ├─ └ ┘─REMOVE─

││└┘─┤ Resource ├─ ├ ┤─UNLOCK─ ──┬ ┬──GROUP(name) ───────────────────────────────────────

││└┘──LIST(name)─ ├ ┤─USERDEFINE──┤ Resource ├─ ──GROUP(name) ─┤ attribute list ├─── └ ┘─VIEW─ ──GROUP(name)──┬ ┬────────────── ─────────────────────────── ├┤─ALL──────────

└┘─┤ Resource ├─

Note:

Consult the

CICS Resource Definition Guide

for information about the attributes

applicable to each resource type.

(1)

────────

(1)

───────

(1)

───

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 ─┤

CEDA—resource definition online

You can go directly to the working screen to make your changes by typing:

CEDA function resource_type

For example:

CEDA DEF CONN

The CEDA keywords are as follows:

AFTER

Controls the placing of a group name in a list.

ALL

All resources are to be copied, deleted, displayed, installed, moved, or renamed.

AS The new name specified for a definition. BEFORE

Controls the placing of a group name in a list.

CONNECTION

The remote system that your CICS system communicates with, using ISC or MRO.

DB2CONN

Defines the CICS DB2 connection.

DB2ENTRY

Defines resources to be used by a transaction or group of transactions when accessing DB2.

DB2TRAN

Associates a transaction ID with a DB2ENTRY.

FILE

The FILE definition describes to CICS file control the physical and operational characteristics of a file.

36 CICS Supplied Transactions

CEDA—resource definition online

GROUP

Every resource definition must have a GROUP name. The resource definition becomes a member of the group and is installed in the CICS system when the group is installed. The GROUP name can be up to 8 characters in length.

JOURNALMODEL

The name of a journal model containing specifications of journal names. An MVS log stream name is associated with each journal model entry.

LIST

The name of the list for which a specified group is to be added, appended, checked, displayed, expanded, installed, locked, removed, or unlocked.

LSRPOOL

The local shared resources (LSR) pool is a reserve of data buffers, strings, and hiperspace buffers that VSAM uses when processing access requests for certain files.

MAPSET

A series of different BMS maps.

PARTITIONSET

A table that describes to CICS how a display screen is to be partitioned.

PARTNER

The PARTNER definition enables CICS application programs to communicate via APPC protocols to a partner application program running on a remote logical unit. PARTNER is one of the four resources (the other three are PROFILE, CONNECTION, and SESSION) that you must specify to allow the System Application Architecture (SAA) communications interface to be used.

| PROCESSTYPE | Use the CICS business transaction services (BTS) API | to define and execute complex business applications | called

PROFILE

PROGRAM

| REQUESTMODEL | A REQUESTMODEL resource definition provides the | connection between an Internet Inter-ORB Protocol | (IIOP).

SESSIONS

processes

A group of programs that control a number of transactions or partners.

The name of the program that is to control a given transaction.

The logical link of two systems that communicate using ISC or MRO.

TDQUEUE

The definition of each transient data queue used in your CICS system. Queue types can be intrapartition, extrapartition, or indirect. Remote queues cannot be specified explicitly; see the

Guide

for more information about defining transient data

queues to be remote.

TERMINAL

The definition of each terminal used in your CICS system. A terminal can be any device linked to your system, for example, visual display units, printers, facsimile machines. To simplify matters, it is possible to group resources that have common features by using TYPETERM and through AUTOINSTALL.

TO The new group to which a definition is to be copied. TRANCLASS

The name of a user-defined class of transactions.

TRANSACTION

The name of the transaction. Within the transaction definition, you can specify options such as transaction priority and length of the transaction work area. You also add to the transaction name the names of related resources: PROGRAM, PROFILE, and PARTITIONSET.

TYPETERM

Some of the common attributes of your terminals. This has to be defined as part of the terminal definition.

CICS Resource Definition

CSD compatibility panel

Figure 22 on page 38 shows a normal ALTER panel with one attribute (PRIMedsize) that is obsolete in CICS/ESA

3.3, protected as indicated by the colon symbol (:). Use the PF2 key to change to the compatibility mode panel

shown in Figure 25 on page 38. PRIMedsize is now shown with the ==> symbols indicating that it can be modified. Use the PF2 key again to return to the normal panel.

See the information about the CSD compatibility panel.

CICS Resource Definition Guide

for background

Chapter 9. Resource definition online CEDA 37

à ð

ALTER TRANS

OVERTYPE TO MODIFY CICS RELEASE = 41 CEDA ALter TRANSaction( ) TRANSaction ==> Group ==> DEscription ==> PROGram ==> TWasize ==> -32767 PROFile ==> PArtitionset ==>

STAtus ==> Enabled | Disabled

PRIMedsize ==> -6552

ISolate ==> Yes | No REMOTE ATTRIBUTES + DYnamic ==> No | Yes

Figure 22. CEDA transaction: normal panel

à ð

REMOTESystem ==> REMOTEName ==> TRProf ==>

Localq ==> No | Yes SCHEDULING PRIOrity ==> -255

TClass : No | 1-1 TRANClass ==> ALIASES Alias ==> TASKReq ==> XTRanid ==> TPName ==> ==> XTPname ==> ==> ==> RECOVERY

DTimout ==> No | 1-68 + INdoubt ==> Backout | Commit | Wait

Figure 23. CEDA transaction: normal panel (continued)

à ð

RESTart ==> No | Yes

SPurge ==> No | Yes

TPUrge ==> No | Yes

DUmp ==> Yes | No

TRACe ==> Yes | No SECURITY

RESSec ==> No | Yes

Cmdsec ==> No | Yes Extsec : TRANSec : 1-64

RSl : -24 | Public

Figure 24. CEDA transaction: normal panel (end)

CEDA—resource definition online

Security checking

The scope of a particular CEDA command can be limited by a combination of several levels of security checking. The normal transaction-attach security is described in the

RACF Security Guide

. CEDA calls the exec interface

CICS

programs to process the user’s commands, in much the same way as CECI or a user’s command-level program would. The resource security and the command security used by the command-level programming interface are thus applicable to the master terminal user.

For programming information about command security checking, see the

CICS System Programming Reference

manual.

CEDA HELP panels

If you press the help key (PF1), the following panels are displayed:

à ð

This panel allows you to see a brief description of the CEDA transaction. For a complete description see Resource Definition (Online) (SC33-666).

Select one of the following topics:

5 Messages

Selection ==>

Press Enter or any PF key to return

Figure 26. CEDA transaction: initial HELP panel

CEDA Help Selection

1 Command Summary 2 Resources, Groups and Lists 3 Using the commands 4 Expand and Display

6 Defaults and Userdefine 7 PF keys

à ð

OVERTYPE TO MODIFY COMPATIBILITY MODE CEDA ALter TRansaction ==> Group ==> DEscription ==> PROGram ==> TWasize ==> -32767 PROFile ==> PArtitionset ==>

STatus ==> Enabled | Disabled

PRIMedsize ==> -6552

TASKDATALoc ==> Below | Any TASKDATAKey ==> User | Cics

REMOTE ATTRIBUTES

DYnamic ==> No | Yes REMOTESystem ==> REMOTEName ==> TRProf ==> + Localq ==> No | Yes

Figure 25. CEDA transaction: compatibility mode panel

à ð

Command Summary

Resource management commands:

DEFINE creates a resource definition (see Topic 6 for USERDEFINE) ALTER,VIEW modify and display the attributes of a resource (or resources) COPY creates new resources from existing definitions DELETE destroys resource definitions MOVE,RENAME change the names and/or groupings of resources

List management commands:

ADD creates or extends a list REMOVE reduces or destroys a list APPEND copies a list or combines lists

General purpose commands:

CHECK cross-checks definitions in a group or list DISPLAY shows the names of groups or lists on the CSD file 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

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

38 CICS Supplied Transactions

CEDA—resource definition online

à ð

You use CEDA to create and modify resource definitions. Using the DEFINE command, you specify a resource's type, name and attributes, which are then stored on the CICS System Definition (CSD) file.

You can see what types of resource there are by using DEFINE on its own 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.

Each resource must belong to a GROUP, which is a collection of resources, usually related in some way. A group of resources can be installed on your running CICS system.

A LIST is a collection of group names, and can be used to specify large numbers of resources during a cold start.

Note that program P, say, may be defined in more than one group. Such definitions are separate resources and may have different attributes. 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

Resources, Groups and Lists

Figure 28. CEDA transaction: HELP Panel 2

à ð

You type CEDA commands on the first line of the screen and press ENTER. You will then see a panel that shows your command in detail, and the results of its execution. You can then either modify the panel to execute a similar command with new values or type a different command on the top line.

You can see the syntax of a command, without executing it, by typing ? in front of the command.

You can shorten command keywords as much as you like provided the result remains unique. Thus ALT and AL both mean ALTER but A is invalid because of ADD. The minimum number of letters you can use is shown in upper case.

You can specify generic names in some commands, by using  and +.  means any number of characters, + means any single character. Thus PROGRAM(P) refers to all programs whose names begin with P.

Current values for GROUP and LIST are kept and are used when either keyword is omitted from commands other than DISPLAY and EXPAND LIST.

Press Enter or any PF key to return to Help Selection Panel

Using the commands

à ð

Messages

Single messages appear near the bottom of panels. If there is more than one message a summary appears instead. PF9 shows the details of such a summary.

Messages are preceded by a single letter indicating the severity: I-Informatory W-Warning E-Error S-Severe

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 be executed by pressing ENTER without making any changes. S-level messages require you to correct the command.

For a command executed on an EXPAND or DISPLAY panel you can see the 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) must still be corrected by you. You can correct a command on the message panel or on the original panel.

Press Enter or any PF key to return to Help Selection Panel

Figure 31. CEDA transaction: HELP Panel 5

à ð

When you DEFINE a resource any attributes you do not specify are defaulted. You cannot change the defaults that DEFINE uses. You can however DEFINE "default resources" with whatever values you like and then create new resources using USERDEFINE.

You DEFINE resources called USER in a group called USERDEF, giving each one the values you would like to have as defaults. These are now your default resources.

USERDEFINE will then behave just like DEFINE except that it will get default values from the appropriate default resource. If a default resource does not exist then USERDEFINE fails.

This facility is restricted to initial values only. Default values are also given by CEDA to attributes you remove from a resource, by overtyping with blanks for instance. These defaults are the same as those used for the DEFINE command and you cannot change them.

Press Enter or any PF key to return to Help Selection Panel

Defaults and Userdefine

Figure 29. CEDA transaction: HELP Panel 3

à ð

The commands you can use on each kind of panel are as follows:

EXPAND GROUP panel - Alter, Copy, Delete, Install, Move, Rename, View EXPAND LIST panel - Add, Remove DISPLAY GROUP panel - Check, Expand, Install , Lock, Unlock DISPLAY LIST panel - Append, Check, Expand, Lock, Unlock

All these commands operate on the thing beside which you enter them. ALTER means ALTER PROGRAM(P) GROUP(G), if these are the object and group values on the line. In this case, since no attributes are changed, you will see a display of the object which you can then overtype. The EXPAND command on a DISPLAY panel also results in a new panel.

You can enter as many commands as you like at one time and you can use = to mean the same command as the last one.

The RENAME option of EXPAND GROUP gives a panel on which you can change the names of objects directly, by overtyping the name fields displayed. When you change a name field a RENAME command is put in the corresponding command field, and causes anything entered there to be ignored.

Press Enter or any PF key to return to Help Selection Panel

Expand and Display

Figure 30. CEDA transaction: HELP Panel 4

Figure 32. CEDA transaction: HELP Panel 6

à ð

PF keys

The PF keys do the following:

1 HELP Gives the initial help panel 2 COM Selects and deselects compatibility mode

3 END Terminates the CEDA transaction if no data has been entered 4 Does nothing 5 Does nothing

6 CRSR Moves the cursor to the command line or first input field

7 SBH Scrolls back half a screen

8 SFH Scrolls forward half a screen

9 MSG Displays the current set of messages

1 SB Scrolls back a full screen 11 SF Scrolls forward a full screen 12 CNCL Cancels changes not yet executed and returns to previous panel

When you press ENTER without having entered any data you will normally be returned to the previous panel.

Positioning the cursor at a PF key and pressing ENTER will have the same effect as pressing the key. PF13 to PF24 have the same effects as PF1 to PF12.

Press Enter or any PF key to return to Help Selection Panel

Figure 33. CEDA transaction: HELP panel 7

Chapter 9. Resource definition online CEDA 39

CEDA—resource definition online

CEDB and CEDC

Two further resource definition transactions, CEDB and CEDC, allow you to use some, but not all, of the functions of CEDA.

CEDB

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

CEDC

The CEDC transaction allows you only to look at data on the CICS system definition (CSD) file. You cannot update either the CSD file or the running CICS system. The only options that are available are DISPLAY, EXPAND, and VIEW.

For background information about the CEDA, CEDB, and CEDC transactions, see the

CICS Resource Definition Guide

Figure 34. CEDB transaction: initial screen

40 CICS Supplied Transactions

CEDF—execution diagnostic facility

Chapter 10. CEDF & CEDX — the execution diagnostic facility

The CICS execution diagnostic facility (EDF) provides two transactions that you can use for testing application programs. These transactions—CEDF and CEDX—enable you to test application programs interactively without having to supply special program testing procedures.

CEDF

Use CEDF to invoke EDF for testing application programs that are associated with user transactions initiated from a terminal.

CEDX

Use CEDX to invoke EDF for testing application programs that are associated with non-terminal transactions.

CEDF transaction

CEDF allows you to intercept your application programs at the program’s initiation, at each CICS command, and at the program termination. CEDF helps you to isolate and focus on problems in your application programs.

For information on how to use the CEDF transaction, see the

CICS Application Programming Guide

You must ensure that the EDF resource definitions are installed. These resource definitions are provided in the IBM-supplied group, DFHEDF. For information about installing the resource definitions, see the

Definition Guide

CICS Resource

You must also ensure that the terminal from which you run EDF is in transceive (ATI/TTI) status.

Command syntax

┌┐─,ON── ─ ──CEDF ──┬ ┬─────────── ──┼ ┼────── ─ ├ ┤─termid──── └ ┘─,OFF─ ├ ┤─sysid───── └ ┘─sessionid─

Command options

OFF

specifies whether the EDF screen is to be switched OFF. If you specify OFF you must enter the preceding comma, as shown in the following examples:

CEDF T33A CEDF T33A ,OFF CEDF ,OFF

specifies whether the EDF screen is to be switched ON. The default is ON. If you specify ON you must enter the preceding comma, as shown in the following examples:

CEDF T33A CEDF ,ON

sessionid

specifies the session identifier used to test a transaction attached across an MRO, APPC, or LU6.1 session. All CICS commands processed by the attached transaction are monitored.

sysid

specifies the system identifier used to test a transaction across an MRO or APPC session.

termid

specifies the identifier of the terminal on which the transaction to be tested is being run. If you do not provide an identifier, the terminal at which you enter the CEDF transaction is assumed.

Beginning an EDF session (single-screen mode)

To start an EDF session with a single terminal, clear the screen and enter the transaction identifier, CEDF. The EDF inputs and outputs are interleaved with those of the transaction. This is known as

CEDF

When you press ENTER, the response is:

THIS TERMINAL: EDF MODE ON

Now clear the screen and enter the name of your transaction. Figure 35 shows the initial screen for a typical transaction using EDF.

à ð

TRANSACTION: ACCT PROGRAM: ACCT TASK: 54 APPLID: 1349 DISPLAY:  STATUS: PROGRAM INITIATION

EIBTIME = 11343 EIBDATE = 89174 EIBTRNID = 'ACCT' EIBTASKN = 54 EIBTRMID = '25L'

EIBCPOSN = 4 EIBCALEN =  EIBAID = X'7D' AT X'543F1E' EIBFN = X'' AT X'543F1F' EIBRCODE = X'' AT X'543F21'

EIBDS = '........'

+ EIBREQID = '........'

ENTER: CONTINUE 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 PF1: PREVIOUS DISPLAY PF11: UNDEFINED PF12: UNDEFINED

Figure 35. CEDF transaction: initial screen

single-screen mode

 Copyright IBM Corp. 1982, 1999 41

CEDF—execution diagnostic facility

Beginning an EDF session (dual-screen mode)

You can also use EDF in what is known as

mode

; that is, using one terminal to monitor a transaction

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 second terminal. If the second terminal is not busy, the message displayed at the first terminal is:

TERMINAL tttt: EDF MODE ON

and nothing further will happen until a transaction is started on the second terminal, when the PROGRAM INITIATION display will appear.

If a transaction is already running on the second terminal, the message displayed at the first terminal is:

TERMINAL tttt: TRANSACTION RUNNING: EDF MODE ON

CEDF then picks up control at the next command processed and presents the appropriate display. At the first terminal, you can then follow the sequence of commands in the transaction running at the second terminal.

dual-screen

Monitoring remote transactions

In a multiregion operation (MRO) or an intersystem communication (ISC) environment (APPC only), you can use 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 (AOR) that the transaction is to be run in EDF mode.

When the remote application ends, if your reply is YES, the terminal remains in EDF mode as usual. However, CICS deletes all the associated temporary storage queues, and none of the previous EDF screens or options is saved: you must type these again for the next transaction. Responding NO at the termination screen ends the EDF session in all participating regions.

Note: CICS supports EDF for remote transactions only

when all the communicating regions are using CICS/ESA.

security checking of transactions running under CEDF.

à ð

TRANSACTION: DLID PROGRAM: DLID TASK: 49 APPLID: IYAHZCIB ADDRESS: 

WORKING STORAGE IS NOT AVAILABLE ENTER: CURRENT DISPLAY PF1 : UNDEFINED PF2 : BROWSE TEMP STORAGE PF3 : UNDEFINED PF4 : EIB DISPLAY PF5 : INVOKE CECI PF6 : USER DISPLAY PF7 : SCROLL BACK HALF PF8 : SCROLL FORWARD HALF PF9 : UNDEFINED PF1: SCROLL BACK FULL PF11: SCROLL FORWARD FULL PF12: REMEMBER DISPLAY

Figure 36. Typical EDF display from which CEBR or CECI can be invoked

To invoke the CEBR transaction from the CEDF screen, press PF2. You can then use CEBR commands to browse temporary storage queues and to delete them. (CEBR commands are described briefly in Chapter 6, “CEBR—temporary storage browse” on page 19; for detailed guidance on using them, see the

Programming Guide

To invoke the CECI transaction from the CEDF screen, press PF5. You can then use CECI commands to display or alter resource status. (CECI commands are described briefly in Chapter 8, “CECI—command-level interpreter” on page 31; for detailed guidance on using them, see the

Application Programming Guide

CEDX transaction

Use CEDX to monitor and debug non-terminal transactions. The transaction you specify for debugging can be:

 Initiated without an associated terminal; for example, by

an EXEC CICS START command, or by a transient data queue trigger-level.

 Initiated at a terminal, which can be either the EDF

terminal or a different terminal.

CICS intercepts the transaction specified on the CEDX command, and displays the EDF diagnostic panels at the terminal at which the EDF command is issued.

CICS Application

CICS

tranid

Invoking CEBR and CECI from CEDF

See Figure 36 for an example of the screen from which CEBR and CECI can be invoked.

Note: If you are not authorized to use the CEBR or CECI

transaction by the external security manager, a warning message will appear on the EDF panel. See

CICS RACF Security Guide

the

for information about

CEDX provides the same function and diagnostic display panels as CEDF, and the same basic rules for CEDF also apply to CEDX.

Command syntax

42 CICS Supplied Transactions

CEDF—execution diagnostic facility

┌┐─,ON── ─ ──CEDX ──tranid ──┼ ┼────── ─ └┘─,OFF─

Command options

OFF

specifies that the EDF screen is to be switched OFF. If you specify OFF you must enter the preceding comma, as shown in the following example:

CEDX TRNA,OFF

specifies that the EDF screen is to be switched ON. The default is ON. If you specify ON you must enter the preceding comma, as shown in the following example:

CEDX TRNB,ON

tranid

specifies the identifier of a transaction that you want to test using the execution diagnostic facility. The diagnostic panels are displayed on the terminal at which you issue the CEDX

tranid

command.

The transaction you specify on the CEDX command must run in the local CICS region.

CEDX cannot interrupt transactions that are already running when you issue the CEDX command. It affects

after

only a transaction that starts command.

The following diagram illustrates the use of CEDX to invoke EDF for a transaction initiated by an EXEC CICS START command:

┌────────────┐ ┌────────────┐ │ CICS │ │ CICS user │ │ terminal │ ┌──────┐ │ terminal │ │ used ├─────────│ BBBB │ │ │ │ for EDF │ └──────┘ │Transaction │ │ │ Transaction │AAAA starts│ │ CEDX BBBB │ BBBB started │ BBBB │ └────────────┘ └────────────┘ The CEDX command is AAAA issues issued at this terminal, EXEC CICS START before BBBB is command to start started, to invoke EDF BBBB, without services to intercept and a terminal. debug the specified transaction.

you issue the

Chapter 10. Execution diagnostic facility CEDF & CEDX 43

CEDF—execution diagnostic facility

44 CICS Supplied Transactions

CEMT—master terminal

Chapter 11. CEMT—master terminal

Use CEMT to invoke all the master terminal functions. 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 CICS, alter the status of the system resources, terminate tasks, and shut down the CICS system.

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) CEOT (see page 213) CEST (see page 219).

The CECI transaction (see page 31 ) ) also uses the same command interpreter as CEMT.

You can start CEMT from IBM 3270 family display devices or equivalent terminals or from the system console. Starting 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 stated otherwise, that you are using a 3270 family display device or equivalent terminal.

To start CEMT, you can either enter the identifier CEMT on the command line by itself, or you can add options on the same line, separated by commas or blanks, to form a complete request.

If you start the transaction by entering CEMT by itself and pressing ENTER, you get a display that prompts you for more information, as described in “CEMT INQUIRE SYSTEM” on page 116.

Press the ENTER key. You get the following response:

à ð

STATUS: ENTER ONE OF THE FOLLOWING

Discard Inquire Perform Set

Figure 37. CEMT transaction: initial screen

This display prompts you to enter one of the keywords shown.

If you then type:

and press ENTER, you get the following screen:

à ð

D STATUS: ENTER ONE OF THE FOLLOWING

Autinstmodel PROGram

| Connection Requestmodel

DB2Conn TCLass

| DB2Entry TCPipservice

DB2Tran TDqueue

| DOctemplate TErminal

| Enqmodel TRansaction

| FENode TSmodel

FEPOol FEPRopset FETarget FIle JModel JOurnalname PArtner

| PROCesstype

PROFile

S At least 4 characters of DISCARD must be specified.

SYSID=JOHN APPLID=I

PF 1 HELP 3 END 5 VAR 9 MSG

Starting the CEMT transaction

Figure 38. CEMT transaction: DISCARD screen

You can construct a CEMT request in stages, or you can enter a complete request in one go. The CEMT transaction checks the syntax of requests and diagnoses errors. If your 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.

If you put a question mark (?) in front of your request, the syntax of your request is displayed but it is not processed.

After you have initiated the CEMT transaction, you need not reenter CEMT on subsequent requests, because the identifier is implied at the beginning of any further request. However, if you are using the system console, you must always start each master terminal request with CEMT.

Enter CEMT on the command line of the screen, as follows:

CEMT

 Copyright IBM Corp. 1982, 1999 45

If you type:

and press ENTER, you get the following screen:

à ð

I STATUS: ENTER ONE OF THE FOLLOWING OR HIT ENTER FOR DEFAULT

| AUTInstmodel FENode PROGram TSQueue

| AUTOinstall FEPOol REquestmodel UOW

| AUXtrace FEPRopset RRms UOWDsnfail

| CFdtpool FETarget STAtistics UOWLink

| COnnection FIle STReamname Vtam

| DB2Conn Gtftrace SYDumpcode Web

DB2Entry INttrace SYStem

DB2Tran IRc TAsk

| DEletshipped JModel TCLass

| DOctemplate JOurnalname TCPIP

| DSAs Line TCPIPService

DSName MODename TDqueue DUmpds MONitor TErminal

| ENQ Netname TRAnsaction

| ENQModel PArtner TRDumpcode

| EXci PROCesstype TSModel

| FEConnection PROFile TSPool

Figure 39. CEMT transaction: INQUIRE screen

CEMT—master terminal

If you type:

and press ENTER, you get the following screen:

à ð

P STATUS: ENTER ONE OF THE FOLLOWING

DEletshipped DUmp ENDaffinity RESet SEcurity SHUTdown SNap STatistics

Figure 40. CEMT transaction: PERFORM screen

If you type:

and press ENTER, you get the following screen:

à ð

S STATUS: ENTER ONE OF THE FOLLOWING OR HIT ENTER FOR DEFAULT

| AUToinstall Gtftrace TCPIPService

AUXtrace INttrace TDqueue Connection IRc TErminal DB2Conn Journalname TRAnsaction DB2Entry Line TRDumpcode

| DB2Tran MODename TSqueue

DEletshipped MONitor UOW

| DOctemplate Netname UOWLink

| DSAs PROCesstype Vtam

| DSName PROGram Web

| DUmpds Requestmodel

| Enqmodel STatistics

FEConnection SYDumpcode FENode SYStem FEPool TAsk FETarget TCLass

| FIle TCPIP

SYSID=JOHN APPLID=I

PF 1 HELP 3 END 5 VAR 9 MSG

PF2 switches the display of character values to

hexadecimal format on an expanded panel (see “Expanded panels” on page 48).

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 command, or by overtyping an old command, this key does not end your session; it is ignored.

PF5 gives a variables display. You can use this to create

values for use in a command.

PF7 scrolls backward half a screen. PF8 scrolls forward half a screen. PF9 expands messages. If more than one message has

been generated in response to your request, a message telling you how many messages have been generated appears near the bottom of the screen. PF9 lets you display all the messages on a separate display. Press ENTER to go back to your original display.

PF10 scrolls backward a full screen. PF11 scrolls forward a full screen.

Minimum abbreviation of keywords

CEMT accepts as few characters of a keyword as needed to uniquely identify it within the request. This means that you can enter the keyword TASK as TA or TAS, but you cannot use T, because it can be confused with TCLASS, TDQUEUE, TERMINAL, TRANSACTION, or TRDUMPCODE. You are prompted if the abbreviation you use is not unique. An exception to this rule is SHUTDOWN, for which you must specify at least SHUT.

Figure 41. CEMT transaction: SET screen

System parameters

If you press ENTER without selecting one of the CEMT keywords, INQUIRE SYSTEM is assumed and you get a display of the system parameters. Full details are given in “CEMT INQUIRE SYSTEM” on page 116.

Program function (PF) keys

When you start CEMT, the lower part of your display contains a list of PF keys. If your terminal does not have such keys, you can get the same effect by placing the cursor under a name in the list, and pressing ENTER.

Here is what the PF keys do: PF1 is a general HELP key. It also gives you a list of all the

PF keys and what they do.

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 the remainder in lowercase characters.

ALL option

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 unless you specify a terminal identifier, a terminal class identifier, or a system identifier.

ALL is not the default on a SET command, however. If you specify the ALL option on a SET command, any changes you request are made to all resources of the specified type that you are authorized to access.

If there are no resources of the type specified on the SET command, a response of NOT FOUND is given.

46 CICS Supplied Transactions

CEMT—master terminal

CLASS option

When operating on terminals, transactions, and programs, the CLASS option can be used to identify the suffix of a TLT, XLT, or PLT. This limits the scope of the INQUIRE or SET commands to those resources defined in the specified table. Any resources whose definitions have not been installed are displayed as NOT FOUND. For information about the TLT, the XLT, and the PLT, see the

Guide

CICS Resource Definition

Family of resources (using * and + symbols)

You can use the symbols * and + as part of an identifier to specify a family of resources. * represents any number of characters (including none), and + represents a single character, for example:

A* all identifiers beginning with A *DATA* all identifiers containing the characters DATA TERM00+ all 7-character identifiers starting with TERM00.

Use of * and + is restricted to selecting existing resources and cannot be used either to create a new set of resources or to discard resources.

| Note: The INQUIRE command and the SET command may | use the generic name in a different way. The | following two examples illustrate the difference:

| CEMT INQUIRE FI() DSN(ABCD) | lists all the files with data sets with a name

| beginning with ABCD. | CEMT SET FI() DSN(ABCD) CLO

| associates all your files with data set ABCD* and | closes them all.

Subdefining resource groups

When you make an inquiry, you can subdefine a resource group by specifying one or more attributes of the group. For example:

CEMT INQUIRE TERMINAL ALL INSERVICE

displays the status of all terminals that are in service. If the subdefined resource group has no members, CEMT

returns a NOT FOUND response. For example, if all the files in the system are closed, the command:

CEMT INQUIRE FILE ALL OPEN

gives the NOT FOUND response. You cannot subdefine a resource group on the SET

command in the same way. For example:

CEMT SET TERMINAL ALL INSERVICE PAGE

puts all terminals both in service and into page status. However, you can manage such groups of resources by

issuing an INQUIRE request, and overtyping the display produced.

Overtyping a display

When you issue an INQUIRE request, you usually get a display that consists of status information for each resource in the specified group. The status information is displayed as a list of abbreviated keywords. You can move the cursor to some fields and change their contents by overtyping. When you press the ENTER key again, CICS reads the contents of all fields that have been changed, and processes any valid operations implied by the changes. If you make an invalid change, you get an error message, and the field is not changed.

| Thus the generic name has the expected effect only | for the resource itself.

List of resource identifiers: You can specify a list of

resource identifiers, rather than a single one, separating the items in the list by commas or blanks. Any errors of syntax are reported.

| CEMT SET TERMINAL(TO1,TO2,TO3,TO4) INSERVICE

You cannot use * or + when the identifier is in a list of identifiers.

| Note: If you use the comma (,) in the name of a resource | identifier, you will not be able to use any commands | that permit the use of lists of resources, because the | comma will be treated as a list separator, and not as | a part of a name.

Chapter 11. Master terminal CEMT

When a field is overtyped, CEMT will accept and identify only as few characters as are necessary to uniquely identify the keyword within the valid options for that position. This is usually only one character.

On many of the status displays, the current status is displayed in certain positional fields at the right-hand side of the display. For some fields, the positional display appears only when the status of a particular resource is ‘on’. You can overtype the current status (when it is either displayed or blank) to change it.

So, for example, if you type ‘CEMT INQUIRE SYD’, you get a display of the current settings of the entries in the system dump table. The various attributes of those entries are displayed in fields across the screen. If CICS is to be shut 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.

CEMT—master terminal

The sequence of the positional fields is given in the descriptions of the various CEMT INQUIRE commands.

Whenever you overtype a display, not only is that particular action taken but all the status information is refreshed. You can avoid the overhead of a large number of table searches either by using the SET command, or by limiting your inquiry to a specific number of resources (either by using a ‘wild card’ in the search argument or by naming a range of resource identifiers).

Tab key

The fields you can change are different in each display. You can detect them, however, by pressing the tab key repeatedly. This causes the cursor to jump from one field to the next.

Scrolling symbol (+ sign)

A plus (+) sign on the first or last line of a display tells you that there is more data above or below your current display. Scrolling backward reveals data above, and scrolling forward reveals data below.

Blank fields in a display

Some displays contain blank fields that allow you to specify options, such as NEWCOPY, on the CEMT SET PROGRAM command, which are not part of the status of a resource. A status, such as NOREAD, which begins NO, is also represented by a blank field. You can detect these fields by using the tab key.

Expanded panels

You can select one resource item from a list, then check and change its options if required. Type the required CEMT INQUIRE or SET command name, then move the cursor to the relevant line on the display panel and press ENTER. This will result in an expanded display showing the attributes of the selected resource item. In the process, an INQUIRE command is executed for the associated resource.

For example, if you enter CEMT INQUIRE TERM, this gives the screen in Figure 43.

à ð

in task STATUS: RESULTS - OVERTYPE TO MODIFY

 Sample screen required 

Figure 43. Sample of screen showing a list of terminals

Move the cursor to the left of the first entry and press ENTER. This selects the first terminal, and displays the relevant information for that terminal (see Figure 44).

à ð

in term RESULT - OVERTYPE TO MODIFY Terminal(bell) Transaction()

Priority(  ) Pagestatus( Pageable ) Servstatus( Inservice ) Atistatus( Noati )

Ttistatus( Tti ) Nature(Local) Purgetype( ) Netname() Termstatus( ) Createsess( ) Task() Remotesystem() Rname() Rnetname() Cid()

Using the ? key

If you precede the command with ?, the syntax for that command appears on the screen. For example ?INQUIRE TERMINAL gives the list of options that you can specify with the inquiry command with the default highlighted. See Figure 42.

à ð

?INQ TERM STATUS: COMMAND SYNTAX CHECK CEMT Inquire TErminal()

Figure 42. Sample of screen showing the syntax of a INQUIRE command

Figure 44. Terminal settings for a selected terminal

Overtype the displayed settings if you want to make changes. Press ENTER to restore the original panel.

You can view a number of expanded panels in succession by 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.

Hexadecimal values

Some values such as TSQUEUE and NETUOWID may contain nondisplayable characters, which are shown as periods. You can use PF2 on the expanded panel to see the hexadecimal values of these characters. To switch back to character format, press PF2 again.

48 CICS Supplied Transactions

CEMT DISCARD

Variables

PF5 gives a display of variables, similar to that for the CECI command. Here are some examples of its use.

From a FILE display, you may wish to inquire of a particular DSNAME, which is typically 26 characters and can be up to 44 characters in length. Go to the expanded panel, position the cursor on the DSNAME line, and press PF5. You now have a variable &DSN with the required value. Type I DSN(&DSN) on the command line, and press ENTER.

You may wish to find all the TSQUEUE names beginning with a nondisplayable character—for example, X'FF'. Press PF5 for the variables display. Enter X and 2 to make a variable &X of length 2. Press PF2 to switch to hexadecimal, and overtype ‘4040’ with ‘FF5C’ (‘%c’ is hexadecimal for the asterisk (*) symbol). Type I TS(&X) on the command line and press ENTER.

For more information on the variables display, see the

Application Programming Guide

CICS

Invoking CEMT from an application program

Many of the CEMT INQUIRE and SET operations are available through the EXEC CICS INQUIRE and EXEC CICS SET commands; for programming information, see the

System Programming Reference

manual.

CICS

Security checking

The scope of a particular DISCARD, INQUIRE, SET, or PERFORM command can be limited by a combination of several levels of security checking. The normal transaction-attach security is described in the

Security Guide

process the user’s commands, in much the same way as CECI or a user’s command-level program would. The resource security and the command security used by the command-level programming interface are thus applicable to the master terminal user.

For programming information about command security checking, see the manual.

. CEMT calls the exec interface programs to

CICS System Programming Reference

CICS RACF

CEMT DISCARD commands

The DISCARD command allows you to remove an installed resource definition and its corresponding catalog entry from an active CICS system.

DISCARD does not affect the CICS system definition (CSD) file, and you can therefore reinstate the resource using CEDA INSTALL(resourcename). DISCARD commands require ALTER access to the resource to provide similar security to that for SET commands (which use UPDATE access). You cannot discard resources that are currently in use or are CICS owned resources (beginning with “DFH” or “C”).

You can discard the following resource types:  Autinstmodel

 Connection  DB2Conn  DB2Entry

 DB2Tran |  Doctemplate |  Enqmodel

 FEPI node

 FEPI pool

 FEPI property set  FEPI target  File  JModel  Journalname  Partner

|  Processtype

 Profile  Program

|  Requestmodel

 TClass

|  TCPIPservice

 TDqueue  Terminal  Transaction.

|  TSmodel

(Programming information about FEPI commands is in the

CICS Front End Programming Interface User's Guide

There are two ways to discard a resource:

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

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.

Chapter 11. Master terminal CEMT

CEMT DISCARD

and a screen similar to Figure 45 on page 50 appears. Use the carriage return key to move the cursor to the beginning of the line for the resource or resources you want to discard, and type “D” as shown and then press ENTER.

à ð

IN PROG STATUS: RESULTS - OVERTYPE TO MODIFY D Prog(ABCDTASK) Len(2936) Ass Pro Ena Pri Ced Res() Use()

Prog(DFHACP ) Len(8232) Ass Pro Ena Pri

Res(1) Use(2) Any Cex Ful

Prog(DFHAKP ) Len(5672) Ass Pro Ena Pri

Res() Use(1) Bel Cex Ful

Prog(DFHAMP ) Len(18432) Ass Pro Ena Pri

Res() Use(9) Any Cex Ful

Prog(DFHAPATT) Len(632) Ass Pro Ena Sha

Res(5) Use(18) Any Cex Ful

Prog(DFHBRCP ) Len() Ass Pro Ena Pri

Res() Use() Bel Cex Ful

Prog(DFHCCNV ) Len() Ass Pro Ena Pri

Res() Use() Any Cex Ful D Prog(ERRTASK ) Len(448) Ass Pro Ena Pri Res() Use()

Figure 45. Example of screen showing the discarding of resources

Notes:

1. A CEMT INQUIRE display can be used to discard more than one entry at a time. If you overtype another value as well as typing ‘D’, the ‘D’ is ignored.

2. When discarding a resource, the use of * or + in the resource name is not allowed.

CEMT DISCARD

Syntax

┌ ┐───────────────────────── ─ ──CEMT Discard ───

├ ┤──DB2Conn ────────────

| ├┤──Doctemplate(value)─ | ├┤──Enqmodel(value) ────

| ├┤──PROCesstype(value)─

| ├┤──Requestmodel(value) | ├┤──TCPIPservice(value)

| └┘──TSmodel(name) ──────



├┤──Autinstmodel(value) ├┤──Connection(value)──

├┤──DB2Entry(value) ──── ├┤──DB2TRAN(value) ─────

├┤──FENode(value) ────── ├┤──FEPool(value) ────── ├┤──FEPropset(value) ─── ├┤──FETarget(value) ──── ├┤──FIle(value) ──────── ├┤──JModel(value) ────── ├┤──JOurnalname(value)─ ├┤──PArtner(value) ─────

├┤──PROFile(value) ───── ├┤──PROGram(value) ─────

├┤──TClass(value) ──────

├┤──TDqueue(value) ───── ├┤──TErminal(value) ──── ├┤──TRansaction(value)─

┴┬┬───────────────────── ─

50 CICS Supplied Transactions

CEMT DISCARD

Options

AUTInstmodel(

specifies the name of the autoinstall model that is to be removed. The name can be up to 8 characters long. The DISCARD AUTINSTMODEL command removes the installed name of an autoinstall model from the autoinstall terminal model (AITM) table and the CICS catalog.

Connection(

specifies the 4-character identifier of the CONNECTION definition to be discarded. When a connection is removed, all its associated sessions are also removed.

For deletion to be successful:

 A non-remote connection must be out of service.  A remote connection must have no active sessions.  For MRO connections, the interregion

 If the local system is a member of a VTAM generic

In some unusual circumstances, it is possible for deletion of an LU61 connection to fail, even though the connection is out of service, because its sessions are still in-service. If this happens, set the connection INSERVICE, then OUTSERVICE, then reissue the DISCARD command.

DB2Conn(

Specifies that the currently installed DB2CONN is to be removed. You can only discard a DB2CONN when the CICS DB2 interface is not active. Note that discarding a DB2CONN also discards all currently installed DB2ENTRYs and DB2TRANs.

DB2Entry(

Specifies the name of an installed DB2ENTRY to be removed. A DB2ENTRY can only be discarded when it is in a disabled state.

DB2Tran(

Specifies the name of the DB2TRAN to be removed. Transaction IDs referenced by this DB2TRAN will be routed to the pool after the DB2TRAN is removed.

| DOctemplate( | Specifies the name of the document template to be | removed.

value

)

value

)

communications facility (IRC) must be closed. (You can use CEMT SET IRC CLOSED to close it.)

resource group, APPC synclevel 2 connections must not have any outstanding recovery information.

can

Other types of connection there is recovery work outstanding for them. However, it is recommended that you do not discard them if there is. You can use the INQUIRE CONNECTION RECOVSTATUS command to check.

value

)

value

)

value

)

value

)

be discarded, even if

| Enqmodel( | specifies the 8-character identifier of the resource to be | discarded.

FENode

FEPool

FEPropset

FETarget

FIle(

JModel(

JOurnalname(

PArtner(

value

)

This is described in the

Interface User's Guide

This is described in the

Interface User's Guide

This is described in the

Interface User's Guide

This is described in the

Interface User's Guide value

)

specifies the name of the file that is to be removed. The name can be up to 8 characters long. The DISCARD FILE command removes the installed name of a file from the CICS file control table and the CICS catalog.

value

)

specifies the name of the installed journal model that you want to remove. The name can be up to 8 characters long. The DISCARD JMODEL command removes the journal model name from the installed journal model table and the CICS catalog. It does not affect any existing journals that have been defined using the journal model name. These continue to use their existing definitions unless they are discarded using the DISCARD JOURNALNAME command.

value

)

specifies the journal name that you want to remove. The name can be up to 8 characters long. The DISCARD JOURNALNAME command removes the journal name from the journal table and the CICS catalog. It does not affect the VSAM data sets currently using the journal as a forward recovery log or autojournal; they continue to use the existing definition until the data sets are closed.

To discard journals defined with a numeric identifier for auto-journaling or forward recovery logs, specify the journal name as DFHJ number in the range 1–99.

Note: Specifying DFHJ01 on this command refers to a

user journal,

Any future reference to the journal name will cause it to be reinstalled using the journal model resource in effect at that time.

value

)

specifies the name of the partner that is to be removed. The name can be up to 8 characters long. The DISCARD PARTNER command removes the installed name of a partner from the CICS side information table and the CICS catalog.

CICS Front End Programming

, where

DFHJ01

is the journal

Chapter 11. Master terminal CEMT 51

CEMT DISCARD

| PROCesstype( | Specifies the 8–character name of the Processtype to be | removed. Only disabled processtypes can be discarded. | If you are using BTS in a sysplex, it is strongly | recommended that you use CPSM to remove them.

PROFile(

specifies the name of the profile that is to be removed. The name can be up to 8 characters long. The DISCARD PROFILE command removes the installed name of a profile from the CICS profile table (PFT) and the CICS catalog.

PROGram(

specifies the name of the program, map set, or partition set that is to be removed. The name can be up to 8 characters long. The DISCARD PROGRAM command removes the installed name of a program, map set, or partition set from the CICS processing program table (PPT) and the CICS catalog.

| Requestmodel( | Specifies the name of the Requestmodel resource | definition to be removed.

TCLass(

specifies the name of the transaction class that is to be removed. The name can be up to 8 characters long. The DISCARD TCLASS command removes the installed name of a transaction class from the CICS program control table (PCT) and the CICS catalog.

Note: ‘TRANCLASS’ is also accepted as a synonym for

| TCPipservice( | Specifies the name of the TCPIP service to be removed.

value

TCLASS.

value

)

value

)

value

)

TDqueue(

TErminal(

TRansaction(

value

)

specifies the name of the transient data queue that is to be removed from a running CICS system. The name can be up to 4 characters long.

Note: When you discard a transient data queue, an

implicit DELETEQ command is issued to free the control intervals used by the queue if the queue is an intrapartition queue. If the queue is a logically recoverable intrapartition queue, a syncpoint is taken after the DELETEQ request, but before the queue definition is discarded. This ensures that the associated control intervals have been freed before the definition is discarded.

value

)

specifies the name of the terminal to be removed. The name can be up to 4 characters long. The DISCARD TERMINAL command removes the installed name of a terminal from the terminal control table (TCT) and the CICS catalog.

Only terminals that use VTAM as an access method or consoles are eligible for deletion. Terminals that represent sessions cannot be deleted with DISCARD TERMINAL; use the DISCARD CONNECTION command instead.

value

)

specifies the name of the transaction that is to be removed. The name can be up to 8 characters long. The DISCARD TRANSACTION command removes the installed name of a transaction from the CICS program control table (PCT) and the CICS catalog.

value

)

52 CICS Supplied Transactions

CEMT INQUIRE COMMANDS  CEMT INQUIRE AUTINSTMODEL

CEMT INQUIRE commands

Most CEMT requests either inquire about (INQUIRE), or change (SET) the status of one or more named instances of a resource (such as a terminal), a particular subgroup of resources (such as a class of terminals), or all resources of a particular type (such as all terminals).

The INQUIRE command causes the status of the specified resources to be displayed. The SET command makes the changes that you specify, and displays the new status of the resources. No changes are made if there are syntax errors in the SET command.

If, for example, you want to inquire about a resource, enter INQUIRE (or a suitable abbreviation) on the command line. The keywords you can use with CEMT INQUIRE are described in the rest of this section.

If you want to perform those functions that are not concerned with resource status, enter PERFORM (or a suitable abbreviation) on the command line. The keywords you can use with PERFORM are described in “CEMT PERFORM commands” on page 155.

And finally, if you want to change the attributes of a 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.

If you enter INQUIRE, you get the following display:

à ð

INQ ─Command Line STATUS: ENTER ONE OF THE FOLLOWING OR HIT ENTER FOR DEFAULT ─Status Line

AUTInstmodel FENode PROGram TSQueue ─┐Resources

| AUTOinstall FEPOol REquestmodel UOW

| AUXtrace FEPRopset RRms UOWDsnfail

| CFdtpool FETarget STAtistics UOWLink

COnnection FIle STReamname Vtam

| DB2Conn Gtftrace SYDumpcode Web

DB2Entry INttrace SYStem DB2Tran IRc TAsk DEletshipped JModel TCLass

| DOctemplate JOurnalname TCPIP

| DSAs Line TCPIPService

DSName MODename TDqueue DUmpds MONitor TErminal

| ENQ Netname TRAnsaction

| ENQModel PArtner TRDumpcode

| EXci PROCesstype TSModel

| FEConnection PROFile TSPool

SYSID=CICS APPLID=CICSHTC1 PF 1 HELP 3 END 5 VAR 9 MSG ─PF keys

Figure 46. Sample of the screen following either the INQUIRE or the SET command

CEMT INQUIRE AUTINSTMODEL

Function: Find out whether a named autoinstall model is

present.

Description: The INQUIRE AUTINSTMODEL command

returns the names of all the autoinstall models installed in your system. There is no CEMT SET AUTINSTMODEL function, but the INQUIRE AUTINSTMODEL screens allow you to use the DISCARD function.

For information about autoinstall models, see the

Resource Definition Guide

Input: Press the Clear key and type CEMT INQUIRE

AUTINSTMODEL (the minimum abbreviation is CEMT I AUTI).

You will get a display screen, a sample of which is shown below.

If you do not type the name of a specific autoinstall model (the name can be up to 8 characters long—for example, cemt i auti(dfhlue2)), the names of all the autoinstall models will be displayed.

Sample screen

à ð

IN AUTIN STATUS: RESULTS Auti(DFHLUE2) Auti(DFHLUM2) Auti(DFHLUM3) Auti(DFHLUM4) Auti(DFHLUM5) Auti(DFHLU2 ) Auti(DFHLU2E2) Auti(DFHLU2E3) Auti(DFHLU2E4) Auti(DFHLU2M2) Auti(DFHLU2M3) Auti(DFHLU2M4) Auti(DFHLU2M5) Auti(DFHLU3 ) Auti(DFHLU62T) Auti(DFHSCSP ) Auti(DFH327 ) + Auti(DFH327P)

Figure 47. CEMT INQUIRE AUTINSTMODEL screen

Note: The ‘+’ symbol in the left margin by the last item on

the screen indicates that further model names are displayed when the PF8 key is pressed.

─ ──CEMT Inquire AUTInstmodel ────┬ ┬───── ─ └┘─All─

CICS

You can inquire about any of the displayed options by typing its keyword after INQUIRE on the command line. For example,

INQUIRE PROGRAM

gives you the status of all programs, and for each program

Displayed fields

All Automatic switching occurs as necessary until the end of

this CICS session without the need for operator intervention.

gives its attributes. Full details are given in “CEMT INQUIRE PROGRAM” on page 105.

Chapter 11. Master terminal CEMT 53

CEMT INQUIRE AUTOINSTALL

Function: Retrieve information about autoinstall values. Description: The INQUIRE AUTOINSTALL command

| displays information and parameters that control the | automatic installation (autoinstall) of VTAM terminals, APPC | connections, and MVS consoles.

For background information about autoinstall, see the

Resource Definition Guide

Input: Press the Clear key and type CEMT INQUIRE

AUTOINSTALL (the minimum abbreviation is CEMT I AUTO).

You will see a display screen, a sample of which is shown below. If you want to change any of the values shown, you can tab to the highlighted fields and overtype them as required.

Sample screen

à ð

INQ AUTOINSTALL STATUS: RESULTS - OVERTYPE TO MODIFY

Auto Max( 1ðð ) Pro( DFHZATDX ) Cur() Pro Ena

Figure 48. CEMT INQUIRE AUTOINSTALL screen

If you place the cursor against the result and press ENTER, CICS displays an expanded format as shown in Figure 49.

à ð

IN AUTOIN RESULT - OVERTYPE TO MODIFY Autoinstall

Maxreqs( 1 ) Program( DFHZATDX ) Curreqs(  )

| Consoles( Fullauto )

| Enablestatus( Enabled )

Figure 49. The expanded display of an individual entry

─ ──CEMT Inquire AUTOinstall ─

Displayed fields

AUTOinstall

identifies this panel as relating to terminal autoinstall.

| COnsoles( | displays the status of autoinstall for MVS consoles in the | CICS region. The values are:

value

)

CICS

| Noauto | Autoinstall for consoles is not active.

| Note: You can change this attribute by overtyping it | with a different value.

| Enablesatus(

value

)

| displays the overall status of the terminal autoinstall | facility, indicating whether CICS is enabled to install | VTAM terminals and MVS consoles. The values | displayed are:

| Disabled | Neither consoles nor terminals can be | autoinstalled in CICS. DISABLED is returned for | the following conditions:

value

Curreqs(

)

displays the number of autoinstall requests that are currently being processed. (This is not the number of terminals currently installed using autoinstall.)

Maximum(

value

)

displays the largest number of autoinstall requests that are allowed to queue at any one time. (This is not the largest number of terminals that can be installed using autoinstall.)

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

different value.

54 CICS Supplied Transactions

CEMT INQUIRE AUXTRACE

Program(

value

)

displays the name of the program that controls the autoinstall process. This is either the CICS-supplied default autoinstall program, DFHZATDX, or a user-written program.

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

different value.

CEMT INQUIRE AUXTRACE

Function: Retrieve information about the status of

auxiliary trace.

Description: Auxiliary trace entries are made to a pair of

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

Problem Determination Guide

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

CICS

Input: Press the Clear key and type CEMT INQUIRE

AUXTRACE (the minimum abbreviation is CEMT I AUX).

You will get a display screen, a sample of which is shown 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.

Chapter 11. Master terminal CEMT 55

CEMT INQUIRE AUXTRACE

à ð

I AUX RESULT - OVERTYPE TO MODIFY Auxtrace Curauxds(A)

Status( Stop ) Switchstatus( Noswitch )

Switchaction( )

Figure 51. The expanded display of an individual entry

─ ──CEMT Inquire AUXtrace ─

Displayed fields

Auxiliary

identifies this panel as relating to auxiliary trace.

value

Curauxds(

displays a 1-character identifier of the current auxiliary data set, which can be ‘A’ or ‘B’. This value is blank if there is no auxiliary trace data set.

STatus(

value

displays the status of auxiliary tracing in your CICS system. The values are:

Start Auxiliary tracing is in progress (the auxiliary trace

Pause

)

data set is open).

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.

Stop Auxiliary tracing has stopped, and the trace data

set is closed.

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

different value.

SWITCHAction(

value) (input only field

)

specifies that the trace data set is to be switched. The value is:

SWITCH

Makes an immediate switch from the current auxiliary trace data set to the alternate trace data set.

SWITCHStatus(

value

)

displays whether automatic data set switching is to occur when the current auxiliary trace data set becomes full. The values are:

Noswitch

Switching does not occur without operator intervention.

NExt Automatic switching occurs when the current trace

data set is full, but not subsequently.

ALl Automatic switching occurs as necessary until the

end of this CICS session without the need for operator intervention.

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

different value.

56 CICS Supplied Transactions

CEMT INQUIRE CFDTPOOL

| CEMT INQUIRE CFDTPOOL | Function: Retrieves information about coupling facility

| data table pools.

Description: INQUIRE CFDTPOOL returns information

| | about any currently installed CFDT pool names. CICS installs | these automatically whenever it installs a file resource | definition that refers to a CFDT.

Input: Press the Clear key to clear the screen, and type

| CEMT INQUIRE CFDTPOOL (the minimum abbreviation is CEMT I | CF). You get a display that lists the names and status of any | coupling facility data table pools to which CICS is connected | through a CFDT server. Note that you cannot change any of | the displayed information.

Sample screen

|à|

| inquire cfdt

| STATUS: RESULTS

| Cfd(DTPOOL1 ) Con

| SYSID=HA61 APPLID=CICSHA61

| 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 |

Figure 52. CEMT INQUIRE CFDTPOOL screen

| | ─ ──CEMT Inquire DOctemplate ──┬ ┬───────── ─────

| ─ ──┬ ┬──────────── ──┬ ┬────────── ──┬ ┬──────── ─── | └┘──Name(name) ├ ┤─Append─── ├ ┤─Ebcdic─ | └┘─Noappend─ └ ┘─Binary─

| ─ ──┬ ┬──────────────────── ───────────────────── | └┘──Templatename(name)

| ─ ──┬ ┬────────────────────────── ──┬ ┬──────── ─ | └ ┘| ─Templatename──(──name──)─ ├ ┤─DDname─ | └┘─DSname─

| Displayed fields | ALL

| This is the default. CICS displays the names of all | installed CFDT pools.

| CFdtpool( | displays information about a named CFDT pool.

| CICS creates a resource entry for a CFDT pool when a | file resource definition that refers to a coupling facility | data table is first installed. The resource entry is | cataloged, and reinstalled from the catalog on a warm or | emergency restart.

| Note: You cannot discard CFDT pool entries other than | by a cold or initial start of the CICS region.

| Connstatus | displays the connection status for the named CFDT pool. | The values are:

| Connected | The server for the coupling facility data table pool | is available in this MVS image, and CICS is | currently connected to it.

| Unconnected | The server for the coupling facility data table pool | is available in this MVS image, but CICS is not | currently connected to it.

| Unavailable | The server for the coupling facility data table pool | is currently unavailable in the MVS image.

value

)

Chapter 11. Master terminal CEMT 57

CEMT INQUIRE CONNECTION

Function: Retrieve information about system connections. Description: CEMT INQUIRE CONNECTION returns

information about the status of connections to a remote system or to another CICS region.

You can reset the options either by typing the SET command or by overtyping at the appropriate place on the INQUIRE screen.

If you want to install a new connection definition when one is already installed, and:

 You are using APPC,  You are using MRO,  You are using remote,  You are using LU6.1, you must set the connection

OUTSERVICE and, if it is VTAM-connected, release it before using the CEDA INSTALL commands for your new definition.

See the

CICS Resource Definition Guide

information about connections.

Input: Press the Clear key to clear the screen. There are

two ways of commencing this transaction:

 Type CEMT INQUIRE CONNECTION (the minimum

abbreviation is CEMT I C). You get a display that lists the current status.

 Type CEMT INQUIRE CONNECTION (CEMT I C) 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 c ins acq, the resulting display will show you the details of only those connections that are in service and acquired.

You can then tab to the highlighted or blank fields and overtype them with the required values.

for further

─ ──CEMT Inquire Connection ──┬ ┬──(value) ────── └┘─ALl─────

─ ──┬ ┬──────────────── ──┬ ┬──────────── ─────────

└┘──NEtname(value)├ ┤─NOTPending─

└┘─PEnding──── ─ ──┬ ┬──────────── ──┬ ┬─────────── ──────────────

├ ┤─INService── ├ ┤─ACquired── └ ┘─OUtservice─ ├ ┤─RELeased── ├┤─OBtaining─ ├┤─FReeing─── └┘─AVailable─

─ ──┬ ┬────────────── ──┬ ┬───────────── ──────────

| ├ ┤─NOTSupported─ ├ ┤─Vtam──────── | ├ ┤─Unattempted── ├ ┤─IRc───────── | ├ ┤─COMPlete───── ├ ┤─XM────────── | └ ┘─Failed─────── ├ ┤─INDirect────

├┤─XCf───────── └┘─RConnection─

─ ──┬ ┬────── ──┬ ┬────────── ──┬ ┬───────────── ──── ├ ┤─EXci─ ├ ┤─XOk────── ├ ┤─RECovdata─── ├ ┤─APpc─ └ ┘─XNotdone─ ├ ┤─NORecovdata─ └ ┘─Lu61─ └ ┘─NRs─────────

─ ──┬ ┬─────────────── ──┬ ┬─────────────────── ───

└┘──Grname(value)└ ┘──Membername(value)

─ ──┬ ┬───────────────────── ────────────────────

└┘──REMotesystem(value)

─ ──┬ ┬────────────── ──┬ ┬───────────────── ─

└┘──RNAme(value)└ ┘──RNEtname(value)

(

value

)

specifies one or more names (1–4 characters) defined for an interregion communication (IRC) or an intersystem communication (ISC) connection.

ALl

is the default.

Sample screen

à ð

IN CONN STATUS: RESULTS - OVERTYPE TO MODIFY Con(G1GA) Ins Irc Exci

Con(ISC1) Net(AUHZCIC1) Ins Acq Vta Appc Xok Unk Con(MRO2) Net(CICSHAA1) Ins Acq Irc Unk Con(MRO4) Net(CICSHAA2) Ins Acq Irc Unk Con(MRO5) Net(CICSHAA3) Ins Acq Irc Unk Con(MRO6) Net(CICSHAB1) Ins Acq Xcf

Figure 53. CEMT INQUIRE CONNECTION screen

Note: There are blank fields on the screen where a value

58 CICS Supplied Transactions

CEMT INQUIRE CONNECTION

If you place the cursor against a specific entry in the list and press ENTER, CICS displays an expanded format as shown in Figure 54 on page 59.

à ð

IN CONN

RESULT - OVERTYPE TO MODIFY Connection(MRO5) Netname(CICSHAA3)

Pendstatus( Notpending ) Servstatus( Inservice )

Connstatus( Acquired ) Accessmethod(Irc) Purgetype( ) Protocol() Xlnstatus()

Recovstatus( Norecovdata ) Uowaction( )

| Cqp( Notsupported )

Grname() Membername() Affinity( ) Remotesystem() Rname() Rnetname()

Figure 54. The expanded display of an individual entry

Displayed fields

Accessmethod

displays the access method in use for this connection.

The values are:

Vtam

The connection is used for intersystem communication (ISC).

IRc The connection is used for multiregion operation

(MRO), and has been defined to use the interregion communication (IRC) program for communication. If the CONNECTION is ACQUIRED, the MRO partner is running on the same MVS image. If the CONNECTION is RELEASED, the MRO partner may not be on the same MVS image; if it is not, the XCF access method will be used when the connection becomes ACQUIRED.

XM The connection is used for multiregion operation

(MRO) and has been defined to use MVS cross-memory (XM) services for communication. If the CONNECTION is ACQUIRED, the MRO partner is running on the same MVS image. If the CONNECTION is RELEASED, the MRO partner may not be on the same MVS image; if it is not, the XCF access method will be used when the connection becomes ACQUIRED.

INDirect

Communication between the local CICS system and the system defined by this connection is through the system named in the INDSYS operand of the connection definition.

XCf The connection is used for multiregion operation

(MRO), and communication uses the cross-system coupling facility (XCF) of MVS. XCF is used for MRO links between CICS regions on different MVS images within an MVS sysplex. It is selected dynamically by CICS for such links when the

access method is defined as IRC or XM in the connection definition.

RConnection

The connection is remote—that is, it is owned by another CICS system.

Affinity (

input only field

)

specifies, where CICS is a member of a VTAM generic resource group, that VTAM is to end an affinity owned by CICS. This option is valid only for APPC and LU61 connections. The connection must be out of service and in NORECOVDATA state. The value is:

Endaffinity

VTAM is to end an affinity owned by CICS.

value

Connection(

)

identifies this panel as relating to system connections, and displays the 4-character name by which the connection is known.

Connstatus

displays the state of the connection between CICS and a remote system. The remote system can be an APPC or an MRO partner identified by (

value

) on the CEMT INQUIRE CONNECTION command. The ACQUIRED and RELEASED values are common to both APPC and MRO; the others are unique to APPC. The values are:

ACquired (APPC and MRO)

The CONNECTION is acquired. The criteria for ACQUIRED for VTAM links are:

 The partner LU has been contacted.  Initial CNOS exchange has been done.

The criteria for ACQUIRED for MRO links are:

 Both sides of the link are in service.  Both sides of the link are successfully logged

on to the CICS interregion communication program (DFHIRP).

 A connection request by each side has been

successful for at least one session, and therefore each side can send and receive data.

RELeased (APPC and MRO)

The connection is released. Although the connection might be in service, it is not usable.

In the case of an MRO link, the released status can be caused by any one of a number of conditions. For example, it could be because the CICS region on the other side has not yet initialized, or not yet signed on to the CICS interregion communication program (DFHIRP); or it could be because CICS interregion communication may have been closed on the other side, or the connection on the other side may have been set out of service.

Chapter 11. Master terminal CEMT 59

CEMT INQUIRE CONNECTION

OBtaining (APPC only)

The connection is being acquired. The connection remains in the OBTAINING state until all the criteria for ACQUIRED have been met.

FReeing (APPC only)

The connection is being released.

AVailable (APPC only)

The connection is acquired but there are currently no bound sessions because they were unbound for limited resource reasons.

Connstatus can be reset with Acquired or Released.

| Cqp(

value

)

| displays the status of the connection quiesce protocol for | the connection. The values are:

| NOTSupported | The connection quiesce protocol is not supported | for this connection.

| Unattempted | CICS has not attempted to use the connection | quiesce protocol (because the connection has not | been released).

Grname(

Membername(

NEtname(

value) (appc only

displays (for an APPC connection to a generic resource when this system is also a generic resource) the 8-character generic resource name of the connected system. Otherwise this field is blank. CICS assumes that the partner is a generic resource if the two NETNAMEs sent with a BIND are different. Thus, information may be displayed for a partner that is but which uses XRF.

value

displays (for an APPC connection to a generic resource when this system is also a generic resource) the 8-character member name (applid) of the connected LU. Otherwise this field is blank. CICS assumes that the partner is a generic resource if the two NETNAMEs sent with a BIND are different. Thus, information may be displayed for a partner that is which uses XRF.

value

)

displays the 8-character name by which the remote system is known to the network.

)

not

a generic resource

)

not

a generic resource but

Pendstatus (

displays whether there are any pending units of work for this connection. The values are:

NOTPending

PEnding

Pendstatus can be reset with Notpending. For further information about pending units of work, see

the

Protocol

displays the protocol in use if this is a VTAM or external CICS interface connection. The values are:

APpc

EXci The connection uses the external CICS interface

appc and mro only

There has been no mismatch of lognames with the partner.

Note: MRO connections to pre-CICS Transaction

Server for OS/390 systems do not use lognames. Therefore, for these connections, PENDSTATUS is always NOTPENDING.

There is resynchronization work outstanding for the connection but the partner system has performed an initial start, preventing completion of the resynchronization process. (If the partner is a pre-CICS Transaction Server for OS/390 system, its performing a cold start has the same effect.) The units of work associated with the connection may need to be individually investigated and forced to commit or backout. Alternatively, the units of work can be unilaterally committed or backed out, according to their associated transaction definitions, by using the SET CONNECTION NOTPENDING command.

If this is an APPC connection, no new syncpoint work (that is, work involving synclevel 2 protocols) can be transmitted across it until a SET CONNECTION NOTPENDING command has been issued. This restriction does not apply to MRO connections.

If you are not concerned by the loss of synchronization caused by the initial (or cold) start of the partner, you can cause the SET CONNECTION NOTPENDING command to be issued automatically by specifying XLNACTION(FORCE) on the CONNECTION definition.

CICS Intercommunication Guide

The connection uses the VTAM LUTYPE6.2 protocol for intersystem communication, or is remote.

for communication between CICS and a non-CICS client program.

)

60 CICS Supplied Transactions

CEMT INQUIRE CONNECTION

Lu61

The connection uses the VTAM LUTYPE6.1 protocol for CICS-to-CICS or CICS-to-IMS intersystem communication.

Purgetype (

input only field

)

specifies how associated transactions are to be purged. The values are:

PUrge (

vtam only and irc only

)

Transactions running on the connected system are abnormally terminated. Transactions are terminated only if system and data integrity can be maintained. A transaction is not purged if its definition specifies SPURGE=NO.

FORCEPurge (

vtam only

)

All transactions running on sessions on the connected system are immediately terminated abnormally. This can lead to unpredictable results and should be used only in exceptional circumstances.

In some extreme cases (for example, if an error occurs during backout processing), CICS might terminate abnormally.

CAncel

Automatic initiate descriptors (AIDs) queuing for the specified connection are to be canceled.

AIDs representing scheduled and allocated requests waiting in the local CICS system for the specified connection are canceled. However, TD AIDs with an associated triggered task already started will not be canceled. In addition, the following CICS system AIDs are not purged unless FCANCEL is specified.

Table 1. System AIDs requiring FCANCEL to remove them

Description Tranid

Remote delete AIDs Remote scheduler AIDs CRSR LU6.2 service manager 1 AIDs CLS1 LU6.2 service manager 3 AIDs CLS3 Remote scheduler PURGE AIDs CRSQ Resource manager resync AIDs CRSY Autoinstalled terminal delete AIDs CATD Autoinstalled terminal restart AIDs CATR

When a canceled SCHEDULE request is found to have a precursor in a remote CICS system, that is, the AID was originally scheduled in a remote system, the remote AID is canceled asynchronously.

Message DFHTF0100 is written to CSMT to indicate how many AIDs have been deleted for the connection 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 CONNECTION command.

FCancel

All AIDs, including system AIDs, queuing for the specified connection are to be canceled. See Table 1 for a list of those system AIDS that require FCANCEL to remove them. This can lead to unpredictable results and should be used only in exceptional circumstances.

Note: FCANCEL does not remove transient data

AIDs with an associated triggered task. These aids may be removed by purging the associated task.

An ‘AIDS CANCELED’ message appears on the CEMT panel whenever AIDs are deleted using the FCANCEL option of the CEMT SET CONNECTION command.

Recovstatus (

appc and mro only

)

displays whether there is resynchronization work outstanding for this connection. The connection may never have been connected, or may have been quiesced and all resynchronization work completed, or disrupted without quiesce—in which case resynchronization may be necessary. The values are:

NORecovdata

Neither side has recovery information outstanding.

NRs CICS does not have recovery outstanding for the

connection, but the partner may have.

RECovdata

There are in-doubt units of work associated with the connection, or there are outstanding resyncs awaiting FORGET on the connection. Resynchronization takes place when the connection next becomes active, or when the UOW is unshunted.

If there is recovery outstanding, on completion of exchange of lognames either resynchronization takes place or, in the case of a cold exchange, the PENDING condition is created.

Recovstatus can be reset with Norecovdata.

value

REMotesystem(

)

displays the 4-character name of a connection, if the subject of the inquiry is a remote or an indirect connection. In either case, the named connection can be either a connection entry that links towards the TOR, or an indirect connection that provides the netname of the TOR.

If the subject of the inquiry is an indirect connection, the value of REMOTESYSTEM is taken from the INDSYS option of the CONNECTION definition.

Otherwise this field is blank.

Chapter 11. Master terminal CEMT 61

CEMT INQUIRE CONNECTION

RNAme(

RNEtname(

Servstatus

Uowaction (

value

)

displays the 4-character name by which this connection is known in a remote system, if the subject of the inquiry is a remote connection.

value

)

displays the 8-character netname of the owning TOR, if the subject of this inquiry is a remote connection. If it is blank, but the connection is remote, the system named in the REMOTESYSTEM field has not been installed, and no value was specified for the REMOTESYSNET option when the connection was defined.

displays whether the system can receive and send data. The values are:

INService

The system is in service; that is, it is available for use.

OUtservice

The system is out of service; that is, it is not available for use.

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

different value.

input-only field

specifies that the normal resynchronization process is to be partially overridden. The value specifies the type of decision to be taken for any units of work that become in-doubt due to a failure of the connection; the decisions are recorded and any data inconsistencies are reported when the connection is next acquired. The values are:

Backout

All UOWs shunted due to the failure of this connection are to be backed out.

COMMit

All UOWs shunted due to the failure of this connection are to be committed.

)

FORCEUow

All UOWs shunted due to the failure of this connection are to be forced to BACKOUT or COMMIT, as specified on the INDOUBT option of the TRANSACTION definition.

Resync

Any UOWs shunted due to the failure of this connection are to be retried (that is, exchange lognames resynchronization for this connection is to be attempted). This process should normally be started automatically when a connection is acquired or when a UOW is unshunted.

Xlnstatus

displays the status of the exchange lognames (XLN) process. The values are:

XOk (

appc only

The exchange log names (XLN) process for the APPC connection has completed successfully.

XNotdone (APPC only)

The exchange log names (XLN) flow for the APPC connection has not completed successfully. The CSMT log can contain information relating to this state. Synchronization level 2 conversations are not allowed on the connection, but synchronization levels 0 and 1 are still allowed.

No status is displayed if exchange log names is not applicable. This can be because the link:

 Is released

 Is MRO, LU6.1, or single-session APPC  Does not support synchronization level 2

conversations.

For information about the APPC exchange log names process, see the

)

CICS Intercommunication Guide

62 CICS Supplied Transactions

CEMT INQUIRE DB2CONN

Function: Retrieves information about the CICS DB2

connection.

Description: INQUIRE DB2CONN returns information

about the attributes of the currently installed DB2CONN, which defines the connection to DB2.

Note that because there can be only one DB2CONN installed at a time, the name of the DB2CONN is not required on input.

Input: Press the Clear key to clear the screen, and type

CEMT INQUIRE DB2CONN. You get a display that lists the current status. You can then tab to the highlighted or blank fields and overtype them with the required values.

Sample screen

à ð

inquire db2conn STATUS: RESULTS - OVERTYPE TO MODIFY

Accountrec( None ) Priority( High ) Authid( ) Purgecyclem(  ) Authtype( Userid ) Purgecycles( 3 ) Comauthid( ) Signid( CICSHTC1 ) Comauthtype( Cuserid ) Security( ) Comthreadlim( 1 ) Standbymode( Reconnect ) Comthreads() Statsqueue( CDB2 ) Connecterror( Sqlcode ) Tcblimit( 12 ) Connectst( Notconnected ) Tcbs() Db2id( DB2A ) Threaderror(N96d) Db2release() Threadlimit( 3 )

Drollback(Rollback) Threads()

Msgqueue1( CDB2 ) Threadwait( Twait ) Msgqueue2( ) Msgqueue3( )

Nontermrel( Release ) Plan( )

Planexitname( DSNCUEXT )

Figure 55. CEMT INQUIRE DB2CONN screen

─ ──CEMT Inquire DB2Conn ─

Displayed fields

Accountrec

returns the minimum amount of DB2 accounting required

for transactions using pool threads. The specified

minimum may be exceeded, as described in the

following options. The values are:

UOW

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

The CICS DB2 attachment facility causes a minimum of one accounting record to be produced for each CICS task.

A transaction containing multiple UOWs may use 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.

Because pool threads are typically used by a number of different transaction IDs, there is an increased chance that a transaction containing multiple UOWs will use a different thread for each UOW (assuming the thread is released at syncpoint. In this case, an accounting record may be produced for each UOW.

None

No accounting records are required for transactions using pool threads.

DB2 does, however, produce at least one accounting record for each thread when the thread is terminated. Additionally, authorization changes cause accounting records to be produced.

Authid

returns an id to be used for security checking when using pool threads. If an AUTHId is returned, AUTHType is not applicable.

Authtype

returns the type of id to be used for security checking when using pool threads. If an AUTHType is returned, AUTHid is blank. The values are:

Group

The 8-character USERID and the connected group name are used as the authorization ID. The following table shows how these two values are interpreted by DB2.

IDs passed to DB2 How DB2 interprets values

CICS sign-on user ID (USERID)

RACF connected group name

Represents the primary DB2 authorization ID.

If the RACF list of group options is not active, DB2 uses the connected group name supplied by the CICS attachment facility as the secondary DB2 authorization ID. If the RACF list of group options is active, DB2 ignores the connected group name supplied by the CICS attachment facility, but the value appears in the DB2 list of secondary DB2 authorization IDs.

If no RACF group ID is available for this USERID, an 8-character field of blanks is passed to DB2 as the group ID.

Sign The SIGNID parameter of the DB2CONN is used

as the resource authorization ID.

Chapter 11. Master terminal CEMT

CEMT INQUIRE DB2CONN

Tern The terminal identification (four characters padded

to eight) is used as an authorization ID. An authorization ID cannot be obtained in this manner if a terminal is not connected with the transaction.

If a transaction is started (using a CICS command) and has no terminal associated with it, AUTHTYPE(TERM) should not be used.

Tx The transaction identification (four characters

padded to eight) is used as the authorization ID.

Opid

The user operator identification associated with the userid, associated with the CICS transaction, is used as the authorization ID (three characters padded to eight).

Userid

The 8-character USERID associated with the CICS transaction is used as the authorization ID.

When the DB2 sample sign-on exit DSN3@SGN is used with AUTHTYPE(USERID), the exit sends the USERID to DB2 as the primary authorization ID and the RACF group ID to DB2 as the secondary ID. When the sample sign-on exit is used, there is no difference between AUTHTYPE(USERID) and AUTHTYPE(GROUP).

Comauthid

returns an ID to be used for security checking when using command threads. If COMAUTHType is returned, COMAUTHid is not applicable.

Comauthtype

returns the type of ID to be used for security checking when using command threads. If COMAUTHType is returned, COMAUTHid is blank. The values are:

If no RACF group ID is available for this USERID, an 8-character field of blanks is passed to DB2 as the group ID.

Csign

The SIGNID parameter of the DB2CONN is used as the resource authorization ID.

Cterm

The terminal identification (four characters padded to eight) is used as an authorization ID. An authorization ID cannot be obtained in this manner if a terminal is not connected with the transaction.

If a transaction is started (using a CICS command) and has no terminal associated with it, COMAUTHTYPE(CTERM) should not be used.

Ctx The transaction identification (four characters

padded to eight) is used as the authorization ID.

Copid

The operator identification associated with the userid that is associated with the CICS transaction is used as the authorization ID (three characters padded to eight).

Cuserid

The 8-character USERID associated with the CICS transaction is used as the authorization ID.

When the DB2 sample sign-on exit DSN3@SGN is used with COMAUTHTYPE(CUSERID), the exit sends the USERID to DB2 as the primary authorization ID and the RACF group ID to DB2 as the secondary ID. When the sample sign-on exit is used, there is no difference between COMAUTHTYPE(CUSERID) and COMAUTHTYPE(CGROUP).

Cgroup

The 8-character USERID and the connected group name are used as the authorization ID. The following table shows how these two values are interpreted by DB2.

IDs passed to DB2 How DB2 interprets values

CICS sign-on user ID (USERID)

RACF connected group name

Represents the primary DB2 authorization ID.

Comthreads

returns the current number of active command threads.

Comthreadlim

returns the current maximum number of command threads the CICS DB2 attachment allows active before requests overflow to the pool.

Connecterror

returns a value when CICS is not connected to DB2 because the adapter is in 'standby mode'. The value shows how this information is to be passed back to an application that has issued a SQL request. The values are:

Abend

The application is abended with abend AEY9.

Sqlcode

The application receives a -923 SQLCODE.

64 CICS Supplied Transactions

CEMT INQUIRE DB2CONN

Connectst

returns the status of the CICS DB2 connection. The

values are:

Connected

CICS is connected to DB2.

Notconnected

CICS is not connected to DB2.

Connecting

CICS is currently attempting to connect to DB2.

Disconning

CICS is currently disconnecting from DB2.

DB2id

returns the name of the DB2 subsystem that the CICS

DB2 attachment is connected to or is to connect to.

DB2release

returns a four-character value indicating the version and

release level of the DB2 susbsytem CICS is connected

to. When CICS is not connected to DB2, blanks are

returned.

Drollback

returns a value showing whether the CICS DB2

attachment is to initiate a SYNCPOINT ROLLBACK if a

transaction is selected as victim of a deadlock resolution.

The values are:

Rollback

the attachment facility issues a sync point rollback before returning control to the application. An SQL return code of -911 is returned to the program.

Norollback

the attachment facility does not initiate a rollback for a transaction. An SQL return code of -913 is returned to the application.

Msgqueue1

returns the name of the first transient data destination to

which unsolicited messages from the CICS DB2

attachment are sent.

Msgqueue2

returns the name of the second transient data

destination to which unsolicited messages from the CICS

DB2 attachment are sent.

Msgqueue3

returns the name of the third transient data destination to

which unsolicited messages from the CICS DB2

attachment are sent.

Nontermrel

returns a value showing whether non-terminal

transactions are to release threads for reuse at

intermediate syncpoints. CVDA values are:

Release

non-terminal transactions release threads for reuse at intermediate syncpoints.

Norelease

non-terminal transactions do not release threads for reuse at intermediate syncpoints.

Plan

returns the name of the plan used for the pool. If a plan name is returned, PLANEXITNAME is blank,

Planexitname

returns the name of the dynamic plan exit used for pool threads. If a PLANEXITNAME is returned, PLAN is blank,

Priority

returns the priority of the pool thread subtasks relative to the CICS main task (QR TCB). CVDA values are:

High subtasks attain a higher priority than the CICS

main task from which the subtask was generated.

Equal

subtasks have equal priority with the CICS main task.

Low subtasks have a lower priority than the CICS main

task.

Purgecyclem

returns in minutes the length of the protected thread purge cycle. The range for PURGECYCLEM is 0-59.

A protected thread is not terminated immediately when it is released. It is terminated only after two completed purge cycles, if it has not been reused in the meantime. Hence if the purge cycle is set to 30 seconds after it is released, a protected thread will be purged 30 - 60 seconds after it is released. An unprotected thread is terminated when it is released (at syncpoint or end of task) if there are no other transactions waiting for a thread on that DB2ENTRY.

Purgecycles

returns in seconds the length of the protected thread purge cycle. The range for PUrgecycles is 30-59.

Signid

returns the authorization ID to be used by the CICS DB2 attachment when signing on to DB2 for pool and DB2 entry threads specifying AUTHTYPE(SIGNID) and command threads specifying COMAUTHTYPE(CSIGN).

Security

has no meaning for INQUIRE. It is supplied to allow overtyping with the REBUILD option, to initiate a CEMT

Chapter 11. Master terminal CEMT 65

CEMT INQUIRE DB2CONN

SET DB2CONN. See SECURITY(REBUILD) on page170.

Standbymode

returns the action to be taken by the CICS DB2 attachment if DB2 is not active when an attempt is made to start the connection from CICS to DB2. The values are:

Noconnect

The CICS DB2 attachment terminates.

Connect

The CICS DB2 attachment goes into 'standby mode' to wait for DB2.

Reconnect

The CICS DB2 attachment goes into 'standby mode' and waits for DB2. Having connected to DB2, if DB2 subsequently fails the CICS DB2 attachment reverts again to standby mode and subsequently reconnects to DB2 when it comes up again.

Statsqueue

returns the transient data destination for CICS DB2 attachment statistics produced when the CICS DB2 attachment is shutdown.

Tcbs

returns the current number of subtask TCBs attached to service command, pool, and DB2ENTRY threads.

Tcblimit

returns the current maximum number of subtasks that can be identified to DB2.

Threaderror

returns the processing that is to occur following a create thread error. The values are:

Abend

| For a second or subsequent SQL error the

transaction abends with abend code AD2S, AD2T or AD2U, dependent on the type of error that

occurred. The transaction must be terminated and reinitialized before it is allowed to issue another SQL request.

N906D

A transaction dump is taken and the DSNCSQL RMI associated with the transaction is disabled. The transaction receives a -906 SQLCODE if another SQL is issued, unless the transaction issues SYNCPOINT ROLLBACK. SYNCPOINT without the ROLLBACK option results in an ASP3 or ASP7 abend. The transaction dump records an abend of AD2S, AD2T or AD2U.

N906

The DSNCSQL RMI associated with the

not

transaction is receives a -906 SQLCODE if another SQL request is issued, unless the transaction issues a SYNCPOINT ROLLBACK. SYNCPOINT without the ROLLBACK option results in an ASP3 or ASP7 abend.

Threadlimit

returns the current maximum number of pool threads the CICS DB2 attachment allows active before requests are made to wait or are rejected (see THREADWait).

Threads

returns the current number of active pool threads.

Threadwait

returns a value showing whether transactions should wait for a pool thread or be abended if the number of active pool threads reaches the threadlimit number. The values are:

Twait

If all threads are busy, a transaction waits until one becomes available.

Notwait

If all threads are busy, a transaction is terminated with an abend code AD3T.

to be disabled. The transaction

not

to be

66 CICS Supplied Transactions

CEMT INQUIRE DB2ENTRY

Function: Returns the attributes of the DB2ENTRY that

defines resources to be used by a specific transaction or by a group of transactions when accessing DB2.

Description: The entry is identified by the name with

which it was defined in CEDA.

Input: For RCTs migrated to the CSD, the name is the

name of the first transaction on the DSNCRCT TYPE=ENTRY statement unless the RDONAME parameter has been specified.

Sample screen

à ð

inquire db2entry STATUS: RESULTS - OVERTYPE TO MODIFY

Db2e(DB2ENT1 ) Use Ena Poo Hig Pro(  ) Pth()

Threadl(  ) Threads() Tpo Plane( DSNCUEXT

Db2e(DB2ENT2 ) Use Ena Poo Hig Pro(  ) Pth()

Threadl(  ) Threads() Tpo Plane( DSNCUEXT

Figure 56. CEMT INQUIRE DB2ENTRY screen

If you place the cursor against the result and press ENTER, an expanded format is displayed as shown in Figure 57.

à ð

inquire db2entry

RESULT - OVERTYPE TO MODIFY

Db2entry(DB2ENT1)

Accountrec( None )

Authtype( Userid )

Enablestatus( Enabled )

Disabledact( Pool )

Priority( High )

Protectnum(  ) Pthreads()

Threadlimit(  ) Threads()

Threadwait( Tpool ) Plan( )

Planexitname( DSNCUEXT ) Authid( ) Drollback(Rollback)

─ ──CEMT Inquire DB2Entry(data-area)──┬ ┬─────────────── ─────

└┘──AT(data-area)

─ ──┬ ┬─────── ──┬ ┬────────────────── ──┬ ┬─────────────────── ───

├┤─START─ ├ ┤──ACCOUNTREC(cvda)└ ┘──AUTHID(data-area) ├ ┤─END─── ├ ┤─UOW────────────── └ ┘─NEXT── ├ ┤─TASK───────────── ├ ┤─TXID───────────── └ ┘─NONE─────────────

─ ──┬ ┬──────────────── ──┬ ┬─────────────────── ────────────────

├┤──AUTHTYPE(cvda)├ ┤──DISABLEDACT(cvda) ├ ┤─GROUP────────── ├ ┤─ABEND───────────── ├ ┤─SIGN─────────── ├ ┤─SQLCODE─────────── ├ ┤─TERM─────────── └ ┘─POOL────────────── ├ ┤─TX───────────── ├ ┤─OPID─────────── └ ┘─USERID─────────

─ ──┬ ┬───────────────── ──┬ ┬──────────────────── ──────────────

├┤──DROLLBACK(cvda)├ ┤──ENABLESTATUS(cvda) ├ ┤─ROLLBACK──────── ├ ┤─ENABLED──────────── └ ┘─NOROLLBACK────── ├ ┤─DISABLED─────────── └┘─DISABLING──────────

─ ──┬ ┬───────────────── ──┬ ┬───────────────────────── ─────────

└┘──PLAN(data-area)└ ┘──PLANEXITNAME(data-area) ─ ──┬ ┬──────────────── ──┬ ┬─────────────────────── ────────────

├┤──PRIORITY(cvda)└ ┘──PROTECTNUM(data-area) ├ ┤─HIGH─────────── ├ ┤─EQUAL────────── └ ┘─LOW────────────

─ ──┬ ┬───────────────────── ──┬ ┬──────────────────────── ──────

└┘──PTHREADS(data-area)└ ┘──THREADLIMIT(data-area) ─ ──┬ ┬──────────────────── ──┬ ┬────────────────── ────────────

└┘──THREADS(data-area)├ ┤──THREADWAIT(cvda) ├┤─TWAIT──────────── ├┤─NOTWAIT────────── └┘─TPOOL────────────

Displayed fields

ACcountrec

returns the minimum amount of DB2 accounting record required for transactions using this DB2ENTRY. The specified minimum may be exceeded, as described in the following options. The values are:

Figure 57. The expanded display of an individual entry

UOW

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

The CICS DB2 attachment facility causes a minimum of one accounting record for each CICS task to be produced.

A transaction containing multiple UOWs may use 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

Chapter 11. Master terminal CEMT 67

CEMT INQUIRE DB2ENTRY

containing multiple UOWs may use a different thread for each UOW. The result may be that an accounting record is produced for each UOW.

NOne

No accounting records are required for transactions using threads from this DB2ENTRY.

DB2 does, however, produce at least one accounting record for each thread when the thread is terminated. Additionally, authorization changes cause accounting records to be produced.

AUTHId

returns an ID to be used for security checking when using pool threads. If an AUTHId is returned, AUTHType is not applicable.

AUTHType

returns the type of ID to be used for security checking for threads on this DB2ENTRY. If an AUTHType is returned, AUTHid is blank. The values are:

Group

The 8-character userid and the connected group name are used as the authorization ID. The following table shows how these two values are interpreted by DB2.

IDs passed to DB2 How DB2 interprets values

CICS sign-on user ID (USERID)

RACF connected group name

Represents the primary DB2 authorization ID.

If the RACF list of group options is not active, then DB2 uses the connected group name supplied by the CICS attachment facility as the secondary DB2 authorization ID. If the RACF list of group options is active, DB2 ignores the connected group name supplied by the CICS attachment facility, but the value appears in the DB2 list of secondary DB2 authorization IDs.

If no RACF group ID is available for this USERID, then an 8-character field of blanks is passed to DB2 as the group ID.

Sign The SIGNID parameter of the DB2CONN is used

as the resource authorization ID.

TErm

If a transaction is started (using a CICS command) and has no terminal associated with it, AUTHTYPE(TERM) should not be used.

TX The transaction identification (four characters

padded to eight) is used as the authorization ID.

OPid

The operator identification associated with the userid that is associated with the CICS transaction is used as the authorization ID (three characters padded to eight).

USerid

The 8-character USERID associated with the CICS transaction is used as the authorization ID.

DIsabledact

returns a value showing what CICS is to do with new transactions accessing DB2ENTRY when it has been disabled or is disabling. If DISABLEDACT is not specified, and DB2ENTRY is disabled, new requests are routed to the pool by default. The values are:

Pool The CICS DB2 attachment facility routes the

request to the pool. Message DFHDB2072 is sent to the transient data destination specified by MSGQUEUEn on the DB2CONN for each transaction routed to the pool.

ABend

The CICS DB2 attachment facility abends the transaction.The abend code is AD26.

SQlcode

An SQLCODE is returned to the application indicating that the DB2ENTRY is disabled.

DRollback

returns returns a value showing whether the CICS DB2 attachment should initiate a SYNCPOINT rollback if a transaction is selected as victim of a deadlock resolution. The values are:

Rollback

The attachment facility issues a sync point rollback before returning control to the application. An SQL return code of -911 is returned to the program.

NORollback

The attachment facility does not initiate a rollback for this transaction. An SQL return code of -913 is returned to the application.

ENAablestatus

returns a cvda indicating whether the DB2ENTRY can be accessed by applications. The values are:

Enabled

The DB2ENTRY can be accessed by applications. DB2ENTRY is installed in an ENABLED state.

Disabled

The DB2ENTRY cannot be accessed by applications.

68 CICS Supplied Transactions

CEMT INQUIRE DB2ENTRY

DISabling

The DB2ENTRY is in the process of being disabled. New transactions cannot access the DB2ENTRY. Existing transactions using the DB2ENTRY will be allowed to complete unless the DB2ENTRY is being disabled with the FORCE option.

PLAN

returns the name of the plan to be used for this DB2ENTRY. If PLAN is returned, PLANEXITNAME is blank.

PLANExitname

returns the name of the dynamic plan exit (if any) to be used for this DB2ENTRY. If PLANEXITname is returned, PLAN is blank.

PRIority

returns the priority of the thread subtasks for this DB2ENTRY relative to the CICS main task (QR TCB). The values are:

High subtasks attain a higher priority than the CICS

main task from which the subtask was generated.

Equal

subtasks have equal priority with the CICS main task.

Low subtasks have a lower priority than the CICS main

task.

PROtectnum

returns the maximum number of protected threads allowed for this DB2ENTRY.

PTheads

returns the current number of protected threads for this DB2ENTRY. A protected thread is an inactive thread

available for reuse by a new transaction. If no transaction has reused the thread by the time it has been processed by 2 purge cycles, the thread is terminated.

THREADS

returns the current number of threads active for this DB2ENTRY.

THREADLimit

returns the current maximum number of threads for this DB2ENTRY that the CICS DB2 attachment allows active before requests are made to wait, overflow to the pool, or are rejected (see THREADWait).

THREADWait

returns whether or not transactions should wait for a DB2ENTRY thread be abended, or overflow to the pool if the number of active DB2ENTRY threads reach the Threadlimit number. The values are:

TWait

If all threads are busy, a transaction waits until one becomes available.

NOTwait

If any threads are busy, a transaction is terminated with an abend code AD2P.

TPOOL

If all threads are busy, a transaction is diverted to use a pool thread. If the pool is also busy, and NOTWAIT has been specified for the THREADWAIT parameter on the DB2CONN, the transaction is terminated with an abend code AD3T.

Chapter 11. Master terminal CEMT 69

CEMT INQUIRE DB2TRAN  CEMT INQUIRE DELETSHIPPED

CEMT INQUIRE DB2TRAN

Function: Returns attributes of a particular DB2TRAN that

associates a transaction or group of transactions with a DB2ENTRY.

Description: The DB2TRAN is identified by the name it

was defined with in CEDA. For RCTs migrated to the CSD, the name is the same as the transaction for which the DB2TRAN is being created.

Input: If a TRANSID is specified on a DB2ENTRY when

the DB2ENTRY is installed, CICS installs a DB2TRAN named DFHtttt, where tttt is the TRANSID.

Sample screen

à ð

inquire db2tran STATUS: RESULTS - OVERTYPE TO MODIFY

Db2t(DFHTXN ) Db2e( DB2ENT2 ) Tra( TXN ) Db2t(DFHTXN2 ) Db2e( DB2ENT1 ) Tra( TXN2 ) Db2t(TXN1 ) Db2e( DB2ENT1 ) Tra( TXN1 )

Figure 58. CEMT INQUIRE DB2TRAN screen

If you place the cursor against the result and press ENTER, an expanded format is displayed as shown in Figure 59.

CEMT INQUIRE DELETSHIPPED

Function: Display system settings that control the CICS

timeout delete mechanism.

Description: The CICS timeout delete mechanism is

invoked at user-specified intervals to remove any shipped terminal definitions that have not been used for longer than a user-specified time.

INQUIRE DELETSHIPPED displays the current settings of the parameters that control the mechanism.

Input: Press the Clear key and type CEMT INQUIRE

DELETSHIPPED (the minimum abbreviation is CEMT I DE). You

will get a display screen. To change attributes, you can:

 Overtype your changes on the INQUIRE screen after

tabbing to the appropriate field.

 Use the CEMT SET DELETSHIPPED command.

Sample screen

à ð

IN DELE STATUS: RESULTS - OVERTYPE TO MODIFY

Del Int( 12 ) Idl( 2 )

à ð

inquire db2tran

RESULT - OVERTYPE TO MODIFY Db2tran(DFHTXN) Db2entry( DB2ENT2 )

Transid( TXN )

Figure 59. The expanded display of an individual entry

──CEMT Inquire DB2Tran─ ──┬ ┬───────────── ─────

└┘──(data-area)

─ ──┬ ┬───────────────────── ────────────────────

└┘──DB2Entry(data-area)

─ ──┬ ┬──────────────────── ─

└┘──Transid(data-area)

Displayed fields

DB2Entry

returns the name of the DB2ENTRY to which this DB2TRAN refers. This is the DB2ENTRY with which this additional transaction should be associated.

Transid

specifies the transaction ID to be associated with the entry. The transaction id can include wildcard characters (see the about use of wildcard characters).

CICS Resource Definition Guide

for information

Figure 60. CEMT INQUIRE DELETSHIPPED screen

If you place the cursor against the result and press ENTER, CICS displays an expanded format as shown in Figure 61.

à ð

IN DELE

RESULT - OVERTYPE TO MODIFY

Deletshipped

Interval( 12 ) Idle( 2 )

Figure 61. The expanded display

─ ──CEMT Inquire DEletshipped ───────────────── ─ ──┬ ┬───────────── ──┬ ┬───────────────── ─

└┘──IDle(value)└ ┘──INterval(value)

Displayed fields

DEl

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

70 CICS Supplied Transactions

CEMT INQUIRE DOCTEMPLATE

installed in this region. When the CICS timeout delete mechanism is invoked, only those shipped definitions that have been inactive for longer than this time are deleted.

The time interval can be in the range 00-99 hours; 00-59 minutes; and 00-59 seconds.

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

different value.

INterval(

value

)

displays, in the form “0hhmmss+”, the interval between invocations of the CICS timeout delete mechanism. The timeout delete mechanism removes any shipped terminal definitions that have not been used for longer than the time displayed by the IDLE option.

The time interval can be in the range 00-99 hours; 00-59 minutes; and 00-59 seconds.

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

different value.

CEMT INQUIRE DOCTEMPLATE

| | Function: Retrieves information about a DOCTEMPLATE

Description: INQUIRE DOCTEMPLATE returns

| | information about any currently installed document template | names.

Input: Press the Clear key to clear the screen, and type

| | CEMT INQUIRE DOCTEMPLATE (the minimum abbreviation is CEMT | IDO). You get a display that lists the names and status of | any document templates. Note that you cannot change any | of the displayed information.

Sample screen

|à|

| I DOC

| STATUS: RESULTS - OVERTYPE TO MODIFY

| Doc(test1 ) Tsq Nam(test1 ) App Ebc

| Tem(test1 ) | SYSID=HA61 APPLID=CICSHA61

| 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 |

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

| | ─ ──CEMT Inquire DOctemplate ──┬ ┬───────── ─────

| ─ ──┬ ┬──────────────────── ───────────────────── | └┘──Templatename(name)

| 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.

Chapter 11. Master terminal CEMT 71

CEMT INQUIRE DSAS

| DOCTEMPLATE | returns the name of this DOCTEMPLATE definition.

| NAME | returns the name of the location defined in | TEMPLATETYPE.

| TEMPLATENAME | returns the extended template name by which the | doctemplate is known outside the resource definition | function.

| TEMPLATETYPE | returns the location of the template. Values are:

| EXITPGM the exit program to be invoked when a | request is made for this template.

| FILE the 8-character name of the CICS file | definition for the data set containing the | template.

| MEMBER returns the name of the member in the PDS | containing the template.

| PROGRAM returns the name of the program in which | the template data is stored.

| TDQUEUE returns the name of the TD queue in which | the template is stored.

| TSQUEUE returns the name of the TS queue in which | the template is stored.

CEMT INQUIRE DSAS

Function: Retrieve information about the local CICS

dynamic storage areas (DSAs).

Description: CEMT INQUIRE DSAS returns the value of

various DSA sizes and limits.

Input: Press the Clear key and type CEMT INQUIRE DSAS

(the minimum abbreviation is CEMT I DSA). To change various attributes, you can:

 Overtype your changes on the INQUIRE screen after

tabbing to the appropriate field (see Figure 64)

 Use the CEMT SET DSAS command.

Sample screen

à ð

IN DSAS STATUS: RESULTS - OVERTYPE TO MODIFY

SOSStatus( NOTSOS )

Dsalimit( 419434 )

Cdsasize( 524288 ) Rdsasize( 262144 ) SDsasize( 262144 ) Udsasize(  )

EDsalimit( 297152 )

ECdsasize( 297152 ) ERdsasize( 3145728 ) ESdsasize(  ) EUdsasize( 148576 )

Figure 64. CEMT INQUIRE DSAS screen

─ ──CEMT Inquire DSAs ─

| TYPE(BINARY|EBCDIC) | returns the format of the template contents.

| BINARY When the template is loaded from the | template library, no parsing of the template's | contents is done.

| EBCDIC When the template is loaded from the | template library, the contents are parsed as | EBCDIC text.

Displayed fields

DSalimit(

SOSStatus

value

)

displays the maximum amount of storage, as a total number of bytes, within which CICS can dynamically allocate storage for the four individual DSAs that reside below the 16MB boundary. (See the

Definition Guide

for a description of the DSALIM system

CICS System

initialization parameter.) Note: You can reset this value by overtyping it with a

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.

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.

72 CICS Supplied Transactions

CEMT INQUIRE DSAS

SOSABOVE

CICS is short on storage in at least one of the dynamic storage areas above 16MB.

SOSBELOW

CICS is short on storage in at least one of the dynamic storage areas below 16MB.

CDsasize(

RDsasize(

SDsasize(

Udsasize(

EDsalimit(

value

)

displays the size, in bytes, of the CICS dynamic storage area (CDSA). The size of this storage area is calculated and managed by CICS automatically, within the overall limits specified for all the DSAs that reside below the 16MB boundary.

value

)

displays the current size of the read-only dynamic storage area (RDSA). The size of this storage area is calculated and managed by CICS automatically, within the overall limits specified for all the DSAs that reside below the 16MB boundary.

value

)

displays the current size of the shared dynamic storage area (SDSA). The size of this storage area is calculated and managed by CICS automatically, within the overall limits specified for all the DSAs that reside below the 16MB boundary.

value

)

displays the size, in bytes, of the user dynamic storage area (UDSA) below the 16MB boundary.

value

)

displays the maximum amount of storage, as a total number of bytes, within which CICS can dynamically allocate storage for the four individual DSAs that reside above the 16MB boundary. (See the

Definition Guide

system initialization parameter.) Note: You can reset this value by overtyping it with a

different value.

If EDSALIMIT specifies a value lower than the current limit, CICS may not be able to implement the new limit

for a description of the EDSALIM

CICS System

immediately, but will attempt to do so over time as dynamic storage is freed in the individual DSAs.

SOSAbove

displays whether CICS is short on storage in any of the dynamic storage areas above 16MB. The values are:

NOTSOS

CICS is not short on storage in any of the dynamic storage areas above 16MB.

SOS CICS is short on storage in at least one of the

dynamic storage areas above 16MB.

ECdsasize(

ERdsasize(

ESdsasize(

EUdsasize(

value

)

displays the size, in bytes, of the extended CICS dynamic storage area (ECDSA) above the 16MB boundary. The size of this storage area is calculated and managed by CICS automatically, within the overall limits specified for all the DSAs that reside above the 16MB boundary.

value

)

displays the size, in bytes, of the extended read-only dynamic storage area (ERDSA) above the 16MB boundary. The size of this storage area is calculated and managed by CICS automatically, within the overall limits specified for all the DSAs that reside above the 16MB boundary.

value

)

displays the current size of the extended shared dynamic storage area (ESDSA). The size of this storage area is calculated and managed by CICS automatically, within the overall limits specified for all the DSAs that reside above the 16MB boundary.

value

)

displays the size, in bytes, of the extended user dynamic storage area (EUDSA) above the 16MB boundary. The size of this storage area is calculated and managed by CICS automatically, within the overall limits specified for all the DSAs that reside above the 16MB boundary.

Chapter 11. Master terminal CEMT 73

CEMT INQUIRE DSNAME

Function: Retrieve information about an external data set. Description: INQUIRE DSNAME returns information

about the status of a data set managed by CICS file control. The data set name is either the name specified on the DSN parameter of the data set’s DD statement, or the DSNAME parameter of the data set’s file resource definition. Its main purpose is to allow you to monitor failing VSAM data sets. Many of the attributes cannot be determined until a file that references the data set has been opened. If this has not happened, blank values are returned for most attributes.

| Note: CEMT has to retrieve QUIESCESTATE information | from the ICF catalog. This can slow down processing | of this command. QUIESCESTATE is not supplied by | default but is retrieved and displayed if requested.

Input: Press the Clear key to clear the screen. There are

two ways of commencing this transaction:

 Type CEMT INQUIRE DSNAME (the minimum abbreviation is | CEMT I DSN). You get a display that lists the current | status except QUIESCESTATE. To retrieve | QUIESCESTATE you can place the cursor at the | beginning of the displayed item (in front of the Dsn field) | 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 range of information that you require. So, for example, if you enter cemt i dsn vs not, the resulting display will show you the details of only those external data sets that are VSAM data sets and are not recoverable.

You can then tab to the highlighted or blank fields and overtype them with the required values.

─ ──CEMT Inquire DSName ─────────────────────── ┌ ┐─ALl────────────────

─ ──┼ ┼──────────────────── ─

├┤──(value) ─────────── ├ ┤──┬ ┬─VSam─ ────────── │ │└┘─BDam─

├┤──FIlecount(value)── ├ ┤──┬ ┬─VAlid─── ─────── │ │└┘─INvalid─ ├ ┤──┬ ┬─Path─ ────────── │ │└┘─BASE─ ├ ┤──┬ ┬─FWDRECOVAble─ ── │ │├┤─NOTrecovable─ │ │├┤─RECOVERAble── │ │└┘─UNDetermined─ ├ ┤──┬ ┬─Static─────── ── │ │├┤─Dynamic────── │ │└┘─UNDetermined─

├┤──FRlog(value) ────── ├ ┤──┬ ┬─AVailable─── ─── │ │└┘─UNAvailable─ ├ ┤──┬ ┬─NOLostlocks── ── │ │├┤─REMLostlocks─ │ │└┘─RECOVERLocks─ ├ ┤──┬ ┬─RETAined─── ──── │ │└┘─NORetained─ ├ ┤──┬ ┬─Quiesced─── ──── │ │└┘─UNQuiesced─

├┤──BASEDsname(value)─

└┘──FWDRECOVLsn(value)

ALl

is the default.

(

value

)

specifies one or more names (1-44 characters) of an external data set.

Sample screen

à ð

IN DSN STATUS: RESULTS - OVERTYPE TO MODIFY 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

74 CICS Supplied Transactions

CEMT INQUIRE DSNAME

displayed. The full set of keywords can be displayed by moving the cursor to the beginning of a displayed item (in front of the Dsn field) and pressing the ENTER key. You get a display of all the keyword information for the displayed item, as follows:

à ð

IN DSN RESULT - OVERTYPE TO MODIFY Dsname(CICSTS13.CICS.CICSH###.DFHCSD) Accessmethod(Vsam) Action( ) Filecount(1) Validity(Valid) Object(Base) Recovstatus(Notrecovable) Backuptype(Static) Frlog()

Availability( Available ) Lostlocks() Retlocks(Noretained) Uowaction( ) Basedsname(CICSTS13.CICS.CICSH###.DFHCSD)

Quiescestate( Unquiesced ) Fwdrecovlsn()

Figure 66. The expanded display of an individual entry

Displayed fields

DSName(

Accessmethod(

Action (

value

)

indicates that this panel relates to an external data set inquiry and displays the 44-character name of an external data set.

value

)

displays the access method of the data set. The values are:

VSam

Virtual storage access method (VSAM).

BDam

Basic direct access method (BDAM).

input only field

)

specifies the action to be taken on this data set. The values are:

Remove

This option is used when a data set is no longer required on the local system. It deletes the data set name block for the named data set. The REMOVE option can be used only when there are no file control resource definition entries that refer to the specified data set. If any file definitions refer to the data set name when you enter SET DSNAME REMOVE, you receive an error message indicating that the use count of the data set name block is not zero. To ensure that no file definitions refer to the data set name:

 Close all files that refer to the data set. These

files can be found using the command:

CEMT INQUIRE FILE() DSNAME(dsname)

 Either remove the data set name from each

file entry (by over-typing the data set name

with blanks on the CEMT display), or discard the file definition entirely.

If you have a base data set with one or more alternate indexes, you are unable to remove the data set name block for the base until you have removed all references to the base data set and all references to paths.

Recovered

The data set has been restored from a backup version and forward recovery has run and completed successfully. CICS normally updates the backup-while-open (BWO) attributes for the base cluster data set BASEDSNAME, using MVS/DFP 3.2 Callable Services.

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 open because the data set is marked as down-level.

Resetlocks (

vsam only

)

Purges shunted UOW log records for backout-failed and commit-failed UOWs that hold locks on this data set, and releases the retained locks:

 Backout-failed UOWs are those that failed

during backout processing.

 Commit-failed UOWs are those that have

updated RLS data sets, and have failed to release locks during the second phase of 2-phase commit syncpoint processing.

If you specify this option, you are accepting backout failure and some loss of data integrity rather than retaining locks and delaying transactions, and therefore it should be used only as a last resort.

For backout-failed and commit-failed UOWs that hold locks on the data set, all records relating to this data set are removed from the system log and all retained record locks held by this CICS for the data set are released. Diagnostic messages are written to the CSFL transient data queue for each backout-failed log record that is removed as a result of the RESETLOCKS operation.

RESETLOCKS applies only to shunted UOW log records that are classed as backout-failed and commit-failed. Therefore it cannot be issued for a BDAM data set. Backout-failed and commit-failed log records are not shunted for BDAM data sets.

You might use RESETLOCKS if backout-failed or commit-failed log records are holding up lost locks recovery for the data set, and there is no other way of resolving them.

Chapter 11. Master terminal CEMT 75

CEMT INQUIRE DSNAME

Notes:

1. This option does not apply to shunted

in-doubt

in-doubt UOWs that hold locks on the data set in other ways before issuing RESETLOCKS; for example, by using COMMIT, BACKOUT, or FORCE (see the CEMT SET DSNAME command for information about these options).

2. RESETLOCKS can fail during the commit phase (for example, if an error occurs while CICS is trying to release the RLS locks), in which case the UOWs revert to being shunted as commit-failed UOWs.

Retry

Specifies that shunted UOW log records, caused by failed backout and commit processing as a result of the failure of this data set, should be retried. This is similar in operation to the EXEC CICS RESYNC command, but applies to backout-failed and commit-failed UOWs only, and not to in-doubt UOWs.

You should use RETRY when the data set has shunted backout- or commit-failed UOWs associated with it, and you believe that some or all of the data set problems are either transient or have been resolved.

Messages, issued at the time of a data set failure that causes UOWs to be shunted, recommend the actions that are required to recover from the failure.

RETRY does not affect data integrity, and can be used safely at any time to enable some failed recovery work to complete.

value

FIlecount(

displays information on how many different files are currently associated with this data set. You can associate a file with a data set by a job control DD statement, or dynamically by a DSNAME parameter on the file definition. If a file has been associated by a job control DD statement, the file name cannot be changed by a CEDA command or by a CEMT or EXEC CICS SET FILE DSNAME command.

FILECOUNT does not show how many files are open against the data set; it only shows how many files are associated with the data set. If a file is associated with a data set and is then closed and associated with a different data set, the FILECOUNT of the first data set decreases by 1, and the FILECOUNT of the second data set increases by 1.

Validity

displays the validity of the data-set name. The values are:

)

UOWs. Try to resolve the shunted

VAlid

The data-set name has been validated against the VSAM catalog by opening a file against that data set.

INvalid

The data-set name has not been validated against the VSAM catalog by opening a file against that data set.

Object

displays the type of the data set. The values are: Path (VSAM only)

This data set is a path leading to another data set.

BASE

The named data set is a base data set, as opposed to a path data set.

Recovstatus

displays the recovery status of the data set. The values are:

FWDRECOVAble

All updates to the data set are logged for both backout and forward recovery.

NOTrecovable

Updates to the data set are not logged. This response may also be returned as the result

of use of the XFCNREC global user exit. A program enabled at XFCNREC may indicate that file opens should proceed even if there is a mismatch in the backout recovery requirements for different files associated with same data set. In these circumstances, the data set is marked as NOTRECOVABLE to indicate that its data integrity can no longer be guaranteed.

The condition remains until cleared by a CEMT or EXEC CICS SET DSNAME REMOVE command, or by an initial or cold start of CICS (if the associated data set is not in backout-failed state). While the data set is in this state, backout logging is performed for a particular request based on the specification in the file definition. Therefore backout logging may occur for requests via one file and not via another.

RECOVERAble

All updates to the data set are logged for backout.

UNDetermined

The recovery status of the data set is not known because files accessing the data set have not been opened for output.

Backuptype

displays the backup type of the data set. The values are: Static

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

76 CICS Supplied Transactions

CEMT INQUIRE DSNAME

serialized by a backup manager such as DFSMS/MVS before a data set backup copy can be made.

Dynamic

The data set is accessed in RLS mode and is eligible for BWO processing. Data set backup is allowed while it is open for output, using a data set backup manager such as DFSMShsm or DFSMSdss.

Notapplic

The data set has not been opened by the CICS region in which the command is issued, or the data set is BDAM or a VSAM PATH. NOTAPPLIC is also returned if the dataset has been opened in RLS mode. The VSAM catalog should be referred to get the BWO status.

FRlog(

value

)

displays the numeric journal identifier of the journal being used to log the updates for forward recovery if this data set is forward recoverable (FWDRECOVABLE). The FRLOG value is undefined if the data set is not forward recoverable. You can define a data set as forward recoverable either in the ICF catalog or, if it is accessed in non-RLS mode, in the file resource definition. This option is meaningful only for data sets accessed in LSR or NSR mode, and for which the forward recovery attributes are obtained from the CICS file resource definition.

For data sets accessed in RLS mode (if DFSMS 1.3 is installed), or non-RLS mode data sets for which CICS obtains the recovery attributes from the ICF catalog, CICS displays a value of zero.

Availability

displays information indicating whether the data set is currently flagged, in this CICS region, as available or unavailable for use. The availability indicator is a local flag that a CICS region maintains in a data set name block (DSNB) for each data set. If the file is a BDAM data set, no information is returned. The values are:

AVailable

The data set is available for use according to the CICS data set name block. CICS can issue either RLS or non-RLS open requests for this data set.

Note: Although a data set is available according

to information held by CICS, an open request could still fail if the ICF catalog indicates otherwise. This can occur, for example, if data set recovery is pending or actually in progress.

UNAvailable

The data set is marked by CICS as not available for use. The CICS region is unable to open the data set in either RLS or non-RLS mode.

AVAILABILITY can be reset by specifying AVAILABLE.

Lostlocks

displays whether there are any lost locks for this data set. The possible values displayed are:

NOLostlocks

The data set has no lost locks.

REMLostlocks

The data set has lost locks, hence is unavailable, but no recovery is required on this CICS. (The lost locks belong to a another (remote) CICS region.)

RECOVERLocks

The data set has lost locks and therefore is unavailable. This CICS system is performing lost-locks recovery.

Retlocks

displays whether there are any retained record locks, as a result of deferred recovery work by this CICS region, for the specified data set.

RETAined

This CICS region has deferred recovery work causing retained locks for the data set. One effect of this is that, if the data set was last opened in RLS mode, the locks are RLS locks and therefore the data set cannot be opened in non-RLS mode.

Another effect is that any FILE definitions that specify this data set cannot be changed to specify a different data set.

If the data set is a BDAM data set, or a VSAM data set accessed in non-RLS mode, the locks are CICS record locks, otherwise they are RLS record locks.

NORetained

This CICS region has no deferred recovery work for the base data set, and therefore no retained locks.

Note: Noretained can also mean that the CICS

region is currently processing deferred recovery work. When the recovery work is successfully completed, the value remains as NORETAINED until more deferred work is created. If the recovery work is not successfully completed, the value reverts to RETAINED.

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.

Chapter 11. Master terminal CEMT

CEMT INQUIRE DSNAME

Quiescestate

displays the RLS quiesce state of the data set. The information is obtained from the ICF catalog entry for the data set. The values displayed are:

Quiesced

A data set has been quiesced. It means that RLS ACBs cannot open against the data set and no CICS region has an RLS ACB currently open against this data set. However, the data set can be opened in non-RLS mode.

UNQuiesced

This is the normal value for a data set that is not quiescing or has not been quiesced. It indicates that RLS or non-RLS ACBs can be opened against the data set, the mode being established by the first open. After an ACB is opened in one mode, other ACBs can be opened only in the same mode.

If a data set is quiescing because a SET DSNAME QUIESCE command was issued in the same region as the CEMT I DSN command, the words “BEING QUIESCED” are displayed.

If a data set is quiescing, the words “BEING QUIESCED” are displayed for the CICS region in which the command was issued.

If quiesce does not apply (for example, for a BDAM data set), nothing is displayed.

Quiescestate can be reset by specifying Quiesced|Unquiesced or:

Immquiesced

Causes all existing CICS open RLS ACBs throughout the sysplex to be closed and the data set to be marked as quiesced in the ICF catalog. Each CICS in the sysplex abends all in-flight UOWs that are accessing the data set before closing ACBs, causing in-flight UOWs to back out.

Any OUWs that fail backout are shunted. No RLS ACBs can open against this data set, but non-RLS open requests are permitted.

Uowaction (

specifies the action to be taken for all shunted units of work that reference this data set. The values are:

Backout

Commit

BASEDsname(

When PATH is displayed as well, this is the name of the base data set with which this path is associated.

When BASE is displayed as well, this is the same as the name shown in the Dsn(

FWDRECOVLsn(

displays the name of the log stream that is used to log the updates if this data set is defined as forward recoverable. CICS returns nulls if the data set is not forward recoverable.

The log stream name returned is either:

input only field

Specifies that all shunted in-doubt units of work that hold locks on the data set should be backed out.

Specifies that all shunted in-doubt units of work that hold locks on the data set should be committed. Specifies that all shunted in-doubt units of work that hold locks on the data set should be forced to BACKOUT or COMMIT, as specified by the ACTION attribute on the transaction resource definition.

value

 The log stream name specified directly in the ICF

catalog, or

 For a non-RLS access mode data set that does not

have forward recovery attributes in the ICF catalog, it is a log stream name identified by CICS through a journal name generated from the FWDRECOVLOG value.

)

) (VSAM only)

value

)

) field.

78 CICS Supplied Transactions

CEMT INQUIRE DUMPDS

Function: Retrieve information about the CICS dump data

sets.

Description: INQUIRE DUMPDS tells you which dump

data set (A or B) is currently open. 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 dumps, see the

Determination Guide

Input: Press the Clear key and type CEMT INQUIRE DUMPDS

(the minimum abbreviation is CEMT I DU). You will get a display screen, a sample of which is shown

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

CICS Problem

─ ──CEMT Inquire DUmpds ─

Displayed fields

DUmpds

indicates that this panel relates to a dump data set inquiry.

Currentdds(

Openstatus

value

)

displays a 1-character indicator as to which of the two dump data sets is active. This can be A or B.

displays the status of the active CICS dump data set. The values are:

Open

The active CICS dump data set is open.

Closed

The active CICS dump data set is closed.

Switch

The currently active dump data set is to become inactive, and the currently inactive data set is to become active.

à ð

IN DUMPDS STATUS: RESULTS - OVERTYPE TO MODIFY

Dum Cur(A) Ope

Figure 67. CEMT INQUIRE DUMPDS screen

Note: There are blank fields on the screen where a value

If you place the cursor against the result and press ENTER, CICS displays an expanded format as shown in Figure 68.

à ð

IN DUMPD RESULT - OVERTYPE TO MODIFY Dumpds Currentdds(A)

Openstatus( Open ) Switchstatus( Noautoswitch )

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

different value.

Switchstatus

displays whether there is to be an automatic switch to the inactive dump data set when the active dump data set is full. The values are:

Autoswitch

The switch occurs only when the active dump data set is full, but not subsequently.

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. You can, however, tab to this field and overtype it with a different value.

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

different value.

Figure 68. The expanded display

Chapter 11. Master terminal CEMT 79

CEMT INQUIRE ENQ

| CEMT INQUIRE ENQ | Function: Retrieve information about enqueues held or

| waited on by a UOW, or about UOWs holding or waiting on a | specified enqueue.

Description: INQUIRE ENQ returns information about the

| | enqueues held by a UOW. Enqueues are used by CICS to | lock recoverable resources such as file records or queues to | the UOW that is updating them. User enqueues obtained by | the EXEC CICS ENQ command are also returned.

| You can use INQUIRE ENQ to indicate which records and | queues would be affected if the UOW were forced.

| The transaction also returns information about UOWs that | are waiting on the enqueues. This enables you to diagnose | enqueue deadlocks between tasks wanting to update the | same resources.

| 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 ENQ 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 ENQ. (For an explanation of | UOW- and task-lifetime enqueues, see the | MAXLIFETIME option of the EXEC CICS ENQ command | in the

| 2. On an in-doubt failure, user enqueues are released, | | MAXLIFETIME(TASK) and it is not the end-of-task | syncpoint that suffers the failure.

Input: Press the Clear key to clear the screen. There are

| | two ways of commencing this transaction:

|  Type CEMT INQUIRE ENQ (the minimum abbreviation is | CEMT I ENQ). You get a display that lists all enqueues for | all the current UOWs.

|  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 | the details only of enqueues on records in VSAM data | sets open in non-RLS mode or CICS-maintained data | tables.

CICS System Programming Reference

unless

the EXEC CICS ENQ command specified

manual.)

| | ─ ──CEMT Inquire Enq ──┬ ┬──────────── ──────────

| └┘──Uow(value) | ─ ──┬ ┬──────────────── ──┬ ┬─────────────── ──────

| └┘──TRansid(value)└ ┘──TAskid(value) | ─ ──┬ ┬────────── ──┬ ┬───────────── ──────────────

| ─ ──┬ ┬──────── ──┬ ┬───────────────── ──────────── | ├┤─Owner── └ ┘──Netuowid(value) | └ ┘─Waiter─

| ─ ──┬ ┬───────────────── ──┬ ┬───────────────── ─── | └┘──ENqfails(value)└ ┘──RESource(value)

| ─ ──┬ ┬───────────── ──┬ ┬────────────────── ────── | └┘──RLen(value)└ ┘──QUalifier(value)

| ─ ──┬ ┬───────────── ─ | └┘──QLen(value)

| Sample screen

|à|

| INQ ENQ

| STATUS: RESULTS

| 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

| Res(g... ) Rle(4) Enq()

Figure 69. CEMT INQUIRE ENQ 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 a specific entry in the list and | press ENTER, CICS displays an expanded format as shown | in Figure 70.

| INQ ENQ

| RESULT

| Enq

| Enq(AC1431D4A7261)

| Transid(CECI)

| Taskid(38)

| State(Active)

| Type(Execenq)

| Relation(Owner)

| Duration()

| Resource(ACCOUNTS.DBASE1)

| Rlen(15)

| Enqfails()

| Netuowid(..GBIBMIYA.IYA2T5C2...Mx...)

| Qualifier()

| Qlen()

Figure 70. The expanded display of an individual entry

80 CICS Supplied Transactions

CEMT INQUIRE ENQ

| Displayed fields | Duration(

| displays the elapsed time (in seconds) since the | enqueue f entered its current state of OWNER, WAITER | or RETAINED.

| ENQFails( | displays, for enqueues held in retained state, the number | of failed enqueue attempts for this resource since the | enqueue was last acquired. This indicates how many | UOWs have received LOCKED responses due to this | enqueue. The ENQFAILS option helps you identify | which UOWs are causing “bottlenecks.”

| For enqueues held in action state, ENQFAILS displays | zero.

| All CICS systems with the same ENQSCOPE value | share the same sysplex Enqueue name space.

| Netuowid( | displays a 27-character string containing the | network-wide LU6.2 name of the UOW that owns or is | waiting for the enqueue.

| Note: Nondisplayable characters appear as periods. | You can use PF2 on the expanded panel: to see | the value in hexadecimal.

| QUalifier( | displays a 1- through 255-character qualifier (for | example, record id) that further identifies the resource | associated with the enqueue lock. The data displayed | depends on the type of enqueue, as shown in Table 2 | on page 82. If no QUALIFIER data applies (that is for | EXECENQ, ADDREXECENQ, or TSQ), a value of zero | is displayed.

| QLen( | displays the length of the data, in the range 0 through | 255, displayed in the QUALIFIER field.

| RELation | displays whether the data is associated with the owner | of the enqueue or with a task waiting for the enqueue. | The values are:

| Owner | The ( | are those of the owner of the enqueue.

| Waiter | The ( | are those of a waiter for the enqueue.

| RESource( | displays a 1- through 255-character string containing the | name of the resource associated with the enqueue lock.

value

)

value

)

value

), NETUOWID, TASKID, and TRANSID

value

), NETUOWID, TASKID, and TRANSID

)

| The data displayed depends on the type of enqueue, as | shown in Table 2 on page 82.

| Note: Nondisplayable characters appear as periods. | You can use PF2 on the expanded panel: to see | the value in hexadecimal.

value

)

| RLen( | displays the length of the data, in the range 0 through | 255, displayed in the RESOURCE field.

| State | displays the state that the enqueue is held in. The | values are:

| ACtive | The enqueue is held in active state.

| RETained | The enqueue is held in retained state. Its owning | UOW has been shunted, or is in the process of | being shunted.

| TAskid( | displays the number of the task associated with the | UOW. If the UOW is shunted, it is the task number | associated with the UOW before it was shunted.

| TYpe | displays the type of resource being enqueued upon. The | values are:

| File The resource is a record in either a BDAM file or a | user-maintained data table. RESOURCE contains | the name of the file and QUALIFIER contains the | record identifier.

| When the file is a BDAM file then the record | identifier is prefixed by the BDAM block identifier. | Note that truncation occurs if this combination | exceeds 255 characters.

| EXecenq | The resource is associated with an EXEC CICS | ENQ request. RESOURCE contains the enqueue | argument passed on the request.

Chapter 11. Master terminal CEMT 81

CEMT INQUIRE ENQMODEL

| TDq The resource is a logically-recoverable transient | data queue. RESOURCE contains the name of the | queue. QUALIFIER contains either the string | “FROMQ” or “TOQ,” indicating whether a read or | write lock is held for the queue.

| TSq The resource is a recoverable temporary storage | queue. RESOURCE contains the name of the | queue.

| The data displayed in the RESOURCE and QUALIFIER | fields depends on the resource type, as shown in | Table 2.

Table 2. Data displayed in RESOURCE and QUALIFIER

| None | argument

| ADDREXECENQ| Address of EXEC

| None | enqueue | argument

value

| Uow( | displays the 16-character local identifier of the | associated unit of work.

)

CEMT INQUIRE ENQMODEL

| | Function: Retrieve information about enqmodel definitions

| on the local system.

Input: Press the Clear key and type CEMT INQUIRE

| | ENQMODEL (the minimum abbreviation is CEMT I ENQM).

| You get a display screen, a sample of which is shown 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

|à|

| INQ ENQMODEL

| STATUS: RESULTS - OVERTYPE TO MODIFY

| Enqm( ) NOT FOUND

Figure 71. CEMT INQUIRE ENQMODEL screen

| | ─ ──CEMT Inquire ENQModel ───────────────────── | ─ ──┬ ┬──(value) ──────── ──┬ ┬────────── ─

| ├┤──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.

82 CICS Supplied Transactions

IBM SC33-1686-02 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual