/TRACE UNITYPE command
Use the /TRACE UNITYPE command to trace events that are related to the physical terminals of the specified type.
Subsections:
Environment
The following table lists the environments (DB/DC, DBCTL, and DCCTL) in which you can use the commands and keywords.
Command / Keywords | DB/DC | DBCTL | DCCTL |
---|---|---|---|
/TRACE | X | X | X |
LEVEL | X | X | |
SET | X | X | X |
UNITYPE | X | X |
Syntax
.-ON--. >>-+-/TRACE-+--SET--+-----+-------------------------------------> '-/TRA---' '-OFF-' .-------------. V | >--UNITYPE----unitypename-+--+--------------+------------------>< '-LEVEL--+-1-+-' +-2-+ +-3-+ '-4-'
Keywords
The following keywords are valid for the /TRACE UNITYPE command:
- LEVEL
- Expands the
LINE, LINK, NODE, or UNITYPE trace functions. The LEVEL specification
is for the entire IMS™ system
and is changed only by reissuing /TRACE with different
values or by restarting the IMS control
region.
LEVEL indicates the extent of the control block trace information desired. The indicated control blocks are only traced at relevant times. All levels are inclusive of numerically lower levels. The following list displays the levels and their associated blocks.
- Level
- Blocks
- 1
- CLB (DECB) or LLB(MSC)
CTB or LTB(MSC)
IOB (for non-VTAM lines) or IOSB (MSC for channel-to-channel links)
- 2
- CNT or LNB(MSC)
CXB
CRB
CIB
CCB
PD stack
- 3
- queue manager buffers
Input/output line buffers
LXB (for channel-to-channel links and processor storage to processor storage)
- 4
- save area sets (IMS dispatching)
If the first /TRACE SET ON command does not specify LEVEL, a default of 4 is used. Specifying LEVEL on subsequent commands will change the defaults.
- MODULE
- Is used to
expand the LINE, LINK, NODE, or UNITYPE trace functions. The MODULE
specification is for the entire IMS system
and is changed only by reissuing /TRACE with different
values or by restarting the IMS control
region.
MODULE indicates which modules are to have their control blocks traced.
- ALL
- Both device-dependent module (DDM) and MFS
- DDM
- Communication analyzer and device-dependent module interfaces
- MFS
- Communication analyzer and Message Format Service module interfaces
If the first /TRACE SET ON command does not specify MODULE, a default of ALL will be used. Specifying MODULE on subsequent commands will change the defaults.
Usage notes
The UNITYPE keyword is used to trace all terminals of a specific type. Parameters (unitypename) are similar to the identifiers displayed in the TYPE column by the /DISPLAY NODE and /DISPLAY LINE/PTERM commands. The following table shows the terminal types for UNITYPE parameters.
UNITYPE parameter | Terminal type |
---|---|
2260R | 2260/2265 REMOTE |
3286 | 3284/3286 |
2980 | 2980 |
3270R | 3270 REMOTE |
3270L | 3270 LOCAL |
RDR/PTR | LOCAL SYSIN/SYSOUT |
FIN | 3600 |
3277 | 3270 VTAM® |
SLU1 | SLU TYPE 1 |
SLU2 | SLU TYPE 2 |
SLUP | SLU TYPE P |
LUT6 | LU TYPE 6 |
NTO | NTO |
CONSOLE | z/OS® SYSTEM CONSOLE |
TWX | TWX SWITCHED |
3275SW | 3270 SWITCHED |
MSCMTM | MSC Memory to Memory communications |
MSCCTC | MSC Channel to Channel communications |
MSCTCPIP | MSC TCP/IP communications |
MSCVTAM | MSC VTAM communications |
If global resource information is kept in Resource Manager, /TRACE UNITYPE sets a global trace status for all of the nodes of a specific type. This requires that the inactive static nodes be processed on every IMS system. The UNITYPE keyword is similar to specifying a generic parameter. If global resource information is not kept in Resource Manager, /TRACE UNITYPE sets the trace status locally.