Well, that explains a mystery. I did not realize that SIGNAL ON was pushed and popped on subroutine calls. I have had this vague problem where my SIGNAL ON NOVALUE did not seem to work but at the time of an error it is always easier to fix the NOVALUE condition than troubleshoot the SIGNAL ON.
Thanks! Charles On Thu, 14 Mar 2024 12:04:00 -0500, Glenn Knickerbocker <n...@bestweb.net> wrote: >On Wed, 13 Mar 2024 11:01:30 -0500, Charles Mills <charl...@mcn.org> wrote: >>And the answer is ... "The three numeric settings are automatically saved >>across internal and external subroutine and function calls." >>I was setting numeric digits in an initialization subroutine, so Rexx >>helpfully unset it on return from initialization. I thought I had done it >>that way before but I guess I have not. > >Funny, I work with a lot of code that has a common subroutine for retrieving a >TRACE setting to set in the main routine, and I never even thought about why, >or about all the stuff that gets saved across calls! From CALL HELPREXX on VM: > >>The status of DO loops and other structures: > --though, importantly, not the *indices* of the loops! >>Trace action: >>NUMERIC settings: >>ADDRESS settings: >>Condition traps: (CALL ON and SIGNAL ON) >>Condition information: >>Elapsed-time clocks: >>OPTIONS settings: ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
