Re: dataset separation within a Storage Group
On Wed, 5 Mar 2008 23:04:11 +0100, R.S. [EMAIL PROTECTED] wrote: Ted MacNEIL wrote: Applications want 3 datasets A.B.** to always be allocated on different packs than 3 datasets A.C.** Why? In an SMS environment, data management is supposed to be taken away from applications. As long as the data is responsive, protected, backed up, and meets business needs, they should not be involved. (Unless, of course, there are politics) There is a method in SMS to separate the datasets. However - it does work on CU basis, not on volume basis (which consistent with assumptions - to isolate failures) - it isn't convenient (my opinion, and other SMS admins I know) - it is rarely in use (see above). BTW: I fully support Ted's opinion about application role here. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl S±d Rejonowy dla m. st. Warszawy XII Wydzia³ Gospodarczy Krajowego Rejestru S±dowego, nr rejestru przedsiêbiorców KRS 025237 NIP: 526-021-50-88 Wed³ug stanu na dzieñ 01.01.2008 r. kapita³ zak³adowy BRE Banku SA wynosi 118.642.672 z³ote i zosta³ w ca³o¶ci wp³acony. -- 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 As Radoslaw noted, the 'dataset separation profile' can do this for SMS-managed datasets but as also noted, it's CU-level, not well known, and somewhat cumbersome to use. Our Allocation Control Center (ACC) product can implement this sort of thing on the volume level via simple policy rules for either SMS or non-SMS datasets. Steve Pryor Senior Software Developer DTS Software, Inc. 770-922-2444 x162 [EMAIL PROTECTED] -- 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: dataset separation within a Storage Group
Dave Myers wrote: What is the best way to separate datasets within a storage group. Applications want 3 datasets A.B.** to always be allocated on different packs than 3 datasets A.C.** These are small files, and I hate to waste an entire volume to create another STG GROUP... just to isolate them... Thanks, Dave -- 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 Assign them a storage class with the guaranteed space attribute and let applications specify the volumes they want the datasets on. -- Mark Jacobs Time Customer Service Tampa, FL The dogmas of the quiet past are inadequate to the stormy present. The occasion is piled high with difficulty, and we must rise to the occasion. We cannot escape history. We will be remembered in spite of ourselves. The fiery trial through which we pass will light us down in honor or dishonor, to the last generation. Abraham Lincoln -- 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: dataset separation within a Storage Group
You could break up a large Stg group into 2 components, assign a.b.** to one of the components, assign a.c.** to the other and concatenate the 2 components for the rest of your allocations. or as Mark suggests let the apps people play storage administrator, something that historically speaking, they are not very good at. From: Dave Myers [mailto:[EMAIL PROTECTED] Sent: Wed 3/5/2008 2:10 PM To: IBM-MAIN@BAMA.UA.EDU Subject: dataset separation within a Storage Group What is the best way to separate datasets within a storage group. Applications want 3 datasets A.B.** to always be allocated on different packs than 3 datasets A.C.** These are small files, and I hate to waste an entire volume to create another STG GROUP... just to isolate them... Thanks, Dave -- 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: dataset separation within a Storage Group
Within a single storage group, the only way I can think to do it is with Guarunteed Space coding volser's. I wouldn't recommend it though. What kind of environment to you have? With Raid hardware, PAV's, etc., these datasets would have to be pretty hot to justify jumping through hoops to separate them. Has anyone looked at any performance data to determine if this is justified? Granted I'm not there to hear the discussions, but I have to wonder if applications is not operating on some very outdated assumptions. It might be to your benefit to take a look at their reasoning. ddk Dave Myers [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 03/05/2008 01:10 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject dataset separation within a Storage Group What is the best way to separate datasets within a storage group. Applications want 3 datasets A.B.** to always be allocated on different packs than 3 datasets A.C.** These are small files, and I hate to waste an entire volume to create another STG GROUP... just to isolate them... Thanks, Dave -- 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 ** This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. ** -- 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: dataset separation within a Storage Group
Applications want 3 datasets A.B.** to always be allocated on different packs than 3 datasets A.C.** Why? In an SMS environment, data management is supposed to be taken away from applications. As long as the data is responsive, protected, backed up, and meets business needs, they should not be involved. (Unless, of course, there are politics) - Too busy driving to stop for gas! -- 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: dataset separation within a Storage Group
Dave, What is the best way to separate datasets within a storage group. Applications want 3 datasets A.B.** to always be allocated on different packs than 3 datasets A.C.** These are small files, and I hate to waste an entire volume to create another STG GROUP... just to isolate them... If you allocate all three datasets in the same jobstep, they should be allocated to different volumes if there are enough candidate volumes in the storage group below the high allocation threshold. There is no guarantee unless you assign a special storage class with guaranteed space set to yes and you specify the volser for each dataset. Then you run the risk of not enough space on the volume for the dataset or you forget and removed the volser. 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
Re: dataset separation within a Storage Group
Ted MacNEIL wrote: Applications want 3 datasets A.B.** to always be allocated on different packs than 3 datasets A.C.** Why? In an SMS environment, data management is supposed to be taken away from applications. As long as the data is responsive, protected, backed up, and meets business needs, they should not be involved. (Unless, of course, there are politics) There is a method in SMS to separate the datasets. However - it does work on CU basis, not on volume basis (which consistent with assumptions - to isolate failures) - it isn't convenient (my opinion, and other SMS admins I know) - it is rarely in use (see above). BTW: I fully support Ted's opinion about application role here. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237 NIP: 526-021-50-88 Według stanu na dzień 01.01.2008 r. kapitał zakładowy BRE Banku SA wynosi 118.642.672 złote i został w całości wpłacony. -- 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
