Re: ACCESS to IFS -- MI400

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

Subject: Re: [MI400] ACCESS to IFS
From: Gene_Gaunt@xxxxxxxxxxxxxxx
Date: Wed, 2 Jan 2002 09:26:23 -0500
List-archive: <http://archive.midrange.com/mi400/>
List-help: <mailto:mi400-request@midrange.com?subject=help>
List-id: MI Programming on the AS400 / iSeries <mi400.midrange.com>
List-post: <mailto:mi400@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/mi400>,<mailto:mi400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/mi400>,<mailto:mi400-request@midrange.com?subject=unsubscribe>

To read IFS stream file in MI:

Call the Call Service Program Procedure (QZRUCLSP) API, in the "Program and
CL Command APIs" book, from your MI program using CALLX.  Put service
program name "QP0LLIB1  QSYS" in parameter one, put stuff like "open" and
"read" and "close" in parameter two.

Unblocked MATAUOBJ will cough up system pointers to the  X"1E01" stream
file objects your profile owns.  Besides MATSOBJ, I think instructions that
work on pointers to X"1E01" objects probably aren't documented in the
Functional Reference.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: ACCESS to IFS , Harry Williams

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.