One gotcha we have -- when we replace an object, we move it to a library
which is lower in the library list to prevent people who are using that
object from dumping out of the program. MOVOBJ. The we compile the
new object into production.

While if we compiled the object directly ontop the existing object, the
authority would stay, since we movobj the authority is replaced with the
defaults.

We have a number of AS/400's. On one of them I'm more in control of
than the others. Things don't change much. There is a CL which runs
nightly and assigns a ton of authorities to objects in case someone's
attempted to change something or forgot the caveat above. We also have
special subsystems for programmer sessions versus normal users. The
same job makes sure the QPADEV* devices have the right authorities...

Anyway, my .02$ worth.




**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email
in error please reply to the sender of the message.

The views expressed in this correspondence may not
reflect the views of Prime, Inc.

This footnote also confirms that this email message has
been scanned for the presence of computer viruses.
http://www.primeinc.com
**********************************************************************


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-2020 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].