Data Queue APIs--Categories - FTP Directory Listing - IBM

Create User Queue (QUSCRTUQ) API
To decrease the size of a user queue, a user must delete the queue and create it again.
There are no APIs to manipulate user queue entries. If you must access a user queue object in a library that
does not permit user-domain user objects, you must use data queue objects. For information about data
queues, refer to the CL Programming book.
If you need to know into which domain the user queue object was created, use either of the following APIs
to retrieve that information:
● Retrieve Object Description (QUSROBJD) API
● List Object (QUSLOBJ) API
Note: For performance reasons, the *USRQ object is created before checking to see if it exists in the
library specified for the qualified user queue name. If you have an application using this API repeatedly,
even if you are using *NO for the replace parameter, permanent system addresses will be used.
Note:User queues created with either the number of queue extensions parameter specified with a
positive, non-zero number or the reclaim storage parameter specified to reclaim the user queue storage are
not eligible to save to a pre-V4R5 system.
Authorities and Locks
Library Authority
*READ and *ADD.
User Queue Authority
*OBJMGT, *OBJEXIST, and *READ. These authorities are required only if the replace parameter
is used and if there is an existing user queue to replace.
User Queue Lock
*EXCL. This applies to both the user queue being created and an existing user queue being
replaced.
Required Parameter Group
Qualified user queue name
INPUT; CHAR(20)
The first 10 characters contain the user queue name, and the second 10 characters contain the name
of the library where the user queue is located. The only special value supported is *CURLIB.
User queues created in the QTEMP and QRPLOBJ libraries are not forced to permanent storage;
they are deleted when those libraries are cleared at sign-off and system IPL, respectively.
Extended attribute
INPUT; CHAR(10)
The extended attribute of the user queue. For example, an object type of *FILE has an extended
attribute of PF (physical file), LF (logical file), DSPF (display file), SAVF (save file), and so on.
The extended attribute must be a valid *NAME. You can enter this parameter in uppercase,
http://infocntr.rchland.ibm.com/pubs/html/as400/v4r5/ic2924/info/apis/quscrtuq.htm (2 of 9) [10/4/1999 2:33:25 PM]