Thank you!  I'll do it.
Julie




bcolwell AT DRAPER DOT COM on 02/06/98 12:51:00 PM

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Julie Phinney/Green Bay/Humana)
Subject:  Re: ADSM-MVS and CA-1 disaster recovery




I can't help with your tape problems, but if you put "noauditstorage" in
the server options file the audit license will run very quickly with little
impact.
Bill Colwell
The Charles Stark Draper Laboratory
Cambridge Ma.
_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: ADSM-MVS and CA-1 disaster recovery
02-06-1998 11:07 AM
We did a disaster recovery test this week at the hotsite for Year 2000
testing.  The first day we brought the system up with the date Feb 2,1998.
The next day we did the1999 rollover to 2000 testing, then did some leap
year (Feb29,2000) testing.
When we brought the system up initially, with the Feb,1998 date, ADSM had a
few errors in the started task log when it tried to expire a couple tapes
in the offsite tape pool (I had marked the onsite pool destroyed).  The
errors were the same for each tape it tried to expire:  TMSTMSTV expire
ignored, not a TMS volume.   I didn't notice those errors and did some
successful restores.
 After we were into the Y2K testing, I issued the command EXPIRE INVENTORY
just to see what it would do, and it started spitting out many TMSTMSTV (as
above) msgs to the syslog while it was trying to expire tapes in my offsite
tapepool, and the task had to be cancelled.   When I tried to bring up the
ADSM started task after that, each time, it did that.  I was unable to
cancel the expiration process.   I checked CA-1 TMS and the status of each
tape in my offsite pool, whether or not it should have been expired, was
*** DELETE STATUS***.  The CPGM and LPGM both said PRE-TMS
It was as if CA-1 didnt know the tapes belonged to ADSM, and since I had a
few of these same errors when we brought the system up the first time,
BEFORE we changed the date to Y2K, I'm guessing ALL my ADSM offsite tapes
were in *** DELETE STATUS*** from the beginning of the entire disaster
recovery.   I have a couple questions:
1. Has anyone ever seen ADSM  (extemally managed tapes to CA-1) show up in
DELETE STATUS after CA-1 has been restored, like at a hotsite?   This didnt
cause any problems during my restores, but definitely is a problem during
expiration processing.
2. Does anyone know how to cancel a process like that?   Also, the AUDIT
LICENSE kicked off the first time I brought ADSM up, and grabbed LOTS of
CPU and WOULD NOT cancel.   I have the expint set to 0 in the
anrserv.options file.  I believe expiration only kicked off because I
kicked it off, but after cancelling the task and restarting the task, the
expiration kept kicking in, right off.   Same with that darned Audit
License.  Any way to stop those processes in an emergency situation?