I finally turned my attention to the 3494. I found I had to manually
eject a tape from one of the two drives. To my dismay, this did not
fix my waiting for tape problem. I have an IBM CE coming on-site
this afternoon to give the 3494 a thorough physical.
I would still like to know if anyone else has this problem and solves it.

> -----Original Message-----
> From: Richard Sims [SMTP:rbs AT BU DOT EDU]
> Sent: Monday, March 15, 1999 11:08 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: ADSM tape mount problem
>
> You're concentrating your attention on ADSM, but what about the 3494?  Run
> some 'mtlib' commands to check the status of the drives and the tapes in
> question (particularly for unexpected category code values); check the
> 3494
> control panel for Int Req and error conditions and drive availability
> settings; check the tape drive panels for their conditions (like unload
> failure).  At the 3494 control panel, look up the tape in the Library
> Manager
> database.  Do an ADSM 'show libr'.  Check the drive status from the point
> of
> view of the operating system.  I'd say that there's something amiss in the
> 3494: ADSM wants the tape to be mounted, but for some reason the Library
> Manager can't do it.
>
> The Mountwait parameter isn't all you might hope for.  ADSM tends to
> wait indefinitely for a mount during a problem condition, ostensibly
> because the mount request has not yet been accepted by the Library
> Manager for the MountWait timeout clock to start ticking.
>
>      Richard Sims, BU