That's an excellent point. I wrote a simple asm "function" that only displayed the hex value of R0. So my Rexx program was simply:
Call RXENVR0 /* Displays R0 in hex */ "ISRDDN" Then I could use ISRDDN, knowing the location of ENVBLOCK, and then I could check out all the control blocks associated with it. I didn't find what I was looking for, but in the table of possible ADDRESS this or that values, I found a bunch of LU2, CPICOMM, APPCMVS things there. Anyway, as you point out, a successful debugger would have to work in all environments, especially TSO/ISPF. Lindy -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin Sent: Saturday, December 30, 2006 10:28 PM To: [email protected] Subject: Re: How to write a full-screen Rexx debugger? Debugging an interpreted language likely requires getting intimate with the interpreter. And Rexx makes this particularly difficult by compiling the Rexx source into an internal text of undocumented format. (Long ago there was a user mod to CMS Rexx that saved the internal text to a file for interpreting later -- the common man's Rexx compiler, now displaced by IBM's own. Nor do I know whether the source code for CMS Rexx remains available.) > Any hints or ideas? I also asked on the Rexx list, but it is holiday season. > You might do better to start with an open-source Rexx such as Regina or Rexx-IMC and hack the interpreter source. Either way you'd need to create the screen handling routines de novo. And my prejudice woud be that such a facility should be available alike whether the Rexx EXEC was called: o Under TSO o Under a Unix System Services shell o From the Rexx API outside TSO. ---------------------------------------------------------------------- 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
