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 (July 2003, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Wed, 23 Jul 2003 09:28:36 -0400
Reply-To:   Ed Heaton <EdHeaton@WESTAT.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   Ed Heaton <EdHeaton@WESTAT.COM>
Subject:   Re: mlogic versus autocall library
Content-Type:   text/plain

Of course, I should have protected myself by making reset a local macro variable.

%macro name () ; %local reset ; %let reset %sysFunc( getOption( mLogic ) ) %sysFunc( getOption( mPrint ) ) ; Options noMLogic noMPrint ; ... Options &reset ; %mEnd name ;

-----Original Message----- From: Ed Heaton Sent: Wednesday, July 23, 2003 9:15 AM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: mlogic versus autocall library

Casey, Paul, et al.;

To further Paul's suggestion, you might not want to assume that the system was set to MLOGIC and MPRINT before the macro was called. So, you can code...

%macro name () ; %let reset %sysFunc( getOption( mLogic ) ) %sysFunc( getOption( mPrint ) ) ; Options noMLogic noMPrint ; ... Options &reset ; %mEnd name ;

Ed

Edward Heaton, Senior Systems Analyst, Westat (An Employee-Owned Research Corporation), 1600 Research Boulevard, Room RW-3541, Rockville, MD 20850-3195 Voice: (301) 610-4818 Fax: (301) 610-5128 mailto:EdHeaton@westat.com http://www.westat.com

-----Original Message----- From: Paul Dorfman [mailto:paul_dorfman@HOTMAIL.COM] Sent: Tuesday, July 22, 2003 6:18 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: mlogic versus autocall library

>From: SAS User <sas@SDAC.HARVARD.EDU> > >Does anyone know of a way to turn off mlogic/mprint specifically for >those macros stored in the autocall library? It's rather annoying and >an interference to try to debug code that just has a %left or %verify >in it. Any suggestions? Thanks. > >-casey

Casey,

Not a complete solution, but if, for all of your autocall macros, you can do this

%macro name () ; option nomlogic nomprint ; .... option mlogic mprint ; %mend name ;

then the only MLOGIC stuff the system will print for this macro execution will be

MLOGIC(NAME): Beginning execution. MPRINT(NAME): option nomlogic nomprint ;

Another approach is to consider replacing %LEFT, %VERIFY and such with corresponding DATA step functions via the %SYSFUNC() interface. I have acquired this habit both for the reason you state here and because it provides for faster execution.

Kind regards, ==================== Paul M. Dorfman Jacksonville, FL ====================

_________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963


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