DBOC/DBIC: Monitoring Local Resources with Operational Commands › INQ=STATS: Displaying System Statistics › Display Example: DBOC INQ=STATS

Display Example: DBOC INQ=STATS

 DBOC INQ=STATS                                                        DELIM &
 
 
DC00400I  SYSVIEW INITIALIZATION PROCESS SUCCESSFUL                            
CURRENT:   ACTIVE TRANS=000       RESERVING TRANS=000    HELD TRANS=000        
TOTALS:    REQUESTS=000000092     HELD=000000014                               
           REQUEST WITHOUT I/O WAIT =000000059                                 
           REQUEST WITH    I/O WAIT =000000033                                 
BACKOUTS:  PGM REQUESTED=0000000  DUE TO ABEND=0000000                         
DATABASE START I/O'S=000000044   AVERAGE SIO'S PER REQUEST=0000.4782           
SPAWNED TRANCODE:NONE      PGMID:NONE      DB CMD:NONE     COUNT=000000        
ABENDS  :  DC01S=000000    DC02S=000000    DC03S=000000    DC05S=000000        
           DC06S=000000    DC07S=000000    DC16S=000000    DC18S=000000        
           DC19S=000000    DCD1S=000000    DCD2S=000000    DCD3S=000000
DC00380I  TRANSACTION COMPLETED.

Field Descriptions

CURRENT:

The following fields:

ACTIVE TRANS

Indicates the total of tasks currently waiting for CA Datacom/DB I/O to complete.

RESERVING TRANS

Indicates the number of tasks which have acquired exclusive control by issuing update requests to CA Datacom/DB.

HELD TRANS

Indicates the number of tasks waiting for access to CA Datacom/DB. If HELD TRANS is not zero (000), the maximum number of concurrent users has been reached. The maximum number of concurrent users is defined in the DBCVTPR macro (see the System Reference Guide).

TOTALS:

The following fields:

REQUESTS

Total number of CA Datacom/DB requests issued since CA Datacom CICS Services initiation or since a DBOC RESET=STATS transaction was issued.

HELD

Total number of requests which had to wait for CA Datacom/DB access since the initiation of CA Datacom CICS Services or since a DBOC RESET=STATS transaction was issued.

REQUEST WITHOUT I/O WAIT

Total number of requests receiving CA Datacom/DB service without an I/O wait. This number includes DBOC/DBEC OPEN and DBOC/DBEC CLOSE commands.

REQUEST WITH I/O WAIT

Total number of requests receiving CA Datacom/DB service after an I/O wait.

BACKOUTS:

The following fields:

PGM REQUESTED

Total number of CA Datacom/DB LOGTB requests issued by application programs.

DUE TO ABEND

Total number of LOGTB requests automatically issued by CA Datacom CICS Services.

DATABASE START I/O'S

Total number of start I/Os issued by CA Datacom/DB.

AVERAGE SIO'S PER REQUEST

Average number of start I/Os issued by CA Datacom/DB per request.

SPAWNED TRANCODE:

(z/OS Multiple MUF environment only) The last transaction that required spawning at the time of the DBOC INQ=STATS. This field could be changing all the time depending upon transaction activity. The following are spawned transactions:

PGMID:

(z/OS Multiple MUF environment only) The program ID associated with the SPAWNED TRANCODE. This indicates the application that needs modifying to adhere to the CICS SYNCPOINT/SYNCPOINT ROLLBACK protocol.

DB CMD:

(z/OS Multiple MUF environment only) The log command executed in the application specified (shown previously) that did not adhere to the CICS SYNCPOINT/SYNCPOINT ROLLBACK protocol.

COUNT=

(z/OS Multiple MUF environment only) The number of tasks specified by the SPAWNED TRANCODE and PGMID (shown previously) that have been spawned due to a log command specified by the DB CMD.

The SPAWNED TRANCODE and its associated program (PGMID) and COUNT fields (both are for z/OS multiple MUF environments only) contain important information for users. The goal is to have the SPAWNED TRANCODE field showing NONE and the COUNT field showing 000000. Any transaction (SPAWNED TRANCODE) that has spawned is a candidate for application (PGMID) rewrite because spawning cannot have two-phase commit protocol. Only CA Datacom/DB log commands(DB CMD) issued by a user are candidates for spawning. A spawn only occurs if a given transaction (SPAWNED TRANCODE) and program (PGMID) has a request of an update type on two or more CA Datacom/DB MUFs when the user issued the log command (DB CMD). Therefore, it is a z/OS only option because z/VSE does not support a multiple MUF environment. This condition occurs for one or two reasons.

• CA Datacom CICS Services determined that there were non-CA Datacom/DB updateable resource managers (including, for example, CA Datacom DB2 Transparency, CA Datacom VSAM Transparency, and so on) involved in this transaction. It could issue a CICS SYNCPOINT/SYNCPOINT ROLLBACK on behalf of the log command.
• CA Datacom CICS Services could not determine if there were other resource managers involved in which case, a SYNCPOINT/SYNCPOINT ROLLBACK is issued for the default MUF which is MUF(1) in a multi-MUF environment that synchronizes all MUFs involved in the transaction.

Rewrite applications (PGMID) to take advantage of standard two-phase commit protocol for integrity purposes. For more information, see Special Logging Commands (DB CMD) Considerations.

ABENDS

Total number of abends per CA Datacom CICS Services ABEND codes. For an explanation about each code, see ABEND Codes in the Message Reference Guide.

Note: In z/OS, the DC00400I is displayed if SYSV=YES is specified in the DBCVTPR and CA SYSVIEW is present and has started successfully.