What do the various abbreviations in the DC001010 task stall MODE field mean? For example, in DC001010 V74 T64 TXNID:44756 PROG:LOCKTEST SUBSCHEMA:EMPSS01 MODE:X; what does MODE: X mean and where are these abbreviations documented in the IDMS manuals?

Document ID : KB000054169
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

What do the various abbreviations in the DC001010 task stall MODE field mean? For example, in DC001010 V74 T64 TXNID:44756 PROG:LOCKTEST SUBSCHEMA:EMPSS01 MODE:X; what does MODE: X mean and where are these abbreviations documented in the IDMS manuals?

Answer:

These two IDMS messages; DC001008 and DC001010 contain references to db-key modes. What do the MODE abbreviations mean and where are they documented in the IDMS manuals?

DC001010 V74 T64 TXNID:44756 PROG:LOCKTEST SUBSCHEMA:EMPSS01 MODE:X

When these messages refer to the <db-key mode>, they are actually referring to the locking mode in which the dbkey is held, i.e., the type lock placed on the dbkey.

These type of locks are documented in section 38.4.2 of the CA-IDMS Database Administration Guide. The abbreviations are:

NL    = No lock
IS    = Intent share
IX    = Intent exclusive
S     = Share
U     = Update
UIX   = Update & intent exclusive
UIX+  = No row locks
X     = Exclusive

The full manual text is as follows:

Mode: Share

Typically used to guarantee that no updates are made to data while a transaction is accessing it. A share lock is compatible with other share locks but not with exclusive locks. A share lock placed on an area implies a share lock on each record within the area.

Mode: Exclusive

Typically placed on a resource to protect transactions from accessing data that is being updated by the issuing transaction. An exclusive lock is incompatible with both share and other exclusive locks. An exclusive lock placed on an area implies an exclusive lock on all records within the area.

Mode: Null-lock

A null-lock is a special type of lock which is placed on a record to signify a notify lock and on an area to signify transient retrieval access. Null-locks provide no protection against concurrent access.

Mode: Intent share

Allows share (S) locks to be placed on records within the area.

Mode: Intent exclusive

Allows exclusive (X) locks to be placed on records within the area.

Mode: Update intent exclusive

Allows exclusive locks to be placed on records within the area by the issuing transaction, but not by other transactions.

References:

CA IDMS Database Administration, chapter 38.4.2 Types of Locks.