Re: Running with LVLCHK *NO in production

LVLCHK(*NO) allows you to add fields to the *end* of an existing record without having to recompile all of the programs that use the record. I've been guilty of using it on occasion but I agree that it's a time bomb when used in a production environment.

P.S. A lot of us miss you on CPF0000.

Booth Martin wrote:

I am curious...

One of the strengths of the IBM midrange platform is that IBM has been extraordinarily diligent in protecting us from ourselves. Bearing that in mind, there must have been some overwhelming reason that allowed LVLCHK(*NO) to make it into the parameter list in the first place. What could it possibly have been, and is it still relevant?





Jon Paris wrote:

On 4-Sep-09, at 6:03 PM, midrange-l-request@xxxxxxxxxxxx wrote:

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

Not in my book - no.

As your situation aptly demonstrates, when you run with LVLCHK *NO it is like driving the wrong way on the Interstate - it is not a question of IF you have a crash - it is a question of WHEN.

And I don't care how good the control systems are - they are never good enough to make the risk worthwhile.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com