Date: mm/dd/ccyy ******************************************************************************** Page: 1 * CA Datacom/DB * Time: hh.mm.ss * General Utility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn ******************************************************************************** CONTROL CARD(S) .........1.........2.........3.........4.........5.........6.........7.........8 Œ COMM OPTION=STATUS FUNCTION=COMM OPTION=STATUS Ž
The command exactly as entered.
An analysis of keywords encountered and expected. Any errors found are flagged with a note in the left margin.
Any messages related to syntax processing.
Date: mm/dd/ccyy ******************************************************************************** Page: 2 * CA Datacom/DB * Time: hh.mm.ss * General Utility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn ******************************************************************************** DB13101I - STATUS MULTI-USER AVAILABLE , SUBID=3 Œ Ž ‘ ’ “ ” • JOBNAME R-UNIT TASK STATUS CMD DBID TBL SEQ TIME I/O ID TSN OWNR/Y TSN-TM DBDVL132 14160 1 READY TO RUN ADDIT 997 C02 95727 DBDBBBDA :01 JOBNAME R-UNIT TASK VALUE/RID STATJOB2 33654 1 1 PAY
Messages indicating the Multi-User job status.
JOBNAME is the name of the active job currently connected to the Multi-User Facility or, if a system task, one of the following:
Accounting
Tasks that process a console request, such as COMM CLRPXX
MUF immediately after the enable to allow accounting, and other system tables the opportunity to open
RESTART function during the enable of the Multi-User Facility
Rare systems functions
History database spill
Asynchronous I/O completion system processing
Index queue
Security
Log spilling
R-UNIT is the run unit number, where nnnnn is the low order five digits with leading zeros suppressed (nnnnn is zero for system tasks).
TASK is the task number nnnn (RWTSA ID) where the task is running.
The status messages occur in groups based on task status. STATUS can be one of the following:
The task has detected a task abend.
An ACCESS with an AREA specified is running and interacting with processes that care about the ACCESS AREA function.
A request is active (only one task can be active).
A task is waiting on a specific Directory (CXX) block to become available.
A task is waiting on a specific data area block to become available.
A task is waiting on a specific Index Area (DXX) block to become available.
A task is waiting on a specific Index Area (IXX) block to become available.
A task is waiting on a specific Log Area (LXX) block to become available.
This task has an outstanding CICS two-phase commit, and CICS has been cold started. The task must be manually researched and then cleaned up with a REQCOMIT or REQROLBK.
A task is waiting on CICS to provide resolution for a two-phase commit.
The task is waiting on the close of the named area-database (aaabbbb).
Reflects that the task is waiting on the MVS DEQ (for MVS) or z/VSE UNLOCK (for z/VSE) of the CXX.
Reflects that the task is waiting on the MVS ENQ (for MVS) or z/VSE LOCK (for z/VSE) of the CXX.
An EOJ is in process.
A task is waiting on the log chain.
A task is waiting for the read forced list lock in a MUFplex environment.
The status is not active.
The task is waiting on the open of the named area-database (aaabbbbb).
A request has been transmitted but has not yet been accepted by the Multi-User Facility.
The Multi-User Facility has accepted the task but has not dispatched it because of priority.
A procedure is running on behalf of this task in a procedure TCB.
The resource upon which the task was waiting has become available. Task is ready to be dispatched, based on priority.
A task is waiting on a close lock that controls flushing statistics to the PXX.
The CICS transaction has a locked thread but is not currently waiting on a Multi-User Facility request.
A task is waiting to update a particular entry in the Accounting buffer.
A task is waiting on the Accounting global chain.
A task is waiting on a specific Accounting table to record or remove information.
A task is waiting on the Accounting Facility.
A task is waiting on access to current log buffer.
A task is waiting for a free buffer (CXX, LXX, IXX, DXX, data).
A task is waiting on access to the CBS buffer lock.
A task is waiting for a set in the CBS buffer to spill to the IXX.
A task is waiting on CICS to provide resolution for a two-phase commit, but the controlling CICS is not up.
A task is waiting on a non-RENT user compression exit.
A task is waiting on the data free space buffer chain lock.
A task is waiting on the Data Space Management lock.
DEFRAG is running and interacting with a read backward request.
A task is waiting for a record that another task has read with exclusive control. The status is followed by OWNER- indicating the task owning the resource and by RID- indicating the type of lock. See the description of VALUE/RID on page Sample Report: COMM STATUS Utility.
A task is waiting on the hash chain for a data area buffer.
A task is waiting on the hash chain for a DXX buffer.
A task is waiting on the hash chain for an Index Area buffer.
A task is waiting on an I/O event.
A task is waiting on access to the index queue.
A task is waiting on the interlock detection lock.
A task is waiting on access to the exclusive (share) list control tables.
A task is waiting on log delay based on your specifying X_LOG_DELAY_BLK.
A task is waiting on the least recently used chain for a Directory (CXX) buffer.
A task is waiting on the least recently used chain for a data area buffer.
A task is waiting on the least recently used chain for a DXX buffer.
A task is waiting on the least recently used chain for an Index Area buffer.
A task is waiting on the least recently used chain for a Log Area (LXX) buffer for transaction backout.
A task is waiting on access to the Memory Manager.
A COMM NEWRXX function is waiting on the open/close subtask to open or close the RXX.
A task is waiting on access to the open list of tables lock.
A task is waiting on open exit.
A task is waiting on access to the posted list.
A task is waiting on the procedure chain processing lock.
A task is waiting for a PROCEDURE TCB. All procedure TCBs are currently in use.
A task is waiting on access to the Statistics and Diagnostics Area (PXX) write module.
A task is waiting on a request in another task area to complete before executing a spill.
A task is waiting on security validation.
A task is waiting on a spill to complete.
A task is waiting on access to the SQL ATTACH list lock.
A task is waiting on access to the SQL GLOBAL list lock.
A task is waiting on an SMP lock around the SQL call to memory manager.
A task is waiting on the SQL miscellaneous lock.
A task is waiting on access to the SQL PLAN list lock.
A task is waiting on access to the SQL STATUS list lock.
A task is waiting on access to the TTM table lock.
A task is waiting on access to the SQL URT list lock.
A task is waiting on the task area lock for status change.
A task is waiting on record owned by another task. The status is followed by OWNER- indicating the task owning the resource and by RID- indicating the type of lock. See the description of VALUE/RID on page Sample Report: COMM STATUS Utility).
QUIESCE is waiting on an active request.
A task is waiting on the timer and cancel lock.
A task is waiting on the TSN lock to check, assign, or remove an active transaction.
A task is waiting on another user exit to complete.
A task is waiting on the write pending chain for a data area buffer.
A task is waiting on the write pending chain for an Index Area buffer.
A task is waiting on access to the wait list.
CMD indicates the command in the Request Area. This is blank for a system task or omitted if the request is NOT ACTIVE, TASK ACTIVE, PENDING, or POSTED.
DBID is a database ID (not listed when not applicable).
TBL is a table name (not listed when not applicable).
SEQ specifies the internal CA Datacom/DB request sequence number. This allows you to abort a request if it is blocking other requests from executing. For a system task, zero is displayed. It is omitted if the request is NOT ACTIVE, TASK ACTIVE, PENDING, or POSTED.
TIME indicates the length of time in minutes and seconds since the Multi-User Facility accepted the request. For system tasks, this is the time since the system started the current work unit. It is omitted if the request is NOT ACTIVE or TASK ACTIVE.
(Page 2 continued)
Date: mm/dd/ccyy ******************************************************************************** Page: 2 * CA Datacom/DB * Time: hh.mm.ss * General Utility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn ******************************************************************************** DB13101I - STATUS MULTI-USER AVAILABLE , SUBID=3 Œ Ž JOBNAME R-UNIT TASK STATUS CMD DBID TBL SEQ TIME I/O ID TSN OWNR/Y TSN-TM DBDVL132 14160 1 READY TO RUN ADDIT 997 C02 95727 DBDBBBDA :01 ‘ ’ “ JOBNAME R-UNIT TASK VALUE/RID STATJOB2 33654 1 1 PAY
I/O indicates the number of I/O events performed during the processing of this request. It is omitted if the request is NOT ACTIVE, TASK ACTIVE, PENDING, or POSTED.
ID is displayed (xxxxxxxx or tran-term-opr-xxxxx) under the following circumstances:
tran The CICS transaction identifier
term The CICS terminal ID
opr The CICS operator ID
xxxxx CICS sequence number
TSN (only listed on updates).
OWNR/Y TSN-TM is the task of the owner (OWNR) and the number (Y) of the Multi-User Facility in the MUFplex upon which the task is waiting. TSN-TM refers to time since the transaction was started. TSN-TM is provided by DBUTLTY STATUS not console.
When you issue a COMM STATUS command, CA Datacom/DB displays status information for tasks that are waiting, where JOBNAME is the name of the active job currently connected to the Multi-User Facility or, if a system task, to one of the entries listed in the table for the JOBNAME column on Page 2 of the report.
R-UNIT is the run unit number, where nnnnn is the low order 5 digits with leading zeros suppressed (nnnnn is zero for system tasks).
TASK is the task number nnnn (RWTSA ID) where the task is running.
VALUE/RID indicates a value lock. The following table identifies the types of locks that can occur. If a task status is WAIT E/C or WAIT TASK, different types of locks can be responsible for the wait. When the lock is a record lock or a table lock, DBUTLTY prints a record ID in the text of a report message line numbered DB01329I to indicate the resource causing the lock that is responsible for the wait, as described in the following chart:
|
Lock Type |
RID Format |
Meaning |
|---|---|---|
|
Record |
tid-rrrrrrrrrrrrrr |
In the RID format, tid is the Table ID and rrrrrrrrrrrrrr is the Record ID. |
|
Internal |
iiiiFFjjjjjjjjjjjj |
Provides internal information. |
|
Table |
ddddtttt |
The dddd is the Database ID and tttt is the Table ID. The remaining five bytes contain zeros. |
When the lock is a value lock, CA Datacom/DB provides additional information as shown in the following table:
|
Type of Value Lock |
Meaning |
Additional Information Available from the COMM STATUS Display |
|---|---|---|
|
DBSCXX |
The Directory (CXX) is locked during URT open and close processing and during maintenance to the CXX when CXX I/O is required. |
(None) |
|
DBSDCB |
CA Datacom/DB has locked this area during a dynamic extend. |
Database ID and Area name |
|
DBSDDL |
SQL Data Definition Language (DDL) has locked the process of choosing internal IDs for various structures. |
Database ID where the created or altered table resides. |
|
DBSDSB |
CA Datacom/DB has locked a database to ACCESS OFF/READ which is open. |
Database ID |
|
DBSIXX |
CA Datacom/DB has a lock while index que/backward read processing. |
Database ID and Block group number |
|
DBSKEL |
A table's key element data is locked during the process to bring it into memory or write it back to the Directory (CXX). |
Database ID and Table name |
|
DBSKEY |
CA Datacom/DB has locked a key to verify that an add or update does not violate a unique constraint. |
|
|
DBSMVR |
A user has executed the DBUTLTY LOCK function to block moved records. |
Database ID and Area name |
|
DBSOPN |
CA Datacom/DB has a lock during URT open and close processing and during maintenance to the CXX. |
Database ID |
|
DBSPLN |
CA Datacom/DB has locked an SQL plan for concurrency. |
AUTHID and Plan name |
|
DBSPRC |
The locking of a prodecure has occurred so that a NEWCOPY can be synchronized. |
Eight-character procedure name |
|
DBSRRD |
CA Datacom/DB has locked a key range to assure the SQL repeatable read function. |
|
|
DBSSIX |
CA Datacom/DB has locked the data space management index during maintenance. |
|
|
DBSSOC |
CA Datacom/DB has locked a database and table to open or confirm the table for SQL processing. |
Database ID and Table name |
|
DBSSPL |
CA Datacom/DB has a lock during the spill. |
(None) |
|
DBSTXB |
CA Datacom/DB has a lock on this transaction while waiting on the rollback to be completed using backward recovery. A previous console message DB00109W requested the recovery. |
Transaction sequence number |
|
DBSURI |
CA Datacom/DB has locked an area during URI validation/assignment. |
Database ID and Area name |
|
Other |
Other lock values are possible. |
|
In Version 12.0 (but not in the release previous to it), the following is also printed per task with the JOBNAME, R-UNIT, and TASK fields (as in the previous release), followed by the (new for Version 12.0) status information fields, BREF, R-TIME, C-TIME, D-TIME, and USER-ID as shown in the following example and explained in the following descriptions:
Date: mm/dd/ccyy ******************************************************************************** Page: 1 * CA Datacom/DB * Time: hh.mm.ss * Multi-User Facility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn ******************************************************************************** Directory: DBDVMUF Œ Ž ‘ ’ “ ” JOBNAME R-UNIT TASK BREF R-TIME C-TIME D-TIME W-TIME PATH U-SYSTEM U-JOBID USER-ID DBDVLSTS 44431 1 *NULL* *NULL* UNKN CA11 JOB39119 COMM
BREF is the number of buffer references to satisfy the current request (SQL, set-at-a-time, record-at-a-time). This is the total for index and data. It is printed in the same format as the I/O column.
R-TIME is the run time in minutes and seconds that the current request (SQL, set-at-a-time, record-at-a-time) has been set by MUF to be active.
C-TIME is the CPU time the current request (SQL, SAAT, RAAT) had completed the last time it allowed a task switch. It is only available if accounting is enabled in the MUF, and if accounting CPU time is also currently set. The format of the field is minutes and seconds (mmm:ss) with two exceptions. A time greater than 999 minutes is reported as +++:++. A time less than one second is reported as blanks, not as 000:00.
D-TIME is the duration time the task has been waiting for that upon which, for this instance, it is currently waiting. It is not the total wait time for the current request, nor is it the wait time for the current data manager request. If the task is not waiting, the field is set to null, and on the report it is printed as the characters *null*. The format of the field is minutes and seconds (mmm:ss) with two exceptions. A time greater than 999 minutes is reported as +++:++. A time less than one second is reported as blanks, not as 000:00.
W-TIME is the total wait time that this request was not selected by the MUF for processing, excluding a current wait, if any, whose time is in D-TIME.
PATH is the path from the user application to the MUF and can be as follows:
LOCAL is the PATH if the user and the MUF are on the same system. If there is no user, that is, the request was generated by the MUF itself, for example from being restarted or by the execution of a console or console-like command.
XCF is the PATH if the z/OS XCF facility is being used for communication.
CCI is the PATH if the CA CCI facility is being used for communication.
IUCV is the PATH if the z/VSE IUCV facility is being used for communication.
UNKN is the PATH if the path cannot be determined (this PATH is not expected to occur).
U-SYSTEM is the system name, where the user application called the interface.
U-JOBID is the z/OS JOBID identification of the user application.
USER-ID is the 32-character user ID, if this request was made through the DBNTRY entry point.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|