× 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.



Tested with this quick program
0001.00 Dtime1 S Z
inz(z'2000-01-01-00.00.00.000000')
0002.00 Dtime2 S Z
inz(z'2000-01-01-24.00.00.000000')
0003.00 Dequal S N
0004.00 /free
0005.00 equal = (time1 = time2);
0006.00 dsply equal;
0007.00 *inlr = *on;
0008.00 /end-free


result was

DSPLY 0

Not equal in the eyes of IBM.




Mark Walter
Paragon Consulting Services, Inc.
IBM Certified System i Specialist
717-764-7909 Ext. 26
mwalter@xxxxxxxxxxxxxxx
www.paragon-csi.com



"Paul Raulerson" <paul@xxxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
11/28/2007 08:23 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
RE: 00:00:00 or 24:00:00






24:00 implies duration, meaning midnight at the end of the day. 00:00
implies no duration, meaning
midnight at the beginning of the day.

So your assumption that 01 Jan 2000 24:00 is really the same as 02 Jan
2000
00:00 is correct.
And the standard says they are the same. :) I don't believe that 01 Jan
2000 00:00 and 01 Jan 2000 24:00
will compare to be equal, though it would be cool if someone had time to
test it.

-Paul



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Peter.Colpaert@xxxxxxxxx
Sent: Wednesday, November 28, 2007 3:24 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: 00:00:00 or 24:00:00

Hi group,

we're having a bit of a discussion here regarding time.

One of our processes involves parsing a directory listing of a windows
shared drive, and there are 6 files which cause problems.

These files have an entry in the listing as follows:

01/01/2000 12:00a 438,082 GN0229084.JPG

The listing is parsed by two different programs (one made by me, the
other
made several years ago by another developer).

His program (using pre-bif methods) returns the time as 00:00:00,
whereas
mine (using the %time built-in function) returns 24:00:00

First of all, I'd like to know whether January 1, 2000 00:00:00 is the
same as January 1, 2000 24:00:00 (I would think that the latter
actually
means January 2).

Second, which one is correct?

Considering that the listing is using *USA time notation, I'm hoping
you
guys from across the pond can point me in the right direction.

My suggestion to my project leader is to manually update the timestamp
to
1 minute past midnight, and avoid the discussion altogether (what are
the
chances of new documents having a timestamp of midnight anyway)

Thanks in advance,

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we. Futile is resistance, assimilated will you be.
-----
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.