Y2K Clarification

Shah, Roshan (Windsor, HQ) shahro01@unisourcelink.com
Fri, 12 Mar 1999 13:01:30 -0500 

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------ =_NextPart_001_01BE6CB3.8557C8D0
Content-Type: text/plain;
	charset="iso-8859-1"

Adding further to this....

Can someone say that whether Powerhouse 7.29C8 ( on HP3000 ) can be
considered a Y2K Compliant in real sense ?? ( Can Companies have a Legal
Y2K Protection from Cognos Standpoint on this version ) ?

What are the chances of Companies on 7.29C8 surviving Y2K ( if Date
Expansion is done ) ?
Is it recommended to go on 8.19 ?

Roshan
"I speak for myself"



> ----------
> From: 	Shawn Gordon[SMTP:Shawn_Gordon@Notes.FH.Com]
> Sent: 	Friday, March 12, 1999 11:25 AM
> To: 	Deskin, Bob
> Cc: 	'Gilles Belliveau'; PowerHouse Listserv
> Subject: 	RE: Y2K Clarification
> 
> 
> 
> The major problem with this behaviour is that it will not correctly
> manage
> dates that do not contain the century.  A perfectly correct method of
> Y2K
> remediation is to not expand the dates, but to use logic to manage the
> change over (not difficult).  On the HP 3000 there are date intrinsics
> that
> are supplied to do various things like format dates, convert dates
> between
> formats, perform date math, etc.   They will all properly work with
> either
> 6 or 8 digit dates across the century where the pivot year can be
> specified
> on a per call basis, or default to the system defined pivot year that
> is a
> variable.
> 
> As a 4GL, I would have expected PowerHouse to have dramatically
> superior
> date handling ability, especially in the version 8 release (which was
> the
> only reason we extended support for another year).  I've been
> extremely
> disappointed with what was supplied, and it exhibits a fundemantal
> lack of
> understanding of how to address Y2K issues, or lack of interest in
> doing
> dates "right".
> 
> 
> 
> 
> 
> 
> "Deskin, Bob" <Bob.Deskin@Cognos.COM> on 03/12/99 08:17:52 AM
> 
> To:   'Gilles Belliveau' <belliveg@nbnet.nb.ca>, PowerHouse Listserv
>       <powerh-l@lists.swau.edu>
> cc:    (bcc: Shawn Gordon/IS/FHM/FHS)
> Subject:  RE: Y2K Clarification
> 
> 
> 
> 
> Yes that is correct. The full story is available in the article on our
> web
> site at
> http://www.cognos.com/suppserv/custsupp/power2000/phcentury.html
> 
> If you have CENTURY EXCLUDED then PowerHouse "assumes" that century
> excluded
> dates are within the DEFAULT CENTURY, so simply changing the default
> century
> may not give you the correct data. Also, the DATE and LASTDAY
> functions
> return century excluded dates that must be within the default century.
> This
> isn't a problem for LASTDAY, but it means that any DATE function must
> deal
> with a number of days since Dec 31, 1899 that falls in the default
> century.
> This is correct behavior for PowerHouse. I believe that I posted the
> long
> explanation a while ago. In order to deal with dates in multiple
> centuries,
> a system should be using CENTURY INCLUDED. There are other ways to do
> this
> through coding, but they are usually worse.
> 
> Bob Deskin
> Senior Product Advisor, Application Development Tools, Cognos Inc.
> bob.deskin@cognos.com (613) 738-1338 ext 4205 FAX: (613) 228-3149
> 3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA
> 
> 
> -----Original Message-----
> From: Gilles Belliveau [mailto:belliveg@nbnet.nb.ca]
> Sent: Friday, March 12, 1999 10:01 AM
> To: PowerHouse Listserv
> Subject: Y2K Clarification
> 
> 
> Hello,
> 
> I would like it if someone could confirm something for me.
> 
> It is my understanding from what I have read on the Cognos web site
> that
> if we have CENTURY EXCLUDED and DEFAULT CENTURY 19 in the dictionary,
> then the DATE function will not be able to return a value of
> 2000/02/29
> or any date after December 31, 1999 for that matter.
> 
> Is this correct or is there a way the DATE function can still give us
> February 29, 2000 without causing a data conversion error?
> (I was not the one who did the Y2K conversion, but I am now the one
> who
> is testing and debuging it because the person who did the conversion
> is
> currently on maternity leave, so my knowledge of Y2K issues is
> limited)
> 
> Thanks,
> Gilles Belliveau
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> = = =
> Subscribe: "subscribe powerh-l" in message body to
> majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to
> majordomo@lists.swau.edu
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> 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
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> 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
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> This list is closed, thus to post to the list, you must be a
> subscriber.
> 

------ =_NextPart_001_01BE6CB3.8557C8D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">



RE: Y2K Clarification




Adding further to =
this....




Can someone say that =
whether Powerhouse 7.29C8 ( on HP3000 ) can be considered a Y2K =
Compliant in real sense ?? ( Can Companies have a Legal Y2K Protection =
from Cognos Standpoint on this version ) ?



What are the chances =
of Companies on 7.29C8 surviving Y2K ( if Date Expansion is done ) =
?

Is it recommended =
to go on 8.19 ?




Roshan

"I speak for =
myself"








------ =_NextPart_001_01BE6CB3.8557C8D0--
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.