×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Hi Jevgeni

How are things, hope all is well.
Did you manage to get the API working?

I have a RPG version coded here. http://wiki.midrange.com/index.php/QDFRTVFD
The API is VERY BIG and my program only gets the basic info of
Fields/Constants and attributes.
But I am not doing so well in converting it to C.

Perhaps you have some suggestions.


Regards
Frank


From: Jevgeni Astanovski <Jevgeni.Astanovski@xxxxxxxxxxxxx>
Date: Fri, 24 Jan 2014 15:01:34 +0000

Thought that "with a little help" from Mark and Carsten I solved my
problem.
How mistaken I've been...
I only need a list of fields with field name, I/O attribute, field type
and length.

Found field names in QDFFNTB structure. Very good. All other necessary
data was also available starting from there.
But then I found out, that hidden fields' names are missing in QDFFNTB
structure at all! Field is mentioned, I can retrieve all attributes - but
not the name...

Continued searching - as Carsten advised - went to QDFWFLEI and from there
to QDFWRCDI and QDFFNTBL.
Very good again, now all names available, including hindden, also field
lengths.
But how to get data type and I/O? There is an index to QDFFFITB, but I saw
that in my DSPF with 7 formats these indexes repeate. So they are unique
inside one format only. And I failed to find reference to format names in
Where-Used part of the puzzle...
The only idea I have by now is to rely on formats order and assume that
order of records in "Where-used" section matches exactly order of formats
in Record format table (QDFARFTE)

Or I am missing something again?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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