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 (May 2007, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 10 May 2007 11:54:48 -0400
Reply-To:     "Fehd, Ronald J. (CDC/CCHIS/NCPHI)" <rjf2@CDC.GOV>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Fehd, Ronald J. (CDC/CCHIS/NCPHI)" <rjf2@CDC.GOV>
Subject:      Re: 'Local' datasets in Macro?
In-Reply-To:  <BAY103-F223FE2FA2AF658F6B00A1EB03A0@phx.gbl>
Content-Type: text/plain; charset=us-ascii

> From: David L Cassell

> I think that no method can be 100% perfect, particularly when > some of these methods ar *not* atomic and hence can be ruined > by the inadvertent creation of a new data set by a different > process in the same library at the exact wrong time.

<sigh> are we getting close to an answer:

1 %Macro TestName(x=); 1.1 %Local TempData; 2 %Put TempData = &SysMacroName.%sysfunc(datetime(),hex16.);%Mend; 3 %TestName; TempData = TESTNAME41D644BFBEF24DD3

note: max(length(data set name)) = 32, eh?

summary: why would you want a length(macro name) gt 16?

Ron Fehd the macro maven CDC Atlanta GA USA RJF2 at cdc dot gov


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