Re: Service program authority adoption

Thanks Ed for the reference.
All kinds of wonderful things in Tech Studio ... I think it has more
technical info on
the iSeries than any other web page area of ibm or anywhere else.
It is not marketing fluff!
http://www.as400.ibm.com/tstudio/
imho
jim franz

----- Original Message -----
From: "Ed Fishel" <edfishel@us.ibm.com>
To: <midrange-l@midrange.com>
Sent: Friday, January 25, 2002 8:34 AM
Subject: Re: Service program authority adoption


>
> Simon,
>
> >The system does support the ability to stop called programs from adopting
> >via a propogate authority attribute but Rochester haven't seen fit to
> >expose that.  I keep asking for it but I guess I'm alone.
>
> This function is there if you are willing to use the Suppress Adopted User
> Profile option on the Modify Invocation Authority Attributes (MODINVAU),
> Call External (CALLX), or Transfer Control (XCTL) MI instructions. See
> http://www.as400.ibm.com/tstudio/tech_ref/mi/ for the latest description
of
> these instructions.
>
> >>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).
>
> It is true, OS/400 suppress adopted authority when calling almost all exit
> programs. As you guessed we do not prevent the called exit program from
> adopting is owners authority.
>
> Ed Fishel,
> edfishel@US.IBM.COM
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>