RE: INFDS layout for Display Files

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
And code/400 has some autocreate's in there for INFDS:  Actions, Smart
Guides, Create D specification, select infds, select type of infds.  If
you are getting ready to create your first INFDS you might want to use
their field names.  In case others there use code.  That way your fields
names will be similar.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




Buck Calabro <Buck.Calabro@commsoft.net>
Sent by: rpg400-l-admin@midrange.com
04/05/2002 11:34 AM
Please respond to rpg400-l


        To:     rpg400-l@midrange.com
        cc:
        Fax to:
        Subject:        RE: INFDS layout for Display Files


Nelson Smith wrote:

>Help!  I'm trying to understand what
>the manuals are telling me the data
>structure layout looks like for Display
>Files.  There is a common I/O area
>starting at position 241 that contains
>stuff like write-counts, read-counts, etc.
>and then a file-type specific area
>starting at 367 where the Aid Byte,
>cursor locations, etc are (for display files).

The RPG Reference section on File Exception/Errors has a decent
explanation
of all this.  There are several feedback areas:

File feedback - RPG specific info about the file
Open feedback - Info updated at OPEN time
I/O feedback - Info updated at time of I/O operation,
               common to all file types
Device specific feedback - Info updated at time of I/O operation,
               common to the specific file associated with the DS
Get attributes feedback - Info filled by POST

>However, it seems that a POST operation goes
>back and overlays the common area starting at 241)
>with a completely different layout?  Am I reading
>that correctly?  Does anyone have a clear layout
>of what the INFDS looks like for display files only,
>and does it really change on a POST operation?

Yes, Yes, Yes and Yes.  Note that POST without a factor 1 specified is
different from POST and factor 1.  You probably want the latter.  The
first
4 feedback areas mentioned above follow one another in memory.  The Get
Attributes area replaces the Device Specific area when POST occurs.

The aforementioned manual has the positions laid out and I know that
several
people have posted a complete INFDS definition (search the archives
http://archive.midrange.com/index.shtml) but if you're still stuck after
reading the manual I'll post a display file-only example.

By the bye, I learnt this stuff on S/38 manuals but I am looking at the
V5R1
books whilst I type this.  I think the V5R1 books are better than their
predecessors in this area.  If you don't find that to be true by all means
send in the reader reply card (better to light a candle than to curse the
darkness, eh?)

  --buck

"This box Rocks!" - related to 2002 NE IBM
Conference attendees by IBM's Stephanie Joy
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.