PDSEs are (were?) funny about having multiple DCB's opened against them, and being opened UPDAT, OUTIN or INOUT. I remember that in an earlier life, we had to disable update in place if the target was a PDSE.
Later, Ray -- M. Ray Mullins Roseville, CA, USA http://www.catherdersoftware.com/ http://www.mrmullins.big-bear-city.ca.us/ http://www.the-bus-stops-here.org/ German is essentially a form of assembly language consisting entirely of far calls heavily accented with throaty guttural sounds. --ilvi > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Craddock, Chris > Sent: Friday 03 February 2006 12:23 > To: [email protected] > Subject: Re: SMP/E SE37 Retry and ++ZAP > > > > >Ed said: > > > > >Not for PDSE. > > Shmuel said; > > > Why would AMASPZAP processing be any different for PDSE? > > It used to be (until I opened a PMR on it 3 or 4 years ago) > that you could not zap program objects. AMASPZAP just curled > up its toes and barfed if you presented it with a program > object. It is probably still the case that you can't zap > program object contents in classes other than B_TEXTxx, but > at least you can apply zaps to code. > > CC > ---------------------------------------------------------------------- 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
