The OP's question was why the
parameter was an address of a word containing another address, rather
than
just taking that other address directly as a parameter.
Actually, it was why the parameter was an address of the STOKEN rather
than the parameter being the STOKEN in a register. Jim Mulde
On Thu, 15 Aug 2019 at 23:33, Jim Mulder wrote:
>> Is there a design reason the service takes a pointer rather than the STOKEN
>> itself?
> The LOCASCB service originated in MVS/ESA SP3.1.0, around 1987. An
> STOKEN is 64 bits, and we did not have 64-bit registers until 13 years later.
Ah, ma
Well, I don't think that's what the OP said. Furthermore, that's not how
LOCASCB works.
I have occasionally seen unnecessary levels of indirection, but this isn't
one of them.
sas
On Fri, Aug 16, 2019 at 10:21 AM Seymour J Metz wrote:
> > I'm a bit puzzled about the original question. Using
at other address directly as a parameter.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Steve Smith
Sent: Friday, August 16, 2019 9:15 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LOCASCB ST
I'm a bit puzzled about the original question. Using addresses of things
is fundamental to how computers work. And as Binyamin said, if you can't
access it, it doesn't matter anyway.
However, it does load up the actual ASID if that option is used (and uses a
completely different linkage... given
On Thu, 15 Aug 2019 22:40:08 -0400 Tony Harminc wrote:
:>I'm a bit puzzled. This service takes a pointer to an STOKEN, and returns
:>an ASCB address. Or a return code indicating that the STOKEN is invalid or
:>obsolete. So if I am passed an STOKEN pointer by my caller, this seems like
:>the right
The LOCASCB service originated in MVS/ESA SP3.1.0, around 1987. An
STOKEN is 64 bits, and we did not have 64-bit registers until 13 years
later.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp.
Poughkeepsie NY
> I'm a bit puzzled. This service takes a pointer to an STOKEN,
I'm a bit puzzled. This service takes a pointer to an STOKEN, and returns
an ASCB address. Or a return code indicating that the STOKEN is invalid or
obsolete. So if I am passed an STOKEN pointer by my caller, this seems like
the right service to tell me if this is pointing to a valid and current
ST
