MVSFORUMS.com Forum Index MVSFORUMS.com
A Community of and for MVS Professionals
 
 FAQFAQ   SearchSearch   Quick Manuals   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Xpeditor Debugging

 
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> Problem Determination
View previous topic :: View next topic  
Author Message
pai_sunil_bs
Beginner


Joined: 19 Sep 2005
Posts: 21
Topics: 11

PostPosted: Mon Feb 05, 2007 11:53 pm    Post subject: Xpeditor Debugging Reply with quote

How to trace the control backwards in an Expeditor?
I tried checking all the KEYS which are mapped. I did not get any clue.
Back to top
View user's profile Send private message
kolusu
Site Admin
Site Admin


Joined: 26 Nov 2002
Posts: 12370
Topics: 75
Location: San Jose

PostPosted: Tue Feb 06, 2007 12:12 am    Post subject: Reply with quote

pai_sunil_bs,

Use MONITOR and REVERSE commands.

Code:

The MONITOR and REVERSE commands are used to activate review mode. Review
mode lets you monitor and review the execution path by stepping backwards
through your program. You can view the statements that were executed     
during normal (forward) execution. You can trace backwards through the   
actual sequence of instructions that led to the current breakpoint and see
the data values as they were at the time. There is no guesswork about     
which of the possible paths the program took; the actual path that was   
taken during forward execution of the program is displayed.               
                                                                         
The MONITOR command records the execution history and the REVERSE command
enables you to review the execution history.                             
                                                                         
To activate review mode, enter the MONITOR command from the primary       
command line. MONITOR without a module name records history for the       
current module1not necessarily the active module that is currently       
executing, but the module indicated by the program field on the third     
line.                                                                     
                                                                           
After issuing the MONITOR command, execute the statements you want to     
review. Then, when your program pauses during logical execution, enter the
following primary command:                                                 
                                                                           
   REVERSE                                                                 
                                                                           
The REVERSE command places the execution arrow on the last statement that 
was executed, and changes the execution direction of your program1from     
forward to reverse (backward). From this point on, the REVERSE command     
acts as a toggle that changes the direction in which your program is       
executed. During review mode, the execution status message on the fourth   
line of the screen indicates the execution direction and the statement     
where execution is paused.                                                 
                                                                           
1. Entering the REVERSE command only changes the direction of execution;   
   it does not cause execution to occur.                                   
                                                                           
2. You must enter the GO n or GO command to begin execution in the current
   direction.                                                             
                                                                           
   The GO n command moves the active arrow n lines in the current         
   direction, which lets you step through the program line-by-line. Unlike
   normal execution mode, a GO n command in review mode ignores module     
   boundaries and will pause after executing n statements, regardless of   
   what modules they are in. It is recommended that you use GO 1 commands 
   to do a backward line-by-line execution.                               

3. In review mode, TRACE does not recognize the default maximum limit of 
   25 statements, and continues execution until it encounters the AT     
   INITIAL EXECUTION POSITION. To halt the reverse trace, press the Attn 
   key.                                                                   
                                                                         


Hope this helps...

Cheers

Kolusu
_________________
Kolusu - DFSORT Development Team (IBM)
DFSORT is on the Web at:
www.ibm.com/storage/dfsort

www.linkedin.com/in/kolusu
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> Problem Determination All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


MVSFORUMS
Powered by phpBB © 2001, 2005 phpBB Group