Re: Issue with Protect Field Using And Indicators. V7R1

[Michael Schutte <mschutte369@xxxxxxxxx>]

Thanks Alan, typically I would just have a field called MSG and populate it
with the message for the first error on the field.  I'm modifying a vendor
program (long story), but making it our own.  But was hoping to to keep it
as close as possible to the original style.



On Mon, Jul 9, 2012 at 4:39 PM, Alan Shore <ashore@xxxxxxxx> wrote:

> Hi Michael
> I have steered away from using ERRMSGID once I discovered something
> We had a program that was using ERRMSGID throughout the DDS.
> So much so that we were rapidly running out of indicators.
> Then we started having problems with what was being displayed was NOT what
> should have been displayed.
> Using STRDBG we could verify that data WAS being changed on the DDS but
> was NOT being displayed.
> It looked like the program and DDS were being controlled by gremlins.
> Then I discovered that as soon as an indicator used on ERRMSGID was
> switched on, any other thing changed on the DDS was not changed in the
> buffer.
> And that was intentional
> Since then, we changed that program to use message subfiles (no need for
> indicators) and the code is self-documenting as to what the problem is.
> It took a while to change the program, but since then, NEVER used
>  ERRMSGID, and the programs are not haunted by gremlins
>
>
> Alan Shore
> Programmer/Analyst, Direct Response
> E:AShore@xxxxxxxx
> P:(631) 200-5019
> C:(631) 880-8640
> "If you're going through Hell, keep going" - Winston Churchill
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
> midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Schutte
> Sent: Monday, July 09, 2012 4:05 PM
> To: Midrange Systems Technical Discussion
> Subject: Issue with Protect Field Using And Indicators. V7R1
>
> We've just upgraded to V7R1 not sure if it makes a difference.  However,
> I'm having this strange issue with field protection on this single record
> format display.
>
> *In98 is turned on when it's time for the user to scan in a location to
> put product away.  When 98 is on, I want to protect the @QTY field from
> being changed.  However, there's a check after the scanned location is
> validated where the quantity entered is compared to the amount of space
> that is left in the scanned location.  If the quantity entered is greater
> than the room left in the location, indicator 62 is turned on and
> re-displayed to the user however, the field is still protected.  I'm just
> not seeing why I cannot type in that field now.  I know that "98N62" is an
> AND condition.
>  Could someone please point out my error?
>
> I know that 62 is turned on because the @QTY is highlighted and positioned
> too. I know that 98 is on because the location field is still shown on the
> display.  I've also debugged the program and checked the values prior to
> EXFMT being executed. I thought maybe the screen was locked because of the
> error. But I've pressed reset and tried, still not able to type in the
> field.
>
> A            @QTY          16A  B  5  6
>
> A  62                                  DSPATR(RI)
>
> A  62                                  DSPATR(PC)
>
> A  52                                  ERRMSGID(IDU0503 *LIBL/WISDOMSG 52)
>
> A  62                                  ERRMSGID(CAP0001 *LIBL/ODWMSGF2 62 -
>
> A                                      &RPLTXT)
>
> A  98N62                               DSPATR(PR)
> A* suggested putaway location and actual putaway.
> A  98                             11  1'Sug:'
> A                                      DSPATR(HI)
> A  98        @SUGLC        16A  O 11  6TEXT('Location')
> A  53                                  ERRMSGID(ILU0504 *LIBL/WISDOMSG 53)
> A  98                             12  1'Loc:'
> A                                      COLOR(WHT)
> A                                      DSPATR(HI)
> A  98        @LOCAT        16A  B 12  6TEXT('Location')
> A  53                                  ERRMSGID(ILU0504 *LIBL/WISDOMSG 53)
>
> Let me know if you need more information.  I cannot think of anything else
> that you would need. Maybe a PTF is needed?
>
> Here is a screen shot after the capacity check is made.
> http://tinypic.com/r/20kf4fa/6
>
> Thank you in advanced.
> --
> 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.
>
>
> Disclaimer: This message contains confidential information and is intended
> only for the individual named. If you are not the named addressee you
> should not disseminate, distribute or copy this e-mail. Please notify the
> sender immediately by e-mail if you have received this e-mail by mistake
> and delete this e-mail from your system. E-mail transmission cannot be
> guaranteed to be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
> The sender therefore does not accept liability for any errors or omissions
> in the contents of this message, which arise as a result of e-mail
> transmission. If verification is required please request a hard-copy
> version. Any views or opinions presented are solely those of the author and
> do not necessarily represent those of the company.
> --
> 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.