|
>>There are some exceptions that can be significant, like triggers, >>which end adoption. > >I didn't know that. I can understand a trigger not inheriting adopted >authority from earlier in the stack but I doubt they stop the trigger >itself from adopting authority via USRPRF(*OWNER). Hmm, I can feel an >investigation coming on -- it'll have to wait a bit though ... I'm busy! Simon ... It is my understanding after several discussions with IBM, that trigger programs are treated as exit programs... at least from an authority adoption point of view. Therefore, adopted authority will not flow down to a trigger program. You have to define it to adopt authority specifically. Kenneth **************************************** Kenneth E. Graap IBM Certified Specialist AS/400e Professional System Administrator NW Natural (Gas Services) keg@nwnatural.com Phone: 503-226-4211 x5537 FAX: 603-849-0591 **************************************** -----Original Message----- From: Simon Coulter [mailto:shc@flybynight.com.au] Sent: Thursday, January 24, 2002 7:38 PM To: midrange-l@midrange.com Subject: Re: Service program authority adoption
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.