Re: Script timing issue with MOVE DATA WAIT=YES
2002-05-19 23:17:16
Subject: |
Re: Script timing issue with MOVE DATA WAIT=YES |
From: |
"Seay, Paul" <seay_pd AT NAPTHEON DOT COM> |
Date: |
Sun, 19 May 2002 23:15:01 -0400 |
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
|
|
|