This table provides status information about active tasks. One row exists for every task area which is currently attached. This table has characteristics in common with the console status command and the DBUTLTY status function. You can query task areas that are currently attached. This includes query task areas being attached with normal user jobs, being attached by CA Datacom STAR, or being attached by internal CA Datacom/DB system tasks such as the ACCT (Accounting Facility) or index queue functions.
|
Column Name |
SQL Data Type |
Nullable |
Description |
|---|---|---|---|
|
BUFFER_REFERENCES
|
INTEGER |
No |
The number of index and data buffers referenced by this task, starting when the request is accepted by the MUF. |
|
CPU_TIME
|
CHAR(6) |
Yes |
This column contains the total CPU time for this request if you have chosen to keep track of CPU time by specifying YES for the cpu-time parameter on the ACCTPRM Multi-User startup option. The format is mmm:ss, where mmm is minutes and ss is seconds. Otherwise this column is null. For more information, see the performance note for cpu-time in the information about the ACCTPRM Multi-User startup option in the CA Datacom/DB Database and System Administration Guide. Because CPU time is only computed periodically, tasks that are actively running might not include all of their CPU time. |
|
CURRENT_STATUS
|
CHAR(15) |
No |
The current status of a task area is the same as is documented for the console status command. The list is long. For more information, see the COMM STATUS information in the CA Datacom/DB DBUTLTY Reference Guide for details. |
|
DB_COMMAND
|
CHAR(5) |
No |
The five-character record-at-a-time or set-at-a-time command being executed or last executed. This field can contain certain internal commands that are only used by CA Support. |
|
DBID |
SMALLINT |
No |
Contains the database ID. |
|
DURATION
|
CHAR(6) |
No |
The duration of the current request in the format mmm:ss where mmm is minutes and ss is seconds. A duration of 000:00 is provided if the request is complete or not yet accepted by the MUF. The minutes wrap after 999. |
|
EOJ_OK |
CHAR(1) |
No |
The EOJ_OK option allows MUF to EOJ without the application closing all URTs. The column can be either Y, S, or N. - Y and N reflect the URT DBURSTR macro parameter EOJ_OK. - S indicates MUF EOJ_OK S=YES has been set for this CA Datacom Server task. For more information, see the CA Datacom/DB Database and System Administration Guide. |
|
JOB_NAME |
CHAR(8) |
No |
The name of the job currently in the task area. Names starting with an asterisk (*) are internal to CA Datacom/DB. |
|
LOCK_VALUE |
CHAR(64) |
No |
Provides a character string of the row lock or value lock upon which is being waited, similar in format to the console STATUS function. The first six characters of the lock value are provided in the status after WAIT E/C. |
|
MUF_NAME |
CHAR(8) |
No |
Name of the MUF specified in the MUF Multi-User startup option or the MUF job name. |
|
MUFPLEX_OWNER |
CHAR(2) |
No |
The MUFplex number at which the task owning a row or value lock resides, if this is a remote wait for exclusive control. |
|
OPTIONAL_ID |
CHAR(16) |
No |
For CICS transactions, contains the transaction ID, terminal ID, operator ID, and sequence number. For CA Datacom Server, contains the logical terminal name. For DBUTLTY, contains literal "DBUTLTY" followed by the DBUTLTY utility function. Otherwise, this field is blank. |
|
OWNER_TASK |
SMALL INTEGER |
No |
If the status is WAIT E/C, the number of the task which owns the lock is reported. Some locks have an owner which is the MUF itself and not a specific task, in which case the OWNER_TASK is reported as a zero (0). This does not occur for data row locks but does for some of the value locks. |
|
PHYSICAL_EXCPS |
INTEGER |
No |
The number of physical I/O events done by this task, starting when the request is accepted by the MUF. |
|
REQUEST_SEQ_NO |
INTEGER |
No |
The internal request sequence number. It starts at one when the MUF starts and is incremented for each request. It wraps as necessary. It is typically used to see that the system is performing new work and to determine if a long-running user application is looping. The entire number (if less than 6 digits or else the low order 6 digits) can be used in the REQABORT utility to cancel a request if desired. |
|
RUN_TIME |
CHAR(6) |
No |
The amount of time this request has been running, minus the amount of time it has been in a CA Datacom controlled wait. The format is mmm:ss, where mmm is minutes and ss is seconds. |
|
RUN_UNIT |
INTEGER |
No |
The internal number assigned by CA Datacom/DB to each CA Datacom job. This number is reported in various possible messages relating to the job. |
|
TABLE_NAME |
CHAR(3) |
No |
Name of the table. |
|
TASK_NUMBER |
SMALL INTEGER |
No |
The number of the task area being used for this request, also known as the RWTSA number. The low numbers are allocated for user applications based upon the TASKS Multi-User startup option, followed by internal CA Datacom/DB system task areas. |
|
TRN_SEQ_NO |
CHAR(8) |
No |
Provides the transaction sequence number (TSN) if the current task is in a transaction, or provides blanks if the current task is not in a transaction. |
|
TSN_DURATION |
CHAR(6) |
No |
Provides the duration of the transaction if the current task is in a transaction, or provides blanks if the current task is not in a transaction. The format of the duration is similar to the current request in that it is provided as mmm:ss, except that a time of zero is set to all blanks and a time greater than 999 minutes is set to +++:++. |
|
USER_PATH |
Char (5) |
No |
USER_PATH specifies the path from the user application to the MUF and can be as follows: LOCAL LOCAL is the PATH if the user and the MUF are on the same system and none of the following options were selected. XCF XCF is the PATH if the z/OS XCF facility is being used for communication. CCI CCI is the PATH if the CA CCI facility is being used for communication. IUCV IUCV is the PATH if the z/VSE IUCV facility is being used for communication. *MUF* Request was generated by MUF itself. This includes system requests, and console or console like requests which require an RWTSA, and restart rollback requests. UNKN UNKN is the PATH if the path cannot be determined (this PATH is not expected to occur). |
|
USER_JOBID |
Char (8) |
No |
USER_JOBID is the z/OS JOBID identification of the user application. This may be blanks. |
|
USER_RQ_DATA |
CHAR(32) |
No |
Associated with each active request is 32 bytes of user request data. For record-at-a-time and set-at-a-time commands this data is passed by the user application program. When running a transparency, the transparency provides the information. Requests that are a part of SQL contain a variety of values. The format and content from all sources is totally unpredictable. |
|
USER_SYSTEM_NAME |
Char (8) |
No |
USER_SYSTEM_NAME is the system name, where the user application called the interface. This may be blanks. |
|
WAIT_DURATION |
CHAR(6) |
Yes |
If this task is currently waiting, this column contains the total amount of time since this wait began. The format is mmm:ss, where mmm is minutes and ss is seconds. If the task is not in a wait, this column is null. |
|
WAIT_TIME |
Char(6) |
No |
Specifies 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 WAIT DURATION. |
|
Copyright © 2014 CA.
All rights reserved.
|
|