POWERHOUSE

[Deskin, Bob]

PowerHouse 7.10.G has all of the Year 2000 Enhancements. It's release is
imminent (unless we find a show stopper, in the next few weeks).

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: 	Arthur Kogan[SMTP:akogan@westpac.com.au]
> Sent: 	May 26, 1998 7:35 PM
> To: 	Conley, Steve
> Cc: 	'Power'
> Subject: 	Re: POWERHOUSE
> 
> Steve,
> 
> you are right to say that PH710F4 gives you Y2K compliance, however it
> does not
> provide the new Y2K features. I believe that for VMS at least some of
> these
> have been rolled into PH710G, which should be available "pretty
> soon"... This
> release has the value of still being version 7 (not 8) and still
> retains all the
> VMS specific features.
> 
> Conley, Steve wrote:
> 
> > I have been holding back but in light of recent comments I thought I
> would
> > add my own.  I have also been working with PH on the VAX since
> release
> > 5.xx(7+ years).  I have been through many upgrades and have worked
> on multi
> > platforms using COGNOS.  We are currently upgrading from 6.10.e1 to
> 7.10.f4
> > in order to become Y2K compliant.  Like many other businesses we
> evaluated
> > if we should go to 7.10.? or take the RISK and go for 8.x release.
> It was
> > my recommendation that we stay with the release that would get us
> into
> > compliance at the same time exposing us to as little risk as
> possible with
> > the upgrade.  I made this decision based on COGNOS's record with
> PAST base
> > releases.  This is not a bash as much as it is reality.  There are
> not many
> > BASE releases of anything that go in without startup problems and if
> they do
> > the saying goes "that it could have been released sooner".  I always
> > evaluate what does the new release provide vs staying with the
> release that
> > is current and in compliance.  I have made recommendations to
> clients to go
> > to base releases simply because they had more functionality going to
> the new
> > release (such as 6.xx to 7.xx was a developers release) than they
> did
> > staying where they were and the risk (new system vs a large already
> in
> > production application) was just an assumed risk.  Like any new
> based
> > product coming out you would like it to be clean but the reality is
> it will
> > not be.  This does not change my position on COGNOS or it's product
> I just
> > look at it a little more objectively having been through the
> trenches
> > before.
> >
> > Thanks Steve Conley
> > PH Consultant
> >
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> = = = =
> > 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.