IBM DS8000 - Manual (Page 270)

248 DS8000 Series: Concepts and Architecture
Table 11-3 Converting a FlashCopy task to DS CLI
So to create the DS CLI command, simply read down the third column:
mkflash -nocp -dev IBM.2105-23953 1004:1005
In Example 11-14 the user uses the DS CLI interactive mode. They issue the mkflash
command and then use lsflash to check the success of the command.
Example 11-14 Using interactive dscli mode without profiles
sharon@aixsrv:/opt/ibm/dscli > dscli
dscli> mkflash -nocp -dev IBM.2105-23953 1004:1005
CMUC00137I mkflash: FlashCopy pair 1004:1005 successfully created.
dscli> lsflash -dev IBM.2105-23953 1004:1005
ID SrcLSS SequenceNum Timeout ActiveCopy Recoding Persistent Revertible
===============================================================================
1004:1005 10 0 120 Disabled Disabled Disabled Disabled
dscli>
You can also confirm the status of the FlashCopy by using the Web Copy Services GUI, as
shown in Figure 11-8.
Figure 11-8 FlashCopy status via the ESS 800 Web Copy Services GUI
ESS CS CLI
parameter Saved task
parameter DS CLI conversion Explanation
Tasktype FCEstablish mkflash An FCEstablish becomes a
mkflash.
Options NoBackgroundCopy -nocp To do a FlashCopy no-copy
we use the -nocp parameter.
SourceServer 2105.23953 -dev IBM.2105-23953 The format of the serial
number changes. you must
use the exact syntax.
TargetServer 2105.23953 N/A We only need to use the -dev
once, so this is redundant.
Source and Target
vols 1004 1005 1004:1005 The volume numbers don’t
change. We simply separate
them with a full colon.