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.