Running SAS on PC, need to delete old compiled macro
in [SAS]
|
From: Kevin Myers on 9 Mar 2010 10:32 I haven't seen these approaches mentioned yet, so you could also consider: 1. Delete the corresponding MACRO entries from the WORK.SASMACR catalog, for example by using either PROC DATASETS or the explorer window. .. 2. Use OPTIONS MRECALL. This will cause force previously encountered macros to be re-compiled when they are encountered again. HTH. s/KAM ----- Original Message ----- From: "SUBSCRIBE SAS-L Dan" <deniseyu001(a)GMAIL.COM> To: <SAS-L(a)LISTSERV.UGA.EDU> Sent: Tuesday, March 09, 2010 08:48 Subject: Re: Running SAS on PC, need to delete old compiled macro > Hi. Daniel: > > I switched from batch mode to SAS window interactive because I am writing > the whole code (header program and macro programs) interactively; also I > want to run the code on the interactive SAS window so I may be able to > check the temporary data sets in the work library. Thanks. > > Dan >
From: xlr82sas on 9 Mar 2010 12:25 On Mar 9, 7:32 am, KevinMy...(a)AUSTIN.RR.COM (Kevin Myers) wrote: > I haven't seen these approaches mentioned yet, so you could also consider: > > 1. Delete the corresponding MACRO entries from the WORK.SASMACR catalog, for > example by using either PROC DATASETS or the explorer window. > . > 2. Use OPTIONS MRECALL. This will cause force previously encountered macros > to be re-compiled when they are encountered again. > > HTH. > > s/KAM > > > > ----- Original Message ----- > From: "SUBSCRIBE SAS-L Dan" <deniseyu...(a)GMAIL.COM> > To: <SA...(a)LISTSERV.UGA.EDU> > Sent: Tuesday, March 09, 2010 08:48 > Subject: Re: Running SAS on PC, need to delete old compiled macro > > > Hi. Daniel: > > > I switched from batch mode to SAS window interactive because I am writing > > the whole code (header program and macro programs) interactively; also I > > want to run the code on the interactive SAS window so I may be able to > > check the temporary data sets in the work library. Thanks. > > > Dan- Hide quoted text - > > - Show quoted text - Hi, I run both batch and interactive. I have a function key that does the following ( I call the macro RunIfChanged) 1. Versions the interactive program (checks it out of SCCS if not already checked out) 2. Saves the interactive program in my utl directory with the leading TLA IE production program 'pmo_lab.sas' where pmo stands for postmenopausal osteoporosis (I have every program I have written over the last 30 years in one directory(+30,000)) (I am moving some of these to my tips) 3. Promotes the program to production on unix removing the 'cr' and the TLA ie production program name is lab.sas 4. Checks the program into SCCCS 5. Runs the program batch UNIX 6. Returns the log, list and a nice logscrub to my interactive session in notepads ,h,i and j. 7. Function keys cntl i, cntl j and cntl h change focus to the correct screen. I posted most of thei functionality on my site.
From: xlr82sas on 9 Mar 2010 12:50 On Mar 9, 9:25 am, xlr82sas <xlr82...(a)aol.com> wrote: > On Mar 9, 7:32 am, KevinMy...(a)AUSTIN.RR.COM (Kevin Myers) wrote: > > > > > > > I haven't seen these approaches mentioned yet, so you could also consider: > > > 1. Delete the corresponding MACRO entries from the WORK.SASMACR catalog, for > > example by using either PROC DATASETS or the explorer window. > > . > > 2. Use OPTIONS MRECALL. This will cause force previously encountered macros > > to be re-compiled when they are encountered again. > > > HTH. > > > s/KAM > > > ----- Original Message ----- > > From: "SUBSCRIBE SAS-L Dan" <deniseyu...(a)GMAIL.COM> > > To: <SA...(a)LISTSERV.UGA.EDU> > > Sent: Tuesday, March 09, 2010 08:48 > > Subject: Re: Running SAS on PC, need to delete old compiled macro > > > > Hi. Daniel: > > > > I switched from batch mode to SAS window interactive because I am writing > > > the whole code (header program and macro programs) interactively; also I > > > want to run the code on the interactive SAS window so I may be able to > > > check the temporary data sets in the work library. Thanks. > > > > Dan- Hide quoted text - > > > - Show quoted text - > > Hi, > > I run both batch and interactive. > > I have a function key that does the following ( I call the macro > RunIfChanged) > > 1. Versions the interactive program (checks it out of SCCS if > not already checked out) > 2. Saves the interactive program in my utl directory with the > leading TLA > IE production program 'pmo_lab.sas' where pmo stands for > postmenopausal osteoporosis > (I have every program I have written over the last 30 years > in one directory(+30,000)) > (I am moving some of these to my tips) > 3. Promotes the program to production on unix removing the 'cr' > and the TLA ie production program name is lab.sas > 4. Checks the program into SCCCS > 5. Runs the program batch UNIX > 6. Returns the log, list and a nice logscrub to my interactive > session in notepads ,h,i and j. > 7. Function keys cntl i, cntl j and cntl h change focus to the > correct screen. > > I posted most of thei functionality on my site.- Hide quoted text - > > - Show quoted text - SOAPBOX ON: As I side note, I lose allmost all of this functionality with the super enhanced Enterprise Guide. I have made quite a few addditions to my comparison of Enterprise Guide to Windows-SAS-with-connect. Unfortunately I think SAS is trying to kludge some functions back into EG, ie SCL. I recently saw a 'priority?' list of products at a major corporation and EG was #3, so watch out. We all have a stake in this. SOAPBOX OFF: http://homepage.mac.com/magdelina/.Public/utl.html /* T003860 A TECHNICAL COMPARISON OF ENTERPISE GUIDE THIN CLIENT TO UNIX VERSUS SAS-CONNECT FAT CLIENT TO UNIX You won't find this kind of information anywhere else. If any EG expent wants to help me 'correct' or 'update' this document please come forward. I will give the expert a lot of leaway and remove all incorrect information.
First
|
Prev
|
Pages: 1 2 Prev: Probit dose-response model with second, random main effect Next: SAS, Mac & VMWare Fusion |