RE: LVLCHK(*NO)

[Frank.Kolmann@xxxxxxxxxx]

FWIW,  I often use LVLCHK(*NO) to move into production a
file that I add fields to (note. never insert the new fields
between existing fields nor change existing fields).
BUT, later at a more convenient time I always recompile all
programs using the file and when that is done I switch the
file to LVLCHK(*YES).
It is nice to be able to separate the task into 2 stages,
the first is concentrate on getting the fix/change done then
later recompile related objects.LVLCHK lets me do this
and I still feel safe that the external file defns are
up to date in all my programs.

Frank Kolmann


-----Original Message-----
From: J Michael Smith

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

--__--__--