Wilt, Charles wrote:
It would seem to me that if you have the authority to replace the
security *SRVPGM in it's entirely...then you'd probably have the
authority to do whatever you want anyway.

Perhaps, but that's a different problem entirely.

Of course, hard coding a service program reference might have ramifications in itself ... especially if you are deploying code to multiple locations with differing configurations. I would say that few service programs are fully qualified when they are bound in.

Besides, couldn't the *MODULE object that get bound into programs be
replaced just as easy? Granted, it'd only affect recompiled programs
and not all existing.

Which pretty much defeats the purpose. The goal of someone who would do this is to substitute their own code at run time. There's no reason at all for a module to be deployed to a production system.

david


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].