> You can cripple your system if you use a macro that is not valid for every > environment.
Good point. Is WTO always an SVC? If so, and you can be called running on an SRB, or certain other situations, then WTO is no good. (If there is a branch option then you must use it in those situations.) Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jon Perryman Sent: Thursday, November 28, 2019 1:39 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WTO On Wednesday, November 27, 2019, 08:20:47 AM PST, scott Ford <idfli...@gmail.com> wrote: > My big issue I was at the mercy of CA code. Not blaming them, > but it’s a CA product and I wished their doc was better. If you are talking about the security exit samples, then they accomplished the desired results by discouraging it's use. This is not an exit to learn about coding exits. For high risk exits, never expect anything more than the basics (control blocks, return codes and something trivial that does nothing). They gave you the gun but don't expect them to load it for you. Creating a sample that covers everything you need to know is impossible. SAF calls can occur in almost any type of environment. You can cripple your system if you don't have recovery correct. You can cripple your system if you use a macro that is not valid for every environment. Have you implemented diagnostic tools that don't make the problem worse. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
