Roger, I am aware of this problem. The only way I have been able to do this is with a KSH script that does a dsmadmc command in the backround and do a sleep for the proper amount of time or an elaborate script to process the output of the q mount after issuing a dismount against the volume and waiting until it is complete. What I have not not tried is to see if you used a dismount command after your commit with a commit following it and then the update command. It may be just enough to put the volume in a dismounting status to free the lock for update.
By the way, what is your MOUNTRETENTION for the device class? Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -----Original Message----- From: Roger Deschner [mailto:[EMAIL PROTECTED]] Sent: Sunday, May 19, 2002 1:31 AM To: [EMAIL PROTECTED] Subject: Script timing issue with MOVE DATA WAIT=YES This is a tsm script: (AIX 4.2.1.9) MOVE DATA $1 WAIT=YES COMMIT UPDATE LIBVOL ATLP3000 $1 STATUS=PRIVATE The idea is, when moving data off of tapes that I suspect have media problems, to avoid having the tape become an available scratch tape and get reused. MOVE DATA can take a long time, and I might not see when it completes. I might not even be awake. The problem is that I get the following error message: ANR8442E UPDATE LIBVOLUME: Volume CPM642 in library ATLP3000 is currently in use. The tape is still mounted according to QUERY MOUNT, because it is rewinding, unloading, and being put away in its slot by my robotic friend inside the library. Either: 1. There is some kind of SLEEP command for scripts that I am overlooking. 2. There is a bug in MOVE DATA WAIT=YES in that it does not wait for the tape to rewind and unload and get put away by the robot. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
