Re: [MI400] ACCESS to IFS

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

My comments for what they are worth:

Since the Source/Sink MI instructions are both blocked and a royal pain to
work with, isn't MI access to database files generally achieved by calling
various QDM* and QDB* "APIs"?  So what's the big deal with calling a
program to access the IFS?  Using pointers and based storage will allow
you to access all the data.

If you want speed then use C.  It will be at least as fast as MI access,
possibly faster, has direct support for the IFS structure and APIs, and
you can embed most MI instructions in C due to support for MI built-ins.
(Actually, you could probably have written the code to do this in the time
it's taken to experiment.)

IFS files are Byte Stream Spaces which are object type X'1E'.  The
documentation for RSLVSP allows that object type which implies that you
can resolve to an IFS object.  BUT the object name supported by RSLVSP is
restricted to 30 characters.  Does that imply that IFS objects have an
additional layer imposing the hierarchy?  Much like QDLS where the
hierarchy resolves to a single-level-store object.

So, if you could convert the IFS path to the underlying *STMF or *DSTMF
(since the images in question are on optical disk) then you should be able
to resolve to it.  If you can resolve to it you should be able to take a
space pointer to it.  If you can set a space pointer then you can access
the data since a *STMF is a much simpler object than a database file.

Does anyone know if this path to object conversion assumption is valid?
If so, does anyone know where the conversion table is located or an API
(probably undocumented) to perform the conversion?

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------