COBOL's HIGH-VALUE and Y2K problems (was Re: Engines to Die for Y2K 
Author Message
 COBOL's HIGH-VALUE and Y2K problems (was Re: Engines to Die for Y2K


>: 'Sounds like a long time ago - HIGH-VALUES is not a numeric value and
>: you get a compiler error if the date field is defined as numeric.

>That depends on what you do with it, and how alert (or picky) your
>compiler is.  There used to be systems where HIGH-VALUES and ALL '9' were
>the same thing.  Of course, it's a tad more difficult to confuse 99/99/99
>with a meaningful date.


I haven't seen/read the whole background of this thread, however, if the
gist is that there is a Y2K problem with using the COBOL HIGH-VALUES
figurative constant with date fields defined with certain PICTURE clauses,
then let me point you to the following.

In the draft Standard (unfortunately probably not to become official until
AFTER Jan 1,2000), there are two new intrinsic functions


These two functions provide solutions for COBOL programming where using
HIGH-VALUES/LOW-VALUES does not provide the expected results.  If this issue
is a real problem for your application(s), then I suggest that you contact
your compiler vendor ASAP.  Many of them have already implemented some of
the new features of the draft Standard (e.g. ACCEPT from DATE YYYYMMDD) and
I suspect that they would look at the 2 "algebraic" functions - if you can
show them to be of significant advantage for handling Y2K problems.

Sun, 23 Jul 2000 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. Long Term, High Earnings Opportunity (not Y2K) for Experienced COBOL Programmer/Analysts

2. I Am Seeking An Entry Level Y2K/COBOL PA Position In Canada

3. Y2K Weather Report # 8 - A Y2K spring.

4. Y2K Weather Report # 8 - A Y2K spring.

5. Y2K Weather Report # 8 - A Y2K spring.

6. COBOL Y2K problem is small

7. COBOL Y2K problem is small

8. Microfocus Level 2 Cobol, y2k problems :-(

9. Looking for a solution for Clipper'87 and Y2K problem

10. Y2K Date 'Goodie'

11. A Y2K 'Fix' Story

12. Python Y2K statement (please don't laugh too hard--I'm serious)


Powered by phpBB® Forum Software