Don't do it without GRS > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Richards.Bob > Sent: Tuesday, September 19, 2006 9:08 PM > To: [email protected] > Subject: Re: SMS question - sharing DASD but not SMS environment > > Absolutely, SMS would get confused. Either use one SMS across > all four lpars or stay with one per lpar. The purpose of a > shared COMMDS is to communicate allocation activity between > lpars to avoid allocation collisions such as you envisioned. > If you are going to share the usercat across all lpars > anyway, why not merge the four separate SMS' in to one "SMSPLEX"? > > Bob Richards > > > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of John M. Cullen > Sent: Tuesday, September 19, 2006 6:02 PM > To: [email protected] > Subject: SMS question - sharing DASD but not SMS environment > > We want to share a few DASD among our four Lpars and have SMS > doing allocation. Each Lpar runs z/OS as a monoplex seperate > from the others. Two are 1.4 and two are 1.7 right now. > We do not have any kind of sysplex. Nor do we have an > SMSplex, whatever that is. > > We would update SMS rules in every Lpar to indicate these > volsers in an SMS storage group and set up storageclass, > dataclass & mgmtclass. Each high level qualifier would be > setup in every Lpar's master catalog using an existing ucat > on a non-SMS dasd that is online to all lpars. > > Would SMS for lpar-P get confused if SMS for lpar-D was > allocating a file on those dasd at the same time she was? > Does SMS from one lpar need to know what SMS from the other > lpar is doing? > > John Cullen > > "'Tis a damn poor mind that cannot think of more than one way > to spell a word." > (Andrew Jackson) >
---------------------------------------------------------------------- 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
