Compiling Options for files with OVRDBF

[John Tremper]

Good Morning, I am trying to modify an old RPGLE program. When I compile I am getting RNF7030 and RNF2120 errors on files that have no descriptions on my system. The missing files have OVRDBF statements to them in a CL that calls the RPGLE program. So, I could create descriptions for the missing files because they may have been on my system at one time. But, I was wondering. Are there any compiler options or workarounds for this situation? Thanks in advance for any advice.

[roverbyte]

No workarounds I have ever seen. You need to have the OVRDBF's in your job when the compiler is run or
your filenames in your f-specs could match your DB filenames (and be in your library list for the compile job)
in which case no overrides are needed.

I have used a utility command which you can call in lieu of the compiler which inspects OVRDBF like specs
embedded in the top of your rpg source specs, issues the overrides for you and then calls the compiler.
Something like the following...

H/TITLE ACSRGM11 Work with Users
*
* Statements for object creation options follow
*@@OV OVRDBF F@@UPDAT *LIBL/ACSLUSRS
*@@OV OVRDBF MYUSRS *LIBL/ACSLUSRS
*@@OV OVRDBF MYUSRSTY *LIBL/ACSLUGUT

The command is called ZCRTOBJ from BCD/Excelsystems which I believe is
owned by Fresch Solutions now. I am pretty sure I have seen some other
third part solutions out there also.

Good luck and happy compiling.

"I would love to change the world,
but they won't give me the source code."

[John Tremper]

Yes: "You need to have the OVRDBF's in your job when the compiler is run", duh, that's it! Rookie mistake. Thanks for rattling the old brain. I knew it was something easy like this. Thanks again!

[jtaylor___]

How about EXTDESC keywords on your File Description specs?

[kitvb1]

John, maybe easier to create a CL to compile it. That way, you never have to remember the override parameters. For example, if your program is OE345, then you could name the compile program OE345CRT.

[jtaylor___]

So you have to create the QTEMP table to compile and create it again to run?

[kitvb1]

Correct... JBA System21 uses this technique quite often.

[jtaylor___]

In the case of QTEMP, you could still specify it in your RPG code. Since you need a CL (or some compile utility) to create the QTEMP table, the difference between the two methods would be minimal. Barring a CL required to create a PF to allow RPG to compile, putting it directly in the RPG code would eliminate the need for the CL.

[John Tremper]

Great idea kitvb1, that's where i was going as well. Thanks!