The mkflash command
initiates a point-in-time copy from source volumes to target volumes.

>>-mkflash--+-------------------------+--+-----------+---------->
'- -dev--storage_image_ID-' '- -tgtpprc-'
>--+--------------+--+--------------+--+----------+------------->
'- -tgtoffline-' '- -tgtinhibit-' '- -freeze-'
>--+----------+--+-----------+--+--------+--+--------+---------->
'- -record-' '- -persist-' '- -nocp-' '- -wait-'
>--+------------------------------+----------------------------->
'- -seqnum--flash_sequence_num-'
>--+-source_volume_ID:target_volume_ID--+-------+-+------------><
| '-. . .-' |
'-" - "----------------------------------------'
Parameters
- -dev storage_image_ID
- (Optional) Specifies the storage image ID, which consists of a manufacturer,
machine type, and serial number. This parameter is required if you do not
specify a fully qualified ID for the source and target volumes and you do
not specify a value for the devid variable
in your profile file.
- Example: IBM.1750-68FA120
- -tgtpprc
- (Optional) Allows the FlashCopy target volume to be a remote mirror and
copy source volume.
- -tgtoffline
- (Optional) Causes the mkflash command to be rejected if the target
volume is online for host system access. This parameter applies only to count
key data volumes.
- -tgtinhibit
- (Optional) Prevents host system write operations to the target while the
FlashCopy relationship exists.
- -freeze
- (Optional) Triggers the queue full condition for the source
volume. All writes to the source volume are queued by the host and are written
after the queue full condition is reset.
- During the queue full condition, the source volume reports long
busy status.
- The queue full condition is reset by an extended long
busy timeout. The timeout condition affects all FlashCopy source volumes
that are contained within a respective logical subsystem and that are established
or modified with the -freeze parameter.
Note: If you need to
modify the extended long busy timeout setting, use the chlss and chlcu commands.
- -record
- (Optional) Records the changed tracks on both volumes within a FlashCopy
pair. Select this parameter when you establish an initial FlashCopy volume
pair that you intend to use with the resyncflash command.
The -persist parameter is automatically selected when this parameter
is selected.
- -persist
- (Optional) Retains the FlashCopy relationship after the background copy
completes. The FlashCopy relationship between the source and the target volumes
remains indefinitely until you issue a rmflash command.
This parameter is automatically selected when the -record parameter
is selected. Select this parameter along with the -record parameter
if you will be using this volume pair with the resyncflash, reverseflash,
or setflashrevertible commands.
- -nocp
- (Optional) Inhibits background copy. Data is copied from the source volume
to the target volume only if a track on the source volume is modified. The
FlashCopy volume pair relationship remains indefinitely until it is broken
by a rmflash command, or until all tracks on the
source volume are modified.
- -wait
- (Optional) Delays the command response until the background copy process
completes. You cannot use the -wait parameter with either the -persist or -nocp parameters.
- -seqnum flash_sequence_num
- (Optional) Associates the FlashCopy relations that are established with
the specified sequence number. This sequence number can be used as an identifier
for a relation or group of relations.
- This parameter is not supported for machine type 2105.
- Example: 0010
- source_volume_ID:target_volume_ID . . . | -
- (Required) Establishes a FlashCopy relationship for the source and target
volume pairs with the specified IDs. This command accepts fully qualified
volume IDs, which consist of storage image IDs or a shortened version without
storage image IDs, if the -dev parameter is specified. You can also
specify a value for the devid variable in your
profile file. You must separate multiple FlashCopy pair IDs with spaces.
- A FlashCopy pair ID consists of two volume IDs: one designated as the
source and the other as the target volume for a FlashCopy relationship. You
must separate the two volume IDs of a FlashCopy pair ID with a colon and no
space. The first volume ID is the source volume. The second volume ID is the
target volume.
Note: It is possible that during processing you will receive
an error message indicating that relationships have been exceeded or that
an initial volume format is in progress. This means that the FlashCopy relationship
cannot be established because the maximum number of relationships have already
been established. Or, the volume was recently created and is still being initialized
to support FlashCopy. You can issue a mkflash command
to establish the FlashCopy relationship after the initial volume format process
is complete.
- 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 FlashCopy pair ID: IBM.1750-68FA120/0001:IBM.1750-68FA120/0004
- Example of a shortened version: 0001:0004
- Example of multiple pairs: 0001:0004 0003:00FF 0008:000C
Example (1750)
Invoking
the mkflash commanddscli>mkflash IBM.1750-68FA120/0100:IBM.1750-75FA120/0200
The resulting outputDate/Time: Sun Aug 11 02:23:49 PST 2004 IBM DS CLI Version: 5.0.0.0
DS: IBM.1750-68FA120
FlashCopy pair IBM.1750-75FA120/0100:IBM.1750-75FA120/0200 successfully created.