Hi,
I have specified the tape deletion exit, and ADSM has worked fine with CA-1
for years at our site... until now.  Has anyone seen a bug with that tape
deletion exit   where in some cases it doesn't work?
I did briefly upgrade to 3.1.2.20, but had to back off to 3.1.2.14.   Would
upgrading, then going back, some how cause a problem with the tape deletion
exit?
Thanks,
Julie




Andreas Buser <Andreas.Buser AT BASLER DOT CH> on 06/04/99 01:55:44 AM

Please respond to Andreas.Buser AT Basler DOT ch

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





Hi Julie,

you have to implement the TAPEDELETION-Exit.

In the ANRSREV.OPTIONS File insert the follwing line:
DELETIONEXIT    xxxxxx (Where xxx is the name of the TAPEVOL-EXIT)

In fact it is the same exit that is used to DFHSM.

The only thing is that you have to be aware of, is that the ADSM Server
must be at Level 3.1.2.20 to use the 31-Bit version of this exit.

If not make with Rmode(24).


Julie Phinney wrote:
>
> I'm running ADSM 3.1.2.14 on MVS.  I've noticed we have a bunch of tapes
> out there now with the ADSM dataset name on them (hlq.BFS)  with a zero
> block count, and I was asked to get rid of them.   I did  a Q VOL on a
> handful of them   and ADSM tells me we have no such volume.   It makes me
> think  ADSM used them, expired them, and forgot to tell CA-1 to return
them
> to Scratch.
> Has anyone else seen this happen?
> Thanks,
> Julie

--
_________________________________________________
_________________________________________________

Kind Regards
Andreas Buser

Tel: ++41 61 285 73 21  Fax: ++41 61 285 70 98

Email: Andreas.Buser AT Basler DOT ch

Address:
Basler Versicherungsgesellschaft
Andreas Buser
Abt. Informatik
Aeschengraben 21
4002 Basel
Switzerland