Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

SWAP-CLONE-SESSION Swaps original and clone attributes of a clone pair

Storage system:

ETERNUS DX/AF

Domain:

DEVICE

Privileges:

TSOS


When using the EC replication function, the /SWAP-CLONE-SESSION command swaps the mirror properties of a clone pair. Before the command is entered, the replication must be interrupted (clone session status SPLIT).

/SWAP-CLONE-SESSION swaps the mirror properties of one or more clone pairs, each of which consists of an original unit and a clone unit. After a successful swap, the new original unit and the new clone unit remain in the SPLIT status. Both can be accessed for applications from the host. From the application’s viewpoint, the clone unit contains all the data of the original unit at command processing time.

The original units of the clone pairs are specified in the UNIT operand.

When the original units are selected via a pubset (UNIT=*BY-PUBSET), clone units must exist for all units of the pubset. The clone pubset on the clone units can be renamed directly using the RENAME-PUBSET operand if an SF pubset is involved.

/SWAP-CLONE-SESSION for a unit which is also the source unit of a remote replication is rejected with message NDE1177.

SHC-OSD checks the global and task-specific security settings before this command is executed (see "Security settings of SHC-OSD"). The current security settings can be displayed with /SHOW-SHC-PROCESSING (see also "SHOW-SHC-PROCESSING Displays settings of SHC-OSD"). They can be changed in the SHC-OSD parameter file (see "Configuration of SHC-OSD") for the next time SHC-OSD is started or with /MODIFY-SHC-PROCESSING for ongoing operations (see "MODIFY-SHC-PROCESSING Changes settings of SHC-OSD").

SWAP-CLONE-SESSION

UNIT = *BY-VOLUME(...) / *BY-PUBSET(...) / *BY-STORAGE(...) / <alphanum-name 2..2> / <x-text 4..4>


*BY-VOLUME(...)



|

VOLUME = <vsn 1..6>


*BY-PUBSET(...)



|

PUBSET = <cat-id 1..4>



|

,RENAME-PUBSET = *NO / *SAME / <cat-id 1..4>


*BY-STORAGE(...)



|

SERIAL-NUMBER = <alphanum-name 3..14>



|

,LOGICAL-VOLUME = <x-text 1..4>

,CLONE-UNIT = *FIRST-POSSIBLE / *FROM-SHOW-OUTPUT(...) / *BY-PUBSET(...) /




*BY-STORAGE(...) / list-poss(256): <alphanum-name 2..2> / <x-text 4..4>


*FROM-SHOW-OUTPUT(...)



|

POSITION = *LAST / <integer 1..16>


*BY-PUBSET(...)



|

CLONE-PUBSET = <cat-id 1..4>


*BY-STORAGE(...)



|

CLONE-LOGICAL-VOLUME = <x-text 1..4>


UNIT =

Selects the units by means of a particular VSN (*BY-VOLUME), a particular catalog ID (*BY-PUBSET), by means of the serial number and the internal number of the logical volume in the storage system (*BY STORAGE), or directly by means of the logical volume's mnemonic device name.

UNIT = *BY-VOLUME(...)
Selects the source units by means of a specific VSN.

VOLUME = <vsn 1..6>
Specifies the volume’s VSN.

UNIT = *BY-PUBSET(...)
Selects units by means of a pubset ID or volume set ID. The pubset is protected against reconfiguration during command processing. When an SF pubset is selected, the volumes of the clone pubset can be renamed using RENAME-PUBSET.

PUBSET = <cat-id 1..4>
Specifies the pubset ID or volume set ID.

RENAME-PUBSET =
Determines the catalog ID of the original (SF) pubset after the swap.

RENAME -PUBSET = *NO
The clone pubset is not renamed, i.e. it retains the same name.

RENAME-PUBSET = *SAME
Following the swap the pubset is renamed with the pubset ID or volume set ID of the original pubset (i.e. with the ID specified in PUBSET).

RENAME-PUBSET = <cat-id 1..4>
Explicit specification of the new pubset ID.

UNIT = *BY-STORAGE(...)
Selects the unit by means of the serial number and the internal number of the logical volume in the storage system.

SERIAL-NUMBER = <alphanum-name 3..14>
Specifies the serial number of the storage system (make sure it is unique!).

LOGICAL-VOLUME = <x-text 1..4>
Specifies the internal number of the logical volume in the storage system

UNIT = <alphanum-name 2..2> / <x-text 4..4>
Selects the unit by means of the mnemonic device name of the logical volume.


CLONE-UNIT =

Selects the clone unit. If more than one clone unit exists for a unit, a specific clone unit must be selected.

CLONE-UNIT = *FIRST-POSSIBLE
Selects the first possible clone unit.

CLONE-UNIT = *FROM-SHOW-OUTPUT(...)
Selects the clone unit via its position in the output list of /SHOW-CLONE-SESSION-STATUS.

POSITION = *LAST
Selects the last clone unit in the output list.

POSITION = <integer 1..16>
Specifies the position of the clone unit.

CLONE-UNIT = *BY-PUBSET(...)
Selects the clone unit via the pubset ID of the activated and renamed pubset.

CLONE-PUBSET = <cat-id 1..4>
Specifies the pubset ID.

CLONE-UNIT = *BY-STORAGE(...)
Selects the clone unit by means of the internal number of the logical volume in the storage system.

CLONE-LOGICAL-VOLUME = <x-text 1..4>
Specifies the internal number of the logical volume in the storage system

CLONE-UNIT = list-poss(256): <alphanum-name 2..2> / <x-text 4..4>
Specifies the mnemonic device name of the logical volume.

Command processing

The following messages are output to SYSOUT for each clone pair and distributed via routing code 0, i.e. they are logged in the CONSLOG file only. You will find detailed information on the CONSLOG file (log file) in the “Introduction to System Administration” manual [5].

  • For successful processing NDE1073

  • For unsuccessful processing NDE2007

Examples

/SWAP-CLONE-SESSION UNIT=*BY-PUBSET(PUBSET=CLON)
/SWAP-CLONE-SESSION UNIT=8300,CLONE-UNIT=3800

Command return codes

(SC2)

SC1

Maincode

Meaning


0

CMD0001

Command executed successfully

1

0

NDE2003

Command successfully executed, no processing necessary

2

0

NDE2004

Command successfully executed but not yet completed


1

CMD0202

Syntax error


1

NDE1036

PUBSET and RENAME-PUBSET have different lengths


32

NDE2002

Internal error


64

CMD0087

Function not permitted in the current input mode or with the current task privileges


64

CMD0216

Required privilege not available


64

NDE1003

Device not attached


64

NDE1003

Data medium not online or not unique


64

NDE1004

Pubset not found or wrong pubset type


64

NDE1005

Pubset not homogeneous


64

NDE1008

Volume cannot be allocated


64

NDE1015

Device not defined in BS2000


64

NDE1043

Pubset type not supported


64

NDE1044

RENAME-PUBSET already exists


64

NDE1044

Pubset cannot be renamed


64

NDE1057

Function not supported


64

NDE1100

Invalid pubset state


64

NDE1101

More than one sharer for pubset


64

NDE1102

Not all volumes could be allocated


64

NDE1103

No reconfiguration lock for pubset


64

NDE1105

Inconsistent pubset


64

NDE1055

Function not supported for Symmetrix/VMAX3 storage system


64

NDE1143

Error occurred during processing of mirror pair


64

NDE1177

Unit is also a source unit for remote copy


64

NDE1178

Device is a target unit


64

NDE1530

No clone function for the unit


64

NDE1531

Different number of devices in the unit and clone unit specifications


64

NDE1535

Device is a clone unit


64

NDE1540

Incorrect state of unit


64

NDE1541

Incorrect state of clone unit


64

NDE1549

No clone unit assigned for clone unit selection


64

NDE1553

Device is not a clone unit


64

NDE1800

Device not found or not in storage system


64

NDE1802

Error communicating with StorMan server


64

NDE1803

Management instance not available


64

NDE1810

Storage system’s operating system version not supported


64

NDE1811

Function not supported for storage system


64

NDE1812

StorMan server switched off by command


64

NDE1814

Storage system’s serial number not found


64

NDE1815

Storage system’s serial number not unique


64

NDE1816

Storage system’s logical volume not found


64

NDE1833

No suitable Storman server found


64

NDE1853

Storage unit locked


64

NDE1890

Management instance not found


64

NDE1899

Command not possible for current status of the mirror pair


64

NDE2000

Execution partially successful


64

NDE2001

Command not executed


64

NDE2014

StorMan error in command


64

NDE2020

No license for local replication (ETERNUS DX/AF)


130

NDE1082

Memory bottleneck during processing of command


130

NDE2005

Command cannot be executed at the moment