Thanks Rob. Turned out to be fairly easy. Dynamically loaded the module into MLPA, wrote a quick program to zap the address into the correct slot in the RCVT
Thanks for your help Regards Paul -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Rob Scott Sent: 07 December 2009 10:12 To: IBM-MAIN@bama.ua.edu Subject: Re: Missing RACF exit Paul, As far as I am aware, if the exit pointer in the RCVT is non-zero then RACF will invoke the exit. About 15 years ago I knocked up a quick+dirty program to dynamically add a RACF exit and it seemed to work OK. I have not seen RACFXITS - however the logic I used was something along the lines of : (o) Determine length of RACF exit (o) Grab that amount of E-CSA and assign ownership to the system (ie I want it to persist) (o) Directed load of the exit module into the E-CSA chunk (o) Store the E-CSA address into the RCVT (remembering to indicate AMODE in bit0) These days you have things like dynamic LPA - so you might be able to avoid most of the heavy lifting and just "zap" in the new exit address. Rob Scott Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: rsc...@rs.com Web: www.rocketsoftware.com - _______________________________________________________ Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983 This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email. _______________________________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
