Creating FlashCopy relationships (Global Mirror setup)

Complete this task to create FlashCopy relationships at the remote site between the Global Copy secondary volumes and the FlashCopy target volumes. This is the third step in setting up your Global Mirror environment.

The following tasks must be completed before you can initiate this step:

Ensure that the fibre-channel paths between all Global Mirror source and target pairs and between the master and subordinate storage units have been created.
Ensure that the Global Copy pairs have been created between the local storage units and the remote storage units.

The purpose of this task is to create a FlashCopy target for the Global Mirror pairs.

Perform the following steps to create FlashCopy relationships at the remote site between the Global Copy secondary volumes and the FlashCopy target volumes. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables.

Issue the mkflash command to create FlashCopy relationships at the remote site between the Global Copy secondary volumes and the FlashCopy target volumes. Enter the mkflash command at the dscli command prompt with the following parameters and variables:
```
dscli>mkflash -dev storage_image_ID -tgtinhibit -persist -record -nocp 
sourcevolumeID:targetvolumeID
```
Example
```
dscli>mkflash -dev IBM.1750-68FA150 -tgtinhibit -record 
-persist -nocp 0001:0004
```
Notes:
1. Specify the storage image ID of the secondary storage unit for the -dev storage_image_ID parameter. If the management console has an IP connection to the specified "remote async site", the command works. If the IP connection is not established, issue the mkremoteflash command with all the same parameters as displayed in the example.
2. Specify the -tgtinhibit parameter to prevent writes to the target volume.
3. Specify the -record parameter to activate the change recording function on the volume pair.
4. Specify the -persist parameter to retain the FlashCopy relationship after the background copy completes.
5. Specify the -nocp parameter to prevent creating a background copy.
A confirmation message is issued for each successful FlashCopy pair that is created.
Issue the lsflash command to check the status information for each FlashCopy relationship at the remote site. Enter the lsflash command at the dscli command prompt with the following parameters and variables:
```
dscli>lsflash -dev storage_image_ID  -l SourceVolumeID:TargetVolumeID
```
Example
```
dscli>lsflash -dev IBM.1750-68FA150  -l 0100:0100
```
Use the -l parameter to provide a more detailed report about the FlashCopy relationships.
Note: If you used the mkremoteflash command, you must enter the lsremoteflash command to perform a status check.