> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of [email protected] > Sent: Thursday, September 19, 2013 12:55 PM > To: [email protected] > Subject: Re: Allocation test > > All, > > > Be aware of the trap that Elardus hinted to: your allocation can be > > modified by ACS routines, possibly differently on different LPARs, > > caused by different variables passed to it. > > Thanks for testing. On our system, I am the master of everything (SMS, > allocation), you name it. There isn't anything defined in SMS to take > over. All I am doing in SMS is sent everything to an SMS-managed volume > (with the exception of a few things that should be non-SMS). No data > classes defined. No ALLOCxx anywhere in the parmlib concatenation, so > we're taking all the defaults. > > It is interesting that some of the newly allocated data sets (nothing > but allocation via iefbr14) contain one or more members already. In that > case I would also think that something is done using "helpful ACS > routines".
In my case it certainly is NOT by ACS-routines! I can only think of reuse of space with a (part of) member index. And this must in a production environment imply a security leak ?! ... Best Regards Thomas Berg ___________________________________________________________________ Thomas Berg Specialist zOS\RQM\IT Delivery SWEDBANK AB (Publ) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
