y2k testing platforms

[Chris Sharman]

>I'm preparing to run some payroll/HR Y2K tests for a client.  The
>powerhouse code has all been converted to handle y2k.  It just hasn't been
>tested with a Y2K system date.
>
>Our production systems run on DEC Alpha OVMS version 7.10 using RMS files.
>We are using Powerhouse 7.10f3.

The 7.10.G1 release is now shipping, & takes most of the work out of y2k.

>My clients have an older Microvax that I thought might be useful as a Y2k
>test machine.  Pretty simple i guess; just set the system time forward to
>post 01/01/2000 and start running critical processes.

I'd be inclined to set it close to midnight 31/12/1999 & let it roll over.
I'd also let it roll into 29/2/2000 to see what else might break.

>My concern is that the Microvax and Alpha have different CPUs and
>architecture, even though they are using the same OS.  In other words,
>there would be untested variables.   eg:  I've been told that the
>Powerhouse executables are not portable between these two machines.

Untrue: .Q%C files *are* portable between VAX & Alpha. Unless you mean the .EXE
files shipped from Cognos (which are CPU-specific) ?

>My question finally;  would this type of test be worthwhile?  Are the
>untested variables something that should be tested?  (like  QUIZ.EXE on the
>Alpha?).

Well, yes: if you find something, well & good. If you don't, you've got your
tests sorted out & they're easier to repeat.
______________________________________________________________________
Chris Sharman			Chris.Sharman@CCAgroup.co.uk
CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.