Re: Do the Name/Token Pair callable services need R13 to point to save area?

Ed, I doubled check and you are right. Sorry. ITschak נשלח מה-iPad שלי ‫ב-23 בדצמ׳ 2016, בשעה 17:55, ‏‏Ed Jaffe ‏ כתב/ה:‬ >> On 12/23/2016 7:17 AM, Itschak Mugzach wrote: >> You can, but pairs are located in private area and shared by tasks in said. >> To place

Re: Do the Name/Token Pair callable services need R13 to point to save area?

Thanks. Happy Hanukkah and merry Christmas from Israel to all. ITschak נשלח מה-iPad שלי ‫ב-23 בדצמ׳ 2016, בשעה 17:43, ‏‏scott Ford ‏ כתב/ה:‬ > Itschak, > > Wow, very interesting. I will have to experiment on my test machine. > > Scott. > > P.S. Happy Hanukkah > > On

Re: Do the Name/Token Pair callable services need R13 to point to save area?

> Not true. There is no such intention. Well I stand corrected, obviously. It seemed to me that a lot of MVS services used to require a save area off R13 and no longer do, but I guess I recalled incorrectly. Charles -Original Message- From: IBM Mainframe Discussion List

Re: Do the Name/Token Pair callable services need R13 to point to save area?

On 12/23/2016 7:17 AM, Itschak Mugzach wrote: You can, but pairs are located in private area and shared by tasks in said. To place them in common you need to be authorized, key zero. Authorized/privileged, yes. But, key zero? I'm pretty sure we create persistent, system-level pairs all the

Re: Do the Name/Token Pair callable services need R13 to point to save area?

As is stated in the documentation: Input register information Before issuing the IEANTCR callable service, the caller does not have to place any information into any register unless using it in register notation for a particular parameter, or using it as a base register. with the analogous

Re: Do the Name/Token Pair callable services need R13 to point to save area?

Itschak, Wow, very interesting. I will have to experiment on my test machine. Scott. P.S. Happy Hanukkah On Fri, Dec 23, 2016 at 10:17 AM, Itschak Mugzach wrote: > You can, but pairs are located in private area and shared by tasks in > said. To place them in common you

Re: Do the Name/Token Pair callable services need R13 to point to save area?

You can, but pairs are located in private area and shared by tasks in said. To place them in common you need to be authorized, key zero. ITschak נשלח מה-iPad שלי ‫ב-23 בדצמ׳ 2016, בשעה 17:12, ‏‏scott Ford ‏ כתב/ה:‬ > Frank, > > Really good question. We initially call an

Re: Do the Name/Token Pair callable services need R13 to point to save area?

Frank, Really good question. We initially call an Assembler routine to do a getmain or 'storage obtain' for K's of storage. The routine returns us the beginning storage address, where we place a token. The storage we obtain is persistant, SP231 . I didnt know you could call IEANTCR in

Re: Do the Name/Token Pair callable services need R13 to point to save area?

Do you really need this assembler routine in order for COBOL to call the IEANTCR callable routine? I call it directly from COBOL: CALL 'IEANTCR' USING NTA-LEVEL NTA-NAME NTA-TOKEN NTA-NOPERSIST NTA-RC. with the following working storage: 05 NTA-LEVEL COMP-5

Re: Do the Name/Token Pair callable services need R13 to point to save area?

> Heres what we do we call it from Cobol.. >We pass in the address of where storage begins and where we want to place the token I have to "sneak in", so I cannot pass some storage. In the meantime I have it working without problems. -- Peter Hunkeler

AW: Re: Do the Name/Token Pair callable services need R13 to point to save area?

Thanks, Greg -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Do the Name/Token Pair callable services need R13 to point to save area?

Peter: Heres what we do we call it from Cobol.. We pass in the address of where storage begins and where we want to place the token SAVE (14,12),,SETTOKEN LRR12,R15R12 IS BASE REG USING SETTOKEN,R12 L R4,0(R1) 1ST PARM = WORK

Re: Do the Name/Token Pair callable services need R13 to point to save area?

Peter, We use tokens all the time, I will look Scott On Thu, Dec 22, 2016 at 9:58 AM, Greg Dyck wrote: > On 12/22/2016 1:47 AM, Peter Hunkeler wrote: > >> When I get control, R13 points to a save area, which my code will use, >> but I do not yet have storage for another

Re: Do the Name/Token Pair callable services need R13 to point to save area?

On 12/22/2016 1:47 AM, Peter Hunkeler wrote: When I get control, R13 points to a save area, which my code will use, but I do not yet have storage for another save area before calling IEANTRT, so I cannot change R13. The Name Token Retrieve service uses BAKR to save and restore the caller's

Re: Do the Name/Token Pair callable services need R13 to point to save area?

I believe it has been the intention of the MVS team over the past several years to make all of the basic assembler macro-invoked services independent of the caller's R13. I recall that once upon a time most of them required a save area off R13, and were so documented. I think now that most or all

Re: Do the Name/Token Pair callable services need R13 to point to save area?

I looked into my code, and it look like you are right. no special regs to set. IStchak ITschak Mugzach Z/OS, ISV Products and Application Security & Risk Assessments Professional On Thu, Dec 22, 2016 at 9:47 AM, Peter Hunkeler wrote: > I'm thinking of using a Name/Token pair to

Do the Name/Token Pair callable services need R13 to point to save area?

I'm thinking of using a Name/Token pair to keep the address of "my" storage area, and X'00' to mean I first need to obtain the storage. This is in RENT code. When I get control, R13 points to a save area, which my code will use, but I do not yet have storage for another save area before