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


  1.  Home
  2. MIDRANGE-L
  3. April 2015

RE: TimeStamp Problem

Jon,

I remember (S/34!) going from Cobol68 to -74. We had a Cobol app that,
though it didn't throw any errors, Geez, we just couldn't get the inventory
to balance (not my app, by the way; contactor B4 I came on board). When I
upgraded to 74, errors flew all over the place. Turned out the original
developers were using pointers and, obviously, knew less than I did (which
is going some!). We had to downgrade to -68 just so our orders would run.

Jerry C. Adams
If you can't laugh at yourself, I'll do it for you.
IBM i Programmer/Analyst
--
NMM&D
615-832-2730

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon
Paris
Sent: Thursday, April 16, 2015 4:59 PM
To: Midrange-L Midrange-l
Subject: Re: TimeStamp Problem

I _think_ it was because at the time that the functionality was added to RPG
the system only provided 3 digits.

Not sure why it has not been updated but often if the compiler folks do
stuff like that then very soon someone is screaming because the 3 digit
accuracy was a "feature" that they rely on. Yes - really - I once was
ordered to pull a fix from the COBOL compiler because GM had built an
application that relied on it not working properly!


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Apr 16, 2015, at 5:43 PM, broehmer@xxxxxxxxxxxxxxx wrote:

Yes. RPG. Just didn't realize until today that it was a known
limitation and I've been doing this for some 30 years.
Just boggles the mind that the developers would do that. Why? What
possible limitation would keep them from doing it right?

Bill


"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the
attachments accompanying it) contain confidential information belonging to
the sender.
The information is intended only for the use of the intended recipient.
If you are not the intended recipient, you are hereby notified that
any disclosure, copying, distribution or the taking of any action in
reliance on the contents of the information is strictly prohibited.
Any unauthorized interception of this transmission is illegal under the
law.
If you have received this transmission in error, please promptly
notify the sender by reply e-mail, and then destroy all copies of the
transmission."






From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/16/2015 04:38 PM
Subject: RE: TimeStamp Problem
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I assume you're doing something in RPG. DB2 goes out to all 6, but
RPG only goes out 3.

I have no idea why.




-----Original Message-----
From: broehmer@xxxxxxxxxxxxxxx [mailto:broehmer@xxxxxxxxxxxxxxx]
Sent: Thursday, April 16, 2015 4:17 PM
To: Midrange Systems Technical Discussion'
Subject: TimeStamp Problem

All right. I'm going to ask one of those "stupid" questions.

Why does the time stamp only use the first 3 positions of the millisecond?
We just tried to find unique records for a file based on time stamp
and got several results returned all with the last 3 positions 0. In
fact, all our files are like that.

Is this by design? Are we doing something wrong when we write them out?



Bill Roehmer


"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the
attachments accompanying it) contain confidential information belonging to
the sender.

The information is intended only for the use of the intended recipient.
If you are not the intended recipient, you are hereby notified that
any disclosure, copying, distribution or the taking of any action in
reliance on the contents of the information is strictly prohibited.
Any unauthorized interception of this transmission is illegal under the
law.
If you have received this transmission in error, please promptly
notify the sender by reply e-mail, and then destroy all copies of the
transmission."




"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the
attachments accompanying it) contain confidential information belonging to
the sender.
The information is intended only for the use of the intended recipient.
If you are not the intended recipient, you are hereby notified that
any disclosure, copying, distribution or the taking of any action in
reliance on the contents of the information is strictly prohibited.
Any unauthorized interception of this transmission is illegal under the
law.
If you have received this transmission in error, please promptly
notify the sender by reply e-mail, and then destroy all copies of the
transmission."

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.




"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the attachments
accompanying it) contain confidential information belonging to the sender.
The information is intended only for the use of the intended recipient. If
you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or the taking of any action in reliance on
the contents of the information is strictly prohibited. Any unauthorized
interception of this transmission is illegal under the law. If you have
received this transmission in error, please promptly notify the sender by
reply e-mail, and then destroy all copies of the transmission."
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.