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 (January 2007, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Wed, 24 Jan 2007 14:00:44 +0000
Reply-To:     toby dunn <tobydunn@HOTMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         toby dunn <tobydunn@HOTMAIL.COM>
Subject:      Re: data-driven solution
Comments: To: tree.frog2@hotmail.com
In-Reply-To:  <1169635552.240748.316160@h3g2000cwc.googlegroups.com>
Content-Type: text/plain; format=flowed

Tree Frog ,

Two ways come to mind,

1.) Write the code out to a temp or Perm file and %include it back into the program. Will do the what you want without the stack overflow problem.

Or

2.) Write a macro that pops the data set and grabs the value. The macro should do this in pure macro language and should return just teh value you want.

Toby Dunn

To sensible men, every day is a day of reckoning. ~John W. Gardner

The important thing is this: To be able at any moment to sacrifice that which we are for what we could become. ~Charles DuBois

Don't get your knickers in a knot. Nothing is solved and it just makes you walk funny. ~Kathryn Carpenter

From: Tree Frog <tree.frog2@HOTMAIL.COM> Reply-To: Tree Frog <tree.frog2@HOTMAIL.COM> To: SAS-L@LISTSERV.UGA.EDU Subject: Re: data-driven solution Date: Wed, 24 Jan 2007 02:45:52 -0800

David L Cassell wrote:

> I just thought I would point out that if you really are going to have this > many customers and this many graphs per customer, then you are likely > to have too many calls to PROC EXECUTE for your own good. > > This has been discussed in SAS-L before, and I believe that Master Ian > (Ian Whitlock, to those who have not mastered The Force) has published > in SAS-L posts some recommendations that oyu might be ableto find in the > SAS-L archives. > > But if you are going to have hundreds of thousands of CALL EXECUTE > statements, you are likely to overflow the queue these go into, and > wreak havoc with your plan. > > So you might have to re-think the design a bit. > > HTH, > David > -- > David L. Cassell > mathematical statistician > Design Pathways > 3115 NW Norwood Pl. > Corvallis OR 97330 > > _________________________________________________________________ > Get in the mood for Valentine's Day. View photos, recipes and more on your > Live.com page. > http://www.live.com/?addTemplate=ValentinesDay&ocid=T001MSN30A0701

David - thanks for this insight. Having not started coding - I'm still very much in the planning stage - do you have a suggestion that doesn't involve CALL EXECUTE? You're right, there are going to be a LOT of customers/graphs. I'm hunting through the SAL-L archives.

It strikes me that this would be a fairly common type of task to design a SAS routine for... does anyone know of anything like it?

Thanks again

TF

_________________________________________________________________ Laugh, share and connect with Windows Live Messenger http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=hmtagline


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