I had a problem with IPLing I think a year behind the current date. This
was running under VM. VM was IPL'd with the wrong date, passing the date
along to each guest. We had 5 DOS guests, one MVS guest, and one VS1 guest
at the time. This was our first conversion of one of the DOS guests to MVS.
I don't think there were any problems while running a year back, but
something led me to check the date, and I discovered we had the wrong one.
We shut everything down, and reIPL'd VM with the correct date, and brought
everything back up. The only problem after coming back up was that anyone
who had logged on TSO while the date was 1 year behind couldn't log on.
That was me, and a few of the programmers and the operator.
This led to my getting my 2nd TSO id, which I wanted in the beginning, but a
girl who worked there for a while didn't want anyone to have 2 TSO ids. It
so happened that she wasn't home, so I kind of sat there and couldn't even
log on for about an hour, until she finally got home and called me. Then I
logged on with her password and ID and reset my own ID. Needless to say, it
didn't take much convincing to get a 2nd TSO id after that.
Eric Bielefeld
Sr. z/OS Systems Programmer
Milwaukee, Wisconsin
414-475-7434
----- Original Message -----
From: "Ed Gould" <[EMAIL PROTECTED]>
I wish the person this had happened to would pipe up, but to set the
record more precisely because of a bad date RACF (This is hear say) did
something to the (RACF) database that essentially rendered the system not
operatrional. Just by IPLing (again) with the correct date was too late
as the RACF database unusable. I do not know if they had backups or any
specifics. I heard they were down for a day or so. Luckily this was a
weekend.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
