Re: adding new fields to PF

I am positive no compilers notice the level check setting. The actual Level Checking is a function only of Open; i.e. run-time. The compiler only and always extracts the level identifier, not the level checking value, irrespective of the level checking value. As such the step-two is worthless [and as dangerous as when any program compiled against the old definition, had run with OVRDBF LVLCHK(*NO) in effect], and so step-four is also not required. Without the step-two, there is no point at which the production file would be exposed to improper access, except by an override.

Regards, Chuck

Jeff Crosby wrote:

You are essentially correct and I have done this to production files.

In the 10,000' view, this is what I did:

1) Add the fields to the DDS.
2) CHGPF FILE(lib/file) SRCFILE(QDDSSRC) SRCMBR(*FILE) LVLCHK(*NO)
The file now has the new fields.
3) Recompile your RPG programs.
4) Do a CHGPF FILE(lib/file) LVLCHK(*YES)
5) Now start doing whatever programming needs done to
actually use these fields.

Note that the above assumes you're using DDS to define the files. I have switched to all DDL. I have not added fields to a file since
the switch to DDL, but the steps would be similar. No CHGPF, but
ALTER TABLE statements instead.

Note that LVLCHK(*NO) on the production file was only for the short
time (minutes usually) needed to recompile the affected RPG programs.