Virtual-storage accessibility is an issue about which the Systems Architecture
team was often asked, by customers, ISVs, and IBM developers.
At a SHARE presentation in 2009, I dragged out my FrameMaker instruction
template and designed the IS IT SAFE (IIS) instruction in about 5 minutes. IIS
Paul,
There is a major issue with just using CLC or OC to verify the address,
at least in my situation.
I can't just set up an exit to trap a soc4 (in my case, using a VSE EXIT
PC) because I am running within someone else's environment. They may
have already, such as in CICS, set up their
On 6/3/24 16:17, Tony Thigpen wrote:
I am also interested in the responses to the original question.
I provide a major subsystem with a very complex API on z/VSE. (EZASMI/EZASOKET)
One of our biggest issues is editing the addresses passed in the parm list.
While we have some code that seems
Just curious
-Mensagem original-
De: IBM Mainframe Assembler List Em nome de
Paul Gilmartin
Enviada em: segunda-feira, 3 de junho de 2024 19:01
Para: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Assunto: Re: RES: The best way to check any virtual address
On 6/3/24 15:34, João Reginato wrote:
> I
I am also interested in the responses to the original question.
I provide a major subsystem with a very complex API on z/VSE.
(EZASMI/EZASOKET) One of our biggest issues is editing the addresses
passed in the parm list. While we have some code that seems to do the
required edits, it's not
On 6/3/24 15:34, João Reginato wrote:
I meant a simplest way to check if the address is still available and don´t
touch it if don't.
Like LRA or TPROT or other similar instructions do
.
Such instructions are prudently designed to detect and report
attempted unauthorized access. Are you
TPROT is not definitive; LRA can tell you, but is privileged and still
has some limitations.
On 2024-06-03 5:34 p.m., João Reginato wrote:
EXTERNAL EMAIL ALERT This email originated from outside of DataKinetics. Do not
click links or open any attachments unless you both recognize the sender,
I meant a simplest way to check if the address is still available and don´t
touch it if don't.
Like LRA or TPROT or other similar instructions do
-Mensagem original-
De: IBM Mainframe Assembler List Em nome
de Binyamin Dissen
Enviada em: segunda-feira, 3 de junho de 2024 17:00
Para:
On Mon, 3 Jun 2024 15:56:17 -0300 João Reginato wrote:
:>What do you guys use to check if a virtual address is still valid to avoid a
:>S0C4?
Why?
What would you code do differently?
Just recover from the 0C4.
You could use VSMLOC, but that won't help you with key mismatches. And, of
course,
We created a subroutine using ESPIE to return none/read/write access.
On 2024-06-03 3:09 p.m., Paul Gilmartin wrote:
EXTERNAL EMAIL ALERT This email originated from outside of
DataKinetics. Do not click links or open any attachments unless you
both recognize the sender, and know the content is
Did you intend to request private replies? The topic seems
to be of general interest.
On 6/3/24 12:56, João Reginato wrote:
What do you guys use to check if a virtual address is still valid to avoid a
S0C4?
Why not set an ESTAE and field the S0C4?
Valid for read or valid for tor store?
Hi
What do you guys use to check if a virtual address is still valid to avoid a
S0C4?
TIA
João
To address Peter's question about "hyphens", we have added a
sentence to the OPTABLE column description as follows:
A dash between levels indicates a range of consecutive levels,
first to last, and a level with a trailing dash indicates that
the instruction has been available since that level
Incredibly useful!
Please let the entire Hursley team know how much we appreciate this
effort...
- Ed Jaffe
On 6/1/2024 1:30 AM, Jonathan Scott wrote:
A table of all 2678 instructions currently supported by HLASM
has now been added as a new appendix to the HLASM Programmer's
Guide (both in
14 matches
Mail list logo