On Fri, 29 Jan 2016 16:25:22 -0500, Jim Mulder wrote: > >"I worked on that project and wrote some of the code. I think >that the reason that it does not apply to an SMS-managed data set is >that it conflicts with the concept that you cannot have two >SMS-managed data sets with the same name. The project was designed for >the system programmer that is building another system. For example he >might have multiple SYS1.MACLIBs." > > So dealing with the situation of having separate catalogs and >SMS-plexes within the same sysplex (and thus allowing more than one >SMS-managed data set with the same name in the same sysplex) was not >a design consideration for that project. > They gotta fix that. Reading this list the anguish is evident.
Even within a single system, to delete a data from one volume when a like named data set on a diferent volume is in use ENQ SHR on the same system. I know it's not easy. They gotta fix it. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
