Yep, that's one way, passing a parm you can do it also. A lot of ways to skin the cat
Scott ford www.identityforge.com from my IPAD > On Apr 4, 2014, at 3:32 PM, "Webster, Chris" <chris_webs...@bmc.com> wrote: > > Don't forget you can turn on/off tracing using the tso executil command. > Saves updating the exec. > > For example, in ISPF, enter: > TSO executil ts > Invoke the exec and it will enter in trace > Enter trace commands to alter what is traced > > After the exec is done, enter trace end to stop other execs from tracing: > TSO executil te > > ...chris. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Joel C. Ewing > Sent: Friday, April 04, 2014 6:45 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: need pub to help me with a REXX exec > >> On 04/03/2014 09:06 PM, Thomas Conley wrote: >>> On 4/3/2014 6:59 PM, John Norgauer wrote: >>> Can someone point me to a pub that explains how to debug and/or trace >>> a REXX exec? >>> >>> Thanks. >> >> John, >> >> The TSO/E Rexx Reference describes the Rexx TRACE command. My >> personal favorite is trace i. >> >> Regards, >> Tom Conley > For REXX execs that are already parsing parameters, one of my favorites was > to always include a "debugt(x...x) parameter which would set a debug variable > that wold be "Exposed" to all procedures and use presence of some chosen > unique substring or subword to conditionally enable one or more strategically > placed "Say"s or or "Trace I" "Trace OFF" sequences within specific > procedures within the EXEC. In other words, build your own specialized > traces into the code as you write it, or as the need arises. If you make it > conditionally executed, you don't even have to remove it when you think > (possibly erroneously) that debugging is complete. Even if you are not > parsing arguments, you can still use that approach and just explicitly assign > a value to a "debug" variable at the front of the the EXEC and just remove or > change that single assignment when no longer needed. > > A simple "TRACE I" to trace everything works well for a simple EXEC, but you > quickly find that with long running and complex REXX execs a full Trace of > the entire EXEC can produce so much output as to be marginally useful. > > -- > Joel C. Ewing, Bentonville, AR jcew...@acm.org > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
