Maybe check with CA then. Ya never know. Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, May 21, 2019 1:11 PM, John McKown <john.archie.mck...@gmail.com> wrote: > On Tue, May 21, 2019 at 12:02 PM Cieri, Anthony aci...@seic.com wrote: > > > This won't help unless you are running IBM System Automation (SA). > > > > > > I believe that IBM SA can be configured to "trap" messages written to > > JESSYSMSG. > > Thanks. We don't run that. We run CA-OPS/MVS. We are heavy into CA products. > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of John McKown > > Sent: Tuesday, May 21, 2019 9:24 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: "Trapping" messages written to JESYSMSG? > > This question was sparked by the thread on tracking PROC usage. I don't see > > any way to "trap" messages written to JESYSMSG. I know that I can process > > them using the SAPI, > > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaf200/sapi.htm > > , > > or the SDSF API or a number of other methods. But they are more "after the > > fact" rather than "in line" (as the messages are issued). > > Any ideas how this might be done? I wish that there were a JES exit for > > this. But I don't see one. > > -- > > This is clearly another case of too many mad scientists, and not enough > hunchbacks. > > Maranatha! <>< > > John McKown > > ------------ > > 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
