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


  1.  Home
  2. RPG400-L
  3. October 2009

Re: "Monitor" does not monitor for RNQ0103 (target for numeric operation is too small)?

I totally agree with the use of *hival and, while hesitant (do to
stubbornness more than anything else <vbg> ), I will use the extra field
if I ever have to change that program again!

Yeah, depending on your company's interpretation, SOX compliance can be a
hassle. [?]

The reason for the extra variable was to reasonably not generate an error
in
the first place. Also using *hival (and the extra field) to represent
max
values of numeric data versus 99999 precludes you having to maintain the
code, even if the variable size changes (like if it's based on a database
field or something). Keep it in mind for future development -- it saves
me
maintenance time when I write code that I don't have to worry about
again!

Stu

Mr. Kerry Lockwood
Celadon Trucking, Inc.
9503 E. 33rd Street
Indianapolis, IN 46235
(317) 972-7000 ext. 2147

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.