Re: DYNALLOC question (Multi-Volume)
If you use this on a wide scale, you might blow up your catalogs. Each dataset reserves 255 (candidate) volumes entries in the catalog record and these take space. Do a LISTC of such a dataset. Ah, good point. Thanks! Bye, Michael -- 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: DYNALLOC question (Multi-Volume)
"Michael Knigge" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > All, > > currently I'm playing around a little bit with the SVC99 DYNALLOC. When > I try to allocate a rather large Dataset, I (sometimes) need to specify > DALVLCNT (Dataset volume count). > > Now... I wonder it it would be safe (or "ok") to specify 255 in all > cases, even when allocating a small dataset. The documentation says > "DALVLCNT specifies the maximum number of volumes an output data set may > require."... **MAY**... > > So... If I don't care if the dataset is a multi-volume or not (I just > want to be sure the dataset can be allocated somehow if space is > somewhere available), is it safe/ok to specify 255 and let z/OS decide > to allocate multi-volume or not? > > If you use this on a wide scale, you might blow up your catalogs. Each dataset reserves 255 (candidate) volumes entries in the catalog record and these take space. Do a LISTC of such a dataset. Kees. ** 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: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DYNALLOC question (Multi-Volume)
Ted, Here is the original email. Nothing about DASD that I can see, although he does mention "space" which could imply DASD: "All, currently I'm playing around a little bit with the SVC99 DYNALLOC. When I try to allocate a rather large Dataset, I (sometimes) need to specify DALVLCNT (Dataset volume count). Now... I wonder it it would be safe (or "ok") to specify 255 in all cases, even when allocating a small dataset. The documentation says "DALVLCNT specifies the maximum number of volumes an output data set may require."... **MAY**... So... If I don't care if the dataset is a multi-volume or not (I just want to be sure the dataset can be allocated somehow if space is somewhere available), is it safe/ok to specify 255 and let z/OS decide to allocate multi-volume or not? Thanks, Michael" Tom Harper IMS Utilities Development Team Neon Enterprise Software, Inc. Sugar Land, TX -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Wednesday, May 28, 2008 9:23 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DYNALLOC question (Multi-Volume) >It's hard to say. I believe it's built by DFSMS code, which could be argued to be part of z/OS. But ownership of the code is a diversion here. >59 volumes is a DASD restriction, not an allocation restriction. You can dynamically allocate a 255 volume tape data set. I thought the OP was discussing DASD, but I could be wrong. - 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 -- 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: DYNALLOC question (Multi-Volume)
>It's hard to say. I believe it's built by DFSMS code, which could be argued to >be part of z/OS. But ownership of the code is a diversion here. >59 volumes is a DASD restriction, not an allocation restriction. You can >dynamically allocate a 255 volume tape data set. I thought the OP was discussing DASD, but I could be wrong. - 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: DYNALLOC question (Multi-Volume)
Thank you guys! bye, Michael -- 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: DYNALLOC question (Multi-Volume)
Ted,
It's hard to say. I believe it's built by DFSMS code, which could be
argued to be part of z/OS. But ownership of the code is a diversion
here. 59 volumes is a DASD restriction, not an allocation restriction.
You can dynamically allocate a 255 volume tape data set.
Tom Harper
IMS Utilities Development Team
Neon Enterprise Software, Inc.
Sugar Land, TX
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ted MacNEIL
Sent: Wednesday, May 28, 2008 7:33 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: DYNALLOC question (Multi-Volume)
>Actually, z/OS supports a maximum of 255 volumes. 59 volumes is a DASD
restriction based on DEB constraints.
Funny!
I thought the DEB was a z/OS construct.
(8-{]}
-
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
--
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: DYNALLOC question (Multi-Volume)
>Actually, z/OS supports a maximum of 255 volumes. 59 volumes is a DASD
>restriction based on DEB constraints.
Funny!
I thought the DEB was a z/OS construct.
(8-{]}
-
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: DYNALLOC question (Multi-Volume)
Actually, z/OS supports a maximum of 255 volumes. 59 volumes is a DASD restriction based on DEB constraints. Tom Harper IMS Utilities Development Team Neon Enterprise Software, Inc. Sugar Land, TX -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Wednesday, May 28, 2008 6:35 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DYNALLOC question (Multi-Volume) >is it safe/ok to specify 255 and let z/OS decide to allocate multi-volume or not? z/OS supports a maximum of 59 volumes. And, it is safe. Nothing significant is used until the volumes are allocated. - 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 -- 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: DYNALLOC question (Multi-Volume)
>is it safe/ok to specify 255 and let z/OS decide to allocate multi-volume or not? z/OS supports a maximum of 59 volumes. And, it is safe. Nothing significant is used until the volumes are allocated. - 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
DYNALLOC question (Multi-Volume)
All, currently I'm playing around a little bit with the SVC99 DYNALLOC. When I try to allocate a rather large Dataset, I (sometimes) need to specify DALVLCNT (Dataset volume count). Now... I wonder it it would be safe (or "ok") to specify 255 in all cases, even when allocating a small dataset. The documentation says "DALVLCNT specifies the maximum number of volumes an output data set may require."... **MAY**... So... If I don't care if the dataset is a multi-volume or not (I just want to be sure the dataset can be allocated somehow if space is somewhere available), is it safe/ok to specify 255 and let z/OS decide to allocate multi-volume or not? Thanks, Michael -- 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
