Now that I look at it, all the code never made it. Comcast changed their email format
on me and it really stinks. Will get it posted tonight when I get home.
Don't have this revision with me at moment. Sorry


Jim

David M. Blocker wrote:

Sorry Jim, I can't tell what part of the original code this in intended to replace, or where it's added in.
David Blocker
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
781-784-1919
Fax: 781-784-1860
Cell: 339-206-0261
----- Original Message -----
From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
To: RBG7-L Mailing List <mailto:[EMAIL PROTECTED]>
Sent: Tuesday, July 06, 2004 8:39 PM
Subject: [RBG7-L] - Re: Tracking Intermediate errors


I've been think a bit here lately of polishing it a bit with a

way to be able to return to the line after the code. Here's

what I have so far.. Rough Draft..



SET VAR vy_labelcount INTEGER = 0
SET ERROR VARIABLE errvar
SET VAR vy_errnum INTEGER = NULL
SET VAR vy_log INT! EGER = 0
SET VAR vy_errsection TEXT = NULL
SET VAR vy_errcritical INTEGER = 0

--other code

--likely problem section or one I want to log
--Defined Section information goes here
SET VAR ! vy_errsection = 'So and So View inop'
--CODE GOES HERE
CREATE VIEW junkieview SELECT ALL FROM

Jim

    -------------- Original message --------------

> That is slick code, jim!!
>
> David
>
> David Blocker
> [EMAIL PROTECTED]
> 781-784-1919
> Fax: 781-784-1860
> Cell: 339-206-0261
> ----- Original Message -----
> From: "Jim Limburg"
> To: "RBG7-L Mailing List"
> Sent: Friday, July 02, 2004 3:38 PM
> Subject: [RBG7-L] - Re: Tracking Intermediate errors
>
>
> > What about writing the to a log
> >
> >
> > SET ERROR VARIABLE errvar
> > SET VAR vy_errnum INTEGER = NULL
> > SET VAR vy_log INTEGER = 0
> > SET VAR vy_errsection TEXT = NULL
> >
> > --other code
> >
> > --likely problem section or one I want to log
> >! --Defined Section information goes here
> > SET VAR vy_errsection = 'So and So View inop'
> > --CODE GOES HERE
> > IF errvar <> 0 THEN
> > SET VAR vy_errmsg = 'Error Creating view'
> > SET VAR vy_errnum = .errvar
> > RUN errhndler IN invsum.x2r
> > GOTO getout1
> > ENDIF
> >
> >
> > RETURN
> > $COMMAND
> > errhndler
> > OUTPUT SCREEN
> > SET VAR vy_errmess TEXT = ('ERROR: # ' + (CTXT(.vy_errnum)) + +
> > ' Msg = ' + .vy_errmsg)
> > PAUSE 1 USING .vy_errmess AT CENTER CENTER
> > IF vy_log = 1 THEN
> > OUTPUT mylogfile.log APPEND
> > WRITE '**************************************'
> > WRITE .vy_errsection
> > WRITE .vy_errmess
> > WRITE '**************************************'
> > OUTPUT SCREEN
> > ENDIF
> > OUTPUT SC! REEN
> > SET VAR vy_errsection TEXT = NULL
! > > ; SET VAR vy_log = 0
> > CLEAR VAR vy_errnum, vy_errmess
> > RETURN
> >
> > Jim
> >
> > Charles Parks wrote:
> >
> > >What are some good strategies for tracking and fixing errors
that do not
> consistently repeat?
> > >
> > >
> > >
> > >
> >
> >
>





Reply via email to