Y2K Testing...

[David Johnston]

We are wanting to perform Y2K tests on our 'home grown' software. To
perform these tests, we want to set the AS400 system date to the half
dozen or so recommended test dates.

This is our production machine. We would be doing these tests on a
weekend so as to not interfere with production. I am concerned about
what effect, if any, switching the system date all over the place would
have on the actual operating system. I'd like to hear any do's or
don'ts from anyone who may have already done similar testing.

Thanks!

David Johnston
The Members Group

[Charles M. Wilt]

IBM has some info one this at their AS/400 service and support website.
http://as400service.rochester.ibm.com

I can't seem to find the document now, but I remember getting it at one
point.

In short, they recommend a SAVSTG before the testing and a RSTSTG after you
are done.
--
Charles Wilt
Miami Luken, Inc.
Springboro, OH. 45066
e-mail: charle...@worldnet.no.spam.att.net
--remove the .no.spam

David Johnston <dav...@psi1.psi-cu.com> wrote in article
<362BF29E...@psi1.psi-cu.com>...

[Uwe Fischer]

Hi David,

we did this with our AS (V4R1).
At first we stopped all scheduled jobs (wrkjobscde). Then we took the AS
out of our Tokenring - Network and used only Terminals for testing. After
this two steps we changed the date to 31.12.1999 - 12.55 and made a
pwrdwnsys restart(*yes).
After the Test we changed the date back, made again a pwrdwnsys and checked
the jobscheduler afterwards, we also deleted the logfiles (QHST) from the
Y2K - Test.
At last we put the AS back in our Network.
All this worked fine and without problems.

Regards

Uwe

David Johnston wrote:

> We are wanting to perform Y2K tests on our 'home grown' software. To
> perform these tests, we want to set the AS400 system date to the half

> dozen or so recommended test dates. ....

--
Uwe Fischer

RZB-Leuchten Bamberg

[George S. Lorrig]

David,

we have done it, and we had only one visible problem: the job scheduler
gets out of sync. He submits a job on schedule and sets the "next date"
to e.g. 03. January, 2000. Resetting the system clock will _not_ change
this setting, so you will have to control all schedules.

HTH,

George

In article <362BF29E...@psi1.psi-cu.com>, David Johnston wrote:
> From: David Johnston <dav...@psi1.psi-cu.com>
> Newsgroups: comp.sys.ibm.as400.misc
> Subject: Y2K Testing...
> Date: Mon, 19 Oct 1998 21:17:02 -0500

>
> We are wanting to perform Y2K tests on our 'home grown' software. To
> perform these tests, we want to set the AS400 system date to the half
> dozen or so recommended test dates.
>

[hkno...@bmi.cnchost.com]

David Johnston wrote:
>
> We are wanting to perform Y2K tests on our 'home grown' software. To
> perform these tests, we want to set the AS400 system date to the half
> dozen or so recommended test dates.
>
> This is our production machine. We would be doing these tests on a
> weekend so as to not interfere with production. I am concerned about
> what effect, if any, switching the system date all over the place would
> have on the actual operating system. I'd like to hear any do's or
> don'ts from anyone who may have already done similar testing.
>
> Thanks!
>
> David Johnston
> The Members Group

Have you guys looked at a date simulator program like simdate or
anydate.

These will send a date other than the system date to the code executing
th etest programs.

But if you have to roll the system dates, I did roll the dates 10 times
in my tests with no ill effects...

[Orangtang]

Before planning on changing the system date, take a look at whetheryour
application uses the system date or job date to get the current date. If it's
job date, which in our case it was, we just changed the job date at signon and
the job date on the JOBD and simulated a system date change. We were fortunate
though to have another AS/400 that we could use to change the system date..but
this was to test the machine rolling over...not so much the application...Good
Luck!. Ron