Just noticed that the z/OS 2.3 manuals mention EXECUTABLE=YES|NO parameter for
IARV64 GETSTOR requests.
Anyone have a summary of what kinds of code we can move above the bar in z/OS
2.3?
Robert Ngan
CeleritiFinTech Services
DXC Technology Company - Headquarters: 1775 Tysons Boulevard, Tysons, V
>>Anyone have a summary of what kinds of code we can move above the bar in
z/OS 2.3?
and
>You can move code that invokes no services or invokes only services that
>support RMODE(64) execution.
And that has basically been true since z/OS 1.13 via LOAD with ADDR64
What is available in z/OS 2.3 ma
On 7/27/2017 5:14 PM, Ngan, Robert wrote:
Just noticed that the z/OS 2.3 manuals mention EXECUTABLE=YES|NO parameter for
IARV64 GETSTOR requests.
Anyone have a summary of what kinds of code we can move above the bar in z/OS
2.3?
You can move code that invokes no services or invokes only servi
>Date:Fri, 28 Jul 2017 00:14:46 +
>From:"Ngan, Robert"
>Subject: LOC=64 executable code?
>Just noticed that the z/OS 2.3 manuals mention EXECUTABLE=YES|NO parameter for
>IARV64 GETSTOR requests.
>Anyone have a summary of what kinds of code we can move
Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Tom Russell
Sent: Friday, July 28, 2017 9:43 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: LOC=64 executable code?
>Date:Fri, 28 Jul 2017 00:14:46 +
>From:"Ngan, Robert"
>Subject: LOC=64 exec
ly 28, 2017 12:07
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: LOC=64 executable code?
In other words, EXECUTABLE=YES is not some new RMODE=64 feature.
EXECUTABLE=NO is a new security feature. It is a guard against buffer overflow
type vulnerabilities in which a bad guy sends you some message
On 7/28/2017 2:29 PM, Ngan, Robert wrote:
There were severe restrictions on LOC=64 code before (mainly, must be
non-interruptible)
Those restrictions were lifted six years ago beginning with z/OS 1.13.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo,
: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: LOC=64 executable code?
Yes, I saw the IEP feature on the z14 announcement. There were severe
restrictions on LOC=64 code before (mainly, must be non-interruptible) so since
they added EXECUTABLE= to the LOC=64 allocation logic, I figured they might
have
>Is the target of an EXECUTE considered to be an executable
>instruction if it's in EXECUTABLE=NO storage?
yes
Peter Relson
z/OS Core Technology Design
-LIST@LISTSERV.UGA.EDU] On
Behalf Of Peter Relson
Sent: Sunday, July 30, 2017 7:25 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: LOC=64 executable code?
>Is the target of an EXECUTE considered to be an executable instruction
>if it's in EXECUTABLE=NO storage?
yes
Peter Relso
10 matches
Mail list logo