Creating remote mirror and copy paths using DS CLI

Complete this task when you create paths because they are required when creating source and target remote mirror and copy volume pair relationships.

Before you begin, ensure that you have met the following conditions:

The remote mirror and copy license key is installed and enabled to allow operations to be performed. If you are using a Model 2105 ESS as part of the configuration, ensure that you have the PPRC Version 2 license enabled.
The I/O ports are configured for paths between source and target LSSs.
The I/O ports that will be used for paths are available and identified.
The worldwide node name (WWNN) of the storage unit is identified because it is a required parameter for this task.

Create paths so that the logical subsystems (LSSs) are associated with each other. These are the paths through which data will be transferred so it essential that bandwidth for these operations be sufficient. In addition, you want to ensure that the ports used for remote mirror and copy operations are not the same ones that will be used for host I/O activity.

Perform the following steps to create remote mirror and copy paths. 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 mkpprcpath command to create the fibre-channel paths for the remote mirror and copy source and target volume pairs. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables:
dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID
-remotewwnn wwnn -srclss source_LSS_ID -tgtlss target_LSS_ID
source_port_ID:target_port_ID
Notes:
1. The -remotedev parameter specifies the ID of the secondary storage unit.
2. The -remotewwnn parameter must specify the WWNN of the secondary storage unit. If you specify the WWNN of the primary storage unit, the command fails.
3. You can specify the -dev and -remotedev parameters or specify fully-qualified srclss and tgtlss parameters, but not both.
4. The shortened version of the -srclss and -tgtlss parameters are shown (value = 00) because the example uses the fully qualified -dev storage_image_ID parameter. If the fully qualified -dev parameter was not used, you must specify the fully qualified -srclss source_LSS_ID and the -tgtlss target_LSS_ID values. For example: -srclss IBM.1750-75FA120/00 -tgtlss IBM.1750-75FA120/01
5. The shortened version of the source_port_ID:target_port_ID parameter is shown (value = I1A10:I2A20), because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_immage_ID parameters. If the fully qualified -dev and -remotedev parameters were not used, you must use the fully qualified source_port_ID:target_port_ID value. For example: IBM.1750-68FA120/I1A10:IBM.1750-68FA150/I2A20.
  The fully qualified source_port_ID:target_port_ID parameter is positional on your command line. It must be placed after the -tgtlss parameter. For example:
  dscli>mkpprcpath -srclss 00 -tgtlss 00 IBM.1750-68FA120/I1A10:IBM.1750-68FA150/I2A20
Example
```
dscli>mkpprcpath -dev IBM.1750-75FA120 -remotedev IBM.1750-68FA150  
-srclss 00 -tgtlss 00 
-remotewwnn 12341234000A000F
 I1A10:I2A20
```
Issue the lspprcpath command to review the list of established remote mirror and copy paths,