× 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: RE: To read a text file directly
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Mon, 25 Oct 1999 12:32:09 -0400

Scott,
I've been compiling that way for so long that I never thought to see if it
changed.  On V4R3 they are indeed in the default RPG binding directory.
Looks like one less thing I need to remember when doing those IFS compiles!

Buck Calabro

> -----Original Message-----
> From: Scott Klement 
> Sent: Monday, October 25, 1999 11:07 AM
> To:   RPG400-L@midrange.com
> Subject:      Re: RE: To read a text file directly
> 
> Hmmmm...
> 
> This may sound strange, but I find that I don't need to bind to
> QC2LE in order to use the IFS or Sockets API.  The "Unix-type"
> API's appear to be in the default RPG binding directory.
> 
> Granted, I end up binding to QC2LE in order to access the errno,
> and strerror functions...
> 
> I'm at V3R2.  Is this also true on newer releases of OS/400?
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.