I *think* this only applies with calls to labels with 'procedure', but I might be wrong.
Also, there's nothing stopping us from using 'procedure exposure name1 name2 name3' to set name1 etc. in a function that initialises them, if we want (especially if we will want to reinitialise everything at some stage). Roops On Thu, 14 Mar 2024, 17:04 Glenn Knickerbocker, <[email protected]> wrote: > On Wed, 13 Mar 2024 11:01:30 -0500, Charles Mills <[email protected]> > 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: > > ¬R > > ---------------------------------------------------------------------- > 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
