> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Craddock, Chris > Sent: Thursday, May 10, 2007 11:11 AM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: Can FRR prevent ESTAE from seeing registers? > > > I have an FRR that erases sensitive material from storage areas before > it > > percolates an ABEND. I also want to erase the registers so that any > ESTAE > > that may get subsequent control cannot see the error-time registers. I > > want the ESTAE to see zeroes in its SDWA. > > > > The error-time registers may also have sensitive material that I don't > > want exposed to a user program that is using my service routine. > > > > Is there a clean (IBM supported) way to achieve this? > > AFAIK you can just scribble on the SDWA. What ever you leave there is > seen by subsequent error recovery exits of the same class. > > See > <http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A800/18. > 2.2.2?DT=20010118152433#HDRSDWAUSE> > > or <http://tinyurl.com/2rwe2f> > > I am not completely certain that also applies for FRR percolation back > to a non-FRR routine. But it -IS- documented that SDWACOMU is copied > from one SDWA to the next, so you can definitely use SDWACOMU to pass > footprint info from an FRR to a non-FRR environment. > > So if you always conspire so that the top of the non-FRR recovery chain > is one of your own recovery exits, you can have that exit notice your > private footprint information in SDWACOMU and do whatever you want with > the SDWA that gets passed along when you percolate. Kinda messy, but > effective. > > CC
Sigh... I am writing a service routine called by clients that must not see the error-time registers. The SDWA is completely reallocated for the transition between FRR and ESTAE processing, with only the SDWACOMU copied to the new SDWA from the old SDWA. However, the client won't care about that field. The client ESTAE routines are not mine. My FRR is established under a stacking PC routine. I cannot use an ARR to muck with the SDWA, because RTM will reallocate the SDWA upon subsequent percolations due to storage key changes. My ARR will get a key zero SDWA. Subsequent client ESTAE routines get a key 8 SDWA. Sigh...again. Jeffrey D. Smith Principal Product Architect Farsight Systems Corporation 700 KEN PRATT BLVD. #204-159 LONGMONT, CO 80501-6452 303-774-9381 direct 303-484-6170 FAX http://www.farsight-systems.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
