Charming man. I wish I had a daughter so I could forbid her to marry one...
Date: Thu, 20 Feb 2003 00:20:17 +0000
Reply-To: Alastair Nicol <calaban.madness@BLUEYONDER.CO.UK>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Alastair Nicol <calaban.madness@BLUEYONDER.CO.UK>
Subject: Re: SAS/Intrnet - trapping errors before the browser displays them
Content-Type: text/plain; charset=us-ascii; format=flowed
Being a Python fan, Python has the cgi traceback which works well :-)
cgi2sas doesnt trap major errors at the mo, just an empty _webout. You
have the source code for cgi2sas to amend as would like. Now that i've
discovered about the syscc, i'll add something (not sure what). the
problem is when a transaction stuffs up what to do??? have an
application recovery or system recovery? At the mo cgi2sas is mosty
compatible with sas/intrnet, its a fine line between compatability and
cgi2sas has better logging facilities than sas/intrnet (imho), i've
taken a more debugging point of view so the log viewer reports any
errors during testing. Production code should never break - well thats
the theory ;-)
David L. Cassell wrote:
>Alastair Nicol <calaban.madness@BLUEYONDER.CO.UK> replied [in small
>>any takers? theres got to be more that 5 ways to skin this cat
>Perl. Since I seem to be on a Perl 'thread' at the moment, let me
>just point out that SAS/Intrnet works with Perl. Perhaps the OP could
>use Perl to trap his errors before passing traffic back to SAS.
>As it is, Perl can make SAS/Intrnet work more smoothly, and can
>facilitate things which SAS/Intrnet doesn't do as well as it ought to,
>like catching web errors (I highly recommend the CGI::Carp module) or
>using a redirect to transfer the user to a 'wait while processing' page
>when a SAS job on the back end will take a while.
>For that matter, would Alastair's CGI2SAS program let one do the
>same? Will it interact with SAS/Intrnet and do error-capture?
>David Cassell, CSC
>Senior computing specialist