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

Re: LVLCHK(*NO)

Michael,

As a rule, lvlchk(*no) is a no-no as a permanent solution to your problem.

But as a temporary solution, giving you time to re-compile all programs
that use the file, in a tight 24x7 type environment, this is exactly the
thing that lvlchk(*no) is good for.

but only as a temporary fix.  once all programs using it have been
re-compiled, just change the pf back to lvlchk(*yes).  otherwise, there are
no guarantees of getting bad data, which is what lvlchk(*yes) is good for.

imo,

rick
---original message----
After reviewing the archives, I find that most would not recommend using
LVLCHK(*NO).

With that as a given, we are considering adding two alpha(3 position
fields)
to a master file.  There are no changes of any kind to the previous
"fields"
and the new fields will be added a the end of the DDS.

Can someone tell me why using LVLCHK(*NO) would the a bad thing to do in
this situation.

Michael Smith

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.