Y2K compliant versions - again -Reply

[Lindley HILL]

It is Monday morning here, and perhaps my brain hasn't kicked in yet - but - if pre-7.10G versions were developed with an 'unsafe' operating system, aren't you effectively saying that those versions aren't to be relied on? And since 7.10G is not 'safe' pre or post 2000 at this point in time, where does it leave us?

By the way - any indication as to when 7.10G1 is going to be available in Oz. Support simply dismiss the question by saying they have no idea, because it has to wait until a CD can be cut. I would hope that is not the cause of the delay, since we're quite keen to get a working version we can use to continue our Y2K work with.

Lindley HIll
NSW Health Department
Sydney Australia

>>> "Deskin, Bob" <Bob.Deskin@Cognos.COM> 29/August/1998 01:29am >>>
Yes 7.10F2 is compliant. The Year 2000 Alert clearly states that
versions prior to 7.10G were built and tested on OpenVMS 6.1 which is
not year 2000 safe. 7.10G was built on OpenVMS 6.2 which is Year 2000
safe according to Digital (Compaq). Also development support (i.e. bug
fixes) on versions prior to 7.10G is no longer available. As for the
bugs reported in 7.10G, we are preparing a rolling bug fix (7.10G1) for
those people affected.

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:  Walker Chris[SMTP:ChrisWalker@tateandlyle.com]
> Sent:  Friday, August 28, 1998 11:11 AM
> To:  'powerhouse list server'
> Subject:  Y2K compliant versions - again
> 
> According to the Cognos Web site (in July, at least), Y2K compliant
> versions
> are "7.10.F2 and later, on OpenVMS (VAX and Alpha)".
> 
> My recently-arrived copy of 7.10G comes with an ominous black-edged
> notice
> headerd "Year 2000 Alert", and containing the following paragraph in
> red:
> "To minimize potential disruption of your operations and to avoid
> additional
> upgrades over the next 12 to 18 months, we strongly recommend that you
> upgrade to Powerhouse 4GL 7.10G immediately."
> 
> What gives?  Either 7.10F2 is compliant, or it isn't.  If it is, why
> should
> I upgrade immediately?  If not, why say it is?
> 
> This advice is particularly disturbing in the light of the serious
> bugs in
> 7.10G recently reported on this list.
> 
> Chris Walker
> Tate & Lyle
> London
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> = = =
> 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.