ur J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List on behalf
> of Brian Chapman
> Sent: Thursday, March 28, 2019 9:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Authorized and unauthorized in same a
Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Brian Chapman
Sent: Thursday, March 28, 2019 9:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Authorized and unauthorized in same address space
Searching through the archiv
*2. Run authorized tasks in parallel with unauthorized tasks - bigger
issue.You cannot use any user key storage - even the passed save area or
the LEanchor. No LM 14,12,12(13) at the end of your module - use SVC 3.
AllSTORAGE/GETMAIN to protected subpools. And if you will be fetching
fetchprotected
Two separate things:
1. Prepare user supplied authorized services and then change the job to
unauthorized - perfectly fine,as long as you follow standard authorized
service logic, i.e., never trust any user supplied address and use protected
storage as your worrkarea.
2. Run authorized tasks in p
Searching through the archives, I quickly saw that this has been a repeat
heated discussion, but
all of the discussions seem to ignore the fact that CICS initializes as an
authorized address space, performs authorized work, and then disables
authorization to load unathorized programs from the DFHRP
