LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (August 1997, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Sat, 2 Aug 1997 04:05:00 -0700
Reply-To:     mmathis@primenet.com
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
Comments:     RFC822 error: <E> Mail origin cannot be determined.
Comments:     RFC822 error: <E> Original tag data was -> Martin Mathis
From:         Undetermined origin c/o LISTSERV administrator
              <owner-LISTSERV@VTVM1.CC.VT.EDU>
Organization: (not affiliated)
Subject:      2GB limit on Solaris and SAS 6.12 workspace

Hi all,

We recently switched to SAS 6.12 on our Solaris 2.5.1 platform. The type=partition option is a real blessing, however I ran into a serious limitation: The 50GB /saswork space wasn't enough for my job so I tried to concatenate additional space by defining additional work filesystems like this in sas config:

-work (/saswork,/filesys1,/filesys2) -partition 1800m

the combined space would have given me some 80GB (50, 20, 10) of disk space that SAS could have spanned my work partitions across, however what I observed was that SAS didn't fill the available space but rather put one single 1800m partition into each filesystem and then abended saying there were insufficient directories/filesystems to continue. With a single filesystem (/saswork) it at least would partition till all the space was used up. I talked to SAS tech support and they said that behavior was by (experimental) design (wait for Solaris 2.6). I was just wondering if anybody had found some way around this. I tried subdirs in the /saswork and the /filesys[12] but there is a limit of 10 that can be specified in config.sas, not enough for my job. Then I tried to juggle my data manually between pseudo-work dirs like "work2" which eventually worked. But I still would like to able to concatenate several designated work-dirs into one continuous disk-space pool? Can that be done?

Cheers,

-Martin ______________________________________________________________ mmathis@primenet.com


Back to: Top of message | Previous page | Main SAS-L page