Ok, this is a piece of information in line of what i was looking for. Could you please refer me to documentation about storage obtain and storage releaseThank youZA
Sent from Yahoo Mail on Android On Mon, Nov 16, 2020 at 5:29 PM, Ngan, Robert<[email protected]> wrote: I found out the hard way that, if you code EXECUTABLE=YES of the STORAGE OBTAIN, you must also code it on the associated STORAGE RELEASE. Evidently, it's implemented as a subpool under the covers, so like subpool getmains, you must have matching values on OBTAIN and RELEASE. Robert Ngan HCL Technologies -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of Steve Smith Sent: Monday, November 16, 2020 11:39 To: [email protected] Subject: Re: security with storage allocation under z.OS There is a new operand on STORAGE, EXECUTABLE=YES|NO. The default is YES, and for earlier releases there was no execute-prevention capability afaik. I don't know what to tell you about the "security model". It's a big subject. sas On Mon, Nov 16, 2020 at 12:24 PM Ze'ev Atlas < [email protected]> wrote: > Hi allIn the 1970's I probably could have done some getmain, write > some code into that obtained memory and jump to that code. I assume > that nowadays, this would be impossible and there is some security > model to prevent such a security breach.Do you know where can I find > information on the mainframe security model under z/OS. > Ze'ev Atlas >
