|
The parameters for the IFS read API returns the Data which must be defined at a max length. Defining this max length makes RPG init this when the program is loaded. If you define the parm at 32000 for a read, then the program must init this field when it is loaded. Is there a way of getting the information without reading the data, just getting the pointer? Moving the pointers is faster than moving the data. If I define the field at say 512. Then it should return the correct pointer location for the data, but I do not think all the data will be guaranteed to be there. I am using the API's but isn't moving the data and clearing the space taking longer than passing the pointer? Harry Leif Svalgaard wrote: > explain. I'm not sure what you are saying... > > ----- Original Message ----- > From: Harry Williams <planesmart@teleteam.com> > To: <mi400@midrange.com> > Sent: Tuesday, January 01, 2002 10:11 PM > Subject: Re: [MI400] ACCESS to IFS > > > The API returns the data in RPG, not the pointer. But the parms are > pointers, I > > guess I get the pointer for the parm and do not care about the length of > the > > parm? > > Harry > > > > > > Leif Svalgaard wrote: > > > > > From: Harry Williams <planesmart@teleteam.com> > > > > I feel if I can get data specifications for the resolve pointer for > IFS, > > > then I > > > > can get the object. Everybody on this MI list knows why. It has to do > > > with all > > > > my last questions. I need to retrieve images from the Optical systems, > and > > > if > > > > they are stored in IFS. I want to do it in MI because of the speed. > > > Maybe, if > > > > I bought a current MI manual, then maybe it would be there. My current > MI > > > > manual is about a version ago. > > > > > > It is not going to be faster in MI. Read it with an RPG program called > > > from your MI-program. > > > > > > _______________________________________________ > > > This is the MI Programming on the AS400 / iSeries (MI400) mailing list > > > To post a message email: MI400@midrange.com > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/cgi-bin/listinfo/mi400 > > > or email: MI400-request@midrange.com > > > Before posting, please take a moment to review the archives > > > at http://archive.midrange.com/mi400. > > > > _______________________________________________ > > This is the MI Programming on the AS400 / iSeries (MI400) mailing list > > To post a message email: MI400@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/mi400 > > or email: MI400-request@midrange.com > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/mi400. > > > > _______________________________________________ > This is the MI Programming on the AS400 / iSeries (MI400) mailing list > To post a message email: MI400@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/mi400 > or email: MI400-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mi400.
As an Amazon Associate we earn from qualifying purchases.
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.