Storage system: | ETERNUS DX/AF, Symmetrix/VMAX3 |
Domain: | DEVICE |
Privileges: | TSOS |
/ACTIVATE-SNAP
The original units of the snap pairs are specified in the UNIT operand.
When the original units are selected via a pubset (UNIT=*BY-PUBSET), snap units must exist for all units of the pubset. The snap pubset on the snap units can be renamed directly using the NEW-PUBSET operand if an SF pubset is involved.
The file consistency over multiple volumes must be ensured by the caller. For this purpose a synchronization point should be created for the data before the command is called, see section "Synchronization point for replications".
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").
For SnapOPC+ on ETERNUS DX/AF and TimeFinder SnapVX on VMAX3
Snap pairs are activated immediately after /START-SNAP-SESSION. They then have the COPY-ON-WRITE status.
/ACTIVATE-SNAP offers renaming of a pubset which has already been activated which consists of snap units (*BY-PUBSET(...) operand). The status of the snap pairs remains unchanged.
For TimeFinder/Snap on Symmetrix
/ACTIVATE-SNAP activates one or more snap pairs, each of which consists of one original unit and one snap unit. After successful activation, the original and snap units are split. Both are available for applications from the host. From the application’s viewpoint, the snap unit contains all the data of the original unit at command processing time.
The command is executed only if the snap pair is in the CREATED status.
The SNAP-UNIT operand enables the snap unit which is to be activated to be selected if several pairs in the CREATED status exist for an original unit. By default the first possible snap unit is activated.
When the SRDF function is used, the original unit can also be the source unit of a remote copy pair. The target unit can also be the original unit of a snap pair. In this case the source unit is specified in the UNIT operand, and the snap pair on the target unit is selected using the SELECT=*TARGET-UNIT operand.
After the snap pair has been activated/split, the Copy-On-First-Write process begins (see the chapter "Local replication with snapshots (ETERNUS DX/AF, Symmetrix/VMAX3)"). The pair is in the status COPY-ON-WRITE or COPIED.
ACTIVATE-SNAP | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
UNIT =
For ETERNUS DX/AF and VMAX3 only UNIT=*BY-PUBSET makes sense.
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-SYMMETRIX/*BY-STORAGE), or directly by means of the logical volume's mnemonic device name.
UNIT = *BY-VOLUME(...)
Only relevant for Symmetrix.
Selects the units by means of a particular 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 snap pubset can be renamed using NEW-PUBSET.
PUBSET = <cat-id 1..4>
Specifies the pubset ID or volume set ID. When HOLD-IO=*UNTIL-ACTIVATED, no volume set ID may be specified.
NEW-PUBSET =
Determines the catalog ID of the snap pubsets of the snap unit(s).
NEW-PUBSET = *SAME
The snap pubset of the snap unit(s) is not renamed, i.e. it retains the same name.
NEW-PUBSET = *SPECIAL-VSN
All volumes of an SF pubset’s snap units are automatically renamed to prevent confusion with the original. For this purpose the period in a VSN in point notation is changed to a colon (e.g. AA.001 to AA:001), or in PUB notation the PUB string is changed to P:B (e.g. PUBA01 to P:BA01).
NEW-PUBSET = <cat-id 1..4>
An SF pubset’s snap pubset is renamed by specifying the new catalog ID explicitly. The catalog ID can also differ in length from the PUBSET operand. The new snap pubset also becomes an SF pubset. An existing MRSCAT entry is used if it is of the correct type. If it is not, it is deleted and created again. See the notes in section "Renaming SF pubsets with SHC-OSD".
HOLD-IO =
Only relevant for Symmetrix.
Handles inputs/outputs on the snap pair during splitting (see “Consistent splitting of a pubset in the shared pubset network” in "Synchronization point for replications").
HOLD-IO = *NO
The inputs/outputs on the original units are executed without any change. This can lead to data inconsistencies on the snap units for applications which are not suspended before splitting takes place.
HOLD-IO = *UNTIL-ACTIVATED
The inputs/outputs on the original units are suspended until all the imported pubset’s snap pairs are in the COPY-ON-WRITE status. Subsequently inputs/outputs are resumed on the units. If an error occurs when inputs/outputs are suspended or resumed, the command is aborted. The input/output activity may need to be resumed using /RESUME-IO.
UNIT = *BY-SYMMETRIX(...)
Only relevant for Symmetrix.
Selects the unit by means of the internal number of the logical volume in the storage system.
SERIAL-NUMBER = <alphanum-name 3..12>
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>
Only relevant for Symmetrix.
Selects the unit by means of the mnemonic device name of the logical volume.
SNAP-UNIT =
Selects the snap units. If more than one snap unit exists for a unit, a specific snap unit must be selected.
SNAP-UNIT = *FIRST-POSSIBLE
Selects the first assigned snap unit possible for the command.
SNAP-UNIT = *FROM-SHOW-OUTPUT(...)
Selects the snap unit via its position in the output list of /SHOW-SNAP-SESSION-STATUS.
POSITION = <integer 1..127>
Specifies the position of the snap unit.
POSITION = *LAST
Selects the last snap unit in the output list.
SNAP-UNIT = *BY-SYMMETRIX(...)
Only relevant for Symmetrix.
Selects the snap unit by means of the internal number of the logical volume in the storage system.
SNAP-LOGICAL-VOLUME = <x-text 1..4>
Specifies the internal number of the logical volume in the storage system.
SNAP-UNIT = list-poss(256): <alphanum-name 2..2> / <x-text 4..4>
Specifies the mnemonic device name of the snap units.
SELECT =
For ETERNUS DX/AF and VMAX3 only SELECT=*STD is supported.
Selects the snap pairs.
SELECT = *STD
Selects the snap pairs which were defined using the UNIT operand.
SELECT = *TARGET-UNIT(...)
Only relevant for Symmetrix.
Selects the snap pairs which are assigned to the target unit of a remote copy pair. The relevant source unit is specified in the UNIT operand.
RA-GROUP =
Selects the target unit using the RA group in the case of concurrent target units.
RA-GROUP = *UNIQUE
Selects the one existing target unit.
RA-GROUP = <integer 1..250>
Specifies the RA group for selecting the target unit.
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 | |
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 | NDE1000 | Device not found or not in the storage system | |
64 | NDE1001 | 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 | NDE1010 | Enginuity version is not supported (too low) | |
64 | NDE1015 | Device not defined in BS2000 | |
64 | NDE1043 | Pubset type not supported | |
64 | NDE1044 |
| |
64 | NDE1087 |
| |
64 | NDE1100 | Invalid pubset state | |
64 | NDE1101 |
| |
64 | NDE1102 | Not all volumes could be allocated | |
64 | NDE1103 | No reconfiguration lock for pubset | |
64 | NDE1104 |
| |
64 | NDE1105 | Inconsistent pubset | |
64 | NDE1108 |
| |
64 | NDE1109 |
| |
64 | NDE1110 |
| |
64 | NDE1111 | Volume allocated to DRV, HOLD-IO not possible | |
64 | NDE1114 | Serial number not found | |
64 | NDE1115 | Serial number not unique | |
64 | NDE1116 | Logical volume not found | |
64 | NDE1120 | Error suspending or resuming input/output access to pubset | |
64 | NDE1153 | Symmetrix device lock set | |
64 | NDE1154 | Disk belongs to a meta-disk | |
64 | NDE1155 | RAID10 devices not supported | |
64 | NDE1171 | Target unit is not unique | |
64 | NDE1172 | RA group invalid for the specified unit | |
64 | NDE1430 | No Snap function for device | |
64 | NDE1431 | Different number of devices in the unit and snap unit specifications | |
64 | NDE1435 | Device is a virtual unit | |
64 | NDE1437 | MNs of the unit and of the snap unit are identical | |
64 | NDE1438 | Unit and virtual snap unit are different types | |
64 | NDE1440 | Incorrect state of unit (of a snap pair) | |
64 | NDE1441 | Incorrect state of snap unit | |
64 | NDE1449 | No snap unit assigned to specified snap unit | |
64 | NDE1453 | Device is not a snap unit | |
64 | NDE1454 | Device is unused snap unit | |
64 | NDE1484 | Snap pair already activated | |
64 | NDE1492 | Snap pair already split and snap unit renamed | |
64 | NDE1496 | Snap pair(s) already activated | |
64 | NDE1702 | Connection to SYMAPI server aborted | |
64 | NDE1800 | Device not found or not in the 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 | 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 | NDE2000 | Execution partially successful | |
64 | NDE2001 | Command not executed | |
64 | NDE2009 | Command aborted with K2 key | |
64 | NDE2011 | Symmetrix license not entered | |
64 | NDE2013 | SYMAPI error in command | |
64 | NDE2014 | StorMan error in command | |
64 | NDE2018 | Error on SYMAPI server during the current editing | |
130 | NDE1082 | Memory bottleneck during processing of command | |
130 | NDE2005 | Command cannot be executed at the moment |