There is no way to handle these errors - except to say that make sure they
never occur!

It is like asking if code A=apples, code B=bananas, then what happens if a
program encounters code C?  What does code C indicate??

You can test if a field is numeric, but then what?  Do you invoice the item
for free if the cost is not numeric???  Maybe yes, maybe no!

Also, testing for numeric validity seems to really slow down program
performance!

Best approach is to ensure data IS numeric and clean prior to running a
program against the data!


-----Original Message-----
From: A. Sivasubrahmanian
[mailto:sivasubrahmanian.ananthakrishnan@wipro.com]
Sent: Monday, January 13, 2003 4:15 AM
To: cobol400-l@midrange.com
Subject: Program Status Exception Handling


Hi *ALL,

I would like to know, how to handle program exceptions like Decimal data
error, Range subscript etc within COBOL program. Please help me with a
sample code. 

Thanks & Regards
Sivasubrahmanian. A
Project Engineer
Wipro Technologies (Finance & Insurance)
Electronics City, Bangalore, India
Phone - 8520408/8520416 x - 4364.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.