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



Jezz, might this be a good reason to use SQL? Nah, better to keep just
compiling the whole table into every program.

On Fri, Sep 4, 2009 at 3:01 PM, Paul Nelson <nelsonp@xxxxxxxxxxxxx> wrote:

<<is there any good reason to use a file in production with
LVLCHK(*NO)?>>

That's like playing Russian Roulette, except there's 3 rounds in the
cylinder instead of one.

Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Rich
Sent: Friday, September 04, 2009 3:45 PM
To: midrange-l
Subject: Running with LVLCHK *NO in production

Hi everyone,

A customer just had a big emergency today. They ran a program that had
been run in many years and it completely ruined their part master file. I
investigated and found that the program had last been compiled in May 1998
and the part master file was last created in June 1998 with LVLCHK(*NO).
Of course, the file layout had clearly changed and when the program ran it
happily destroyed every record in the part master file.

My question is: is there any good reason to use a file in production with
LVLCHK(*NO)? If a level check had happened, this whole fiasco would have
been avoided. I didn't write the software (happily) and I can't think of
any reason why they would have built this file with LVLCHK(*NO).

James Rich

if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev
--
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.



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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.