Date: Wed, 17 Sep 2008 12:09:44 -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: Help with understanding large SAS legacy system
In-Reply-To: <004901c918d2$92442cb0$b6cc8610$@com>
Content-Type: text/plain; charset=us-ascii
> From: mschult
>
> Dear SAS-L:
> I've inherited a large SAS application that consists of several
> complex macros. I need to understand in detail how the code works
> since modifications are occasionally called for. While I'm familiar
> with the macro debug options of MPRINT, MLOGIC, etc. I find they
> generate a awful lot of listing. I'd appreciate a discussion of how
> best to go about learning someone else's code when the original
> developer is long departed.
if you are the SysOp or SAS Site Admin
you may want to consider saving job information,
both the job logs and rtrace files
http://www.sascommunity.org/wiki/Saving_Job_Information
see also:
http://www.sascommunity.org/wiki/Reading_job_logs
http://www.sascommunity.org/wiki/Reading_Rtrace_logs
Ronald J. Fehd, IT Spec
team lead: Statistical Software
and Knowledge Worker Support
HelpDesk Level 3: SAS
CDC SAS site representative
| 
