RE: adding new fields to PF

Change control - boy it makes life so much simpler





From:
Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
To:
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
Date:
06/03/2008 09:01 AM
Subject:
RE: adding new fields to PF



i disagree...LVLCHK(*NO) is *never* acceptable. if you change the file
keep it allocated until you've recompiled the programs....after all you
had to have exclusive lock to recompile/modify the file to begin with, so
why not handle the whole ball of wax at the same time?

Thanks,
Tommy Holden



From:
"Wilt, Charles" <WiltC@xxxxxxxxxx>
To:
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Date:
06/03/2008 08:47 AM
Subject:
RE: adding new fields to PF

I believe that by adding the fields to the end of the file using CHGPF
that all programs that were compiled prior to the change will still work
fine(regardless of level check *YES or *NO) but will not recognize the
added fields until recompiled.

Incorrect.

Programs accessing a file that has changed since the program was last
compiled will always fail if the
file has LVLCHK(*YES).

With the file set LVLCHK(*NO), if the only change was the addition of new
fields and those new fields
were placed at the end of the file, then the program will work normally
but will ignore the new
fields.

If LVLCHK(*NO) but field sizes and/or types where changed or new fields
were added at the beginning or
middle of the file, then the program will seem to run normally, but the
data will be screwed up.

IMHO, LVLCHK(*NO) is never acceptable. But Jeff's example of using it for

a short well defined period
may be ok if you don't have a CMS.



Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx





This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a

named addressee you are hereby notified that you are not authorized to
read, print, retain, copy or disseminate this communication without the
consent of the sender and that doing so is prohibited and may be unlawful.

Please reply to the message immediately by informing the sender that the
message was misdirected. After replying, please delete and otherwise
erase it and any attachments from your computer system. Your assistance
in correcting this error is appreciated.