year 2000 compliance

[Deskin, Bob]

For those who can't get to the web site, here's the current Cognos Year
2000 Position Statement.

COGNOS
YEAR 2000 POSITION STATEMENT 

1.  Cognos supplies software tools ("Cognos Software") that its
end-users and third party partners ("Customers") use to develop
applications or analyze data.  The Cognos Software listed below is "Year
2000 Compliant" meaning that there are no date issues that will impair
the reporting of data or the proper functioning of an application run
before, during, or after the year 2000, including February 29, 2000, and
there is no year that by its occurrence that will cause the software to
cease functioning. This does not apply to:

(a) non-Year 2000 Compliance arising from the design of a particular
application built using Cognos Software or its underlying operating
system, file system, database or hardware,

(b) non-Year 2000 Compliance caused, present or inherent in the data,
database or native file system that the Cognos Software accesses,
including, but not limited to, dates or date formats that are not
century aware, and

(c) non-Year 2000 Compliance that cannot be demonstrated to occur in
another copy of the same Cognos Software.

2. Customer must notify Cognos promptly of any non-Year 2000 Compliance
and provide Cognos with a reasonable opportunity to remedy any
non-compliance, and assistance in identifying and remedying any
non-compliance, including: providing hard copy documentation of
problems, remote dial-in access, additional computer runs to duplicate
the non-compliance and allowing access to data files, listings and
console logs. 

3.  Cognos reserves the right to implement remedies to non-compliance in
currently supported versions of Software only.  This may require
Customers using Software that is not currently supported by Cognos to
upgrade to a currently supported version.

4. The Cognos Software to which this statement applies appears below:

Business Intelligence Software 

PowerPlay -  Version 4.0 and later
Impromptu -  Version 3.5 and later
Scenario -  all versions
4Thought -  all versions

Application Development Software

PowerHouse Series 6
· 6.07.E and later, on AS/400 (CISC and RISC)

PowerHouse Series 7
· 7.10.F2 and later, on OpenVMS (VAX and Alpha)
· 7.29.C8 and later, on MPE/iX
· 7.33.D3 and later, on designated UNIX platforms
· 7.33.E2 and later, on designated UNIX platforms 

PowerHouse Series 8
· 8.00.C1 and later, on OpenVMS (VAX and Alpha)
· 8.01.C1 and later, on designated Windows NT platforms
· 8.03.C1 and later, on designated UNIX platforms
· 8.09.C and later, on MPE/iX 

Axiant 2.02 and later

PowerHouse Client 2.1C and later

28/4/98

Bob Deskin              
Senior Product Advisor  bob.deskin@cognos.com
Cognos Inc.             (613) 738-1338 ext 4205 FAX: (613) 228-3149
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA


> ----------
> From: 	Deskin, Bob[SMTP:Bob.Deskin@cognos.com]
> Sent: 	Thursday, May 28, 1998 6:56 AM
> To: 	'PH User Group'
> Subject: 	RE: year 2000 compliance
> 
> Yes. On OpenVMS, prior to version 7.10.F2 (where we fixed the bug),
> PowerHouse returned an incorrect system date when running after Feb
> 28,
> 2000 if you had a default century of 19. This was fixed in 7.10.F2 and
> up and that's what we're certifying. A complete list of certified
> versions is available on our web site at www.cognos.com.
> 
> Bob Deskin              
> Senior Product Advisor  bob.deskin@cognos.com
> Cognos Inc.             (613) 738-1338 ext 4205 FAX: (613) 228-3149
> 3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA
> 
> 
> > ----------
> > From: 	Clark, Andrew[SMTP:andrew.clark@acco-uk.co.uk]
> > Sent: 	May 28, 1998 4:16 AM
> > To: 	'PH User Group'
> > Subject: 	year 2000 compliance
> > 
> > Good morning all,
> > 
> > I have recently subscribed to this service, and over the last two
> days
> > I
> > have seen a number of messages pertaining to PH and year 2000
> > compliance.  All the versions quoted as being compliant (or with the
> > y2k
> > enhancements) appear to be 7.10G +.  We currently use version
> 7.10.E6
> > is
> > this year 2000 compliant - are there any known millennium issues
> with
> > this release?
> > 
> > Cheers,
> > 
> > Andrew Clark
> > ACCO UK LTD
> > (IT Development)
> > 
> > Tel:	01296 397444 ext:4075
> > Fax:	01296 311018
> > Email:	Andrew.Clark@ACCO-UK.co.uk
> > <mailto:Andrew.Clark@ACCO-UK.co.uk> 
> > 
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> > = = =
> > 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.