I would assume that any system macro destroys R15-R1 unless the documentation says otherwise. In the case of WTO, the documentation decribes the use of all three registers. For that matter, the documentation mentions the use of AR14-AR1.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Rupert Reynolds <rreyno...@cix.co.uk> Sent: Friday, November 8, 2019 4:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WTO Perhaps I misunderstood, but it seems more likely that WTO has changed registers and affected the processing of the exit. Obvious candidates are condition code and regs 0,1,15 (I can't remember whether R0 is used). Are you using MF=(E, PARMLIST)? Time for a test module to run the edit where you can debug it interactively? Rupert On Fri, 8 Nov 2019, 20:29 scott Ford, <idfli...@gmail.com> wrote: > All: > > I have a bit of an issue I am trying to resolve in Assembler. We use a > skeleton exit from another vendor and it has been working fine. > It is re-entrant and keep seeing normal WTO's , i.e. ; WTO > 'XXXXX',ROUTCDE=11 , are not appearing on SYSLOG. We are using the > WTOS to track through the flow of the exit. Could what i am seeing the exit > being re-entrant and since WTO's use R1 that R1 is being destroyed by > some task ?? > > Scott > > -- > > > > *IDMWORKS * > > Scott Ford > > z/OS Dev. > > > > > “By elevating a friend or Collegue you elevate yourself, by demeaning a > friend or collegue you demean yourself” > > > > http://secure-web.cisco.com/1Y9RGaDY1lsLpqlnmCd7fGFWlUeTiPSkPZXtT9huDbeYCLBl8qMZQT97ZjLxkcVVk3AaNwyepCDPRRusSgTEzgnu-6gH_bXJ_rvDvdTYK7H69eNj_uO7PRbR-yLOZVd1hmPrz00usZHuuO9iCZX_nhbXEYYW4XWkwZAy0szI3GsS12MRg2URPkSqdAjIZamDP3OidQQgoy5uQ5lOX4FbzIHkJ_nk4iJoROihx-8C1r08djM0F60rzJz_gDueGTdlmtlh6BmcE0QU2sxiS3H9Ejni_1MyfA9aCpMDeSSPZYGvlSUXnShvDOWGQsfMlw7hD68mKISFnNvQ77n6VGC2RgmxUC9PpAqmZ2NTfBHsR8Du741Nzsvryq61Ezm2LId8-OysS-sdKqrP8VJRLtHiICmlQoYjsUULdpD9pdHJIwLRk7T6T71_9L_HZSLCDB8j7/http%3A%2F%2Fwww.idmworks.com > > scott.f...@idmworks.com > > Blog: > http://secure-web.cisco.com/1Fv8GdSDGaZNUpBv4m3tDHWdxoG9YP7DuVfUqWRhCyIwEqYOeeOBGhFaN30l7w8qYj4l_tSXfBoemX8byFyPw6mJMM5eSHyNd8Kyg1aT-je4lCDxhHsvCfWeDDGJAAn4b8TtTSpxgmTEFO_J_hKLayHC_AcZh8SXhtTByGQJH39oRxAAogbkJkEu_ny9LvqFiTMDjxqKlKqHmkuqk11b-4pRDZNR6bkgTV2mgNa547-8nfOUsJi6ZDu2ejBTFWP89SiTcHO88iqE11O0NPRvQ3YeO_9hy-JLNyrKwADD47eiBjLdOMzKBSJaS7UPKxi-mLyx-P1kEgF2qrjinFtszso3hhShrscrO0HqJmZtOqkBvs8wkewQ-aBR0I5PdqYVsT7aW4Mi-JyrNSpujnnhJjHJtcOr1GsyoRuubPGM_TkZhrQSHDjB7rfguvF8_5ZqG/http%3A%2F%2Fwww.idmworks.com%2Fblog > > > > > > *The information contained in this email message and any attachment may be > privileged, confidential, proprietary or otherwise protected from > disclosure. If the reader of this message is not the intended recipient, > you are hereby notified that any dissemination, distribution, copying or > use of this message and any attachment is strictly prohibited. If you have > received this message in error, please notify us immediately by replying to > the message and permanently delete it from your computer and destroy any > printout thereof.* > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN