DEQUEUE Command

CA Ideal uses enqueues to protect components including programs, panels, reports, and members, and so on. CA Ideal components are protected from simultaneous update, even by another CICS region or a batch job. This protection is at the individual component level (program, panel, report, and so on) rather than at the data set level.

Online, when a transaction abends, the program being edited might remain enqueued. When you sign on again, an attempt to re‑edit the program results in the “resource busy” message. This can also happen when a system failure occurs while displaying an index, output, or jobcard. You cannot dequeue the program from another region because the operating system keeps track of where the enqueue came from. This problem does not occur for a batch job, however, because, when any batch job ends (including CICS), the operating system automatically cleans up all enqueues left outstanding by that job.

The site CA Ideal Administrator has the responsibility to DEQUEUE entities. The site administrator should always determine that the outstanding enqueue is a result of a transaction abnormal termination before issuing the DEQUEUE. For example, if one programmer is editing a panel and a second programmer tries to edit the same panel, the second programmer gets the same “resource busy” message. If the administrator issued a DEQUEUE in this situation and allowed the second programmer to begin editing the panel, serious library corruption could result.

The Command Reference Guide includes the format of this command. Also, see the Administration Guide for information regarding enqueues.

Do not try and relate CA Ideal entities enqueued and dequeued to system data sets or other system objects. CA Ideal generates a unique internal enqueue name for each object. This internal enqueue name does not correspond to any object known to the operating system.

The format for a CA Ideal enqueue name is:

10     20	
+----+----+----+----
$Itsssxxxxxxxxebbbbbbvvv	For PGM, PDL, WDT, PRM,RPT, PGMOBJ, 	and PNL names.
$Itbbbyyyyyyyyyyyyyyyvvv	For PER, SYS, PLA, DVW names.
$Ituuuzzzzzzzzbbbbbbbbbb	For MEM names.

T Type code are defined as follows:
B Plan
D Dataview
K Sequential dataview
L Program procedure source
P Program parameter data
R Report
S Program DD entity
T Program object data
U Panel
W Program working data
X'BB' Person entity (user)
X'CE' System entity
Z Data member
sss System ID.
x..x Program, panel, or report name.
y.. Person, system, or dataview Datadictionary name.
vvv Version number.
e Optional enqueue code to uniquely identify names across systems. Blank if not used.
b..b Spaces.
uuu User ID.
z..z Member name.

For z/OS the major or queue name, ADRPRDCT, is used with the minor or resource name. These names are compressed for VSE to a 12‑byte format. The resulting name might not be printable.

Example

DEQUEUE PGM DEMO1 VER 1 SYS DOC

Dequeues program DEMO1 in system DOC.

DEQUEUE LIBRARY $IDLIB

Dequeues VLS dataview library $IDLIB.