Re: Service programs and QSRVSRC

*PRV is a useless feature. There is not much of a history or any
safegard that one can get out of the *prv. *PRV does nothing but create
work and possible mistake that could cause program to fail.

There is only two options for me:
Option 1:
Use static sig and if you really want to force a massive recompile, add
version to the static sig.

Option 2:
Don't use binding language. Just always do export all. This will mean
that each time you add/remove export procedure, you will need to
recompile all the programs that use that service program.




"M. Lazarus" <mlazarus@xxxxxxxx> wrote in message
news:<mailman.6343.1255456396.1811.rpg400-l@xxxxxxxxxxxx>...

Hi Buck,

A downside to that approach is that the programmer looking at the
single sig doesn't know that there was some history to this
*SRVPGM. Using *PRV would usually accomplish the same goal (no
recompile required to those programs that are not using the new
functionality), but would let the programmer know that there might be
multiple versions around.

It's no big deal either way, but I don't see a huge advantage to
named sigs. As to IBM's not using *PRV in their own modules, I'm
curious how they manage their object generation so that everything is
in sync and it's never an issue.

-mark