Mark Perry wrote:
----- Start Original Message -----
Sent: Fri, 28 Jul 2006 12:35:26 +0200
From: Rob van der Heij <[EMAIL PROTECTED]>
To: [email protected]
Subject: Re: Bad Linux backups
<SNIP>
I would hope that anything that prevents the flashcopy
from starting could be reported for example with a command reject upon
device end.
<SNIP>
I have not analyzed a CCW trace of the whole FLASHCOPY operation, but the z/VM
FLASHCOPY command returns immediately if the request can be queued to the
Shark. At some later point in time an error may be received by z/VM and an
asynchronous console message is issued.
This is the complication that Mike related to, in that handling such
asynchronous messages in a REXX script is complicated and not for a novice.
Once again this is practical advice, not theoretical. I have been through this,
and it was painful.
It seems to me simple enough:-)
One script that initiates the copy.
A second that is run when (or waits until) the copy _should_ have
completed, confirms that it has worked and takes appropriate action
depending on the results.
I'll leave it to the more skilled to determine _how_ to tell whether the
copy's done, is still in progress or has failed.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
