IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

How to debug a rexx program ?


IBM Mainframe Forums -> CLIST & REXX
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
sreepriya

New User


Joined: 19 May 2005
Posts: 4

PostPosted: Thu May 19, 2005 4:13 pm
Reply with quote

Hi all,

Can i know how to debug a rexx program ? If possible explain with steps. If already answered pls provide the link.

Thanks in advance,
Priya
Back to top
View user's profile Send private message
Prandip

New User


Joined: 04 Mar 2005
Posts: 84
Location: In my tiny cubicle ...

PostPosted: Thu May 19, 2005 5:37 pm
Reply with quote

Use the TRACE instruction. There are a few different parameters, depending on what kind of trace you require. Check the REXX Reference Manual for the list of parameters. My personal favorite is TRACE I (to activate an Intermediate trace) followed by TRACE N (to disable the trace).
Back to top
View user's profile Send private message
MGIndaco

Active User


Joined: 10 Mar 2005
Posts: 432
Location: Milan, Italy

PostPosted: Thu May 19, 2005 8:13 pm
Reply with quote

These are the Trace option with explanation:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4A350/3.23?DT=20040623084642
Back to top
View user's profile Send private message
MGIndaco

Active User


Joined: 10 Mar 2005
Posts: 432
Location: Milan, Italy

PostPosted: Thu May 19, 2005 8:18 pm
Reply with quote

To have a better view of Rexx debug aids see also:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4A350/11.0?DT=20040623084642#HDRDEBUG
Back to top
View user's profile Send private message
new2cobol

New User


Joined: 04 Jan 2006
Posts: 77
Location: Bangalore

PostPosted: Wed Feb 01, 2006 10:22 pm
Reply with quote

I would suggest the TRACE R option if you are not accessing a lot of values.
Back to top
View user's profile Send private message
amitava
Warnings : 1

Active User


Joined: 30 Oct 2005
Posts: 186
Location: India

PostPosted: Thu Feb 02, 2006 9:41 am
Reply with quote

Ya TRACE is the best option to debug a REXX routine. But if your program is too long, you may lose your control over the program. Then I think you can use -
1. The postions where you are thinking a faulty position, insert a SAY statement.
2. If any wrong responses are coming then you can also insert "SAY rc zerrlm" - statement. This will tell you the return code of the previous statement executed and also the reason of the error (in words).
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CLIST & REXX

 


Similar Topics
Topic Forum Replies
No new posts Compile Several JCL JOB Through one r... CLIST & REXX 4
No new posts Using API Gateway from CICS program CICS 0
No new posts Running REXX through JOB CLIST & REXX 13
No new posts Error to read log with rexx CLIST & REXX 11
No new posts isfline didnt work in rexx at z/OS ve... CLIST & REXX 7
Search our Forums:

Back to Top