It's not really all that strange for a debugger to abend on a program that runs ok w/o the debugger. I would try using the EX inst instead of the program modifying itself as prior poster is hinting.
Duffy Nightingale Sound Software Printing, Inc. du...@soundsoftware.us www.soundsoftware.us Phone: 360.385.3456 Fax: 973.201.8921 The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although Sound Software Printing, Inc. attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. On Jul 26, 2015, at 10:55 PM, glen herrmannsfeldt <g...@ugcs.caltech.edu> wrote: >> Is the EXECUTE instruction broken on your machine? > >> With what you are doing, you could possibly cause ABEND047 >> (or all sorts of other abends) not on the STC instruction, >> but on the AP instruction, if you had set a breakpoint on >> the AP under TSO TEST. That could happen because you would >> be changing the SVC number in the SVC instruction that replaces >> the first two bytes of the AP for the breakpoint. >> That could certainly cause some head-scratching. > > And what does TSO TEST do if you EXecute a breakpoint SVC? > > It would seem an interesting case for it to get right. > > -- glen > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
