Re: ACCESS=PUBLIC on ALESERV macro
Okay ... Just wanted to understand the concept -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chris Craddock Sent: Tuesday, February 21, 2012 4:24 PM To: IBM-MAIN@bama.ua.edu Subject: Re: ACCESS=PUBLIC on ALESERV macro On Tue, Feb 21, 2012 at 2:15 PM, Micheal Butz wrote: > If I adding the STOKEN of another address to either my DU-AL PASN-AL can I > specify PUBLIC on the ALESERV macro and bypass the authorization) > > Typically when I get the alet of another address I do a AXSET to give > myself > authorization to go there > >Would adding PUBLIC entry for the ALET of another address space via > ALESERV bypass the need to do a AXSET > No and no. Just don't do it. Adding addressability to another address space this way is not really supported outside of BCP components - even though the macro documentation might seem to suggest otherwise. Consider it a wild hare that escaped. The supported approaches are documented in the extended addressability guide. -- This email might be from the artist formerly known as CC (or not) You be the judge. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: ACCESS=PUBLIC on ALESERV macro
On Tue, Feb 21, 2012 at 2:15 PM, Micheal Butz wrote: > If I adding the STOKEN of another address to either my DU-AL PASN-AL can I > specify PUBLIC on the ALESERV macro and bypass the authorization) > > Typically when I get the alet of another address I do a AXSET to give > myself > authorization to go there > >Would adding PUBLIC entry for the ALET of another address space via > ALESERV bypass the need to do a AXSET > No and no. Just don't do it. Adding addressability to another address space this way is not really supported outside of BCP components - even though the macro documentation might seem to suggest otherwise. Consider it a wild hare that escaped. The supported approaches are documented in the extended addressability guide. -- This email might be from the artist formerly known as CC (or not) You be the judge. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
ACCESS=PUBLIC on ALESERV macro
Hi, If I adding the STOKEN of another address to either my DU-AL PASN-AL can I specify PUBLIC on the ALESERV macro and bypass the authorization) Typically when I get the alet of another address I do a AXSET to give myself authorization to go there Would adding PUBLIC entry for the ALET of another address space via ALESERV bypass the need to do a AXSET -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
