LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (February 2004, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Wed, 11 Feb 2004 08:56:49 -0600
Reply-To:     Paul Thompson <paul@WUBIOS.WUSTL.EDU>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Paul Thompson <paul@WUBIOS.WUSTL.EDU>
Organization: Washington University in St. Louis
Subject:      Re: Debug errors for SAS/IntraNet
Content-Type: text/plain; charset=us-ascii; format=flowed

Crystal Vierhout wrote: > Hello, > > I'm have a small problem of catching an debug error in a production application. I realize you are never supposed to have errors in a production application but its not the case in this program. I'm not get the error to come up in any of SAS's normal logs. Is there a way when an end user gets a debug error of having a email sent to me or drop a record into a specific dataset when it occurs. Is there a good answer? > > Crystal

1) use proc printto to route all logs to a dataset.

2) after the production SAS/IntrNet process has finished, shell out a SAS job which post-processes the log to find the error.


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