01-02-2014 11:04 AM
I'm building a tape eject script with the following assumptions:
I'm trying to build a cron script to eject media. I'm having a problem with the vmchange command.
Without the flag, the command seems to work, UShortly afterwards, (30min as per documentation for -multi_eject), the tapes are moved back into the library. I want to avoid this behavior. I can't assume the operator will remove the tapes imediately. I just want them to open the library sometime during their shift and put the tapes they see in a box.
Is there anyway to lengthen the 30 minute timeout, or simply remove it altogether?
Yes, I read (yet possibly skimmed) the following:
Solved! Go to Solution.
01-02-2014 03:53 PM
From a command stand point there would really be no way to modify the 30 mins. It would be best to have the operator available during a time frame in which they can do it.
Maybe you could have cron email, or sms, the operator just after the vmchange is run to alert of the 30 min window?
01-02-2014 03:53 PM
From a command stand point there would really be no way to modify the 30 mins. It would be best to have the operator available during a time frame in which they can do it.
Maybe you could have cron email, or sms, the operator just after the vmchange is run to alert of the 30 min window?
01-03-2014 06:56 AM
That is too bad. The email alerting is a good idea.
01-03-2014 01:34 PM
This CAN be done. Just add this setting to your vm.conf:
ROBOT_MULTIPLE_EJECT_TIMEOUT = <seconds>
This was introduced in 7.1 but darned if I can find anything in SymWISE describing it!
01-03-2014 02:45 PM
Ahh, nice one Chris - I started to comment on this yesterday, but didn;t post in the end because I had a feeling there was a way to do it that I couldn't remember, and like yourself, couldn't find a TN.