HP3000-L Archives

April 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Mon, 17 Apr 2000 13:40:10 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Dear Listers,

we are looking for a solution for our POWEHOUSE BATCH programs, to trap
DATA CONVERSION ERRORS:

1) If the DATA CONVERSION ERROR occurs in a subscreen (which has been
called bei RUN SCREEN ..... ON ERROR TERMINATE)
    the following occurs in the screen:
    - 0 is assigned to the field, for which the DATA CONV ERROR occurs
    - the progam proceeds to its end
    - returns to the MAIN SCREEN which then terminates

    Nevertheless, the subscreen might already have done other processing
(in our case it PUTTED a record, which has processing errors in it, due to
the CONVERSION ERROR).

    Is there any way, to stop the SUBSCREEN from processing or to check any
predefined variable to be able to realize the problem in the SUBSCREEN?

2) If the DATA CONVERSION ERROR occurs in the MAIN SCREEN, then the program
proceeds further (calls subscreens etc.) and displays the message at the
end of processsing.


In general, as this are no ONLINE but BATCH  programs, and the data which
is being processed is sent to from external, we need to make sure - as much
as possible - that RUN TIME ERRORS do not cause serious problems in our DB.
Are there any other suggestions, to accomplish this?

THANKS Friedrich

P.S. I heard of a POWERHOUSE newsgroup, does someone know the address?

ATOM RSS1 RSS2