Re: Y2K

> Subject: Re: Y2K
>
> At 03:50 PM 8/16/99 -0400, you wrote:
> >We are going to set the dates on our development box CISC 3.2 and one of our
> >production boxes RISC 4.2 to the year 2000 and beyond.  Has anyone had "any"
> >experience in doing this?  Everything  I read says at the end of the test to
> >scratch and reload.  Can we do this is in a controlled environment and not
> >do the scratch reload?  Any advice and/or help will be appreciated.
> >

I have taken a number of AS/400s to 2000 and back. Every customer who
wanted the
"quick" test I firmly recommended the full reload (but some ignored me).
I did at least
confirm that they were prepared for a full reload (Save Full System,
etc). Those that
were successful at not reloading were smaller systems, not journalling,
no package
software, little use of monitoring or utility programs. We did turn off
IBM's Service
Director, held all entries on the Job Scheduler, set all profiles to not
expire, and
did the full backup prior to going into 2000. Then we ran our testing.
Prior to the
setting the system back, we again held all entries on Job Scheduler, set
profiles again
to not expire (all of these were turned on for testing in 2000), ended
all subsystems,
changed system date, then immediately IPL'd. We were up to date with all
the Y2K ptfs
prior to starting any of this. We were ready to reload, but did manage
some without it.
One big issue we had, which I hope IBM has fixed by now, is PassThru and
SNADS between
AS/400's on different releases, in different centuries. We were testing
some AS/400s in
2000 via PassThru from systems in current century, and locked up QSNADS
subsystem on both machines. No halt, but no action either.  Had to
telnet to the other machine to reset Snads. Plan as if your going to
reload.
Jim Franz
Systematic Control, Inc
jfranz@sysctl.com

begin:vcard 
n:Franz;Jim 
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:franz99@ibm.net
x-mozilla-cpt:;0
end:vcard