× 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 Thursday 03 January 2002 08:14, Steve Richter wrote:
> So:
>
> Stream file objects are not stored in contexts.
>
That's true, in general.

> Stream file objects are located by the machine via the "directory contents
> data space index".
>
That's true.

> -----------------------------
>
> Is the directory contents data space index stored in a context ?
>
QP0DSystem_Root and QP0DHidden_System_Root are in the QSYS context, but the
other ones are not in a context.

> Without the context, does the machine have a way of materializing a list of
> all the objects on the system, all the stream file objects on the system ?
>
It can start at the root DSI's and walk the tree.  This is similar to the
QSYS filesystem in which there's a "machine context" that lists all the
libraries (contexts), which list their objects.  The difference is that QSYS
is limited to 2 levels, while IFS is not limited.

> If a "directory contents data space index" becomes damaged, does all its
> member stream file objects become orphans ?   ( compared to when a context
> object is damaged, its member objects still point back to the damaged
> context )
>
Streamfiles have pointers back to the DSI's.  Also, each DSI has a connected
DS (Data Space) that I haven't mentioned, and the streamfile points to the DS
as well.  And I think there are other structures that I'm not familiar with.

--Dave


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.