Re: Display file puzzlement

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

According to infocenter, that is mostly the behavior.  The exception is that
RESET key is not required to proceed.

Thanks Booth and Simon.  When I had a class on this in 1983 (can't BELIEVE it
was that long ago), either the keywords did not as yet exist, or teacher did
not choose to present them.  Every keyword I have pickup over the years since
has been by reading a manual.  It was a LOT easier to read a manual 
when it was
printed.  I was actually taking the things home to read.

John McKee

Quoting Booth Martin <booth@xxxxxxxxxxxx>:

> Test to see how the ERRSFL keyword affects behavior.  I  believe if you
> specify that keyword at the top of your dds specs you will find that all
> your errors are available on the status line (use the page keys to see
> each of them,)  I believe it also stops the need for the user to press
> the enter key to proceed.
>
> Jeff Young wrote:
> > The ERRMSG keyword will display the message text on the message 
> > line, and set the DSPATR(RI PC) attributes on the field.
> > If there are multiple ERRMSG conditions, the first condition that is 
> > met will display the message.  All others will just set the field 
> > attribute to RI.
> > The ERRMSG keyword also implicitly will not allow the contents of 
> > the screen display to change.
> >
> > Hope this helps,
> >
> >
> > Jeff Young
> > Sr. Programmer Analyst
> > IBM -e(logo) server Certified Systems Exper - iSeries Technical 
> > Solutions V5R2
> > IBM  Certified Specialist- e(logo) server i5Series Technical 
> > Solutions Designer V5R3
> > IBM  Certified Specialist- e(logo)server i5Series Technical 
> > Solutions Implementer V5R3
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ----- Original Message ----
> > From: John McKee <jmmckee@xxxxxxxxxxxxxx>
> > To: midrange-l@xxxxxxxxxxxx
> > Sent: Friday, April 18, 2008 1:38:51 PM
> > Subject: Re: Display file puzzlement
> >
> > Thanks everyone for the help.  I was trying to come up with what I had
> > done from
> > memory last night.  Not as handy as being in front of the screen.  I 
> > now have
> > PUTOVR at the record level, conditioned by an indicator.  At the field
> > level, I
> > have OVRATR and DSPATR, also conditioned by an indicator.  When I 
> > tested a few
> > minutes ago, there was no difference.  It was only when I commented out the
> > ERRMSG that the DSPATR worked.  I am not so sure I like how ERRMSG works
> > anyway, since it locks the keyboard and only one error is shown.
> >
> > Quoting Simon Coulter <shc@xxxxxxxxxxxxxxxxx>:
> >
> >
> > > On 18/04/2008, at 10:15 AM, John McKee wrote:
> > >
> > > > Both PUTOVR and DSPATR are conditioned by the same indicator used
> > > > to condition
> > > > the ERRMSG keyword.
> > > Read what I wrote! Read what the Information Centre says about
> > > PUTOVR! You need OVRATR!
> > >
> > >
> > > > Error indicator is initially set OFF.
> > > >
> > > > I thought DSPATR went on the second line, but tried first one
> > > > anyway.  Made no
> > > > difference.
> > > A  23                        DSPATR(HI RI PC)
> > > A O 28
> > >
> > > will cause a compile error. However,
> > >
> > > A  23
> > > A O 28                        DSPATR(HI RI PC)
> > >
> > > will not. Therefore ...
> > >
> > > Regards,
> > > Simon Coulter.
> > > --------------------------------------------------------------------
> > >    FlyByNight Software        OS/400, i5/OS Technical Specialists
> > >
> > >    http://www.flybynight.com.au/
> > >    Phone: +61 2 6657 8251  Mobile: +61 0411 091 400        /"\
> > >    Fax:  +61 2 6657 8251                                  \ /
> > >                                                              X
> > >                  ASCII Ribbon campaign against HTML E-Mail  / \
> > > --------------------------------------------------------------------
> > >
> > >
> > >
> > > --
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
>
> --
> ---------------------------------
> Booth Martin
> http://www.Martinvt.com
> ---------------------------------
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.