CBSTAT subcommand — obtain control block status

Use the CBSTAT subcommand to analyze a specific control block. IBM® provides exit routines that process ASCBs and TCBs; the exit routines are specified by parmlib members embedded in the BLSCECT parmlib member. CBSTAT generates a report for ASCBs that encompasses address space level information. Similarly, CBSTAT generates a report for TCBs that contains task level information about control blocks other than the TCB.

You can also use CBSTAT to get information about resource initialization modules (RIMs) that fail during IPL/NIP processing. Specify the STRUCTURE attribute parameter, but instead of a control block name, specify STORESTATUS. CBSTAT returns the name of the failing RIM(s) with corresponding abend and reason codes. (See the example on viewing data about failing NIP RIMs..)

IPCS may issue the accompanying messages when:

No CBSTAT report is generated.

BLS01040I No errors were detected by the CBSTAT exits

CBSTAT does not analyze a requested control block, where yyyyyyyy is the name of the specified control block that CBSTAT does not analyze, such as the ASXB.
```
BLS01041I The CBSTAT exits defined in BLSCECT do not process
STRUCTURE(yyyyyyyy)
```
The CBSTAT subcommand syntax check fails. This may occur when the address for the requested control block is not in virtual storage or when the STRUCTURE parameter is omitted.
```
BLS01043I CBSTAT requires the specification of a STRUCTURE
in virtual storage
```
The specified address cannot be accessed.
```
BLS18100I adr-space adr NOT AVAILABLE
```
The control block identified in the STRUCTURE parameter fails the validity check.
```
BLS18058I Errors detected in STRUCTURE(name) at ASID(n) address
```

To perform its processing, the CBSTAT subcommand uses the CBSTAT service. This service is IBM-supplied and can be used when writing your own dump exit. See z/OS MVS IPCS Customization for information about these services and for information about writing CBSTAT exits.

Syntax

    CBSTAT       data-descr

-------- SETDEF-Defined Parameters -------------------------
Note: You can override the following SETDEF parameters.
See SETDEF subcommand — set defaults.

                [ FLAG(severity) ]
                [ PRINT | NOPRINT ]
                [ TERMINAL | NOTERMINAL ]
                [ TEST | NOTEST ]

Parameters
data-descr
Specifies the data description parameter, which consists of five parts:
- An address (required)
- Address processing parameters (optional)
- An attribute parameter (see note below)
- Array parameters (optional)
- A remark parameter (optional)
Data description parameter explains the use and syntax of the data description parameter.
Note: The STRUCTURE(cbname) attribute parameter is required; all other attribute parameters are optional. The following values are valid for cbname:
- ASCB
- CSRCPOOL
- SSRB
- STORESTATUS
- TCB

Return codes

Code	Explanation
00	Successful completion.
04	Attention, subcommand completed with a condition that may interest you.
08	Error, subcommand encountered an error condition that may interest you.
12	Severe error, no CBSTAT exits exist for the requested control block type or user request forced early end to the subcommand processing.
16	Ending error, the identified control block failed the validity check.

Example 1: Analyze the ASCB in the master scheduler address space.
- Action
```
COMMAND ===> cbstat ascb1 structure(ascb)
```
- Result
  CBSTAT generates the output (see Figure 1) for the master scheduler address space, after accessing and validity checking the ASCB. IPCS invokes the CBSTAT exits for ASCBs. Note that if the symbol, ascb1, is defined in the IPCS symbol table and if that symbol has the STRUCTURE attribute defined, the STRUCTURE parameter can be omitted from the example.
  Figure 1. Example CBSTAT command output
```
STATUS FOR STRUCTURE(ASCB) AT 00FC8B00. NOCPU ASID(X'0001')
   IRA10102I This address space is on the SRM IN queue.
```

Example 2: Analyze a TCB at a specified address.

Action

COMMAND ===> cbstat 7fa030. structure(tcb)

Result

CBSTAT generates the output for the specified TCB (Figure 2) . IPCS invokes the CBSTAT exits for TCBs.

Figure 2. Example CBSTAT command output (analyze a TCB)

STATUS FOR STRUCTURE(TCB) AT 007FA030. ASID(X'07D1')
  IEA21005I Task is in recovery processing, LIFO summary of active
              recovery environments follows:
  IEA21007I In ESTAE at IGC0006C+010D70 for S003F at IGC0006C+01045A,
              SDWA at 007B0B40

Example 3: Analyze an ASCB at a specified address.

Action

COMMAND ===> cbstat f62180. structure(ascb)

Result

CBSTAT generates the output for the ASCB (Figure 3).

Figure 3. Example CBSTAT command output (analyze an ASCB)

STATUS FOR STRUCTURE(ASCB) AT 00F62180. CPU(X'00') ASID(X'0001')
   IRA10102I This address space is on the SRM WAIT queue.
   IRA10104I The reason for swap-out is long wait (3).

Example 4: View data about failing NIP RIMs.

Action

COMMAND ===> cbstat structure(storestatus)

Result

CBSTAT generates the output shown in Figure 4.

Figure 4. Example CBSTAT command output (view data about NIP RIMs)

STATUS FOR STRUCTURE(STORESTATUS) AT 00FD7100 NOCPU ASID(X'0001')
IEA41001I NIP RIM IEAVNP11 has failed
IEA41002I ABEND=0C4 REASON=04