Interesting twist in the problem. Good to know how you eliminated the problem, but as a real sysprog I am curious what the cause of the problem was. How could the other subsystem interfere with the MPF exit? How does it 'trap' the message? It looks like it is not serialized with the MPF exit, so it could change things, while the MPF exit was working on it. Can you give a clue?
Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Sebastian Welton > Sent: 06 September, 2019 11:09 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: MPF Exit calling System REXX - S0C4 abend > > Thanks to everyone who responded and although he tried out all the options > provided, nothing actually worked however it looks like it is working now. > The first step was to implement the original it was based upon from the > Redbook and that worked fine out of the box. I then looked at what > messages he was processing via MPF and saw a couple that looked familiar > as being used by another subsystem which also 'traps' messages. Once I > removed the startup of the STC and all references to it in PARMLIB (IEFSSN > in particular), no more abends occurred. So it basically wasn't the fault > of the code (apparently he has coded MPF exits before, just wanted to try > a different method and to use System REXX) but the interaction with other > subsystems. Personally I could have done this with System Automation in a > couple of minutes but this is a good learning curve for both of us in > particular during the investigation. Once again, many thanks to everyone > who took the time and effort to reply, it was much appreciated and did > help in furthering our education (particularly me.) > > Seb. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
