MVSFORUMS.com

[pradeepg]

Hi,
I am pretty new to REXX. I am wondering is there any way we can do line by line debugging of REXX procs. Some thing like how we do cobol program debugging in XPEDITOR or IBM DEBUG tool. I feel really time consuming and difficult to trace the syntax problems while executing the REXX programs.

Please guide me in right direction.

Thanks,
Pradeep

[Jeba]

Pradeepg,

Please see the following link
http://www.mvsforums.com/helpboards/viewtopic.php?t=1157&highlight=trace
_________________
Thanks,
Jeba
(Known is a drop Unknown is an ocean)

[superk]

If you use the ISPF editor to enter your REXX code, then you should rarely incur any syntactical errors, since the editor highlights syntax errors as you type, much the same way as it does for COBOL and JCL source statements.

Logical and run-time errors are, of course, a different issue, which the use of the TRACE statement should help to identify.

[stefan]

An exciting alternative to changing the code by insering trace statements is to issue a "TSO EXECUTIL TS" before starting your rexx program. This causes any subsequently running rexx program to fall in trace mode. After debugging you should reset your environment by issuing "TSO EXECUTIL TE". Have a look in the manuals for further options, like EXECUTIL HT or HI.

The benfit of this procedure is, that you don't have to alter the code, and that you are able to trace all rexx programs contained in a call chain. The trace condition can be disabled for each program individually by entering "trace off" when the first line of this program is displayed.

The benfit of using the TRACE statement is, that you can restrict the effect of tracing to that part of coding which is suspicious to you.

Hope this helps.

Stefan

[Phantom]

Stefan,

[infoman123]

pradeep,

the best way to learn rexx is take an existing code and put a trace command in the begining and execute the rexx.You can easily learn the logic as well as get a good knwledge in the syntax,keywords etc...