Here is Richard Sims' recommendation in this situation:
- TSM may have to be told that the library is in manual mode. You cannot achieve this via UPDate LIBRary: you have to define another instance of your library under a new name, with LIBType=MANUAL. Then do UPDate DEVclass to change your 3590 device class to use the library in manual mode for the duration of the robotic outage.
-Ted
At 02:40 PM 3/18/2004 -0500, you wrote:
Any 3494 wizards out there -
Something new every minute... Our gripper is dead (there is a part circling an airport somewhere, waiting to land).
At first, we just switched the library into MANUAL mode, opened the doors, and we 2-legged robots have been responding to the mounts on the library manager console.
Then a drive also died. TSM was waiting for the mount on that drive, which cannot be satisfied, process will not cancel. The only way I know out of that is to bounce TSM, which I did.
When TSM came back up, it says the library is UNAVAILABLE.
Now the library is still doing its manual-mode thing for the other system attached to it, so I ASSUME this is because the library was not in a "normal" state when TSM came back up.
So, is there anything I can do to get TSM to talk to the library again while it is in MANUAL mode?
Thanks Wanda
