× 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

Glenn,
It's both a management problem and a vendor
problem. We can only go to 7.1 because we are
using a mimix solution that doesn't support 7.2.
Manglement is dragging their hind quarters across
the prairie for 7.1 just because they might have to
take some time to really review the process.

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: Glenn Gundermann <glenn.gundermann@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/16/2015 05:37 PM
Subject: Re: TimeStamp Problem
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Bill,

Why wouldn't you go to 7.2? It's been out since May of last year, and I
presume considered very stable.
(7.1 will be 5 years old next week.)

Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144




On 16 April 2015 at 17:56, <broehmer@xxxxxxxxxxxxxxx> wrote:

We're on 6.1 hopefully moving to 7.1 before end of summer.

To answer your question....it's an old file that is more or less for
historical purposes. Not a real problem yet but we were trying
to solve a "last record" for a group problem and ran into duplicates
using SQL.
Not a show stopper but close.


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: Alan Campin <alan0307d@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/16/2015 04:49 PM
Subject: Re: TimeStamp Problem
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Depends what release you are. The more current releases have more
precision. Why are you using a timestamp for a unique value. Why not use
an
identity key?
On Apr 16, 2015 3:16 PM, <broehmer@xxxxxxxxxxxxxxx> wrote:

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.


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



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.