RE: Processes after CRTSRVPGM

["Aaron Bartell" <albartell@xxxxxxxxx>]

I always thought you would run into problems when inserting new records from
a program that hasn't been recompiled against the new format.  For example,
if you added a numeric field to the end of the DDS, wouldn't there be
potentially invalid data in that field when an insert was done?

Aaron Bartell
http://mowyourlawn.com

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Buck
Sent: Thursday, February 14, 2008 9:28 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Processes after CRTSRVPGM

M. Lazarus wrote:

>  If you would have the ability to directly set the level ID on a file, 
> would you?  In the vast majority of cases, of course not!  Because the 
> system knows to generate a new level ID / signature *automatically* when 
> a significant attribute changes.

I'm not saying you're wrong, only presenting a different opinion.  In 
fact, I agree that using LVLCHK(*YES) and EXPORT(*ALL) provide protection.

For practical considerations, I have used LVLCHK(*NO) rather than 
compile thousands of programs that don't need the new field.  Likewise, 
I use hard signatures over EXPORT(*ALL) to avoid locating and 
recompiling every consumer program.

It may not be best practice, or even good practice, but it sure is 
practical.  When an expert takes a short cut, he's efficient.  When an 
apprentice takes a short cut, he's sloppy.  I guess it depends a lot on 
the composition of the staff that determines the relative merits.
   --buck