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?
-----Original Message-----
From: c400-l-bounces@xxxxxxxxxxxx [mailto:c400-l-bounces@xxxxxxxxxxxx] On Behalf Of Flensburg, Carsten
Sent: Wednesday, January 22, 2014 6:48 PM
To: 'Bare Metal Programming IBM i (AS/400 and iSeries)'
Subject: Re: [C400-L] Struggling with API QDFRTVFD
There's also a " Specified length of field (DDS field length)" (WDFWLFLD) in the Where-Used Field Information Structure (QDFWFLDI).
Cheers,
Carsten
-----Original Message-----
From: c400-l-bounces@xxxxxxxxxxxx [mailto:c400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jevgeni Astanovski
Sent: 22. januar 2014 16:39
To: 'Bare Metal Programming IBM i (AS/400 and iSeries)'
Subject: Re: [C400-L] Struggling with API QDFRTVFD
Thanks a lot Mark!
I saw this field but could not understand what means its description:
Program length. User's program field length for floating point fields indicates precision 4 is defined as *SINGLE; 8 is defined as *DOUBLE.
I've been looking for a field length, not a program length. Probably that was my biggest mistake :-)
Whatever. This is exactly what I needed.
Jevgeni
-----Original Message-----
From: c400-l-bounces@xxxxxxxxxxxx [mailto:c400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Wednesday, January 22, 2014 5:35 PM
To: Bar- Metal Programming IBM i (AS/400 and iSeries)
Subject: Re: [C400-L] Struggling with API QDFRTVFD
Jeygeni:
Search the InfoCenter page for QDFRTVFD for "Named Field Header Table
(QDFFFNAM) -- see position 4 WDFFPLEN ... this should be the length of the field as defined in the buffer(s) -- as your programs will see it.
Note that the next field in this data structure is the number of decimal places (WDFFDEC). If you want the length of the field when it is displayed on the screen, see the "Field Indexing Table" (QDFFFITB), offset 6 - WDFFDLEN ...
If you do a google search for "QDFRTVFD API" (without quotes) you can also find several helpful articles that discuss using this API.
Hope that helps,
Mark S. Waterbury
On 1/22/2014 8:53 AM, Jevgeni Astanovski wrote:
Hi,
I've spent 3 full days fighting with API QDFRTVFD (Retrieve Display File Description).
People say that it is one of the most (if not the most) complicated APIs to use.
So far so ALMOST good.
My goal is to retrieve output, both and hidden fields from all formats together with their names, types and sizes.
I cannot use much simplier QUSLFLD, as there is no information about the field "attribute" - output/hidden/both - and I need it.
I've got ALMOST everything I needed.
The only thing that I cannot find is field length!
For example if my DSPF's DDS contains row
VERSION 3A O 1 11TEXT('Program version')
then I would like to get "3" from somewhere.
All the rest (field name, data type, field type, position on screen) I found, but not the length.
The only thing that looks similar is field offset in the buffer, but it would be stupid to sort and subtract.
Does anyone know what structure of this API keeps field data length?
Thanks in advance,
Jevgeni
--
This is the Bare Metal Programming IBM i (AS/400 and iSeries) (C400-L) mailing list To post a message email: C400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/c400-l.
--
This is the Bare Metal Programming IBM i (AS/400 and iSeries) (C400-L) mailing list To post a message email: C400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/c400-l.
This communication is intended only for use by the addressee.It may contain confidential or privilegedinformation.
If you receive this communication unintentionally, please inform us immediately and delete this e-mail and any attachments.
Warning: Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
--
This is the Bare Metal Programming IBM i (AS/400 and iSeries) (C400-L) mailing list To post a message email: C400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/c400-l.
midrange.com
