The mkpprc command
establishes a remote mirror and copy (formerly PPRC) relationship for a volume
pair.

>>-mkpprc--+-------------------------+-------------------------->
'- -dev--storage_image_ID-'
>--+-------------------------------+-- -type--+-mmir-+---------->
'- -remotedev--storage_image_ID-' '-gcp--'
>--+------------------+--+-----------+--+-------------+--------->
'- -mode--+-full-+-' '- -cascade-' '- -tgtonline-'
'-nocp-'
>--+-----------+--+------------+--+----------------+------------>
'- -tgtread-' '- -critmode-' '- -resetreserve-'
>--+--------+--+----------------+--+----------------+----------->
'- -wait-' '- -srcss--ss_ID-' '- -tgtss--ss_ID-'
>--+-SourceVolumeID:TargetVolumeID--+-------+-+----------------><
| '-. . .-' |
'-" - "------------------------------------'
Parameters
Notes: - When you specify subsystem IDs, the source and target volumes are restricted
to one LSS for the source and one LSS for the target.
- If you are using the Cisco MDS 9216 Multilayer Fabric Switch, you must
not enable the write acceleration feature. The mkpprc command might
fail if the write acceleration feature is enabled.
- -dev storage_image_ID
- (Optional). Specifies the source storage image ID, which includes manufacturer,
machine type, and serial number. This parameter is required if you do not
specify a fully qualified source volume ID.
- Example: IBM.1750-75FA120
- -remotedev storage_image_ID
- (Optional). Specifies the target storage image ID, which includes manufacturer,
machine type, and serial number. This parameter is required if
you do not specify a fully qualified target volume ID, or if the -dev parameter
is selected.
- Example: IBM.1750-68FA120
- -type mmir | gcp
- (Required). Establishes one or more remote mirror and copy volume relationships
as either Metro Mirror (Synchronous) or Global Copy (Extended Distance) relationships.
- mmir
- Metro Mirror maintains the remote mirror and copy relationship in a consistent
(synchronous) manner by returning I/O write completion status to the application
when the updates are committed to the target. This process becomes slower
as the physical distance between source and target increases.
- gcp
- Global Copy maintains the remote mirror and copy relationship in a nonsynchronous
manner. I/O write completion status is returned to the application when the
updates are committed to the source. Updates to the target volume are performed
at a later time. The original order of updates is not strictly maintained.
- -mode full | nocp
- (Optional). Specifies the initial data copy mode for the remote mirror
and copy volume relationships.
- full
- Full mode copies the entire source volume to the target volume. This is
the default when you do not specify no copy.
- nocp
- No Copy mode does not copy data from source to target volumes. This option
presumes that the volumes are already synchronized.
- -cascade
- (Optional). Enables a remote mirror and copy target volume to
be a remote mirror and copy source volume for a different remote mirror and
copy volume relationship. The default value for this parameter is disabled.
- -tgtonline
- (Optional). Establishes a remote mirror and copy volume relationship,
including when the target volume is online to host systems. This parameter
applies to S/390 or zSeries volumes and does not apply to Open Systems volumes.
The default value for this parameter is disabled.
- -tgtread
- (Optional). Allows host servers to read from the remote mirror
and copy target volume. For a host server to read the volume, the remote mirror
and copy pair must be in a full-duplex state. This parameter applies to open
systems volumes and does not apply to IBM S/390 or zSeries volumes. The default
value for this parameter is disabled.
- -critmode
- (Optional). Protects the source volume from receiving new data.
If the last path fails between the pairs and results in the inability to send
information to the target, the source is protected. Current updates and subsequent
attempts to update the source fail with a unit check on S/390. The default
value for this parameter is disabled.
Note: This parameter applies only to S/390 or zSeries volumes.
- Critical mode operates in one of three ways depending on the
setting of the LCU critical mode and the setting of the -critmode parameter
in this command. The following table presents an overview of how the critical
volume mode works.
| Critical Mode |
LCU, Critical Heavy |
Mkpprc critmode |
Description |
| Normal |
Disabled or Enabled |
Disabled |
- Suspends the primary volume.
- Allows write operations to the primary volume.
|
| Critical Volume |
Disabled |
Enabled |
- Suspends the primary volume when the last path to the secondary volume
has failed.
- Inhibits write operations to the primary volume.
|
| Critical Heavy |
Enabled |
Enabled |
- Suspends the primary volume when the secondary volume cannot be updated
for any reason.
- Inhibits write operations to the primary volume.
|
Notes: - Use the -critmode parameter only for log devices, not for devices
that the system requires. In extreme cases, the host system might have to
be IPLed in order to recover a device that is write inhibited. Whenever possible,
use the freezepprc command as an alternative to using the -critmode parameter.
- The -critmode parameter cannot be used with Global Copy or remote
copy and mirror cascading volumes.
- To reset a volume that is write inhibited because of critical
mode, you can issue the mkpprc, pausepprc, or rmpprc command
to this volume.
- Use automation software as part of any solution that includes critical
mode. Automation software is not a part of the software that is provided with
the storage unit; you must supply it. However, IBM has offerings to assist
with this automation. For more information, contact your IBM storage representative.
- -suspend
- (Optional). Suspends the remote mirror and copy relationship when the
task completes. This parameter is not valid for a Global Copy (Extended Distance)
remote mirror and copy volume relationship. This parameter is not valid for
a Metro Mirror (Synchronous) remote mirror and copy volume relationship that
is established with the No Copy option. The default value for this parameter
is disabled.
- -resetreserve
- (Optional - open system volumes only). Allows the establishment of a remote
mirror and copy relationship when the volume on the secondary logical subsystem
is reserved by another host. This parameter can only be used with open system
volumes. If this option is not specified and the volume on the secondary logical
subsystem is reserved, the command fails.
- -wait
- (Optional). Delays the command response until the remote copy and mirror
volumes are in one of the final states: simplex, full duplex, suspended, secondary
full duplex, secondary suspended or secondary simplex (until the pair is not
in the Copy Pending state). The default value for this parameter is disabled.
Notes: - This parameter cannot be used with the -type gcp or -mode nocp parameters.
- When you use the -wait parameter, you must wait until the original
command completely processes before you can issue a new command.
- If you are running in single-shot mode, you can periodically issue the lspprc command
to check the remote mirror and copy volume pair state, and then continue with
new commands when the correct state is reached.
- -srcss ss_ID
- (Optional). Specifies the subsystem ID of the primary logical subsystem
in the format 0x0001 - 0xFFFF.
- This value is required for the IBM System Storage™ Enterprise
Storage Server versions 2.4.0 and 2.4.1.
- Example: 0010
- -tgtss ss_ID
- (Optional). Specifies the subsystem ID of the secondary logical subsystem
in the format 0x0001 - 0xFFFF.
- This value is required for the IBM System Storage Enterprise
Storage Server versions 2.4.0 and 2.4.1.
- Example: 0010
- SourceVolumeID:TargetVolumeID . . . | -
- (Required). Specifies the remote mirror and copy volume relationship for
the source and target volume pairs with the specified IDs.
- This parameter accepts fully qualified volume IDs, which includes storage
image IDs or a shortened version without storage image IDs, if the -dev parameter
is specified. You must separate multiple remote mirror and copy pair IDs with
spaces.
- A remote mirror and copy pair ID consists of two volume IDs: one designated
as the source and the other as the target volume for a remote mirror and copy
relationship. You must separate the two volume IDs of a remote mirror and
copy pair IDs with a colon and no space. The first volume ID is the source
volume. The second volume ID is the target volume.
- The volume ID is a 32 bit number that can be represented as 4 hexadecimal
digits in the form of XYZZ where X is the address group (0 -
1), XY together is the logical subsystem number 00
- 1E (for 1750) , and ZZ is
the volume number (00 - FF).
- If you specify the dash (-), this parameter information is automatically
supplied.
- Example of a fully qualified pair: IBM.1750-68FA120/0100:IBM.1750-68FA150/0100
- Example of a shortened version: 0100:0100
- Example of multiple pairs: 0101:0101 0102:0102 0103:0103
Additional processing tips
The following examples
represent some CLI volume format options that you might want to incorporate
in your processing:
- Processing multiple volumes
- The following two examples are ways that this circumstance might be processed,
and both are correct. The first method might be fine if you were managing
a few volumes, while the second allows you to process hundreds or thousands
of volumes more efficiently.
mkpprc -dev IBM.1750-13AB79A -remotedev IBM.1750-13AB76A –type mmir
-mode full -tgtread 1000:1205 1001:1206 1002:1207 1003:1208 1004:1209
....... and so on
mkpprc -dev IBM.1750-13AB79A -remotedev IBM.1750-13AB76A –type mmir
-mode full -tgtread 1000-1004:1205-1209
- Using the grouping method in your command
- You can also group the volumes. However, the order of the volumes is
critical when you group them, and they must be contiguous. The following shows
how to code for grouping:
mkpprc -dev IBM.1750-13AB79A -remotedev IBM.1750-13AB76A –type mmir
-mode full -tgtread 1000-1004:1205-1209 1100-1104:1300-1304
Example (1750)
Invoking
the mkpprc commanddscli>mkpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150
0100:0100 -type mmir 0101:0101 0102:0102 0103:0103
The
resulting output (an example only) Date/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0
DS: IBM.1750-68FA120
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship
0100:0100 successfully created.
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship
0101:0101 successfully created.
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship
0102:0102 successfully created
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship
0103:0103 successfully created