Filter
Top Products
80 IBM System Storage DS6000 Series: Copy Services with IBM System z
commitflash -dev IBM.1750-13ABC2A 0001-0005
Date/Time: July 10, 2005 2:46:18 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A
CMUC00170I commitflash: FlashCopy volume pair 0001:0001 successfully committed.
CMUC00170I commitflash: FlashCopy volume pair 0005:0005 successfully committed.
lsflash -dev IBM.1750-13ABC2A -l 0000-0005
Date/Time: July 10, 2005 2:46:47 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
======================================================================================================================================
0001:0101 00 1 300 Disabled Enabled Enabled Disabled Disabled Enabled Disabled
0005:0105 00 1 300 Disabled Enabled Enabled Disabled Disabled Enabled Disabled
#--- Example 2
commitflash -dev IBM.1750-13ABC2A 0003:0103
CMUN03027E commitflash: 0003:0003: FlashCopy operation failure: action prohibited by current FlashCopy state
The following explanations apply to the cases presented in Example 9-4:
Example 1: commit the FlashCopy relationship.
This example shows the properties of the two FlashCopy relationships 0001:0101 and
0005:0105 using the lsflash command prior and after issuing the setflashrevertible
command. After the commitflash command is executed the properties of the two
FlashCopy relationships are listed again.
Example 2: error occurs when trying to commit FlashCopy relationship.
When trying to commit a FlashCopy relationship that isn’t revertible (property Revertible is
disabled) an error will be the result. The script will end after this command with return code
2 and any other commands following the one that causes the error will not be executed.
Incremental FlashCopy using resyncflash
With the resyncflash command an existing FlashCopy relationship can be incremented. To
run this command, the FlashCopy relationship must have the options Recording and
Persistent enabled.
To make sure an existing FlashCopy relationship can be incremented multiple times, it is
necessary to repeat the -record and -persist parameters with the resyncflash command.
Example 9-5 shows examples where the resyncflash command is used.
Example 9-5 resyncflash command examples
#--- Example 1
mkflash -dev IBM.1750-13ABC2A -record -persist -seqnum 01 0001:0101 0005:0105
Date/Time: July 10, 2005 5:04:48 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A
CMUC00137I mkflash: FlashCopy pair 0001:0101 successfully created.
CMUC00137I mkflash: FlashCopy pair 0005:0105 successfully created.
resyncflash -dev IBM.1750-13ABC2A -seqnum 13 0003:0103
Date/Time: July 10, 2005 5:05:18 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A
CMUC00137I mkflash: FlashCopy pair 0003:0103 successfully created.
lsflash -dev IBM.1750-13ABC2A 0000-0005
Date/Time: July 10, 2005 5:05:45 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
0001:0101 00 1 300 Disabled Enabled Enabled Disabled Disabled Disabled Enabled
0003:0103 00 3 300 Disabled Enabled Enabled Disabled Disabled Disabled Enabled
0005:0105 00 1 300 Disabled Enabled Enabled Disabled Disabled Disabled Enabled
Tip: You do not have to wait for the background copy to complete before you do the Flash-
Copy resynchronization. The resyncflash command can be used at any time.