After following the advice in all the other previous answers, sooner or later you will still need to know how to test your SRB and its recovery routine. You probably won't be able to instruction-step or trace either very easily with TSOTEST or XDC. What I do to test code that is sEEEriously difficult to test, at least when no VM or P/390 is available, is to spew OI instructions liberally throughout the code, typically putting one after each test-branch combination. Each such OI turns on a unique bit in some flag byte in some working storage somewhere. Then after the code has executed, I dump the working storage, study the inputs to the code, and see which flag bits were turned on. That tells me the exact path that my code took for that set of inputs. I may also store some intermediate values in registers into the same working storage. I have often used this technique to debug code that must run disabled for I/O interrupts, holding locks, in SRB mode, FRRs, etc.
Bill Fairchild -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Micheal Butz Sent: Thursday, October 27, 2011 8:19 PM To: [email protected] Subject: Testing g RTM routine Hi, Would anyone know how to test the RTM routine of a SRB when I issue a schedule even though SRB activity is asynchronous it takes off automatically ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
