DATA CONVERSION ERRORS in PH8

Pickering, John (NORBORD) PICKERIJ@norbord.com
Tue, 18 Apr 2000 10:11:16 -0400


Unless someone from Cognos jumps in here and reveals some undocumented
feature I think you're out of luck trying to detect data conversion errors
after they have happened.

What you'll need to do is to ensure that the data is valid *before*
attempting to process it. More editing - is it numeric, is it reasonable,
are the intermediate items in any calculations big enough to hold all
possible results, are any dates really dates, watch the substring function
on null strings. Assume you're going to get garbage in your "outside data" -
*never* trust it. Not fun, just part of the job of accepting "outside data".

> -----Original Message-----
> From:	Friedrich.Harasleben@oekv.com [SMTP:Friedrich.Harasleben@oekv.com]
> Sent:	Tuesday, April 18, 2000 2:58 AM
> To:	powerh-l@lists.swau.edu
> Subject:	DATA CONVERSION ERRORS in PH8
> 
> 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
> 
> Oesterreichische Kreditversicherungs AG
> Stubenring 24
> 1010 Wien
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.