y2k testing platforms
Hamilton, Allison
Allison.Hamilton@Cognos.COM
Tue, 13 Oct 1998 10:06:59 -0400
If you are running VMS 6.1 or later on your Microvax, then your PH 7.10.Fn
executables should have no problems running on your Microvax. We are doing
some Y2K testing on a MicroVax 3100 running VMS 6.2.
If you upgrade to PH 7.10.G1 then you will need VMS 6.2 or later to run
PowerHouse.
Your tests should give you a pretty good indication. There's a remote
possibility that the Microvax clock may not handle Feb 29, 2000 (if it's an
antique!), but I doubt it has a problem. You can easily check that it is
handled correctly before doing any other testing.
The architectural differences between machines should not be significant if
you are running an appropriate version of VMS.
Allison Hamilton
> ----------
> From: Pablo Grim[SMTP:grim@gorge.net]
> Sent: Monday, October 12, 1998 5:46 PM
> To: powerh-l@lists.swau.edu
> Subject: y2k testing platforms
>
> Hello,
>
> 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.
>
> 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.
>
> 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.
>
> 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?).
>
> tx
>
> p
>
>
> ps My clients are also looking into renting an alpha but that would be a
> few weeks down the road and I need to get going.
>
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> 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.