Sorry Charles problem is resolved . Another vendor issue. On Sun, Nov 10, 2019 at 5:33 PM Charles Mills <charl...@mcn.org> wrote:
> If the load module it is in is marked as RENT or REUS in the load library > then (1) assemble the code with option RENT and watch for assembly > diagnostics and (2) visually examine the code listing for stores into the > code CSECT. Either one is a problem. > > What exactly was the symptom? What is the original problem? I thought it > was something like "we do the WTO but there is no message in the log"? > > A RENT-type issue would be highly unlikely to cause that problem. I seem > to recall the answer was some sort of message routing issue? Have you > solved that and this is a new problem (with the same subject line)? > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of scott Ford > Sent: Sunday, November 10, 2019 2:11 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WTO > > Guys, > > Yeah I found it it happens to be another Well known ISV’s exit. But I have > a question in regard to when this exit is called it’s like IRREVX01 , so I > assume (I know ) that the WTO should be re-entrant. We are basically using > it for diagnostics if needed. Is my assumption correct on the WTO ? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Scott Ford IDMWORKS z/OS Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
