robtest worked (i believe it calls acstest for an acs robot). I was
able to move media in and out of drives etc. What failed was vmupdate
with a communications error. I'll talk to the mainframe people today
and see if we can come up with a test plan that doesn't involve sunday
morning at 4AM so that I can try the debug logs etc.

On 8/29/05, ida3248b AT post.cybercity DOT dk <ida3248b AT post.cybercity DOT 
dk> wrote:
> Hello Charles
> 
> I would create the volmgr/debug/daemon directory, put verbose=99 in vm.conf
> and then restart the media daemons.
> 
> What happens if you run acstest -r <libstation> by hand ?
> 
> Also check the syslog/messages file if you are on UNIX
> 
> Regards
> Michael
> 
> 
> On Sun, 28 Aug 2005 06:47:13 -0500, Charles Ballowe wrote
> > In the process of testing an upgrade of LibStation, I had problems
> > with vmupdate - it came back with something similar to "robotic
> > hardware or communication error (225)" (the exact error has scrolled
> > off my screen since that point). Every other piece of functionality
> > seemed to work fine, but not that one. Any thoughts as to what might
> > be the problem? Any further information that I could provide to
> > someone? (Unfortunately, the LibStation + HSC upgrade requires an IPL
> > on the mainframe so my only shot for testing with them is 4AM sunday
> > - with 2 weeks notice given to the users so I'd like some ideas that
> > give a reasonable expectation of success before trying again.)
> >
> > Thanks,
> > -Charlie
> >
> > _______________________________________________
> > Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> 
> --
> Cybercity Webhosting (http://www.cybercity.dk)
> 
>