> I'm a bit puzzled about the original question. Using addresses > of things is fundamental to how computers work.
Using addresses of addresses is not. 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. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Steve Smith <sasd...@gmail.com> Sent: Friday, August 16, 2019 9:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: LOCASCB STOKEN= 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 Jim's history lesson, not surprising). It may be that this isn't really your program's problem. A S0C4 is appropriate for LOCASCB, and it may be for your program. But if not, ESPIE or ESTAE might work, although I'm not sure if they need memory for parms. You'd have to trigger the S0C4 before LOCASCB does though. sas On Fri, Aug 16, 2019 at 5:51 AM Binyamin Dissen <bdis...@dissensoftware.com> wrote: > On Thu, 15 Aug 2019 22:40:08 -0400 Tony Harminc <t...@harminc.net> wrote: > > :>I'm a bit puzzled. This service takes a pointer to an STOKEN, and returns > :>an ASCB address. ... Is there a design reason the service takes a > pointer rather than the > :>STOKEN itself? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
