• Subject: Native Files - was "MI" of ILE programs
  • From: "Hans Boldt" <hboldt@xxxxxxxxxxxx>
  • Date: Wed, 1 Oct 97 09:05:46 EDT

John Carr <74711.77@compuserve.com> wrote:
>If VARPG and RPGIV are from the same base complier and since VARPG has
>native file support(being able to read the following C:\MYDIR\MYFILE.DOC)
>in that it can read them as program described data.
>How hard would it be to "Port" that capability to RPGIV?  I mean
>it would be great to be able to read "Native" files on the AS/400 in the
>IFS file system like E:\MYDIR\MYFILE.DOC ,  How about it?
>Right now we can't get AS/400 data to a *STMF in the IFS without doing it
>manually(File Tranfer via CA/400)  or copy to QDLS then copy to a named
>directory/stream file.   Why not just let us "Read & Write" to a named
>directory we created on the IFS like VARPG(hence RPGIV compiler)?
>Maybe a new runtime parm on via a F-Spec keyword like;
>Where &PATH is passed in to the program?

How difficult would it be to implement since VARPG already has it?
About as much work as if VARPG did not have it already!  Don't forget,
there are always system specific considerations.  But we'll add the
requirement to our list.

>Its already in the compiler, Right?  (remind George F. of a
>late night disccussion after CUDS)

Well, I prefer to spend my late nights asleep.  (I've learned not to
trust any work done after midnight!)

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, hboldt@vnet.ibm.com
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

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

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