/DIAGNOSE
Format
|
|
| .-LENGTH(8)------.
|>>-+-/DIAGNOSE-+--SNAP--+-ADDRESS(address)-+----------------+-+--------------+-+-><
| '-/DIAG-----' | '-LENGTH(length)-' '-KEY(-+-0-+-)-' |
| | '-7-' |
| +-BLOCK(-+-ALL--+-)------------------------------------+
| | +-CMDE-+ |
| | +-ESCD-+ |
| | +-LSCD-+ |
| | +-MWA--+ |
| | +-QSCD-+ |
| | +-SCD--+ |
| | +-SQM--+ |
| | '-TSCD-' |
| +-LTERM(ltermname)-------------------------------------+
| +-NODE(nodename)---------------------------------------+
| +-TRAN(tranname)---------------------------------------+
| '-USER(username)---------------------------------------'
|
|
Environments
Table 43 lists the
environments (DB/DC, DBCTL, and DCCTL) from which the command can
be issued.
Table 43. Valid Environments for the /DIAGNOSE Command and Keywords
Command / Keywords |
DB/DC |
DBCTL |
DCCTL |
/DIAGNOSE |
X |
X |
X |
|ADDRESS |
X |
X |
X |
BLOCK |
X |
X |
X |
|LTERM |
X |
|
X |
NODE |
X |
|
X |
SNAP |
X |
X |
X |
TRAN |
X |
|
X |
|USER |
X |
|
X |
Usage
|The /DIAGNOSE command allows users to retrieve diagnostic information for
|system resources such as IMS control blocks, user-defined nodes,
|or user-defined transactions at any time without taking a console
|dump.
|
|- SNAP
|- Captures storage information and writes the information to
|the OLDS as type X'6701' records. Storage information can
|be captured for IMS control blocks, user-defined nodes, and user-defined
|transactions.
|
|
|
|- ADDRESS
|- Captures information about a specific area stored in memory.
|The address identifies the area and must
|specify a hexadecimal value between 0 and 7FFFFFFF.
|
|
|- LENGTH
|- Specifies the length of the address. The LENGTH parameter
|is optional and has a default value of eight. If the LENGTH parameter
|is specified, the length must be a numeric
|value between 1 and 65536.
|
|- KEY
|- Alters the PSW key prior to accessing the specified storage.
|The KEY parameter is optional. Valid values for the KEY parameter must
|be a numeric value between zero and seven.
|
|
| |
|- BLOCK
|- Captures information for a specific IMS control block. A control
|block name or ALL is required. Valid control block names include:
|
|
|- ALL
|- Captures information for all valid control blocks currently
|available.
|
|- CMDE
|- Captures information for the Commands SCD Extension control
|block.
|
|- ESCD
|- Captures information for the Extended System Contents Directory
|control block.
|
|- LSCD
|- Captures information for the LU 6.2 Extension to SCD control
|block.
|
|- MWA
|- Captures information for the Modify Work Area control block.
|
|- QSCD
|- Captures information for the Queue Manager Extension to SCD
|control block.
|
|- SCD
|- Captures information for the System Contents Directory control
|block.
|
|- SQM
|- Captures information for the Shared Queue Master control block.
|
|- TSCD
|- Captures information for the OTMA Extension to SCD control
|block.
|
|
| |
|- LTERM
|- Captures information about the logical terminal specified
|in the parameter, ltermname. If an LTERM
|is locally defined, the local control block information is captured.
|In a shared queues environment, if an LTERM is not defined on the
|local system issuing the command, global information for that LTERM
|is gathered from an available Resource Structure. If a control block
|is available, information associated with the specified LTERM is
|captured. Following is a list of control blocks:
|
|
|- CLB
|- Communication Line Block
|
|- CTB
|- Communication Terminal Block
|
|- CTT
|- Communication Translate Table
|
|- CRB
|- Communications Restart Block
|
|- SPQB
|- Subpool Queue Block
|
|- CNT
|- Communication Name Table (maximum of five)
|
|- CCB
|- Conversational Control Block
|
|- CIB
|- Communication Interface Block
|
|- INBUF
|- Input Line Buffer
|
|- OUTBF
|- Output Line Buffer
|
|
| |
|- NODE
|- Captures information about the node specified in the parameter, nodename.
|If a NODE is locally defined, the local NODE information is captured.
|In a shared queues environment, if a NODE is not defined on the
|local system issuing the command, global information for that NODE
|is gathered from an available Resource Structure. If a control block
|is available, information associated with the specified NODE is
|captured. Following is a list of control blocks:
|
|
|- CLB
|- Communication Line Block
|
|- CTB
|- Communication Terminal Block
|
|- CTT
|- Communication Translate Table
|
|- CRB
|- Communications Restart Block
|
|- SPQB
|- Subpool Queue Block
|
|- CNT
|- Communication Name Table (maximum of five)
|
|- CCB
|- Conversational Control Block
|
|- CIB
|- Communication Interface Block
|
|- INBUF
|- Input Line Buffer
|
|- OUTBF
|- Output Line Buffer
|
|
|
|- TRAN
|- Captures information about the transaction specified in the parameter, tranname.
|This keyword captures the SMB data for a specified transaction.
|
|
|- USER
|- Captures information about the user specified in the parameter, username.
|If a USER is locally defined, the local USER information is captured.
|In a shared queues environment, if a USER is not defined on the
|local system issuing the command, global information for that USER
|is gathered from an available Resource Structure. If a control block
|is available, information associated with the specified USER is captured.
|Following is a list of control blocks:
|
|
|- CLB
|- Communication Line Block
|
|- CTB
|- Communication Terminal Block
|
|- CTT
|- Communication Translate Table
|
|- CRB
|- Communications Restart Block
|
|- SPQB
|- Subpool Queue Block
|
|- CNT
|- Communication Name Table (maximum of five)
|
|- CCB
|- Conversational Control Block
|
|- CIB
|- Communication Interface Block
|
|- INBUF
|- Input Line Buffer
|
|- OUTBF
|- Output Line Buffer
|
|
| |
|
|
Example for /DIAGNOSE Command
Entry ET:
/DIAGNOSE SNAP TRAN(tranname)
Response ET:
DFS058I DIAGNOSE COMMAND COMPLETED
Explanation: Diagnostic information about transaction tranname
is captured on the IMS log.

IBM Confidential