See z/OS 2.5 TSO/E REXX Reference, SA32-0972-50. There are three ways to write an assembler routine. The first two are almost identical and have access to services documented in Chapter 12. TSO/E REXX programming services at <https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R5sa320972/$file/ikja300_v2r5.pdf#page=265>, have the interface documented in External functions and subroutines, and function packages at <https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R5sa320972/$file/ikja300_v2r5.pdf#page=289>.
1. As a REXX function; it receives parameters in R0 and R1, and is responsible for returning a string to REXX as a result. You can also invoke it with a REXX call statement. 2. As a REXX callable routine; same as 1, except it does not pass a result. 3. As a command; the interface depends on the environment in which it is invoked. Some environments are documented in Commands to external environments at <https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R5sa320972/$file/ikja300_v2r5.pdf#page=48>. None of these change the current environment. An address TSO statement just makes SYSCALL not the current environment but SYSCALLS("OFF") actually makes the SYSCALL environment unusable until another SYSCALLS("ON"). -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Steve Smith [[email protected]] Sent: Tuesday, June 28, 2022 7:03 PM To: [email protected] Subject: Re: Some questions on SYSCALL It would be nice if the USS people would get their command environment built in to REXX, like TSO, etc. Yeah, I can't imagine anything syscalls(on) could do that's worth being undone. But I doubt that's the problem. Calling an assembler routine certainly doesn't inherently reset the command environment, but how exactly is it invoked? It could be set up as an external routine, which doesn't care about the environment, or you might use address LINKMVS or something. Of course you said you didn't. Barring another address statement, I see no reason why the SYSCALL environment should get lost. sas sas On Tue, Jun 28, 2022 at 6:55 PM Ed Jaffe <[email protected]> wrote: > On 6/28/2022 3:50 PM, Charles Mills wrote: > > And another question: what makes ADDRESS SYSCALL "go away"? > > Years ago on MVS-OE we were advised by Bill Schoen not to attempt > SYSCALLS("OFF"). > > Once you turn it on, leave it on... > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
