Re: z/OS DASD Allocation using Esoterics
Raymond, Follow up question: what is the reason that you want the datasets spread over the volumes, load balancing / contention? There is intelligent software that can handle this: Dynamic PAV management. You mentioned you are running WLM Goal mode. If you have PAV capable storage, you can have WLM managed the number of parallel access paths to you devices and you don't have to care anymore about the allocation of the datasets. Regards, Kees. "Raymond Noal" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>.. . > First I want to thank all of you that responded. > > The gist of the responses tells me that I may be giving z/OS allocation > logic too much credit. Not what I hoped for of course but this is why we > do testing - right? > > The cigar goes to John Kington who suggested allocating my eight data > sets in a single job step. Sure enough, each of the eight data sets was > allocated to different device numbers. I failed to mention the results > of this test when using SMS managed volumes. SMS allocated seven of the > data sets to seven different device numbers with only one device number > being used for two data sets. Since the underlying reason for this > testing will be for a SMS/HSM environment, maybe things won't be too > bad. > > Again, thanks to everyone for their time and assistance. > ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** -- 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
Re: z/OS DASD Allocation using Esoterics
Thanks David, I will definitely add this to my 'must read' list. HITACHI DATA SYSTEMS Raymond E. Noal Senior Technical Engineer Office: (408) 970 - 7978 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Betten Sent: Thursday, June 15, 2006 12:41 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: z/OS DASD Allocation using Esoterics You may want to look at the DFSMSdfp Storage Administration Reference topic 6.6, SMS Volume Selection for Data Set Allocation. This discusses in detail the criteria used by DFSMS for volume selection. Have a nice day, Dave Betten DFSORT Development, Performance Lead IBM Corporation email: [EMAIL PROTECTED] DFSORT/MVSontheweb at http://www.ibm.com/storage/dfsort/ IBM Mainframe Discussion List wrote on 06/15/2006 03:17:21 PM: > Raymond's point is excellent. It is also possible that there was not > adequate space or there was some other constraint at the time SMS made the > decisions. It would be interesting to see if you got the exact same > results at different periods, repeating the same experiment. > > I think I'm in trouble here because I just implied that the software can > actually THINK! I must need a vacation. > > Regards, > > Rob Weiss > z/SWITA and z/Series I/T Security and Privacy Consultant > IBM Software Group Sales > > IBM Mainframe Discussion List wrote on 06/15/2006 > 01:01:40 PM: > > > Raymond, > > > > Are all of the SMS managed volumes in ENABLE status? Maybe one of the > > volumes > > is in QUIESCE status or even DISABLE or DISABLE, NEW. > > Regards, > > John > > > > -- > > 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 > -- > 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 -- 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 -- 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
Re: z/OS DASD Allocation using Esoterics
You may want to look at the DFSMSdfp Storage Administration Reference topic 6.6, SMS Volume Selection for Data Set Allocation. This discusses in detail the criteria used by DFSMS for volume selection. Have a nice day, Dave Betten DFSORT Development, Performance Lead IBM Corporation email: [EMAIL PROTECTED] DFSORT/MVSontheweb at http://www.ibm.com/storage/dfsort/ IBM Mainframe Discussion List wrote on 06/15/2006 03:17:21 PM: > Raymond's point is excellent. It is also possible that there was not > adequate space or there was some other constraint at the time SMS made the > decisions. It would be interesting to see if you got the exact same > results at different periods, repeating the same experiment. > > I think I'm in trouble here because I just implied that the software can > actually THINK! I must need a vacation. > > Regards, > > Rob Weiss > z/SWITA and z/Series I/T Security and Privacy Consultant > IBM Software Group Sales > > IBM Mainframe Discussion List wrote on 06/15/2006 > 01:01:40 PM: > > > Raymond, > > > > Are all of the SMS managed volumes in ENABLE status? Maybe one of the > > volumes > > is in QUIESCE status or even DISABLE or DISABLE, NEW. > > Regards, > > John > > > > -- > > 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 > -- > 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 -- 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
Re: z/OS DASD Allocation using Esoterics
Raymond's point is excellent. It is also possible that there was not adequate space or there was some other constraint at the time SMS made the decisions. It would be interesting to see if you got the exact same results at different periods, repeating the same experiment. I think I'm in trouble here because I just implied that the software can actually THINK! I must need a vacation. Regards, Rob Weiss z/SWITA and z/Series I/T Security and Privacy Consultant IBM Software Group Sales IBM Mainframe Discussion List wrote on 06/15/2006 01:01:40 PM: > Raymond, > > Are all of the SMS managed volumes in ENABLE status? Maybe one of the > volumes > is in QUIESCE status or even DISABLE or DISABLE, NEW. > Regards, > John > > -- > 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 -- 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
Re: z/OS DASD Allocation using Esoterics
Raymond, Are all of the SMS managed volumes in ENABLE status? Maybe one of the volumes is in QUIESCE status or even DISABLE or DISABLE, NEW. Regards, John -- 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
z/OS DASD Allocation using Esoterics
First I want to thank all of you that responded. The gist of the responses tells me that I may be giving z/OS allocation logic too much credit. Not what I hoped for of course but this is why we do testing - right? The cigar goes to John Kington who suggested allocating my eight data sets in a single job step. Sure enough, each of the eight data sets was allocated to different device numbers. I failed to mention the results of this test when using SMS managed volumes. SMS allocated seven of the data sets to seven different device numbers with only one device number being used for two data sets. Since the underlying reason for this testing will be for a SMS/HSM environment, maybe things won't be too bad. Again, thanks to everyone for their time and assistance. HITACHI DATA SYSTEMS Raymond E. Noal Senior Technical Engineer Office: (408) 970 - 7978 -- 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
