Re: Y2K testing

[Glenn Ericson <Glenn-Ericson@xxxxxxx>]

Chuck you got my vote here.
Setting the system date forward should be reserved for final  full systems
testing .

SimDate is a good product and there are others depending on your environment.

 
Glenn
___________________________________________________
Glenn Ericson,          Phoenix Consulting                      
P O Box 701164   East Elmhurst NY 11370-3164 USA                            
Phone 718 898 9805       Fax 718 446 1150
AS/400 & Year 2000- - Solutions Specialists
 © 1998 copyright,  all rights reserved
____________________________________________________


At 11:52 AM 7/14/98 -0400, Chuck Lewis  wrote:
>Use SimDate or SOMETHING... I REALLY don't think that you want to change
the system
>date... Unless you want to do a FULL reload of the development box...
>
>IBM has finally come out with info on this and they more or less straddle
the fence
>(although my feeling is they still lean against doing this....)
>
>I can't find the URL that I base the above comments on, but try this one
for info:
>
> http://www.softmall.ibm.com/as400/year2000/rldss/cdttime.html
>
>Chuck
>
>
>
>Lisa Abney wrote:
>
>> We're just now in the process of moving everything from our production
box to a
>> development box for Y2K testing.  We, too, were concerned about
licenses, but
>> found that vendors (including SSA!) were most co-operative in giving us a
>> temporary license on the development box.  We are using a third party
product
>> with 4.0.5, rather than 4.0.5CD, and plan on changing the system date as a
>> final test.  We've heard everything from "What's the big deal?" to "Don't
>> change the system date even on a development box ... period!"  Anybody
who's
>> done it have an opinion?
>>
>> Sue Underwood wrote:
>>
>> > Hello all...
>> >
>> > We are looking for a way to test our Y2K converted applications
(4.05CD) by
>> > changing the system date and then performing a "real-time" systems test.
>> > We have a separate AS/400 (V3R7) for development and will not affect our
>> > production systems.  What types of problems can we expect in relation to
>> > the operating system, licenses, other products, etc.?   If you don't plan
>> > to change the system date, then how do you plan to get a 'real-time'
test?
>> > Any and all responses will be appreciated.
>> >
>> > TIA
>> >
>> > +---
>> > | This is the BPCS Users Mailing List!
>> > | To submit a new message, send your mail to BPCS-L@midrange.com.
>> > | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
>> > | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
>> > | Questions should be directed to the list owner: dasmussen@aol.com
>> > +---
>>
>> +---
>> | This is the BPCS Users Mailing List!
>> | To submit a new message, send your mail to BPCS-L@midrange.com.
>> | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
>> | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
>> | Questions should be directed to the list owner: dasmussen@aol.com
>> +---
>
>
>
>+---
>| This is the BPCS Users Mailing List!
>| To submit a new message, send your mail to BPCS-L@midrange.com.
>| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
>| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner: dasmussen@aol.com
>+---
>
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---