Adopted Authority Exceptions, Part 2

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Authority Experts,

About a week ago I posted a message about adopted authority exceptions.  I now 
know that adoption is aborted by the system for triggers.  This is not 
documented 
as far as I can see and is somewhat inconsistent.  This makes resource based 
authority much more difficult when triggers are used.  I wonder why the 
database 
developers decided to end adoption as it is a whole lot easier to end adoption 
in a 
user program than to get it back.  My guess is that this problem would tend to 
make 
systems less secure rather than the more secure.

My main question is where does IBM document programs that will terminate 
adoption?  Are system programs that end adoption a bug or a feature?

David morris



>>> dmorris@plumcreek.com 04/10/00 02:30PM >>>
While doing some testing I found several system facilities that ignore adopted 
authority, several areas have work-arounds, but triggers in particular do not. 
At this point I suspect that adopted authority is only viable in a discrete 
application. Does anyone know where I can find a list of system supplied 
programs and functions that ignore adopted authority?  Are there any other ways 
to end adoption other than the specifying USEADPAUT(*NO) on the program or 
MODINVAU MI instruction?  If there are no other ways to end adoption, is 
possible to find all programs that use MODINVAU?

Thanks,

David Morris

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---