I have gotten the same ACCEPT DATE message on my test/demo NT machine. It
seems that ADSM thinks that the date might have been set in error if it has
been a long time since the last ADSM startup. In my case, it was a month or
two. In your case it was many months (your date in 2000). My server is fine
after typing in ACCEPT DATE at the server console (I ran my server in a
MS-DOS box that particural time).

~~~~~~~~~~~~~~~~~~~~
Joerg Pohlmann
Certified IT Specialist
Storage Systems
Telephone: 1-604-878-0295
Internal Mail: BG0/701/VAN
Internet: jpohlman AT ca.ibm DOT com



Julie Phinney <jphinney AT HUMANA DOT COM> on 99-03-11 14:19:30

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Joerg Pohlmann/CanWest/IBM)
Subject:  ANR0110E during Y2K testing





I got the following message during our most recent Y2K test.   I used the
ACCEPT DATE command, and things appeared to be
fine.

ANR0110E An unnexpected system date has been detected; the server is
disabled.
Use the ACCEPT DATE command to establish the current date as valid.


During last year's Y2K test, I don't recall this message.  I assume it's
new with server level 3. something  (we're at 3.1.2.14).

Does anyone know if I can assume things are fine?