CICS comes with the following transactions. Although at some locations not all transactions are installed, and those installed are not always available to your userid. Some CICS transactions are menu driven, while others can be entered as a command.
Database recovery controlUse 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.
There are two ways of commencing this transaction:
Use CDBI to inquire about the status of the interface between CICS and DBCTL.
Start the transaction by typing the identifier, CDBI, on the command line of your display, and press the ENTER key.
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.
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.
To use CDBM you must: 1. Have a DBCTL system running IMS/ESA 5.1 or later 2. Generate and add to the DBCTL system, a PSB named DFHDBMP. 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.
You can also start the transaction by typing the identifier, CDBM, on the command line of your display.
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 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 CEBRS209" CICS responds with a display of the queue.
Alternatively, you can start the CEBR transaction from CEDF. You do this by pressing PF5 from the initial CEDF screen (see Figure 32) 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 invoking CEBR without a queue name or from an EDF session at terminal S21A is shown in Figure 11.
If you enter CEBR from CEDF, you will return to the EDF panel when you press PF3 from the CEBR screen.
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.
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.
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.
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".
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 a screen which shows the options available within CEDA.
CEDA provides the following functions:
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.
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.
Use CEDF, which invokes the CICS execution diagnostic facility (EDF), to test your command level application programs interactively without having to supply special program testing procedures.
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.
Command syntax
|-,ON--|
>>--CEDF--|-----------|--|------|--><
|-termid----| |-,OFF-|
|-sysid-----|
|-sessionid-|
Command options
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): CEOT - Terminal status CEST - Inquire or set terminals, lines, control units or tasks
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.
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. You cannot use * or + when the identifier is in a list of identifiers.
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. Thus the generic name has the expected effect only for the resource itself.
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.
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.
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).
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.
Inquire about the status of your own terminal, and change some of its values.
Use CEOT to inquire about the status of your own terminal, and to change some of its processing values. You cannot use CEOT to inquire about or change the values of any other terminal.
You can start CEOT from 3270 family display devices, or from equivalent terminals, or from the operating system console.
Press the Clear key to clear the screen. There are two ways of using this transaction: in inquiry mode and in set mode.
Use the CESF transaction to sign off from the CICS system.
This transaction:
If you are using CESF to disconnect a terminal and security is active, a message will still be sent to the log if the signoff fails. However, this will not stop the terminal being disconnected if it is a preset terminal or if the terminal is not signed on.
The syntax of the CESF transaction is as follows:
>>--CESF--|-----------|--><
|-GOODNIGHT-|
|-LOGOFF----|
If you simply type CESF by itself, you are signed off the CICS system. Your terminal can still start transactions without you having to request them, and messages can be sent to it. You can sign on again at that terminal at any time.
The effects of typing CESF with the GOODNIGHT value or the LOGOFF value depend on the access method in use, as shown below:
|---------------------------------------------------------------| | Effect of CESF LOGOFF and GOODNIGHT with different access | | methods | |------------------|-----------------------|--------------------| | | VTAM | Otherwise | | | DISCREQ=YES | | |------------------|-----------------------|--------------------| | CESF | TTI | TTI | |------------------|-----------------------|--------------------| | CESF LOGOFF | Disc, TTI | TTI | |------------------|-----------------------|--------------------| | CESF GOODNIGHT | Disc, TTI | NOTTI | |------------------|-----------------------|--------------------|where:
DISCREQ=YES is an operand of the TYPETERM definition associated with the terminal, and means that CICS is to honor a disconnect request. If DISCREQ=NO, a disconnect request (for example, a CESF LOGOFF request) is not honored.
If a CESF GOODNIGHT is given when there are outstanding automatic transaction initiation (ATI) requests, the ATI requests are actioned and the session is reacquired irrespective of the RDO options.
The user ID specified for this transaction is used in error messages and so on, to identify the user.
Notes:
A user can also sign on by providing all the user information along with the transaction id, as follows:
>>--CESN--USERID=uuuuuuuu--|-------------------|---->
|-,GROUPID=gggggggg-|
>--|---------------|--|--------------|--|-----------------|--><
|-,LANGUAGE=lll-| |-,PS=pppppppp-| |-,NEWPS=password-|
Use CEST to invoke a subset of the master terminal (CEMT) transaction. The CEST INQ|SET commands allows you to inquire about and alter some of the values of lines, netnames, tasks, and terminals.
CEST can be invoked from 3270 family display devices, or from equivalent terminals, or from the operating system console.
All of the CEST commands require the SUPRID keyword to be specified. SUPRID identifies the supervisor invoking the transaction, and its value is the 1-or 2-character suffix of a terminal list table (TLT). For information about the SUPRID keyword, see the CICS Resource Definition Guide.
For example, CEST INQ TERMINAL SUPRID(AL) displays the status of all the terminals in the DFHTLTA1 table. Values can be changed by overtyping the display or by using CEST SET commands. Apart from the requirement that SUPRID has to be specified, the syntax of the commands and the meaning of the values is exactly as described in CEMT INQUIRE|SET LINE, NETNAME, TASK, and TERMINAL.
Use CETR to control CICS tracing activity.
Use CIND to:
Note: For a description of the concepts involved in the synchronization of distributed applications, including in-doubt periods and shunted UOWs, see the CICS Intercommunication Guide.
CIND can operate in a standalone system; it provides a way of changing the UOW so that it is distributed, and of causing a failure during syncpoint processing in the in-doubt window.
It can be used to cause a failure in syncpoint processing as follows:
You can also use CIND to shunt a UOW that is genuinely distributed across multiple CICS systems. It must be activated on the CICS system where the syncpoint is initiated, so that it can assume the role of syncpoint initiator and coordinator before any other CICS systems try to do so. In particular, CIND should not be activated for CICS mirror transactions unless the mirror can be guaranteed to be the syncpoint initiator (that is, a mirror running a server transaction that has been DPLed to specifying SYNCONRETURN).
When active, CIND forces all transactions defined to be in a new transaction class, DFHTCIND, to fail in-doubt when they reach syncpoint.
Note: You cannot use CIND on internal CICS system transactions. If you change a system transaction so that it is defined in transaction class DFHTCIND, CIND detects that it is to be used with a CICS system task, and issues message DFHIN1014 to CSMT. The system task continues to run and CIND does not cause it to fail in-doubt when it reaches syncpoint.
Use CMAC to give you individual message information as provided in the CICS Messages and Codes manual.
Use CMSG to send messages from your terminal to one or more destinations. The destination may be:
You can specify that the message is to be sent at some future time. If the message cannot be sent, your terminal is notified.
In addition, standard routing lists can be provided using the terminal list table (TLT), which can include terminal and operator identifiers. Multiple routing lists can be specified at the time the message is entered, and individual destinations can be deleted from, or added to, the lists at this time.
CICS message switching is provided by a service program invoked by a user-defined transaction identifier that must be defined to CICS. This transaction identifier can be CMSG or any user-defined 4-character transaction identifier. CMSG is the transaction identifier assumed throughout this book.
You can extend message switching to include predefined messages and even complete message-switching transaction input formats.
The terminals from which message switching is initiated, and all terminals of message destinations, must support BMS.
Routed messages can be directed to a terminal, including the transaction terminal, that supports partitions. However, such messages reset the terminal to "base" state.
Use CRTE to run transactions that reside on a remote system.
Transaction routing in a multiregion operation (MRO) environment or for intersystem communication (ISC) is usually achieved by making entries in the PCT. The entries define the transaction as remote, and name the system on which it is to be processed. Entering the transaction code then causes CICS to route the requests to the named system.
The CRTE transaction provides you with another way of running a transaction on a remote system. Use CRTE, rather than making special PCT entries, for infrequently-used transactions or when using transactions such as CEMT which reside on all systems. You must use CRTE when EDF is used to test a transaction running on a remote system. However, because the session has to be established and canceled explicitly, additional signon operations may be required. CRTE can be invoked from a 3270 terminal, but not on LU6.1 links.
The syntax of the routing transaction is:
>>--CRTE--SYSID=sysid--|----------------|--><
|-,TRPROF=trprof-|
where
The routing transaction verifies that the specified remote system is known and is available. If it is, a message is displayed confirming that a routing session to the required system has been started.
When you have received this message, you can clear the screen and enter the transaction identifier for the transaction that is to be run on the remote system. In fact, you can use the terminal as if it were connected directly to the remote system, although you might be asked to sign on to the remote system before being allowed to run any transactions. The transactions that you can invoke include pseudoconversational transactions, BMS paging transactions, and even CRTE itself. However, you cannot use transactions CEOS and CEOT with CRTE, and you cannot use PA or PF keys to invoke transactions under CRTE.
You end a routing session by entering CANCEL. If you have signed on to the remote system, the CANCEL request automatically signs you off.
Notes:
Use CSFE to diagnose terminal problems and software problems. This transaction is mainly intended to be used by system programmers and IBM field engineers.
Use this transaction to:
Some transactions, especially those performed on screens, produce a response that is too large to be displayed or printed at one time. The whole response is held on direct access storage, and only the first portion (called a page) is displayed. You can manipulate these pages, through basic mapping support (BMS), using the CSPG page retrieval transaction. You can use paging to view all pages of the response, in any order. All the pages produced by a transaction make up a logical message.
A page retrieval session begins when you enter the first page retrieval command, or when the first page is presented by automatic transaction initiation (ATI). During the session, CICS passes commands directly to BMS terminal paging, without following the normal transaction identification procedure.
When using BMS for IBM 3780 Communication Terminal transactions, switch off the SPACE COMPRESS EXPAND (standard feature), TRNSPCY (special feature), and the INHIBIT IRS (special feature) switches.
Pages to be manipulated with paging commands must have been created by BMS, which must be active in the system to service the commands. Paging commands enable you to:
Use CWTO to send messages to the console operator.
Start the transaction by entering CWTO, optionally followed by the text of your message, on the command line of the screen, as follows:
>>--CWTO--|---------|--><
|-message-|
The following are some general points about the format of your messages: