The z/OS Communications Server in use—is the LU at fault?
If you have found that the access method and terminal control are not causing the wait, the terminal itself must be waiting for some reason. You need now to look at some fields in the TCTTE for the terminal to find its status.
CICS® system dumps contain an index to the SNA LU entries. It appears in the terminal control (TCP) summary section of the dump.
Information about the status and attributes of the SNA LUs appears in an interpreted form at the end of the control block for each terminal entry. The information shown depends on the attributes of the terminal.
===TCP: TERMINAL CONTROL SUMMARY (SNA LUs)
TERMINAL TASK IN ERROR ACTIVE RPL WORK ZNAC INTERVENTION AUTOINSTALL
TERMID TYPE LOGGED ON ATTACHED SERVICE STATS. REQUEST TO DO QUEUED REQUIRED ACTIVITY
R51 C0 NO NO YES 00000000 NO NO NO NO N/A
R52 C0 NO NO YES 00000000 NO NO NO NO N/A
R53 C0 NO NO YES 00000000 NO NO NO NO N/A
R54 C0 NO NO YES 00000000 NO NO NO NO N/A
R55 C0 NO NO YES 00000000 NO NO NO NO N/A
S51 C0 NO NO YES 00000000 NO NO NO NO N/A
S52 C0 NO NO YES 00000000 NO NO NO NO N/A
S53 C0 NO NO YES 00000000 NO NO NO NO N/A
S54 C0 NO NO YES 00000000 NO NO NO NO N/A
S55 C0 NO NO YES 00000000 NO NO NO NO N/A
-AAA C0 NO NO YES 00000001 NO NO NO NO N/A
-AAB C0 NO NO YES 00000000 NO NO NO NO N/A
TCTTE.R51 03B5C420 TCT TERMINAL ENTRY
0000 D9F5F140 C0000504 03B5C424 00000000 00000000 00000000 00000000 00080000 *R51 ......D.....................* 03B5C420
0020 00000000 0C000000 C5D5E400 00008080 00000000 00000000 00000000 00000000 *........ENU.....................* 03B5C440
0040 00000000 00000000 00000000 00000000 00000000 01D80000 00000000 03B22030 *.....................Q..........* 03B5C460
0060 00000000 00000000 00000000 03B58690 00000000 00000000 03B46390 00000000 *..............f.................* 03B5C480
0080 00000000 00000000 00000000 00000000 03B430F8 00000000 00000000 00000000 *...................8............* 03B5C4A0
00A0 00000000 00000000 00000000 00840000 00000000 00000000 00000000 00000000 *.............d..................* 03B5C4C0
00C0 00000000 80000000 00000000 00000000 00000000 0000003B 01000000 00000000 *................................* 03B5C4E0
00E0 10000000 00000000 00000000 03B5C618 00000000 00000000 00000000 00000000 *..............F.................* 03B5C500
0100 3A008400 00000000 00000000 00000000 00000000 FFFF0000 00000000 00000000 *..d.............................* 03B5C520
0120 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 *................................* 03B5C540
0140 10001000 10000000 00000000 00000000 00000000 00000000 00000000 00000000 *................................* 03B5C560
0160 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 *................................* 03B5C580
0180 08090000 00000000 00000000 00000000 00000000 00000000 00000000 03B59421 *..............................m.* 03B5C5A0
01A0 00440000 00001008 D4FD6038 80800014 00000000 00000000 00000000 00000000 *........M.-.....................* 03B5C5C0
01C0 00000000 00000000 00000000 00000000 00000000 00000000 *........................ * 03B5C5E0
TERMID = R51 EXIT FOOTPRINTS (HEX) = 00000000
IN SERVICE TCTTECA (NO TASK ATTACHED)
TCTECCV (STARTED BY TTI) TCTECSM (CA-MODE)
INPUT STATISTICS (DECIMAL) = 00000000 OUTPUT STATISTICS (DECIMAL) = 00000000
ERROR STATISTICS (DECIMAL) = 00000000 TCTE1RY (CICS IS PRIMARY)
TCTELSE (LUC CONTENTION LOSER) TCTESBIF (SBI/BIS SUPPORTED)
The values that are given below for fields in the TCTTE are not the only possibilities, but they show important things about the terminal status. If you find any other values for these fields, look in the Data areas to find out what they mean.
- Is the terminal in service? Look at field TCTTETS of the TCTTE,
to find the terminal status. The values that indicate why a terminal
was failing to respond include:
Look also at field TCTESEST, to find the session status with respect to automatic transaction initiation (ATI) for the terminal. Some of the values you might see are:TCTTESPO = 1 and TCTTESOS = 1 terminal out of service TCTTESOS = 1 only terminal in error recovery
A value of TCTESLGI = 0, with TCTESLGT = 0, too, shows that CREATESESS(NO) has been specified in the TYPETERM definition. This means that EXEC START requests and ATI requests cannot cause a session to be created. The request is either queued or rejected when no session is currently established. This can put a terminal into an indefinite wait state, especially if the terminal is a printer.TCTESLGI = 0 CREATESESS(NO) in TYPETERM definition TCTESLGI = 1 CREATESESS(YES) in TYPETERM definition TCTESLGT = 1 recovering CREATESESSA value of TCTESLGI = 1 shows that CREATESESS(YES) has been specified in the TYPETERM definition. This means that CICS is allowed to create sessions for the terminal, so the CREATESESS status is not the cause of the wait.
A value of TCTESLGT = 1 means that the session is in error recovery. This could explain why there is no response from the terminal.
- Has a task been created for this terminal? Look first at field
TCTTECA of the TCTTE.
- If its value is nonzero, there is a task attached to the terminal.
You can tell whether the task has been started from a terminal, or
by ATI, from field TCTEICCV:
TCTECCV = 0 the task has been started by a terminal TCTECCV = 1 the task has been started by ATI - If its value is zero, look in fields TCTTEIC and TCTECTI. The
values you might find there are:
TCTTEOIC = 1 ATI is waiting to start TCTECTI = 1 there is ATI work for ZCP to do
- If its value is nonzero, there is a task attached to the terminal.
You can tell whether the task has been started from a terminal, or
by ATI, from field TCTEICCV:
- Is there a task related to the terminal? You can find the task
session state with SNA from field TCTEMOST, and, if bracket protocol
is required (from field TCTEIBPE), its conversation state with the
terminal from field TCTEIINB. The significant values that might provide
further clues to the cause of the wait are:
Look now at field TCTEIBPE, to see if bracket protocol is required:TCTECSM = 1 the task is in conversation with the terminal TCTECSM = 0 terminal control will accept new tasks from the terminal
If you find that bracket protocol is required, look in field TCTEIINB:TCTEBPE = 1 bracket protocol is requiredTCTEINB = 0 a conversation has not been started TCTEINB = 1 a task is in conversation with the terminal - Is the terminal logged on to CICS?
Look first at the node session status in the TCTTE. The three stages
of session creation are represented by three separate bits, in fields
TCTEILOS, TCTEIOPD, and TCTEINSD:
If all three bits are set, so the value of the byte is TCTENIS, the node is in session.TCTELOS = 1 the node is logged on TCTEOPD = 1 z/OS Communications Server OPNDST macro issued TCTENSD = 1 Start Data Traffic sentYou next need to see if the terminal is logging off, or if it has already been logged off. The fields of interest are TCTEINND, TCTEINBD, and TCTEIPSA. The values to look for are:
If any of these bits are set, the terminal might not be able to respond to the waiting task.TCTENND = 1 the terminal is to be logged off TCTENBD = 1 the terminal is logging off because of an error TCTEPSA = 1 the session with the terminal ended abnormally —look for any explanatory message on CSMT - Should the terminal respond to the task? Field TCTEIPRA tells
you this:
TCTEPRA = 1 the terminal should respond
If the values you have found in all these fields suggest that the terminal status is normal, the terminal is probably waiting for some activity to complete before it responds. The type of investigation you need to do next depends on the type of terminal involved in the wait. You should already have determined this, for example by using the system programming command EXEC CICS INQUIRE TERMINAL DEVICE.