mkpprc

Parameters

-dev storage_image_ID

(Optional) The source storage image ID consists of the manufacturer name, machine type, and serial number. The storage image ID is required if you do not specify a fully qualified source volume ID, do not set the devid variable in your profile or through the setenv command. The storage image ID is also required if the HMC is aware of more than one storage image. Using the -dev parameter temporarily overrides any defined value for devid for the current command.

Example: IBM.2107-75FA120

-remotedev storage_image_ID

(Optional) The target storage image ID consists of the manufacturer name, 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.

-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) The following 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 value is the default when you do not specify the no copy mode.

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 IBM® Z 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 z System 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 IBM Z . The default value for this parameter is disabled.

Note: This parameter applies only to IBM Z volumes.

Critical mode operates in one of three ways that depend on the setting of the LCU critical mode and the setting of the -critmode parameter in this command. The Critical volume mode definition overview table describes how the critical volume mode works.

Table 1. Critical volume mode definition overview

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 fails. 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:

1. Use the -critmode parameter only for log devices, not for devices that the system requires. In extreme cases, the host system might require you to load the initial program to recover a device that is write inhibited. Whenever possible, use the freezepprc command as an alternative to using the -critmode parameter.
2. The -critmode parameter cannot be used with Global Copy or remote copy and mirror cascading volumes.
3. To reset a volume that is write inhibited because of critical mode, you can enter the mkpprc, pausepprc, or rmpprc command to this volume.
4. 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 system; 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. You can use this parameter only with open system volumes. If this option is not specified and the volume on the secondary logical subsystem is reserved, the command fails.

-incrementalresync enable | enablenoinit | disable | recover | override

(Required for three-site Metro/Global Mirror recovery) The resynchronization method that is used in a three-site Metro/Global Mirror disaster recovery configuration. A three-site Metro/Global Mirror configuration usually involves the following sites:

• Site A (local site), which contains the production volumes (or the A volumes).
• Site B (intermediate site), which contains the B volumes and a local, synchronous copy.
• Site C (remote site), which contains the C volumes and an asynchronous copy that is located remotely from sites A and B.

You can specify the following options when you first establish volume pairs by using the mkpprc command or on established volume pairs with this command.

enable

The change recording features are enabled on each of the primary Metro Mirror volumes to process the microcode to monitor and track data in a Metro/Global Mirror configuration. This is data that has been written to the primary volumes but not secured on the remote site volumes.

enablenoinit

The change recording features are not created or started on the primary Metro Mirror volumes in a Metro/Global Mirror configuration. Only use this option in specific recovery scenarios.

disable

The current incremental resynchronization function is stopped on the primary volumes of the Metro Mirror volume pairs.

recover

A new Global Mirror volume pair is established by using an existing primary Metro Mirror (A) volume at the local site and a secondary Global Copy (C) volume at the remote site. When this command processes, only changes to the local Metro Mirror volumes are copied to the volumes at the remote site.

Note: When you specify this option, the system verifies that the failed secondary volumes for the volumes in a Metro Mirror relationship are the primary volumes for the volumes in a Global Copy relationship and that the specified volumes have the intermediate volumes in common. That is, the primary specified volumes are the A volumes and the secondary specified volumes are the C volumes in a Metro/Global Mirror configuration.

override

A new Global Mirror volume pair is established by using an existing primary Metro Mirror (A) volume at the local site and a secondary Global Copy (C) volume at the remote site. When this command processes, only changes to the local Metro Mirror volumes are copied to the volumes at the remote site.

Note: When you specify this option, there is no validation to ensure the secondary relationship in this configuration before the mkpprc command is processed. Therefore, you must ensure that the primary specified volumes are the A volumes and the secondary specified volumes are the C volumes in a Metro/Global Mirror configuration.

-tgtse

(Optional) Identifies the PPRC secondary volume as a space efficient volume.

-disableautoresync

(Optional) Disables the mechanism that automatically resumes a suspended Global Copy relationship. The default is not disabled. The -disableautoresync parameter is available only in Version 5 Release 3 or later.

-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:

1. This parameter cannot be used with the -type gcp or -mode nocp parameters.
2. When you use the -wait parameter, you must wait until the original command completely processes before you can enter a new command.
3. If you are running in single-shot mode, you can periodically enter the lspprc command to check the remote mirror and copy volume pair state. Then, continue with new commands until the correct state is reached.

SourceVolumeID:TargetVolumeID ... | -

(Required) 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 include 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 four hexadecimal digits in the form of XYZZ, where:

XY

The logical subsystem number, 00 - FE.

ZZ

The volume number, 00 - FF.

X

The address group, 0 - F.

The ellipsis (...) indicates that, optionally, you can specify multiple values. If you use the dash (-), the specified value is read from standard input. You cannot use the dash (-) while you are in the DS CLI interactive command mode.

Example of a fully qualified pair: IBM.2107-75FA120/0100:IBM.2107-75FA150/0100

Example of a shortened version: 0100:0100

Example of multiple pairs: 0101:0101 0102:0102 0103:0103