Re: What part of an RPG program is re-used?

On 05-Jul-2011 11:01 , Joe Pluta wrote:

And the user space wins over the user index because I can retrieve
the pointer. There doesn't seem to be a corresponding QUSPTRUS API
for a user index.

Materialize Context (QusMaterializeContext), Materialize Context (MATCTX), and Resolve System Pointer (RSLVSP) can each get the system pointer to a *USRIDX. AFaIK the "User Index" external object type [with user domain] allows the methods supported for an "independent index" to be used; i.e. those with INX in the mnemonic. One doc reference "User index considerations" notes "Modify Independent Index (MODIDX) MI instruction" for a User Index but presumably that meant to suggest MODINX:
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/apiref/conIndexCons.htm

Of course for access by address, some of the QUSxxxUI [User Index] APIs can be bypassed, while some others necessarily must be bypassed. The create and add activity should be able to be performed using the QUSCRTUI and QUSADDUI, and then for the lookups against the [static] object can be performed by FNDINXEN using the system pointer to the object.

http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/apis/obj4a.htm
"In addition to the user index APIs, you can work with user indexes through the following:

* ILE C programming language
* Machine interface (MI) instructions..."

http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/rzarl/rzarle86.htm
"Access
Direct access to a user index using MI instructions (only allowed for a user domain user index in a library specified in the QALWUSRDMN system value."

The above quoted doc references presumably both intend to suggest that one can get "access to a user index using _the various independent index_ MI instructions...". And while C may have the MIH file for the C includes, proper definitions should allow them in other languages too. In support of that, there is a sample program [with a hilarious find\replace substitution that will preclude a successful compile] which uses the QUSCRTUI API to create the *USRIDX, but then uses the MI instructions both to insert and to find index entries:
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/apiref/apiexcredir.htm

The SETACST for the system pointer to the user index should enable placing the object and data into main storage, similar to how that would be done with the space pointer for placing the data of a user space into main storage.

Regards, Chuck