IBM SC33-1686-02 User Manual

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

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.

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

+ 287 hidden pages