× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The problem is due to the way ERRMSG is handled.
When you use ERRMSG, it does *not* refresh the screen display with the current
contents of the fields.
What you need to do is after you clear the #Msg field, issue a WRITE to the
record format. This will *not* cause the screen to be redisplayed, but *will*
refresh the contents of the screen buffer.
When you issue the ERRMSG next, the screen will reflect the correct contents
for the #ERMSG field.

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: Doug Palme <dpalme@xxxxxxxxxxx>
To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
Sent: Monday, April 30, 2007 9:40:45 AM
Subject: RE: Field not getting cleared while Displaying Error Message on Screen


Excellent point Alan,
I know we ran into some of the same issues and decided to just add a blank
field for error messaging; was far easier and faster to handle.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Alan Shore
Sent: Monday, April 30, 2007 9:37 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Field not getting cleared while Displaying Error Message on
Screen

Derek - the problem that you are seeing is due to the fact that you are
using ERRMSG.
See the IBM manual on the definition and inner workings of ERRMSG.
We had the same problem. Used debug and saw that a particular field was in
fact changing, but the DDS screen did NOT reflect that change.
We ended up changing ERRMSG to subfile error messaging.



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill

rpg400-l-bounces@xxxxxxxxxxxx wrote on 04/30/2007 10:05:00 AM:

Hi,

I have developed a new Maintenance Program. In this Program I have used a

user defined field on the Main Screen #Msg to diaplsy the informational
messages as 'Record Added' 'Record Updated'.
This field is being cleared each time after the EXFMT of the record
fortmat.
Now when the user comes back after Updating a record, The messge is
diaplayed as 'Record Updated'. Now without Pressing Enter, if the user
enetrs invalid values and presses enter the error message is popped up(I
have used ERRMSG for the Error Messages), but the message 'Record
Updated'
still remains on the screen, though actually #Msg has been cleared and
its
value is Blank.
Any suggestions or help will be appreciated0.(I have attachecd Screen
Shots
and the code of the Main subroutine)

Thanks in Advance

Derek

_________________________________________________________________
Get a FREE Web site, company branded e-mail and more from Microsoft
Office
Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
[attachment "SMZ0182.txt" deleted by Alan Shore/NBTY] --
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.