IBM DS6000 - Manual (Page 324)

300 IBM System Storage DS6000 Series: Copy Services with IBM System z
24.2.2 Establish FlashCopy using DS CLI
Example 24-3 shows how to create the FlashCopy relationship between the B and the C
volumes using the DS CLI command
mkflash .
Example 24-3 Create FlashCopy between B and C volumes using DS CLI
dscli mkflash -record -persist -nocp -seqnum 0000 6500:6502 -cfg
$DSCLI/profile/DS8300-box2.profile
The mklfash DS CLI command identifies the B and the C volumes through additional
information that is found in a configuration file, which usually contains the serial number of the
storage disk subsystems.
Example 24-4 shows an example of how this configuration file looks for commands to be run
in a DS8000 environment. In this case, it indicates that the commands have to go through the
HMC, which is identified by its corresponding IP address. For a DS6000 it also identifies the
external SMC with the necessary software stack to handle the Copy Services commands.
Example 24-4 Content of the -cfg file $DSCLI/profile/DS8300-box2.profile
hmc1: 192.168.93.14
username: Jack
password: Stor123agE
devid: IBM.2107-7573731
remotedevid: IBM.2107-7506551
For simplicity, a required user ID and password is specified in plain text. Administrators of the
storage disk subsystem have to set up a user ID and password for users who want to work
through the SMC. This information is usually hidden in an encrypted password file.
Example 24-5 shows the creation of a FlashCopy relationship. The source volume and target
volume are indicated by the LSS and device number pair
6500:6502 . It also indicates the start
change recording attribute, which actually implies the persistent attribute. It also indicates the
nocopy option. An optional FlashCopy sequence number makes it simpler to refer to this
FlashCopy relationship in further commands. Note that you may either put the configuration
information in the DS CLI command as Example 24-4 shows, or use the configuration file as
explained previously.
Example 24-5 Create FlashCopy between B and C with DSCLI and explicit device specifications
dscli mkflash -record -persist -nocp -seqnum 0000 6500:6502 -dev ibm.2107-7573731-remotedev
ibm.2107-7506551
As shown here in Example 24-6, an inband triggered FlashCopy would require a different DS
CLI command,
mkremoteflash .
Example 24-6 Inband FlashCopy between B and C with DS CLI
dscli mkremoteflash -dev ibm.2107-7506551 -conduit ibm.2107-7573731/00 -tgtinhibit -record
-nocp -seqnum 0000 6500:6502
The parameter -conduit is equivalent to the DEVN TSO parameter in Example 24-2 on
page 299. With it you select the primary volume at the local site to where the command is
addressed. Note that the DS CLI has to go through an SMC, whereas the TSO commands
are directly targeted to the storage disk subsystems by means of the host channel
connection.