>Thanks Richard, I understand that but I think it's definitely a programming
>bug. Let me try to explain it a little clearer.
>I issue a move media command.
>The tape it needs is not in the library so it begins issuing the standard
>CHECKIN LIBVOLUME message. It will continue issuing this message for 60
>minutes and then timeout if I do not check the volume in within that time.
>At some time after it begins with the CHECKIN LIBVOLUME message I issue the
>checkin libvolume command with the appropriate volume.
>The server then says insert the volume bla bla bla and issue reply with this
>message number after the tape is in the library.
>Now if I'm lucky and check the volume in fast enough, the volume gets
>checked in successfully and the move media mounts the tape and continues on
>happily.
>There seems to be some kind of internal timer where the server checks the
>status of the volume. If this timer ends after I issue the checkin libvolume
>and before I issue the reply nnn, that's when I get the error message about
>the volume being checked in or checked out.
>What should happen is if the volume is being checked in/out, the server go
>back in a loop and re-check the volume status in say another minute or so.
>Not issue the message the volume is being checked in/out and fail.
>Does this make any sense?

That makes sense, Mark.
As Andy recommends, compare your Devclass MOUNTWait value against the reality.
How you perform the CHECKIn LIBVolume can be a significant factor...  Consider
doing CHECKLabel=No if your library is unchanging and you believe that checking
the volume label is superfluous: remember that a mount can take considerable
time (available time, problems with tape or drive causing mount completion
delay, etc.).

   Richard Sims, BU