LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (February 2011, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 3 Feb 2011 11:54:47 -0800
Reply-To:     Sterling Paramore <gnilrets@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Sterling Paramore <gnilrets@GMAIL.COM>
Subject:      Out of memory?
Content-Type: text/plain; charset=ISO-8859-1

Dear SAS-L,

I assume the following is failing due to the system running out of memory (way to go SAS - not only do you not tell me what the problem is, this doesn't even register as a real ERROR, only a warning) because if I run it with an OBS= statement, it completes just fine.

To solve the problem, I've tried first sorting the dataset (6 minutes), then doing proc means with a by (7 minutes). I also tried using proc sql and it required only 5 minutes.

Any other ideas? I'd prefer not to have to rewrite a bunch of my proc means as sql.

Thanks, Sterling

16 17 proc means noprint missing nway data = WORKERR._BMClaims_Concat; 18 var Claim_Counter ClaimLine_Counter ClaimLine_Paid_Amt ClaimLine_COB_Paid_Amt 19 Claim_Interest_Amt ClaimLine_Savings_Amt; 20 class Claim_Id Claim_Diag_Primary Claim_Prim_Hosp_Proc_Cd Claim_Bill_Type; 21 output out = WORK._BMClaims (drop = _TYPE_ _FREQ_) sum()=; 22 run;

NOTE: The SAS System stopped processing this step because of errors. NOTE: There were 70619390 observations read from the data set WORKERR._BMCLAIMS_CONCAT. WARNING: The data set WORK._BMCLAIMS may be incomplete. When this step was stopped there were 0 observations and 10 variables. NOTE: PROCEDURE MEANS used (Total process time): real time 2:23.15 cpu time 3:08.01


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