Bill, Your input and advice and "tools and toys" for z/OS have been most helpful to so many of us over all these years. Thank you for everything you have done for us.
May you enjoy good health and a relaxed retirement. All the best. Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Bill Schoen Sent: Wednesday, June 29, 2022 8:48 AM To: [email protected] Subject: Re: Some questions on SYSCALL There are quite a few topics in this thread, some well addressed, some maybe not, but I'll pitch in... re: syscalls environment should be integrated into rexx this is included in the default environments for rexx running in mvs (irxjcl), tso, and ispf calling syscalls('ON') is not required to use address syscall all that does is define the syscall variables The only reason I can imagine if you get errors if not using syscalls() is you probably have replacements for the default environments that were probably made a long time ago and do not include syscall. re: syscalls('ON') and return code used as above is a function call which does return a return code. if you don't assign that to a variable or use it in an expression or use call, the rexx processor will execute the return code in the current address environment as a command re: syscalls('OFF') this causes your process to undub which is typically unnecessary and often results in confusion re: write buffer is a variable name This was done for a variety of reasons, but primarily, rexx has a limit to number of parameters that can be passed to an address environment. I think TSO rexx limits it to 20. If it took a string you would be limited to very few blank delimited words. a number of syscall commands take variable/stem names to avoid issues with input or output rexx restrictions. . Probably my last post before retirement tomorrow. Bill Schoen -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
