Re: *ISO date in COBOL? - FIXED! -- COBOL400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Thanks Chuck - I'll pass this along to the programmer handling it now that
we've got it going.

Tom

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Saturday, November 30, 2013 11:22 AM
To: cobol400-l@xxxxxxxxxxxx
Subject: Re: [COBOL400-L] *ISO date in COBOL? - FIXED!

On 30-Nov-2013 08:19 -0800, Tom Hightower wrote:

(Problem fixed <<SNIP>>

After initializing the BEGIN-DATE (date) to '9999-12-31' and JELLA
(time) field to '23.59.59' , the program compiled and ran. Now to hand
it back to the programmer for her to continue working with it.

FWiW: The database treats the time 24:00:00 as greater than the time
00:00:00, such that they are not considered equivalent *except* when they
are part of two TIMESTAMP values for successive dates whereby the prior date
has 24.00.00 time and the [next day] later date has 00.00.00 time. Thus the
effective *HIVAL for the TIME is '24.00.00', not '23.59.59'.

This mailing list archive is Copyright 1997-2024 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.