×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 16-Jul-2014 16:24 -0500, CRPence wrote:
<<SNIP>>
Note: The older archived discussions, with some topics mentioning the
Object Information Repository (OIR), remain on the archived MI400
list. However I am not aware of any code examples that traverse the
index and\or the space to locate any of the Text, Service,
Save/Restore, Attribute, or Usage information of a particular object.
http://archive.midrange.com/mi400/
Indirectly from one of those discussions, I found what might include
[though doubtful] an MI code example for access to the OIR objects; for
the .USAGE- information anyhow, if at all. But since the code is
available only as a SAVF instead of as source, what is included is not
easily visible for review to determine. And what is there appears only
to be CL and RPG; nothing obvious as MI, although apparent references to
work with User Index (*USRIDX), which the *QDIDX is [effectively].
however the User Idx code does some insert activity, so my inference is
that probably, the user index work is _not against the OIR Index_, but
instead is part of some work processing the records of the output file
of DSPPGMREF data. So FWiW; and anyone is welcome to confirm\reply if
any of the code is MI, used to access the OIR objects via the pointers
stored in the associated space of a resolved library object:
<
http://www.fisketjon.no/firma/as400/dspobjref.htm>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.