Validation – HP P6000 Continuous Access Software User Manual
Page 189
In the following example, a launch command on line 9 suspends host I/O to a storage volume
(virtual disk). The transaction begins at line 10 and ends on line 16. The Do consists of lines 10
through 12, and the Always consists of lines 13 through 16.
Task
Line
...
Launch ( %source_host%, %suspend_command_line%, "", WAIT, "0" ) onerror
pauseat E1:
9
DO {
10
transaction start >
$Rep1 = SnapshotStorageVolume ( %array_name_source_storvol_unc1%,
FULLY_ALLOCATED, SAME, %dest_storvol1%, NOWAIT ) onerror pauseat E1:
11
transaction end >
//
12
} ALWAYS {
13
// Resume the host application.
14
Launch ( %source_host%, %resume_command_line%, "", WAIT, "0" )
15
}
16
...
In this example, if the snapshot command in the Do portion of the transaction fails, for whatever
reason, the launch command in the Always portion is executed to resume host I/O to the storage
volume. This transaction helps ensure that host I/O is not suspended indefinitely.
Validation
Validation refers to the use of resource validation commands in a job and subsequently performing
a validation of the job. Job validation, especially at run time, helps ensure that a job instance runs
successfully.
The values that you enter for arguments within job commands are checked in the job editor only
for compliance with basic syntax rules. See job command
Resource validation commands
There are several types of resource validation commands. Each type validates a different type of
resource or the status of the resource.
For example, ValidateStorageVolume checks for the availability of a specific virtual disk on a
specific storage system, while ValidateSnapcloneStorageVolume checks whether the storage volume
is available and if it can be copied using snapclone replication.
IMPORTANT:
HP recommends placing resource validation commands together, in the first lines
of a job. They can be preceded by comments, but not by other types of commands.
Resource validation processing
Jobs can be run and validated for resources from the GUI or the CLUI. When done from the GUI,
a new job instance is displayed in the Monitor Job window. Validation processing generally occurs
as follows.
•
Normal. If the line is a validation command, it is executed. If successful, the next line is
executed. If not successful, the job is stopped with a failure status.
•
Validate-only. If the line is a comment, SetVariable command or validation command, it is
executed. If successful, the next line is checked. If not successful, the job is stopped with a
Job concepts 189