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 (June 2004, 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 Jun 2004 08:52:59 -0400
Reply-To:     "Richard A. DeVenezia" <radevenz@IX.NETCOM.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Richard A. DeVenezia" <radevenz@IX.NETCOM.COM>
Subject:      Re: Can a macro variable be unassigned in version 6.12

Mark S Goldberg wrote: > I've seen a few places that state explicitly that a macro variable > CANNOT be unassigned (that is until the version 8.2 "call symdel" > command was implemented). I, however, remain of fervent hope that > someone knows someway to accomplish this. > > I'm looking to validate a series of macros and, among other things, > to test how they respond to missing expected macro variable > assignments. The easiest way to do this would be to leave the whole > infrastrucure of the system in place and just have individual > programs unassign a particular variable and then call the macro. > > Thanks for your help! > > Mark > Forest Research Institute > Jersey City, NJ

Not in any supported way. Your best bet is probably to setup a bunch of unit tests in individual program files and run each one in batch.

The unsupported way involved changing the number of catalogs cached and deleting some files via an x command. The archives should contain at least thread describing the process.

-- Richard A. DeVenezia http://www.devenezia.com/downloads/sas/samples


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