I still wonder why you need such a complex construction of dataclasses, if all differences seem to be in the space. Can't you create a common space value, that is adequate for the smaller datasets and supplies enough growth with secondary extents and multivolume allocations for the larger ones? E.g., what is the difference between TINY and SMALL and can't SMALL not be a TINY with a number of extents?
Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Buckton, T. (Theo) Sent: 30 March, 2016 8:02 To: [email protected] Subject: Re: Dataclases according to data set sizes Thanks for the replies. These will be for new data sets - delete and defines on a daily basis. Nine data classes needs to be created, each one with its own allocation size. In the ACS routines I would then need to code 9 FILTER LISTS which would include all the data sets with common allocation attributes (in this case, the SPACE AVGREC where the PRIMARY and SECONDARY space allocation will the same for all data sets under a particular filter list) eg. FILTLIST GZTINYTINY INCLUDE ( DNGG*.**.AID000.**.RR**, DNGG*.**.ACBANK.**.RR** ) FILTLIST GZSMALLSMALL ( DNGG*.**.ANFSYS.**.RR**, DNGG*.**.ATDEND.**.RR** ) IF (&DSN EQ &GZTINYTINY) THEN DO SET &DATACLAS='@TINYTINY' EXIT CODE(0) END IF (&DSN EQ &GZSMALLSMALL) THEN DO SET &DATACLAS='@SMALLSMALL' EXIT CODE(0) END This is only an example of what is needed to be coded, except that the FILTLISTS would contain up to thousands of these data sets... I hope this makes sense now. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of retired mainframer Sent: 29 March 2016 07:31 PM To: [email protected] Subject: Re: Dataclases according to data set sizes Are you talking about new data sets or existing ones? What do you mean by data sets being grouped? What data class attributes would you like to be dependent on the size of the data set. The ALTER command cannot change the data class of an existing data set. Even if it is possible with another utility, changing the data class would have no effect on the other data set attributes stored in the catalog and VVDS. What would you hope to accomplish? The data class ACS routine has access to the &SIZE and &MAXSIZE read-only variables. You can use them as part of the decision process for assigning a data class to a new data set. The management class and storage class ACS routines would have access to this decision and could use that when making their assignments. But those routines would also have access to the variables and could use them directly. What is your real intent that you think different data classes will satisfy? > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Buckton, T. (Theo) > Sent: Tuesday, March 29, 2016 7:04 AM > To: [email protected] > Subject: Dataclases according to data set sizes > > Hi, > > I have thousands of VSAM RR data sets that are grouped according to > their sizes, which > comes to about 9 groups or data classes. It is not too much work to > create the 9 data classes, > but to code these thousands of data sets according to NODE3 in the ACS routines seems a > bit too hectic. Is there perhaps a smarter way to do this? > > Note: We are rolling out z/OS 2.2 which I am studying for any > enhancements related to this > query. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************** Nedbank Limited Reg No 1951/000009/06. The following link displays the names of the Nedbank Board of Directors and Company Secretary. [ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email is confidential and is intended for the addressee only. The following link will take you to Nedbank's legal notice. [ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ] ******************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** 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. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
