Tom,

I haven't tried this as yet because V8 is sitting under my desk waiting to be installed.

Form what I have read, multivolume SAS datasets in V8 follow the same rules as other multivolume datasets, no more guaranteed space, dynamic allocation of extra volumes... definitely worth pursuing further.

Check out the following link on the SAS web site: http://www.sas.com/service/library/onlinedoc/v8/whatsnew/tw5508/zenid-42.htm

I would also check out the SAS Companion for MVS in the V8 doco. for further detail and examples.

Regards, Rick.

> -----Original Message----- > From: Hanan, Thomas J [SMTP:HananTJ@AETNA.COM] > Sent: Wednesday, January 31, 2001 8:13 AM > To: SAS-L@LISTSERV.UGA.EDU > Subject: SAS version 8.1 on MVS, allocating SAS datasets on multiple > DASD volumes > > Hello SAS-Lers, > > I have a coworker having a problem running out of space when creating a > very, very, very large indexed SAS dataset on MVS, running version 6.09. > I was looking through the documentation on allocating multiple-volume > datasets and remembering the horror stories I've heard about trying to do > such a thing (especially related to dataset migration, copying, etc.). > We're going to be moving to version 8.1 this weekend, and I was wondering > if anybody knew if the new version made this task (allocation of SAS > datasets on multiple volumes) any easier/less dangerous. Has anybody done > this on version 8.1? Can you give me any examples/JCL/etc.? Should I > even pursue this any further? > > Thanks in advance for any guidance you can provide. > > Tom ********************************************************************** CAUTION: This Message may contain confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you received this message in error please notify Mail Administrators immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of Woolworths Ltd. **********************************************************************