This function is only necessary for EC.
Clone pairs created and managed with QuickOPC will be activated automatically after their creation.
In order to use clone units, the clone pairs must be activated in a clone session using /ACTIVATE-CLONE. The clone pair must be in the status SYNCHRONIZED.
Considerations on a synchronization point and renaming should therefore be taken into account already at the creation of the clone pairs (see the respective descriptions in section "Synchronization point for replications").
Following successful activation, the unit and the clone unit are split, i.e. both can be accessed by the server for applications. The clone unit contains all the data which was on the unit at the time the command was processed.
The clone pairs which are activated can be selected in different ways: via their VSN, their mnemonic name, their internal number in the storage system, or the ID of the pubset or volume set to which they belong. The most frequent method is selection via the pubset ID, which enables all clone pairs of this pubset to be activated. This method is described below.
Entire pubset
All clone pairs in a pubset are activated using the following command:
/ACTIVATE-CLONE UNIT=*BY-PUBSET(PUBSET=<cat-id>,...),...
Further sequence of operations
/UNLOCK-DISK is executed internally for all clone units (see the “Commands” manuals [1]) provided these are attached.
Console message NDE0060 indicates that the activation process has been completed. After the split process has been completed, the status can also be displayed using /SHOW-CLONE-SESSION-STATUS.
When all clone units of a pubset have been activated, the clone pubset can be imported as soon as the split process has been completed and the SPLIT status has been assumed. The associated MRSCAT entry is automatically created or updated.