|
Matthias Oertli <oertlim@s054.aone.net.au> wrote: >PRG-AUTH adopts authority, PRG-NOAUTH doesn't. > >1. If PRG-AUTH calls PRG-NOAUTH, does PRG-NOAUTH run with the users >authority or with the authority adopted by PRG-AUTH? In this scenario PRG-AUTH remains in the stack above PRG-NOAUTH so PRG-NOAUTH uses the adopted authority of PRG-AUTH. >2. If PRG-AUTH transfers control (TRFCTL) to PRG-NOAUTH, does >PRG-NOAUTH run with the users authority or with the authority adopted >by PRG-AUTH? In this case PRG-AUTH is no longer in the stack so PRG-NOAUTH does not adopted authority from it. >Are there any gotchas with either scenario? In order to adopt authority the USEADPAUT parameter of PRG-NOAUTH must be set to *YES. If it is set to *NO the program will be unable to adopt authority from a program higher in the stack. Dave Kahn, ABB Steward Ltd. +--- | 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 +---
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.