Date: Thu, 19 Aug 2010 15:26:33 -0400
Reply-To: saslearn chicago <sasswamy@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: saslearn chicago <sasswamy@GMAIL.COM>
Subject: Re: SAS / Linux OS
In-Reply-To: <001701cb3fbf$71e4e200$55aea600$@com>
Content-Type: text/plain; charset=ISO-8859-1
*Philip,*
WRK is just a Global path I am using in the program , to make sure to create
all the tables needed for the processing
in a specific path.
nothing related to the SAS . WORK folder
*Tom , *
I looked at the links , good Information.
Well the same program with the same amount of data , works fine in a Sun OS
5.10 machine , apart from the
different machine SUN OS compare with Linux - Program , Data remains the
same.
- Swamy.
On Thu, Aug 19, 2010 at 12:56 PM, Philip Rack <PhilRack@minequest.com>wrote:
> I'm no expert on Linux, but looking at your log, do you have your WORK
> folder redirected somehow? I would have thought that SAS would indicate
> that
> folder by using WORK and not WRK as per your log.
>
> Philip Rack
> MineQuest, LLC
> SAS & WPS Consulting and WPS Reseller
> Tel: (614) 457-3714
> Web: www.MineQuest.com <http://www.minequest.com/>
> Blog: www.MineQuest.com/WordPress <http://www.minequest.com/WordPress>
>
>
> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
> saslearn chicago
> Sent: Thursday, August 19, 2010 12:14 PM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: SAS / Linux OS
>
> Thanks Tom,
>
> Actually the file is 64.89 GB in size , so for sure SAS / Linux allows
> larger files ,
> It errors out right at this point. ( ran couple of times )
>
> Do you know where I need to look at SAS Or Linux config file to look for
> any
> Limitation , when I tired ulimit -a this is what I see :
>
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 280064
> max locked memory (kbytes, -l) 32
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 10240
> cpu time (seconds, -t) unlimited
> max user processes (-u) 280064
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
>
> Error message
> ==========
> ************************************************************************
> ERROR: Write to WRK.CASES.DATA failed. File is full and may be damaged.
> NOTE: The SAS System stopped processing this step because of errors.
> NOTE: SAS set option OBS=0 and will continue to check statements. This may
> cause NOTE: No observations in data set.
> NOTE: There were 1896230604 observations read from the data set WRK.CASES.
> NOTE: There were 33453662 observations read from the data set WRK.PERSON.
> WARNING: The data set WRK. CASES may be incomplete. When this step was
> stopped there were 1896230603 , observations and 8 variables.
> WARNING: Data set WRK. CASES was not replaced because this step was
> stopped.
> NOTE: DATA statement used (Total process time):
> ************************************************************************
>
> Can someone please Advice
>
> - Swamy.
> On Tue, Aug 17, 2010 at 2:11 PM, Tom Abernathy
> <tom.abernathy@gmail.com>wrote:
>
> > Check if the output file is greater than 2Gigabytes. If so you need to
> make
> > sure that your unix and SAS installations can support "largefiles".
> >
>
>
|