Verifying SNA LU operations
You can perform a number of activities to verify that CICS® is working properly, for example, logging on, using transactions, running sample programs, and shutting CICS down.
Logging on to a SNA LU
When the DFHIVPOL
job displays the console message CONTROL IS BEING GIVEN TO
CICS, you can log on to CICS using an IBM® 3270 Information Display system terminal.
Use the CICS application identifier that you specified when you started CICS to log on through your SNA LU. For example, unless you changed the APPLID as specified as at system initialization (CICSIVP1), enter LOGON APPLID(CICSIVP1).
If you are using autoinstall, your logon request is passed to CICS and, if all the autoinstall requirements described in Autoinstall have been met, CICS installs your LU. It does so by creating a TCT terminal entry (TCTTE) using the model definitions defined in the group list, DFHLIST, and the LU identifier returned by the autoinstall user program (DFHZATDX in this case).
If you are using a LU defined in the CSD explicitly, and included in the group list specified in the startup job stream, CICS identifies the installed resource definitions by the SNA net name and creates the required TCTTE.
When you log on to CICS, your LU can display a good morning message as specified on the GMTRAN system initialization parameter. The default transaction, CSGM, displays a welcome message as defined by the GMTEXT system initialization parameter.
Using CICS provided transactions through a terminal
After you have started CICS with the DFHIVPOL job, you can use the CICS provided transactions to try out various functions of CICS to help you verify that CICS is working properly. You can use the transactions at a CICS terminal, for example, CEMT and, if you defined one, the system console.
For information about the CICS transactions that you can try with the DFHIVPOL job, and about the message-switching responses to those transactions, see CICS supplied transactions descriptions.
| Operator Input | System Response |
|---|---|
| CEMT | Status: ENTER ONE OF THE
FOLLOWING Discard
Inquire Perform Set |
| I |
Status: ENTER ONE OF THE FOLLOWING
OR PRESS ENTER FOR DEFAULT (Followed by a list of options) |
|
PROG
Press ENTER key |
STATUS: RESULTS - OVERTYPE TO MODIFY
Prog(CEECBLDY) Len(0000000) Ass Pro Ena Pri Res(000) Use(0000000000) Any Cex Ful |
|
Press F3 key
Press CLEAR key |
|
| CEMT PERFORM STATISTICS | |
|
Press F3 key
Press CLEAR key |
SESSION ENDED |
| CETR | |
|
Press F3 key
Press CLEAR key |
Clear or F3 pressed
Normal termination of CETR |
| CEMT I TA | Displays list of tasks in the system |
|
Press F3 key
Press CLEAR key |
SESSION ENDED |
|
CEMT I
PROG(DFHFEP) |
Prog(DFHFEP )Len(005848) Ass Pro Ena Pri
Res(000) Use(0000000) Any Cex Ful Qua |
|
Press F3 key
Press CLEAR key |
SESSION ENDED |
|
CEOT
(Inquire about this terminal) |
Ter (tmid) Tra (CEOT) Pri (nnn) Pag Ins Ati Tti
(Remember 'tmid' for use in next transaction, CMSG) |
|
Press F3 key
Press CLEAR key |
SESSION ENDED |
| � | |
| CMSG 'HELLO',R=tmid,S |
(Send the message 'HELLO' to your terminal)
MRS OK MESSAGE HAS BEEN ROUTED (briefly at lower right of screen) HELLO (at upper left of screen) |
You can enter your CEMT input in either uppercase or lowercase, because the main terminal transaction translates all input to uppercase. Use the CLEAR key and the F3 key as indicated.
If you enter the CETR transaction, CICS displays the status of the various trace options.
You can alter the status of any of the trace options
by over typing the current value, indicated by ===> on
the CETR display.
Using the CEDA transaction
When DFHIVPOL starts up CICS, system initialization specifies GRPLIST=DFHLIST, which causes all the CICS resource definitions that are required for normal running to be installed.
You can see which resources are included in DFHLIST by using the CEDA transaction; for example, by using the CEDA EXPAND LIST(DFHLIST) command.
Press F8 to see the continuation of the list. If you started the DFHIVPOL job with your own group list specified instead of the DFHLIST group list, specify the name of your list in the CEDA EXPAND command. The CICS-defined groups all begin with DFH
. For information about CEDA and the
interactions for a typical sequence of CEDA commands, see CEDA - resource definition online.
DFH$. To use the sample programs, therefore, you must first install the resource definitions for the required samples. For example, to use the FILEA sample application:
- Install the sample programs that are required for the FILEA applications.
Use this command:
CEDA INSTALL GROUP(DFH$AFLA) - Make the FILEA data set available to CICS, by performing one of the following tasks:
- Install a FILE resource definition for the FILEA data set:
CEDA INSTALL GROUP(DFH$FILA) - Provide a DD statement for the FILEA data set in your CICS startup JCL. For example,
//FILEA DD DISP=SHR,DSN=CICSTS56.CICS.CICSHTH1.FILEA
- Install a FILE resource definition for the FILEA data set:
To end the CEDA session, press F3.
Invoking and running sample programs
To try the assembler language version of the FILEA sample application, install group DFH$AFLA and then enter the AMNU transaction.
Using transactions from a console device
You can invoke CICS transactions other than CECI from a console device, and other CICS operators can communicate with the console operator. In particular, you can use the console device for CICS main terminal functions to control CICS terminals or to control several CICS regions with multiregion operation.
- The CEDA transaction can be used from a console device only to INSTALL resource definitions.
- The CECI transaction and the sample programs cannot be used from a console device.
If you issue the MVS command d consoles,
a list of console devices is displayed. This list identifies the console
devices by name.
You can use a console device to submit MODIFY commands from your job stream if you define a console device in your CSD as CONSNAME(INTERNAL).
For further information about defining consoles, see Defining console devices to CICS.
{MODIFY|F}� jobname,[']command[']- jobname
- Is the region identifier for the CICS region. This identifier is either the name of the job being used to run CICS, for example, DFHIVPOL, or the name of a procedure if CICS was initiated as a started task.
- command
- Is a string of data, starting with a CICS transaction identifier. If the transaction requires further input, the operator is prompted in the same way as any normal terminal operator. The message from CICS contains a reply number that must be quoted in the reply.
You can use the commands shown in Figure 1 to verify the CEMT and CEOT transactions from the MVS console.
Entering commands from TSO
CONSOLE {MODIFY|F} cicsid,[']command[']
CONSOLE
{MODIFY|F}� cicsid,[']command[']
ENDWhen the TSO CONSOLE command is used, TSO checks the user for authority to issue console commands. Further, if console operator command security is active, the TSO user must be specifically authorized to issue MODIFY cicsid.
The TSO user can interact with an alternate CICS by using the command CONSOLE MODIFY altcics,CEBT.
Operator input System response
f dfhivpol,'cemt i terminal' Displays a list of terminals attached
to CICS
f dfhivpol,'cemt i dump' Displays status of transaction dump
data sets
f dfhivpol,'cemt p statistics' CICS writes statistics to SMF data sets
f dfhivpol,'cemt i ta' Displays number and types of tasks
currently running
f dfhivpol,'cemt p dump' CICS invokes SDUMP macro for system
dump to be taken
f dfhivpol,'cemt i prog(dfhpep)' Displays details of DFHPEP module
f dfhivpol,'ceot' Displays details of operator console
f dfhivpol,'cemt i journalname' Displays status of CICS logs
Stopping CICS
To stop CICS, enter CEMT P SHUT from the SNA LU or MVS console. CEMT P SHUT is a short form of CEMT PERFORM SHUTDOWN.
The system responds with message DFH1713 and following messages as shown in the sample job log shown in Figure 1.