|
ERRSFL is a file level keyword. It has not effect on field level
display attributes. Reverse image and cursor blinking is control by
field level error keyword such as ERRMSG/ERRMSGID... Below is from IBM:
Conditions occurring during message display:
The displaying of a message using ERRMSG and ERRMSGID is similar to the
displaying of messages by the OS/400 program when field validation
errors are detected.
When a message is displayed because of either the ERRMSG or the ERRMSGID
keyword, all fields on the display are kept, including the field the
message is associated with. Except for option indicators, data in the
output buffer is ignored (that is, any new data from the program is not
sent to the display).
The function keys valid following display of a message are:
Function keys specified at the file level
Function keys specified for the record format for which a message is
displayed, if selected when the message is displayed
When the message is displayed, the following conditions occur:
For all errors:
The message is highlighted.
The cursor is blinked and the keyboard locked until the work station
user presses the Reset key.
For errors associated with input-capable fields:
All fields in error are displayed with their images reversed.
If a field in error has both the underline (UL) display attribute and
the highlight (HI) attribute or the underline (UL) attribute and
COLOR(BLU, WHT, or YLW) specified, its image is not reversed.
The cursor is repositioned to the first displayed field that is in
error.
For errors associated with output-only fields:
The display attribute of the field is not changed.
The cursor is not positioned to the field (it does not change position).
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Monday, April 21, 2008 1:44 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Display file puzzlement
Cursor gets positioned to first error field. Error subfile has all the
errors messages. Absolutely no reverse image with ERRSFL. There is no
CHGINPDFT in the source.
I could post portions, like the file level, record level, and one field
if that would help. Maybe there is a conflicting keyword in that mess
somewhere. Based on the fact that it was written prior to v2r2 (no
ERRSFL), there may be something else wrong.
John McKee
Quoting Booth Martin <booth@xxxxxxxxxxxx>:
?? huh? Reverse image is not working on error fields? What about
cursor positioning?
What you have described should have given you all fields in error as
RI and the cursor should be positioned at what it believes is the
first error field.
I am curious: Are the input-capable fields ever reverse imaged at
some other place, like CHGINPDFT?
John McKee wrote:
I removed PUTOVR, OVRATR, and OVRDTA. Still no RI capability. With
the ERRSFL, though, I guess I can live with it.
John McKee
Quoting Jeff Young <cooljeff913@xxxxxxxxx>:
Remove the PUTOVR, OVRATR and DSPATR keywords.
When you are using ERRMSG / ERRMSGID you do not need them.
The PUTOVR prevents the screen from being updated with the new buffer
contents.
The ERRMSG keyword(s) will handle the DSPATR(PC RI) function.
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: Monday, April 21, 2008 11:17:08 AM
Subject: Re: Display file puzzlement
Back on topic (sort of):
I have been working with ERRSFL, and it is indeed extremely cool.
But, I am not getting the attributes changed on the fields with
errors.
Unfortunately, I do not have access to the email that Simon posted
with the required keywords. However, I am at the computer now, and
here are the keywords I am using and where:
Record level, no conditioning indicator, PUTOVR Field level, no
conditioning indicator, OVRATR Field level conditioning indicator
line by itself and immediately below it
letter O conditioning indicator, DSPATR(RI HI PC)
Cursor does get positioned, but neither RI or HI work. I am assuming
that the only reason that PC appears to work is due to ERRMSG
processing.
I have been looking at the infocenter exaxple page, here:
http://publib.boulder.ibm.com/iseries/v5r1/ic2924/index.htm?info/rzak
c/rzakcmst76.htm
and I don't see why what I am doing does not work. This is
definitely not critical. Or required. But, it is bugging me. Am I
missing a keyword somewhere?
John McKee
Quoting Dave McKenzie <davemck@xxxxxxxxxxxxx>:
[Hide Quoted Text]
That was "amazing" Grace Hopper:
http://en.wikipedia.org/wiki/Grace_hopper
who also found the first computer bug (a moth).
--Dave
Vernon Hamberg wrote:
Have heard it said - it's better to ask forgiveness than to ask
permission!!
At 07:53 AM 4/21/2008, you wrote:
John McKee wrote:
Nobody there read any manuals at all. It was discouraged by theReminds me of the "manager" I had in '74 or '75. I had just read
nitwit "manager". Wastes too much time.
John McKee
some articles about some, relatively, new concepts - structured
programming and top-down design. Maintenance was just starting on
a new system that a lot of novice programmers (including moi) had
programmed, and it was a mess. So I proposed studying and then
using these techniques to develop more maintainable programs. But
the boss said we had too much backlog to waste our time on such
nonsense (unproven concepts in his mind). The lead programmer and
listI just went ahead and did it anyway. The boss was clueless.
* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* * voice
615.995.7024
fax
615.995.1201
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>
--
---------------------------------
Booth Martin
http://www.Martinvt.com
---------------------------------
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
