× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



And this makes perfect sense!  People keep thinking of their 5250
application.  If I have my library list just right and my adopted authority
just right then this trigger behaves this way.  But folks - the trigger has
to work when some user - without a valid library list - or an existing
program stack - updates the data using UPDDTA, Excel, etc.  Which is why
some triggers hardcode libraries.  For example if I update FILEA and want
to log to FILEB when something happens, even if they update the data with
Excel - well let me tell you - excel has no easily maintainable library
list and the odds are high that you didn't store FILEB in QSYS.


Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "Graap, Ken"
                    <keg@nwnatural.com>       To:     
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
                    Sent by:                  cc:     "'shc@flybynight.com.au'" 
<shc@flybynight.com.au>
                    midrange-l-admin@mi       Fax to:
                    drange.com                Subject:     RE: Service program 
authority adoption


                    01/25/2002 11:53 AM
                    Please respond to
                    midrange-l






>>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
_______________________________________________
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.







As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.