Yes.  Because the the EDM (external data manager) in CA1 is keyed off
creating pgm name, the tape will be 'registered' to ADSM even though
ADSM doesn't know about it.   CA1 doesn't care if data was written or
not.
EDM is a facility that basically tells CA1 to keep its hands (?) off the
tape, the application will take care of the expiration.  This is very
valuable for keeping CA1 from erroreously scratching tapes from
cancelled tasks but does lead to interesting situations like you just
described.  The same is true for other EDM applications such as DMS/OS
or HSM.  A periodic audit/compare is a good idea.
Regards.
> ----------
> From:         Jerry Lawson[SMTP:jlawson AT THEHARTFORD DOT COM]
> Sent:         Wednesday, April 30, 1997 4:28 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      MVS Tape Processing question
>
> Date:     April 30, 1997      Time:    1:30 PM
> From:     Jerry Lawson
>      The Hartford Insurance Group
>      (860) 547-2960           jlawson AT thehartford DOT com
>
> Hopefully, this is a simple question, but somehow I think it isn't.
> Here is
> the scenario...
>
> The platform is MVS with TMS exits installed.
>
> An ADSM process, such as a reclaim or migration, asks for a scratch
> mount.
> MVS and TMS get control, and start to do their thing.  Before control
> is
> returned to ADSM, a cancel request for the process that requested the
> mount
> is made, and the process terminates.
>
> What happens to the tape that was being mounted.  We seem to think
> that the
> tape is assigned to ADSM by TMS, but ADSM never actually opens it, and
> in
> fact, doesn't even know about it - the TSN doesn't show up in the DB.
> Is
> this in fact what happens?
>
>
>                                          Jerry
>