RE: INFDS layout for Display Files -- RPG400-L

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
In fixed format you could specify the INFDS on the post command.  This
would update a separate data structure.  Thus you could use two different
data structures.  Therefore you could have two external definitions.

This might be the way to go.  Please read about the post operation
carefully:

Even when a POST operation code is not processed, its existence in your
program can affect the way the RPG IV language operates. Usually, the
INFDS is updated at each input and output operation or block of
operations. However, if anywhere in your program, you have specified a
POST operation with no program-device specified, then RPG IV updates the
I/O Feedback Information area and the Device Dependent Feedback
Information area in the INFDS of any file only when you process a POST
operation for that file. The File Dependent Information in the INFDS is
updated on all Input/Output operations. If you have opened a file for
multiple-member processing, the Open Feedback Information in the INFDS
will be updated when an input operation (READ, READP, READE READPE) causes
a new member to be opened.

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




"Smith, Nelson" <NSmith@lincare.com>
Sent by: rpg400-l-admin@midrange.com
04/05/2002 12:15 PM
Please respond to rpg400-l


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


Thanks, Buck.  I didn't ask the question right.

I've used the INFDS for years using an externally defined DS based on the
layouts in the manuals you mentioned.  What I've never used before was the
POST operation and in reviewing it I was seeing a lot of good information
that could be brought into my programs.

What had me confused is how to define the two different layouts for the
same
display file (since I've always used a physical file to bring in the
definitions). I guess, if you want to use both layouts on the same dspf,
the
datastructure will have to be defined internally with both sets of fields
defined over some of the same spaces in the datastructure. This precludes
the use of external definitions, but I guess a /Copy of the source will
have
to suffice for dspf's.  Do you know of any better way to do it?

> -----Original Message-----
> From:          Buck Calabro [SMTP:Buck.Calabro@commsoft.net]
> Sent:          Friday, April 05, 2002 11:34 AM
> To:            rpg400-l@midrange.com
> 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.


************************************************************************************************************************************************************************************************************
This message originates from Lincare Holdings Inc. It contains information
which maybe confidential or privileged and is intended only for the
individual or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the
contents of this message.
All personal messages express views solely of the sender, which are not to
be attributed to Lincare Holdings Inc., and may not be copied or
distributed without this disclaimer.
If you received this message in error, please notify us immediately at
MailAdmin@lincare.com or (800) 284-2006.
************************************************************************************************************************************************************************************************************

_______________________________________________
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.