Data Queue APIs--Categories - FTP Directory Listing - IBM
Data Queue APIs--Categories - FTP Directory Listing - IBM
Data Queue APIs--Categories - FTP Directory Listing - IBM
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Create User Index (QUSCRTUI) API<br />
Modification 0. A user-domain user index can be directly manipulated with MI instructions and can also<br />
be accessed using system <strong>APIs</strong> at all security levels. On a system with the QSECURITY system value set<br />
to 40 or greater, you must use system <strong>APIs</strong> to access system-domain user indexes. If you create a<br />
permanent object by using this API, you cannot delete the object by using the MI instruction DESINX<br />
when the system security level is set to 40 or greater. You would have to delete the object by using the<br />
Delete User Index (QUSDLTUI) API.<br />
If the user index was created prior to Version 2 Release 2 Modification 0, the size of the user index is<br />
limited to a maximum of 1 gigabyte. (A user index with a size greater than 1 gigabyte cannot be saved to<br />
or restored from a release prior to Version 2 Release 2 Modification 0.) If the user index was created on or<br />
after Version 2 Release 2 Modification 0, the size of the object is limited to a maximum of 4 gigabytes.<br />
The size is dependent on the amount of storage needed for the number and size of index entries and<br />
excludes the size of the associated space, if any.<br />
Note: You can tell whether a user index object can be saved to a release prior to Version 2 Release 2<br />
Modification 0:<br />
●<br />
●<br />
By ensuring that the current object size is less than 1 gigabyte by using one of the following:<br />
❍ The Display Object Description (DSPOBJD) command<br />
❍ The List Objects (QUSLOBJ) API<br />
❍ The Retrieve Object Description (QUSROBJD) API<br />
By ensuring that the key length field is 120 bytes or less by using either of the following:<br />
❍ The Materialize Index Attributes (MATINXAT) MI instruction<br />
❍ The Retrieve User Index Attributes (QUSRUIAT) API<br />
Note: For performance reasons, the *USRIDX object is created before checking to see if it exists in the<br />
library specified for the qualified user index name. If you have an application using this API repeatedly,<br />
even if you are using *NO for the replace parameter, permanent system addresses will be used.<br />
Authorities and Locks<br />
Library Authority<br />
*READ and *ADD.<br />
User Index Authority<br />
*OBJMGT, *OBJEXIST, and *READ. These authorities are required only if the replace parameter<br />
is used and there is an existing user index to replace.<br />
User Index Lock<br />
*EXCL. This applies to both the user index being created and an existing user index being replaced.<br />
Required Parameter Group<br />
Qualified user index name<br />
INPUT; CHAR(20)<br />
The name of the user index being created, and the library in which it is to be located. The first 10<br />
http://infocntr.rchland.ibm.com/pubs/html/as400/v4r5/ic2924/info/apis/quscrtui.htm (2 of 10) [10/4/1999 2:33:41 PM]