What if you: - Built a full-screen application with two panes. The upper pane would be for output. A user could scroll up and down through the output, so s/he could readily see output produced earlier in the session.
- The lower pane would be for input. A user could either type a command, or select and edit a previous command, like ISPF function 6. Perhaps there could be some good way of copying addresses from the output pane to the input. - Replaced the I/O routine as described in the doc. Emulated non-terminal I/O "as-is." Trapped all Say and Trace output (I believe Trace "uses" Say) and displayed it in the upper pane. Supplied input from the lower pane. Perhaps PF keys could be mapped to common commands like "=". - You might have your own call to IRXIC to turn tracing on and off. You would not do any "interrupting" yourself. You would just trap and display Rexx TRACE output. I'm not sure what you mean by your references to "original source" but perhaps executing SOURCELINE would solve the problem? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Lindy Mayfield Sent: Saturday, December 30, 2006 10:59 AM To: [email protected] Subject: Re: How to write a full-screen Rexx debugger? I've gone through all of those docs quite a bit, but the one point I don't find is how to "interrupt" the flow of the exec and how to either know what the actual statement is or how to map it to the original exec. I read Chapter 14 many times, but I don't see a way to get between the user and the exec and the language processor. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
