RE: Capture field name

["Dass, Naveen" <Naveen.Dass@xxxxxx>]

Paul,

      I have already used QUSLFLD API to capture the fields in my program and I 
love to use API's. Infact most of my programs are API driven.  I was just 
curious whether there is any other way to do the same. Like some file 
information function. 

-----Original Message-----
From: paul cunnane [mailto:paul@cunnane.net]
Sent: Monday, November 06, 2000 9:19 AM
To: RPG400-L@midrange.com
Subject: Re: Capture field name


> Is there a way I could capture field names of a file into a
> variable in a RPG program other than using DSPFFD or API's.

I usually try to only offer constructive contributions to this list, but:

Can someone explain to me why there are so many questions (here, and in
other fora) asking for ways to access system information without using API
calls?  For years, we lived in the twilight zone of closed systems, begging
IBM for openness.  They finally delivered, in the form of APIs.

What can be easier than calling an API?  It's just a program call.  Granted,
the list APIs take some getting used to, but they have a consistent
structure that is actually quite easy to work with, especially with a
pointer to a user space.

I'm not ranting, I'm just curious -- can anyone give me an example of a
situation where the use of an API is entirely inappropriate, or too
difficult to use, or whatever?

--
Paul


+---
| 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
+---
+---
| 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
+---