DEQ call
The Dequeue (DEQ
) call is used to release
a segment that is retrieved using the Q command code.
Format (full function)
Format (Fast Path DEDB)
Call Name | DB/DC | DBCTL | DCCTL | DB Batch | TM Batch | |
---|---|---|---|---|---|---|
For Full-Function and DEDB: | DEQ | X | X | X |
Parameters
- DEDB pcb (Fast Path only)
- Specifies any DEDB PCB for the call.
- i/o pcb (full function only)
- Specifies
the I/O PCB for the
DEQ
call. This is an input and output parameter. - aib
- Specifies the AIB for the call. This is an input and output parameter.
These fields must be initialized in the AIB:
- AIBID
- Eye catcher. This 8-byte field must contain DFSAIBbb.
- AIBLEN
- AIB lengths. This field must contain the actual length of the AIB that the application program obtained.
- AIBRSNM1
- Resource name. This 8-byte, left-justified field must contain the PCB name IOPCBbbb.
- AIBOALEN
- I/O area length. This field must contain the length of the I/O area specified in the call list.
- i/o area (full function only)
- Specifies the 1-byte area containing a letter (A-J), which represents the lock class of the locks to be released. This is a mandatory input parameter.
Usage
The DEQ
call
releases all segments that are retrieved using the Q command code,
except:
- Segments modified by your program, until your program reaches a commit point
- Segments required to keep your position in the hierarchy, until your program moves to another database record
- A class of segments that has been locked using a different lock class
If your program only reads segments, it can release them
by issuing a DEQ
call. If your program does not issue
a DEQ
call, IMS releases
the reserved segments when your program reaches a commit point. By
releasing the segments with a DEQ
call before your
program reaches a commit point, you make them available to other programs
more quickly.
For more information on the relationship between
the DEQ
call and the Q command code, see the topic
"Reserving Segments for the Exclusive Use of Your Program" in IMS Version 15 Application Programming.
Restrictions
In a CICS® DL/I environment, calls made from one CICS (DBCTL) system are supported in a remote CICS DL/I environment, if the remote environment is also CICS (DBCTL).