Re: Display file puzzlement

Adding DSPATR was my idea to make it a little better. Original code did not
have DSPATR(RI HI PC) in it. The ERRMSG line does display, with and without
the DSPATR keyword. I was wondering if I needed to use a keyword to force
redisplay. I had seen that in the manual, but when I looed at another display
file, did not see it used.

John McKee

Quoting Booth Martin <booth@xxxxxxxxxxxx>:

This may work; I am not promising anything.
1-Comment the DSPATR(HI RI PC) line.
2-Make sure the error message is conditioned at that field in the
display file, so the display file knows which line is in error.
3-Then test it.

That may give you your desired behavior.

John McKee wrote:

I inherited a program/display file that needs modification. There is a weird
bug in the display file that I do not understand.

At the record level, there is the conditioned keyword PUTOVR.

At the field level, there is a conditioned DSPATR (HI RI PC).

The same indicator used for PUTOVR and DSPATR is also used to condition an
ERRMSG.

The error message is displayed, but the field that it perains to is unchanged.

Is there another keyword that needs to be included to cause the effected field
to be displayed with the appropriateattribute changes?

Also, if I need the DSPATR to be conditioned by two indicators connected by OR,
on which of the two lines is the DSPATR keyword used on?

Been way to long since I have done much with display files.

Thanks in advance.

John McKee

--
---------------------------------
Booth Martin
http://www.Martinvt.com
---------------------------------

--