SHC-OSD V15.0 (en)

&pagelevel(3)&pagelevel

Storage system:	ETERNUS DX/AF
Domain:	DEVICE
Privileges:	TSOS

/HOLD-REMOTE-COPY interrupts remote copy mode. The remote copy pair is given the remote copy state IN-HOLD. On successful execution of this command, no further data is transferred to the target unit (no synchronization). Both source unit and target unit note the data delta as pending writes for each other.
In concurrent remote copy configurations, remote copy mode can be interrupted either for a specific target unit or for both target units.
The command is used for recovery procedure tests.

CAUTION!
The target unit and source unit can contain inconsistent or differing data if an asynchronous processing mode is set.

The command is executed only for source units.

The file consistency over multiple volumes must be ensured by the caller.
A synchronization point should be created for the data before the command is called, see the description of a synchronization point on "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 REC

When REC replication is suspended, as in the case of local replication with EC the server can immediately access the target unit (READY status).

Synchronous REC pairs in which the target unit and source unit are not synchronized can only be split using the FORCE=*YES operand.

/HOLD-REMOTE-COPY is also executed in REMOTE-COPY-STATUS=ERROR in order to permit switchover after the storage system has failed.

The remote pubset can be renamed directly using the NEW-PUBSET operand if an SF pubset is involved.

In the event of switchover after failure of the storage system with the source units, note that you cannot specify the units via the pubset as in this case the pubset can no longer be accessed. In this case perform the switchover for each mnemonic name or for the entire storage system.

The command can be entered for REC pairs in remote copy status ACTIVE or ERROR.

HOLD-REMOTE-COPY

UNIT = BY-VOLUME(...) / BY-PUBSET(...) / *BY-STORAGE(...) /
			list-poss(256): <alphanum-name 2..2> / <x-text 4..4>
	*BY-VOLUME(...)
		\|	VOLUME = <vsn 1..6>
	*BY-PUBSET(...)
		\|	PUBSET = <cat-id 1..4>
		\|	,NEW-PUBSET = SAME / SPECIAL-VSN / <cat-id 1..4>
		\|	,HOLD-IO = NO / UNTIL-SPLIT
	*BY-STORAGE(...)
		\|	SERIAL-NUMBER = <alphanum-name 3..14>
		\|	,LOGICAL-VOLUME = *ALL-SOURCE-UNITS(...) / <x-text 1..4>
		\|		*ALL-SOURCE-UNITS(...)
		\|			\|	SELECT = ANY / ALL-DEFINED / *ATTACHED
,*FORCE = NO** / *YES
,TARGET-UNIT = UNIQUE / ALL / FIRST-POSSIBLE / BY-STORAGE(...) /
						<alphanum-name 2..2> / <x-text 4..4>
	*BY-STORAGE(...)
		\|	TARGET-SERIAL-NUMBER = <alphanum-name 3..14>

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.
If VOLUME or PUBSET is specified, the action is automatically performed for the correct unit (i.e. the source unit). A mnemonic name or the internal number of the logical volume in the storage system can only be specified for source units.

UNIT = *BY-VOLUME(...)
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 remote pubset can be renamed using NEW-PUBSET.

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

NEW-PUBSET =
Only relevant for SF pubsets.
Determines the catalog ID of the remote pubset.

NEW-PUBSET = *SAME
The remote pubset is not renamed, i.e. it retains the same name.

NEW-PUBSET = *SPECIAL-VSN
All volumes of the remote copy 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 remote pubset is renamed by specifying the new catalog ID explicitly. The catalog ID can also differ in length from the PUBSET operand. The new remote 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 SF pubsets.
Processing of input/output operations on the remote copy pair while the pair is being split (see “Consistent splitting of a pubset in the shared pubset network” in "Activating clone pairs").

HOLD-IO = *NO
Input/output on the remote copy pair continues as before. This can lead to data inconsistencies on the remote copy units for applications which are not suspended before splitting takes place.

HOLD-IO = *UNTIL-SPLIT
Input/output on the remote copy pair is stopped until all remote copy pairs of the imported pubset are in the SPLIT 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-STORAGE(...)
Selects the units 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 = *ALL-SOURCE-UNITS(...)
Selects the source units of the specified storage system.

SELECT = *ANY
Selects all source units of the specified storage system.

SELECT = *ALL-DEFINED
Selects all source units (generated in BS2000) of the specified storage system.

SELECT = *ATTACHED
Selects all source units (attached in BS2000) of the specified storage system.

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

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

FORCE =
FORCE controls the interruption of remote copy mode for remote copy pairs that are not (yet) synchronous. The operand has the same effect in synchronous and asynchronous processing mode.

FORCE = *NO
The command is executed even if the remote copy pair is in ERROR status.

FORCE = *YES
Remote copy mode is always interrupted.

TARGET-UNIT =
Controls selection of the target unit for concurrent remote copy.

TARGET-UNIT = *UNIQUE
Remote copy mode is interrupted for the one existing target unit.

TARGET-UNIT = *ALL
Remote copy mode is interrupted for all target units.

TARGET-UNIT = *FIRST-POSSIBLE
Remote copy mode is interrupted for the first target unit which permits /HOLD-REMOTE-COPY.

TARGET-UNIT = *BY-STORAGE(...)
Selects the target unit using the serial number in the storage system.

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

Command processing

The following messages are output to SYSOUT for each device 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

/HOLD-REMOTE-COPY UNIT=*BY-VOLUME(VOLUME=RDF.00)

/HOLD-REMOTE-COPY UNIT=*BY-PUBSET(PUBSET=RDF)

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
3	0	NDE1067	Remote copy pair not yet synchronized
3	0	NDE1069	No current information available about some remote copy pairs
	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	NDE1002	Controller not found
	64	NDE1003	Data medium not online or not unique
	64	NDE1004	Pubset not found or wrong pubset type
	64	NDE1005	Pubset not homogeneous
	64	NDE1015	Device not defined in BS2000
	64	NDE1020	No remote copy function for the specified unit
	64	NDE1021	Device is not a source unit
	64	NDE1022	Device is or has no target unit
	64	NDE1028	Volume not unique in the unit
	64	NDE1043	Pubset type not supported
	64	NDE1044	`NEW-PUBSET` already exists
	64	NDE1060	Remote copy state is not `ACTIVE`
	64	NDE1062	Access to target unit of the remote copy pair is `DIRECT`
	64	NDE1063	Source unit does not have the state `READY`
	64	NDE1067	Remote copy pair is not synchronized
	64	NDE1079	None of the selected devices is attached
	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	NDE1107	No pubset allocation possible
	64	NDE1152	FORCE option not permitted
	64	NDE1171	Target unit is not unique
	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	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	NDE1860	Remote copy pair not in `ACTIVE` status
	64	NDE1862	Remote copy pair already in `IN-HOLD` status
	64	NDE1863	Remote copy pair already in `IN-HOLD` status Target already renamed
	64	NDE1866	No remote link available
	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	NDE2017	Command not possible for current status of the replication
	130	NDE1082	Memory bottleneck during processing of command
	130	NDE2005	Command cannot be executed at the moment

Your Browser is not longer supported

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

HOLD-REMOTE-COPY Interrupts remote copy mode

For REC

Command processing

Examples

Command return codes