DAYS function not consistent
Maloney, Charlie
Charlie.Maloney@Cognos.com
Mon, 29 Jan 2001 14:24:54 -0500
Here are some previous snips from the list regarding
HP3000 SYSDATE issues. They all seem to point to the TZ
variable...
<snip>
-----Original Message-----
From: Hamilton, Allison [mailto:Allison.Hamilton@Cognos.COM]
Sent: Tuesday, October 03, 2000 2:29 PM
To: 'Brown, Doug'; 'Powerh-l@sphere.swau.edu'
Subject: RE: Sysdate problem in Quiz
FYI From one of our developers "We reworked the MPE/iX specific SYSDATE
logic between versions 819C4 and 819C5 so that we no longer use the HP C
library routines that introduced this problem. Users no longer need to set
the TZ variable in order to have PowerHouse report the correct date."
-----Original Message-----
From: Brown, Doug [mailto:DBrown@alliedcarpets.com]
Sent: Tuesday, October 03, 2000 4:11 AM
To: 'Powerh-l@sphere.swau.edu'
Subject: Re: Sysdate problem in Quiz
Hi List
We had the same problem with the date in Quiz a few weeks back. One of my
colleagues contacted COGNOS in Bracknell, UK and they gave us the following
info:
For Info - In case you have any overnight jobs that use SYSDATE
SYSDATE now returns the correct date between midnight and 05:00 am
Previously it returned the previous days date.
Explanation
To overcome an HP millennium bug Cognos had to read the date directly from
the Hardware clock rather than via intrinsic's. This clock runs on New York
time.
This bug only affects SYSDATE ; SYSTIME has always been ok.
The fix was to add a line in the SETPOWERHOUSE UDC to set the TZ ( Time
Zone) systems variable.
Somebody may need to remember this for the next PowerHouse upgrade.
Regards
Douglas Brown
work: +44 (0)1689 89-5105
mobile: +44 (0)7710 71-6147
fax/voicemail: +44 (0)870 168-3769
web-mail: Mailto:dgb@fsmail.net
<snip>
<snip>
-----Original Message-----
From: Brown, Doug [mailto:DBrown@alliedcarpets.com]
Sent: Tuesday, October 03, 2000 4:11 AM
To: 'Powerh-l@sphere.swau.edu'
Subject: Re: Sysdate problem in Quiz
Hi List
We had the same problem with the date in Quiz a few weeks back. One of my
colleagues contacted COGNOS in Bracknell, UK and they gave us the following
info:
For Info - In case you have any overnight jobs that use SYSDATE
SYSDATE now returns the correct date between midnight and 05:00 am
Previously it returned the previous days date.
Explanation
To overcome an HP millennium bug Cognos had to read the date directly from
the Hardware clock rather than via intrinsic's. This clock runs on New York
time.
This bug only affects SYSDATE ; SYSTIME has always been ok.
The fix was to add a line in the SETPOWERHOUSE UDC to set the TZ ( Time
Zone) systems variable.
Somebody may need to remember this for the next PowerHouse upgrade.
Regards
Douglas Brown
work: +44 (0)1689 89-5105
mobile: +44 (0)7710 71-6147
fax/voicemail: +44 (0)870 168-3769
web-mail: Mailto:dgb@fsmail.net
<snip>
<snip>
-----Original Message-----
From: bert.dn@arma.nl [mailto:bert.dn@arma.nl]
Sent: Wednesday, May 12, 1999 5:18 AM
To: 'Noack, Andreas M.'
Cc: 'POWERH-L@lists.swau.edu'
Subject: RE: Y2K test fails
Have a look at document 73072 in the Cognos Supported Area or just look
down here.
Description:
PowerHouse returns wrong date for SYSDATE
Solution:
There's a document available as part number 20625 and should be ordered
when requesting PH729C8 or higher. As these questions are specific to
MPE/iX operating systems, please be sure to check HP's web page at:
http://jazz.external.hp.com/year2000/index.html
The PowerHouse 729C8 (and up) century 2000 data conversion features were
achieved by reading the hardware clock instead of using the MPE/iX
intrinsic CALENDAR. Clients using this feature must ensure that the
hardware clock is set correctly. The underlying SYSDATE software is
sensitive to the value in the environment variable, TZ, which refers to
time zone. EST5EDT is the default. On the other hand, SYSTIME is based on
the software clock which is not sensitive to the value in the environment
variable, TZ. Therefore, it is imperative that the software clock and the
hardware clock be synchronized to the second and if you are not in the
Eastern Time Zone that the right TZ variable be used.
The TZ strings can used by the time and date library functions for
adjustment to specific time zones. Refer to the description of the ctime
function in chapter 3 of HP/XL C Library Reference Manual for details. The
first line of each entry contains the time zone name followed by the
Daylight Savings Time zone name, if appropriate. The next few lines contain
the geographic locations associated with this time zone. The last line
contains the TZ environment variable string that corresponds to this time
zone. These can also be found in the file
TZTAB.LIB.SYS.
-----Oorspronkelijk bericht-----
Van: Noack, Andreas M. [SMTP:Andreas.Noack@BetzDearborn.com]
Verzonden: woensdag 12 mei 1999 9:43
Aan: 'POWERH-L@lists.swau.edu'
Onderwerp: Y2K test fails
Hi all,
though we just opened a call with Cognos maybe the list can help, as it is
very urgent.
We set our test system (HP3000-Allbase-PH819) to the 31st of Dec 1999 today
to perform testing. Now obviously the function sydate returns still
12/05/1999. Anybody an idea where this is set?
Thank you very much in advance for help.
Kind regards
Andreas Noack
Hercules BetzDearborn
Development Group Europe
The opinions expressed above are my very own. Due to this fact they may
change anytime without further notice.
<snip>
<snip>
-----Original Message-----
From: Shawn Gordon [mailto:Shawn_Gordon@Notes.FH.Com]
Sent: Monday, February 08, 1999 9:33 AM
To: mao@krifapost.dk
Cc: powerh-l@lists.swau.edu
Subject: Re:
Sysdate is using the TZ variable to offset the date, but doesn't use it on
the time. The TZ var defaults to eastern time, so you should set it
correctly for wherever you are located in the world. The TZTAB file in the
SYS account shows all the different values.
shawn
mao@krifapost.dk on 02/08/99 04:16:27 AM
To: powerh-l@lists.swau.edu
cc: (bcc: Shawn Gordon/IS/FHM/FHS)
Subject:
Hi
We are running PH 8.19 C3 on HP3000. There seems to be a problem
with sysdate in PH. If we stream a job ex. today the 8 feb. 1999 to start
at 2.00 AM, sysdate will still be the 8. feb. 1999 at 2.00 AM!
Systime is ok but sysdate doesn, t change at midnight. Does anybody know
of the problem?
MIkaelOlesen/dkf/Denmark
<snip>
-----Original Message-----
From: Leonard_Berkowitz@harvardpilgrim.org
[mailto:Leonard_Berkowitz@harvardpilgrim.org]
Sent: Monday, January 29, 2001 2:02 PM
To: powerh-l@sphere.swau.edu
Subject: DAYS function not consistent
The DAYS function returns 36,919 on all of our systems, except one, where it
returns 36,920.
The sysdate is the same 01-29-2001 on all 14 machines. The version is
8.19.c3 on
all machines.
Any ideas?
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax: 617-509-3737
pager: 781-226-2431
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.