Trace information is written out to the stderr output stream, but you are redirecting only stdout. This should work if you use
“D:\Rexx\script.rex” >>log 2>&1 which will capture both stdout and stderr. Alternatively, you can make a change in your program to to redirect the trace to write to stdout: .traceoutput~destination(.stdout) that's the 4.2.0 version...on earlier versions you would need to use .error~destination(.stdout) Rick On Mon, Aug 11, 2014 at 3:08 AM, Roger Bilau <s...@bilau.de> wrote: > If I start a rexx script with trace I in a windows command window, I see > the trace output. > > > > If I start a rexx script with trace I in a rexx script with e.g. > > > > “D:\Rexx\script.rex” >>log > > > > (log is defined as D:\Rexx\Log\log.txt), I find any output from say > instructions or other programs, but I couldn’t find any trace output. > > Also I couldn’t find output from e.g. a syntax error like > > Error 4 running … > > Error 4.1: Program interrupted … > > > > It would be very helpful, if somebody could explain to me this behavior or > what I should do to get the estimated output. > > Regards > > Roger > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-users mailing list > Oorexx-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-users > >
------------------------------------------------------------------------------
_______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
