× 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.



I tried your suggestion and it comes back as UNDER on the screen even
though 53 is on because the error message shows up but not the OVER
LIMIT.

Thanks for the suggestion anyway..

Any other ideas anyone?

Thanks.
Brad 

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Muthathal_Ramasamy
Sent: Thursday, April 28, 2005 12:35 PM
To: COBOL Programming on the iSeries/AS400
Subject: RE: [COBOL400-L] Conditioned Field
Importance: High

Hello Brad,

Here is one suggestion.
Hope it helps you.

You can condition the output only field (that displays "over limit" /
"under") using the same indicator 53 like this.

That is, in the display file,
 53              3 20'OVER LIMIT'
N53              3 20'UNDER'

This is one simple solution.

And when you trigger the output error message in the COBOL code, Say
your input field value > MAX-VALUE,

You can use like this,

IF INPUT-VALUE > MAX-VAL
   MOVE B"1" TO IND53
ELSE
   MOVE B"0" To IND53
END-IF

Thanks,
 

------------------------------------------------------------------------
-

 

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx]
Sent: Thursday, April 28, 2005 9:00 PM
To: cobol400-l@xxxxxxxxxxxx
Subject: [COBOL400-L] Conditioned Field

I have a screen with an IO field and another output only field.
 
If the user types a value over a certain limit into the IO field, I set
an indicator 53 in the COBOL on and move a message to the output only
field saying "over limit".
 
On my screen I have an error message on the IO field for indicator 53.  
 
What I want to happen is that the error message triggers AND the "over
limit" shows in the output only field.
 
What actually happens is the error message gets triggered but the output
only field shows a previous value of "under" even though when I display
the value of that field just before the write to the screen the value is
indeed "over limit".
 
What would be causing this?
 
Thanks.
 
Brad
_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/cobol400-l.




DISCLAIMER:
This email (including any attachments) is intended for the sole use of
the intended recipient/s and may contain material that is CONFIDENTIAL
AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or
copying or distribution or forwarding of any or all of the contents in
this message is STRICTLY PROHIBITED. If you are not the intended
recipient, please contact the sender by email and delete all copies;
your cooperation in this regard is appreciated.

_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/cobol400-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.