"I believe OUTTRAP catches lines written by PUTLINE(?) but not by TPUT. Why must there be two of them? If TPUT must be retained for comaptibility, couldn't it be made simply a wrapper for PUTLINE, providing uniform behavior?"
TPUT is specifically for terminal output. PUTLINE is more generalized and issues TPUT if the current output is destined for the terminal. I suspect the original perception may have been that TEST would have always been interactive, ie. driven directly via a terminal rather than some kind of script. Sent from my iPhone On Jul 3, 2016, at 13:45, Paul Gilmartin <[email protected]<mailto:[email protected]>> wrote: On Sun, 3 Jul 2016 09:32:18 -0400, Joseph Reichman wrote: I am basically trying to save the output of test i.e. Output of a test list command into variables and compare them and based on the result do a "AT" breakpoint command As a last resort, you might try a terminal emulator that has a logging facility. I believe OUTTRAP catches lines written by PUTLINE(?) but not by TPUT. Why must there be two of them? If TPUT must be retained for comaptibility, couldn't it be made simply a wrapper for PUTLINE, providing uniform behavior? On Jul 3, 2016, at 9:16 AM, Rupert Reynolds wrote: TEST behaves differently (or did, when I used it in the 90s) in CLIST. As I remember it, the CLIST that starts TEST keeps running for the TEST session, so the next line of a CLIST after the TEST command itself can be subcommands such as AT and GO. As I remember it, there were important differences in SYSOUTTRAP as well. I had a small collection of REXX and CLIST that could be run in TEST to do things such as single step and redisplay registers, storage, code, PSW and so on, almost half way to a full screen debugger. I found the differences meant I had to mix REXX and CLIST to get the job done. I believe this behavior is called "modal". CLIST (but not Rexx) interfaces similarly with (non-ISPF) Edit. Perhaps others? Likewise CMS EXEC (but not EXEC2 nor Rexx) interacts similarly with old CMS (non-X-)EDIT. And Rexx sorely lacks any facility for instream data. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
