Actually, my point was, if your allocation is able to be done at a "low enough" level, you get below "OPEN/CLOSE/EOV" and 14/15 & 30 are not written. So, unless an exit had been put in to prevent the SMF records that someone did not tell me about (I was not the only developer doing things), we did NOT get any SMF records for these allocations (I had the system recording ALL records in SMFPRMxx being used at the time.
WYLBUR, in using SVC32, also did its own read/write of VTOC records, attempted to consolidate data sets to single extent, etc. Which is why SVC32 is not a good idea in an SMS managed shop. Long live WYLBUR. -- If anyone is still running WYLBUR, I'd love to hear about it. Later, Steve Thompson On Tue, 2006-02-07 at 23:00 -0600, IBM-MAIN automatic digest system wrote: > Date: Tue, 7 Feb 2006 07:54:29 +0100 > From: "Kaiser, Gerald (IT/IEG)" <[EMAIL PROTECTED]> > Subject: AW: SMF 14/15 Confidence > > Hi, > no exit required, not finding any R14/R15 can be achieved by excluding > their being written. See PARMLIB-member SMFPRMxx in parameter > SYS(TYPE(from1:to1,from2:to2).. whether R14/R15 is excluded, which > then means they are not written to SMF-datasets. > > Regards, > Gerald Kaiser > W&W Informatik GmbH ---------------------------------------------------------------------- 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
