CA Datacom Core 15.1

PDF
15.1 15.0
English

COMM STATUS (Print Status of MUF Jobs)

The COMM STATUS option displays the status of all jobs operating through the MUF. If a job is waiting, the status report shows the reason. When executed through DBUTLTY, that is, COMM OPTION=STATUS, the utility job is always listed in the report with a status of ACTIVE, except in z/OS with a DBSIDPR not specifying XCF.
datacom
The COMM STATUS option displays the status of all jobs operating through the MUF. If a job is waiting, the status report shows the reason. When executed through DBUTLTY, that is, COMM OPTION=STATUS, the utility job is always listed in the report with a status of ACTIVE, except in z/OS with a DBSIDPR not specifying XCF.
The COMM STATUS function communicates with one MUF. Be aware of the following:
  • Ensure that DBUTLTY is communicating with the desired MUF by executing DBUTLTY with the same System Identifier module (DBSIDPR) that is being used by the MUF, and
  • Ensure proper load library concatenation by keeping the System Identifier modules (DBSIDPR) in separate load libraries.
If the z/OS Cross-System Coupling Facility (XCF) is being used, ensure that the TOGROUP DBSIDPR parameter is correctly defined.
When using a console command, these steps are unnecessary.
When to Use
Use the COMM STATUS option when you want to display the status of a job.
How to Use the Console Command
The MUF must be active when you execute this command. The console STATUS command provides substantial information but not all of the information that is provided using DBUTLTY COMM STATUS.
Use the following in your command to initiate this function from the system console. Consult your site operating system documentation for additional syntax information.
►►─┬────────┬─ STATUS ────────────────────────────────────────────────────────►◄
   └─ COMM ─┘
Command
  • COMM
    You can omit the COMM function name when submitting this console command.
  • STATUS
    Requests a display of the current tasks in the MUF.
How to Use the DBUTLTY Command
Execute the COMM function with the following command format:
►►─ COMM OPTION=STATUS ─┬──────────────────────────┬──────────────────────────►
                        └─ ,DEST= ─┬─ PRINTER ◄ ─┬─┘
                                   └─ CONSOLE ───┘

 ►─┬──────────────────────┬───────────────────────────────────────────────────►◄
   └─ ,IGN68= ─┬─ NO ◄ ─┬─┘
               └─ YES ──┘
Command
  • COMM
    Invokes the function to pass communication to the MUF.
Required Keyword
  • OPTION=STATUS
    Requests that the current status of tasks in MUF be displayed.
    In z/OS, when DBUTLTY is executing on the same System as the MUF, the data is returned directly from memory with no MUF request. Also note that the DBUTLTY COMM OPTION=STATUS provides more information than the console STATUS, and this additional information may or may not be important to see.
Optional Keywords
  • ,DEST=
    Specifies the destination for the status report. CONSOLE causes the report to appear on both the console and SYSPRINT. PRINTER causes the report to appear on SYSPRINT only.
    When routing print to the console, headings do not appear.
  • IGN68=
    Specify IGN68=YES to ignore a return code 68. IGN68= is allowed for every ACCESS and COMM function. By ignoring return code 68, you can set up and run JCL that incorporates a stack of DBUTLTY functions without requiring that the MUF be enabled. IGN68= would therefore be useful, for example, if you wanted to load a database without first enabling the MUF, perhaps to allow restart to properly occur. Following is an example showing a stack of DBUTLTY functions that use IGN68=.
     ACCESS STATUS=UTLTY,DBID=997,USERS=WAIT,IGN68=YES
 COMM   OPTION=CLOSE,DBID=997,IGN68=YES
 INIT   AREA=IXX,DBID=997
 INIT   AREA=A01,DBID=997
 LOAD   AREA=A01,DBID=997,FORMAT=NONE,KBYTES=9999,SORT=1
 ACCESS STATUS=WRITE,DBID=997,IGN68=YES
    If the CXX is externally secured, the INIT and LOAD functions do not execute without the MUF being available, and IGN68=YES is therefore not recommended.
    A function or functions specified with IGN68=YES generates message DB13001E to note that the function did not occur. Because no error was recognized, however, other functions in the stack continue to execute, and the DBUTLTY step ends without a recognizable error. Message DB13001E signals that the MUF was not enabled.
    For details about DB13001E, access the Messages.
    The DBSYSID macro parameter DELAY68= can be used to specify the number of minutes that the MUF connection can wait if the MUF is not currently available. But if IGN68=YES is specified, DELAY68= is ignored and the function continues. If the delay is desired, however, either do not specify IGN68=, in which case it defaults to NO, or specify IGN68=NO.
    • Valid Entries:
      NO or YES
    • Default Value:
      NO
Example JCL
The following shows the command to print the status of all jobs operating through the MUF.
Use the following as a guide to prepare your JCL. The JCL statements are for example only. Lowercase letters in a statement indicate a value you must supply. Code all statements to your site and installation standards.
 //jobname    
See the previous note and 
.

 //       EXEC PGM=DBUTLTY,REGION=2M
 //STEPLIB    
See the previous note and 
.

 //SYSIN    DD *                                   Command input
           COMM     OPTION=STATUS
 /*
Sample Report
Following is a sample report page. For an example report header, see Sample Report Headers.
DDB--Sample Report COMM STATUS Utility (15.0)
                    CONTROL CARD(S)
                    .........1.........2.........3.........4.........5.........6.........7.........8
                   COMM OPTION=STATUS

                    FUNCTION=COMM
                       OPTION=STATUS
The page of the report shows the following:
  • 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.
 MULTI-USER DBDVM02  AVAILABLE         TASKS - ATTACHED-----1, AVAILABLE----24

 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
This page of the report shows the following:
  • MULTI-USER DBDVM02 AVAILABLE
    This is a message indicating the MUF job status.
  • JOBNAME
    Displays the name of the active job currently connected to the MUF or, if a system task, one of the following:
    • ***ACTNG
      Accounting
    • ***CDCL*
      A Change Data Capture Listener (CDCL) task
    • ***CDCM*
      A Change Data Capture Monitor (CDCM) task
    • ***CONSL
      MVS modify /F processing
    • ***D-DDB
      Datacom/Star
    • ***DBCOM
      Tasks that process a console request, such as COMM CLRPXX
    • ***DBKEY
      Dedicated to 24x7 asynchronous index definition additions and deletions.
    • ***DBOPN
      MUF immediately after the enable to allow accounting, and other system tables the opportunity to open
    • ***DBRST
      RESTART function during the enable of the MUF
    • ***DBSYS
      Rare systems functions
    • ***DBURI
      When the
      CA Datacom® Datadictionary™
       attribute URI-REUSE is set to Y (yes), after the URI count reaches 3G, an asynchronous scan of the data area is scheduled in the MUF. This scan uses a system task with a jobname of ***DBURI.
    • ***HISTR
      History database spill
    • ***IOCMP
      Asynchronous I/O completion system processing
    • ***
      MOVDS
      MUF command ONLINE_AREA_MOVE
    • ***MPLXX
      MUFplex system processing - normal
    • ***MPLXY
      MUFplex system processing - normal
    • ***MPLXZ
      MUFplex system processing - abnormal
    • ***RCPAD
      MUF command REMOVE_COMPRESS_PAD OR REPORT_COMPRESS_PAD
    • ***QUEUE
      Index queue
    • ***SCRTY
      Security
    • ***SPILL
      Log spilling
    • ***STAR
      CA Datacom®
       STAR system
    • ***STARX
      CA Datacom®
       STAR user requests
    • ***TA24
      Table Alter 24x7 using Datadictionary DDUPDATE with 1000 ALTER for a table
  • R-UNIT
    Displays the run unit number, where nnnnn is the low order five digits with leading zeros suppressed (nnnnn is zero for system tasks).
  • TASK
    Displays the task number nnnn (RWTSA ID) where the task is running.
  • STATUS
    The status messages occur in groups based on task status. STATUS can be one of the following:
    • ABENDING
      The task has detected a task abend.
    • ACCESS AREA SMP
      An ACCESS with an AREA specified is running and interacting with processes that care about the ACCESS AREA function.
    • ACTIVE
      A request is active (only one task can be active).
    • ANOTHER MUFPLEX
      A task is waiting on another MUF in the MUFPLEX to take an action.
    • BUFFER, CXX
      A task is waiting on a specific Directory (CXX) block to become available.
    • BUFFER, DATA
      A task is waiting on a specific data area block to become available.
    • BUFFER, DXX
      A task is waiting on a specific Index Area (DXX) block to become available.
    • BUFFER, IXX
      A task is waiting on a specific Index Area (IXX) block to become available.
    • BUFFER, LXX
      A task is waiting on a specific Log Area (LXX) block to become available.
    • CDC TSN RC14
      A CDCU program is waiting for a TSN record to be added.
    • CICS COLD START
      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.
    • CICS IN DOUBT
      A task is waiting on CICS to provide resolution for a two-phase commit.
    • CLOSE,
      aaabbbbb
      The task is waiting on the close of the named area-database (
      aaabbbb
      ).
    • DEQ/UNLOCK CXX
      Reflects that the task is waiting on the MVS DEQ (for MVS) or z/VSE UNLOCK (for z/VSE) of the CXX.
    • ENQ/LOCK CXX
      Reflects that the task is waiting on the MVS ENQ (for MVS) or z/VSE LOCK (for z/VSE) of the CXX.
    • EOJ IN PROCESS
      An EOJ is in process.
    • HISTORY SPILL
      Either a close is waiting on the history spill task, or the history spill task is waiting on a close.
    • LOG CHAIN LOCK
      A task is waiting on the log chain.
    • LOG FORCE BLOCK
      A task is waiting for the read forced list lock in a MUFplex environment.
    • MOVER BA24 TM24
      A task is waiting to start a DBUTLTY LOCK MOVER on a BA24 or TM24 or the reverse. Those items are in conflict.
    • MUFPLEX LIST CF
      A task is waiting on an outstanding XES list request.
    • NOT ACTIVE
      The status is not active.
    • OPEN, aaabbbbb
      The task is waiting on the open of the named area-database (aaabbbbb).
    • PENDING
      A request has been transmitted but has not yet been accepted by the MUF.
    • PLEX LIST DBAR
      Directory (CXX) area control record, MUFplex Coupling Facility lock. With this condition, the DBID field contains the specific base required, and the table name field contains the specific area required.
    • PLEX LIST DBCR
      Directory (CXX) base control record, MUFplex Coupling Facility lock. With this condition, the DBID field contains the specific base required.
    • PLEX LIST DBFC
      Log Force Area (FXX), MUFplex Coupling Facility lock.
    • PLEX LIST DBLC
      Log control/current blocks, MUFplex Coupling Facility lock.
    • PLEX LIST DBLF
      Directory (CXX) table control record, MUFplex Coupling Facility lock. With this condition, the DBID field contains the specific base required and the table name field contains the specific table required.
    • PLEX LIST DBLG
      Log add record, MUFplex Coupling Facility lock.
    • PLEX LIST DBUL
      Log uncertainty block, MUFplex Coupling Facility lock.
    • PLEX LIST DBYJ
      TSN, MUFplex Coupling Facility lock.
    • PLEX LIST DBYR
      Run unit record, MUFplex Coupling Facility lock.
    • PLEX LIST DBYU
      Assigned lock index, MUFplex Coupling Facility lock.
    • PLEX LOCK CF
      A task is waiting on an outstanding XES lock request.
    • PLEX MSG REPLY
      A task has sent a message to another MUF in the MUFplex and is waiting on a response from that MUF.
    • POSTED
      The MUF has accepted the task but has not dispatched it because of priority.
    • PRC TCB RUNNING
      A procedure is running on behalf of this task in a procedure TCB.
    • READY TO RUN
      The resource upon which the task was waiting has become available. Task is ready to be dispatched, based on priority.
    • SYS STATS FLUSH
      A task is waiting on a close lock that controls flushing statistics to the PXX.
    • TASK ACTIVE
      The CICS transaction has a locked thread but is not currently waiting on a MUF request.
    • VARIABLE LOG
      A task is waiting on a control within the log area
    • WAIT ACCT ENTRY
      A task is waiting to update a particular entry in the Accounting buffer.
    • WAIT ACCT GLOBL
      A task is waiting on the Accounting global chain.
    • WAIT ACCT TABLE
      A task is waiting on a specific Accounting table to record or remove information.
    • WAIT ACT'G
      A task is waiting on the Accounting Facility.
    • WAIT ADD LOG RC
      A task is waiting on access to current log buffer.
    • WAIT BFR LOCK C
      A task is waiting to access a CXX block on another task owning lock.
    • WAIT BFR LOCK D
      A task is waiting to access a data block on another task owning lock.
    • WAIT BFR LOCK E
      A task is waiting to add an expand buffer on another task owning lock to add an expand buffer
    • WAIT BFR LOCK I
      A task is waiting to access an index IXX block on another task owning lock.
    • WAIT BFR LOCK L
      A task is waiting to access a Log Area LXX block on another task owning lock.
    • WAIT BFR LOCK X
      A task is waiting to access an index DXX block on another task owning lock.
    • WAIT CBS
      A task is waiting on access to the CBS buffer lock.
    • WAIT CBSBFR SPL
      A task is waiting for a set in the CBS buffer to spill to the IXX.
    • WAIT CDCL POLL
      This Change Data Capture Listener task is waiting for work.
    • WAIT CICS START
      A task is waiting on CICS to provide resolution for a two-phase commit, but the controlling CICS is not up.
    • WAIT CMPUS EXIT
      A task is waiting on a non-RENT user compression exit.
    • WAIT DATA SP MG
      A task is waiting on the Data Space Management lock.
    • WAIT DB MISC
      A task is waiting to own DB miscellaneous lock on another task owning lock.
    • WAIT DBIO 24BIT
      A task is waiting to add another DBIO 24-bit control block on another task owning lock.
    • WAIT DBLC LOCK
      A task is waiting on the logging current block lock on another task owning lock
    • WAIT DBUL LOCK
      A task is waiting on the log uncertainty list (DATACOM STAR) lock on another task owning lock
    • WAIT DBYJ LOCK
      A task is waiting on the TSN Coupling Facility record on another task owning record.
    • WAIT DBYU LOCK
      A task is waiting on the YU Coupling Facility record on another task owning record.
    • WAIT DEFRAG
      DEFRAG is running and interacting with a read backward request.
    • WAIT E/C
      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.
    • WAIT HASH DATA
      A task is waiting on the hash chain for a data area buffer.
    • WAIT HASH DXX
      A task is waiting on the hash chain for a DXX buffer.
    • WAIT HASH IXX
      A task is waiting on the hash chain for an Index Area buffer.
    • WAIT HASH STAR
      A task is waiting on the HASH list within Datacom STAR on another task owning the list.
    • WAIT I/O
      A task is waiting on an I/O event.
    • WAIT INDEX QUE
      A task is waiting on access to the index queue.
    • WAIT INTERLCK D
      A task is waiting on the interlock detection lock.
    • WAIT LOCK LIST
      A task is waiting on access to the exclusive (share) list control tables.
    • WAIT LOG DELAY
      A task is waiting on log delay based on your specifying X_LOG_DELAY_BLK.
    • WAIT LRU CXX
      A task is waiting on the least recently used chain for a Directory (CXX) buffer.
    • WAIT LRU DATA
      A task is waiting on the least recently used chain for a data area buffer.
    • WAIT LRU DXX
      A task is waiting on the least recently used chain for a DXX buffer.
    • WAIT LRU IXX
      A task is waiting on the least recently used chain for an Index Area buffer.
    • WAIT LRU LXXTXB
      A task is waiting on the least recently used chain for a Log Area (LXX) buffer for transaction backout.
    • WAIT MRDF (C/V)
      A task is waiting on the COVERED/VIRTUAL area lock on another task owning the lock.
    • WAIT MU-DSF
      A task is waiting on a MUF DSF control lock on another task owning the lock.
    • WAIT NEWRXX
      A COMM NEWRXX function is waiting on the open/close subtask to open or close the RXX.
    • WAIT OFT
      A task is waiting on access to the open list of tables lock.
    • WAIT OPEN EXIT
      A task is waiting on open exit.
    • WAIT PHY READ
      BA24 or TM24 are waiting on a physical read task or a physical read task is waiting on BA24 or TM24.
    • WAIT PLEX ABEND
      A MUF is in the process of being enabled in a MUFplex environment, and it is waiting on a prior MUF to finish recovering from an ABEND.
    • WAIT PLEX BDE
      A task is waiting on MUFplex processing for a particular BDE.
    • WAIT PRC CHAIN
      A task is waiting on the procedure chain processing lock.
    • WAIT PROC TCB
      A task is waiting for a PROCEDURE TCB. All procedure TCBs are currently in use.
    • WAIT REBUILD CF
      A task is waiting on the Coupling Facility rebuild process on another task owning the lock.
    • WAIT REQ
      A task is waiting on a request in another task area to complete before executing a spill.
    • WAIT RL-PLEX-JN
      A task is waiting on DBID that is transitioning to shared in a MUFplex.
    • WAIT SECURITY
      A task is waiting on security validation.
    • WAIT SEQBUFS SQ
      A task is waiting to start a BA24 but a task has sequential buffers at a smaller size still running.
    • WAIT SPILL
      A task is waiting on a spill to complete.
    • WAIT SQL ATTACH
      A task is waiting on access to the SQL ATTACH list lock.
    • WAIT SQL GLOBAL
      A task is waiting on access to the SQL GLOBAL list lock.
    • WAIT SQL MEMORY
      A task is waiting on an SMP lock around the SQL call to memory manager.
    • WAIT SQL MISC
      A task is waiting on the SQL miscellaneous lock.
    • WAIT SQL PLAN
      A task is waiting on access to the SQL PLAN list lock.
    • WAIT SQL SOURCE
      A task is waiting on an SQL resource on another task owning the resource.
    • WAIT SQL STATUS
      A task is waiting on access to the SQL STATUS list lock.
    • WAIT SQL TTM
      A task is waiting on access to the TTM table lock.
    • WAIT SQL URT
      A task is waiting on access to the SQL URT list lock.
    • WAIT STAR 2PHAS
      A task is waiting on STAR two-phase commit lock on another task owning the lock.
    • WAIT STAR SCHED
      A task is waiting on access to
      CA Datacom®
       STAR scheduling.
    • WAIT STAR STOR
      A task is waiting on access to
      CA Datacom®
       STAR storage.
    • WAIT STAR
      A task is waiting on
      CA Datacom®
       STAR distribution.
    • WAIT SUBTASK
      A task is waiting on a subtask completion.
    • WAIT TASK
      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 Sample Report: COMM STATUS Utility).
    • WAIT TASK DELAY
      QUIESCE is waiting on an active request.
    • WAIT TIMER LOCK
      A task is waiting on the timer and cancel lock.
    • WAIT TSN
      A task is waiting on the TSN lock to check, assign, or remove an iiiiiiiiictive transaction.
    • WAIT W/P CH DAT
      A task is waiting on the write pending chain for a data area buffer.
    • WAIT W/P CH IDX
      A task is waiting on the write pending chain for an Index Area buffer.
    • WAIT XCF RQST
      A task is waiting on an XCF request lock on another task owning the lock.
    • XCF RRS RESET
      A task is waiting on an RRS RESETon another task owning the lock.
  • CMD
    Displays the command in the Request Area. This might be blank for a system task.
  • DBID
    Displays a database ID (not listed when not applicable).
  • TBL
    Displays a table name (not listed when not applicable).
  • SEQ
    Displays 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
    Displays the length of time in minutes and seconds since the MUF 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.
  • I/O
    Displays 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
    Displays (xxxxxxxx or tran-term-opr-xxxxx) under the following circumstances:
    • Under
      CA Datacom®
       Server 5.0 or later, the ID field contains an 8-character transaction identifier and the 8-character name associated with the PC.
    • If a CICS transaction has a request active or if CICS has a transaction without an active request but a locked task area, the following are displayed:
      • tran The CICS transaction identifier
      • term The CICS terminal ID
      • opr The CICS operator ID
      • xxxxx CICS sequence number
    • If executing a DBUTLTY function with a request in the MUF, the field provides the literal 'DBUTLTY ' followed by the function being executed (except DBTEST PGM=DBTSTPR, which is treated as an easy test program and not as a privileged utility function).
  • TSN
    Only displayed on updates after a Transaction Sequence Number has been assigned.
  • OWNR/Y TSN-TM
    Displays the task of the owner (OWNR) and the number (Y) of the MUF 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.
  • JOBNAME
    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 MUF 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
    Displays the run unit number, where
    nnnnn
     is the low order 5 digits with leading zeros suppressed (
    nnnnn
     is zero for system tasks).
  • TASK
    Displays the task number
    nnnn
     (RWTSA ID) where the task is running.
  • VALUE/RID
    Displays 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
CA DMS
CA-Disk has serialized a process within this MUF.
Variable (format unknown to
CA Datacom®/DB
)
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 queue/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.
Database ID
Table ID
Key ID
Key value to be added/updated.
DBSMVR
A user has executed the DBUTLTY LOCK function to block moved records.
Database ID and Area name
DBSOIF
Concurrent ONLINE_INDEX_FORMAT2 processes are prevented from running simultaneously against the same database. It also serializes creating a new KEYID when ONLINE_INDEX_FORMAT2 is running against a database.
Database ID
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 procedure 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.
Database ID
Table ID
Key ID
Key range
DBSSIX
CA Datacom®/DB
 has locked the data space management index during maintenance.
Database ID
Area name
Block group number
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.
The following is also printed per task with the JOBNAME, R-UNIT, and TASK fields, followed by the new 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:
JOBNAME R-UNIT TASK BREF R-TIME C-TIME D-TIME W-TIME  PATH U-SYSTEM  U-JOBID USER-ID                         EOJ_OK
 DBDVLSTS 44431    1                    *NULL* *NULL* UNKN CA11     JOB39119 COMM                            YES
  • BREF
    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
    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
    C-TIME is the CPU time that the current request (SQL, SAAT, or 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
    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
    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
    PATH is 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. 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
      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.
    • UNKN
      UNKN is the PATH if the path cannot be determined (this PATH is not expected to occur).
  • U-SYSTEM
    U-SYSTEM is the system name, where the user application called the interface.
  • U-JOBID
    U-JOBID is the z/OS JOBID identification of the user application.
  • USER-ID
    USER-ID is the 32-character user ID, if this request was made through the DBNTRY entry point.
  • EOJ_OK
    EOJ_OK is YES or NO as specified. For more information, see the DBURSTR parameter EOJ_OK.
Sample COMM STATUS Online
     .
     .
     .
 DB01311I - STATUS
 DB01327I - Multi-User AVAILABLE, Tasks - Attached----63, Available----87
 DB01328I - TIME   I/O  JOBNAME  R-UNIT TASK CMD-DBID-TBL    SEQ STATUS          ID                       OWNR/Y TSN-TM
 DB01329I -    :06  257 ***SPILL         157 SPILL               WAIT I/O
 DB01329I -             QA#@T796  43571   71                     TASK ACTIVE     MLT:-T004-DB:-35651
 DB01329I -             QA#@T796  43571   73                     TASK ACTIVE     MLT:-T006-DB:-67725
 DB01330I -             QA#@T796  43571   68 NOT ACTIVE(0002)
 DB01329I -             QA#@T796  43571   70 DELET 796F01 678444 READY TO RUN    MLT:-T003-DB:-48157
 DB01329I -           1 QA#@T796  43571   74 ADDIT 796K01 678392 WAIT I/O        MLT:-T007-DB:-16740
 DB01329I -           2 QA#@T796  43571   72 ADDIT 796F03 678393 WAIT I/O        MLT:-T005-DB:-21126
 DB01329I -             QA#@T797  43572   77                     TASK ACTIVE     MLT:-T003-DB:-28504
     .
     .
     .
 DB01329I -             T784TST1  43561   23 ADDIT 784F03 736153 WAIT E/C DBSMVR MLT:-T005-DB:-18420      21
 DB01329I -             T784TST1  43561   24 ADDIT 784RNA 736160 WAIT E/C DBSMVR MLT:-T006-DB:-25068      21
 DB01329I -             T784TST1  43561   21 ADDIT 784F01 736183 WAIT E/C DBSMVR MLT:-T003-DB:-22024      21
 DB01329I -             T787TST1  43566   42                     TASK ACTIVE     MLT:-T006-DB:-29239
 DB01329I -             T787TST1  43561   39 ADDIT 784F01 736564 READY TO RUN    MLT:-T003-DB:-27574
     .
     .
     .
 JOB05796  DBDVMUF7:DB01331I - JOBNAME  R-UNIT TASK VALUE/RID
 JOB05796  DBDVMUF7:DB01332I - T784TS1   43561   23   784 F03
 JOB05796  DBDVMUF7:DB01332I - T784TS1   43561   24   784 RNA
 JOB05796  DBDVMUF7:DB01332I - T784TS1   43561   21   784 F01