Y2K testing

[Richard Kessler]

Wanda, 
Am curious what sort of problems you could have that would be unexpected
!?!
While I agree with everyone here that actually having a system where the
date can be pushed ahead to past 2000 is a very good idea,  I see that as
testing the compatability of the system hardware and operating system
with Y2K, NOT testing the PowerHouse code suitability. 

Am also questioning Bob Deskins earlier statement in the same manner in
that :
I should think that if you rework your powerhouse code (presumably under
8.1x)
and unload and reload the data with addcentury so that the 8 digit dates
contain 8 digits (19981222) then it does not matter for testing - at least
the powerhouse coding and powerhouse interface with the operating
system aspect - whether the century used is 19 or 20.

Am I missing something by thinking that the powerhouse coding Y2k
problem is separate from the hardware/operating system problem, or just 
overreacting to everyone's good idea to also test (the system) by
pushing the date ahead ??

Richard Kessler
71051.1106@compusereve.com

Message text written by "Ravenscroft, Wanda L"
>
If it's something your company can do, I would do it.  I work on a VMS
system and we have a development system set up whereby we can change the
date to a year 2000 date and it has been of great value to us.  We've found
and resolved alot of problems that we had not expected we would have.

Wanda Ravenscroft
Energizer
VMS 6.1, Powerhouse 7.10F1
<

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.