Y2K testing

[Deskin, Bob]

If you haven't tested past 1999, you haven't really tested for year 2000
compliance. If you can set the machine ahead, that's best. If you can't do
that (for production reasons, for example), invest in one of the many
utilities that allow you to set the clock ahead. Check dates like Dec 31,
1999, Jan 1 2000, Feb 28, 29, Mar 1, 2000, Dec 31, 2000, Jan 1, 2000, etc.
Also, remember to check data that will represent what you'll get after 1999.
If you test your application with today's data, it may not include dates
past 1999. You want to ensure that you test the rollover and test date
combinations in both centuries. For example, if you're comparing two dates
in a record, try to have one before 2000 and one after 1999. That way you'll
ensure that your date comparisons are working.

Good luck.

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: 	John Pearce[SMTP:jpearce@rmi.net]
> Sent: 	Monday, December 21, 1998 10:54 PM
> To: 	powerh-l@lists.swau.edu
> Subject: 	Y2K testing
> 
> Seasons Greetings!
> 
> The PH apps at this site have used four digit years since 1990 (no, it
> wasn't great planning).  We will finish converting to PH8.19C in late
> January.  We've checked the PH code using the top ten problem areas listed
> in a recent support newsletter and didn't find anything.  We've also
> checked the JCL for conditional execution of QTP & Quiz and found that
> it's
> simply a case of a file existing or not existing, i.e., not date related.
> 
> What's the feeling on this list about setting the system clock ahead (or
> using a date intercept program) and testing?  Is it A) mandatory, B) nice
> to do, or C) not necessary?
> I'd really like to get input from the Cognos people even if it's just
> their
> own personal opinion and/or via private e-mail.
> 
> I made a decision a month ago and now I'm rethinking it so I'd like some
> input from the list members.
> 
> Thanks.
> 
> 
> ------------------------------------------------------------------
> John Pearce  <jpearce@rmi.net>       | Bethesda Management Company 
> Speaking for only myself             | Colorado Springs, CO  USA
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> 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.