× 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.



I'm using "pointer" in the generic sense--these are not 16 byte MI pointers,
but 8 byte virtual addresses.  They're manipulated by SLIC code below the MI,
not QSYS pgms above the MI.

The "pointer" to the DSI is the address of the beginning of the index object,
not to an entry.  (However the pointer to the DS record IS the address of the
record.)

A pointer (in any sense) can't point to an entry in any kind of index because
an index entry doesn't exist as a contiguous group of bytes; it's made up of
(possibly) multiple nodes at various places in a binary tree.  The SLIC code
that does index retrieval collects data from the nodes into a contiguous
bytestring that's returned to your pgm.

--Dave

On Thursday 03 January 2002 17:58, srichter wrote:
> From: Dave McKenzie <davemck@zbiggroup.com>
>
> >If there are multiple hard links to a *STMF, the *STMF's pointer to the
> > DSI is empty.  But the *STMF's pointer to the DS (Data
>
> DSI is data space index.  Is the pointer to the DSI a 16 byte pointer ?  Is
> this a pointer to the index object or an entry in the index ?
>
> The point of my question being: can a pointer be set to a data space index
> entry ? And can a pointer be set to a user index entry ? So that an index
> entry could be accessed without the use of the FNDINXEN instruction.
>
> Thanks,
>
> Steve Richter


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.