HP 418800-B21 - StorageWorks Modular Smart Array 70 Storage Enclosure, Руководство пользователя

Страница: 202 / 462

Usage
Labels are:
• Local to each job and cannot be referenced across jobs.
• Not case sensitive.
Format
• Must be at least two characters and end with a colon.
• Upper and lower case, alpha and numeric are allowed.
• Underscores are allowed; spaces are not allowed.
Pause and continue
Pause
A pause action or command halts execution of a running job instance and places the job in a paused
state.
• You can use a GUI action, a pause command within the job, or a CLUI command.
• When using a pause command within a job, execution is halted on the pause step.
• When using the GUI or CLUI, the job instance typically completes the current step, then halts before
starting the next step. However, if the step is an interrupt-enabled wait command, the job instance
immediately halts. Interrupt-enabled wait commands include: Wait , WaitForJob and WaitUntil .
Continue
A continue action or command resumes execution of a job instance that is paused , or waiting . See
job status and states .
• You can use a GUI action or CLUI command.
• When used for a waiting job instance, the wait is ended and execution continues at the next step.
• When used for a paused job instance, execution typically continues at the next step.
However, if the job instance was paused on an interrupt-enabled wait command, the wait
condition is checked before continuing. If the wait condition has been detected, then the next
step is executed. Otherwise, the job instance waits for the condition to be detected before
starting the next step.
For example, if a job command speci fi es a 10-minute wait and the continue occurs after 20
minutes, the next step would be immediately executed. If the continue occurs after 5 minutes, the
job instance would wait 5 minutes before starting the next step.
Resource names and UNC formats
Resources in a SAN are identi fi ed in several ways, including UNC format. UNC (Universal or Uniform
Naming Convention) identi fi es a resource in terms of its hierarchical location in a network.
See the following for name and UNC formats: DR groups , enabled hosts , host volumes , Oracle ,
storage systems , and virtual disks (storage volumes)
Resource names in job commands
When you initially enter a command in a job, the command’s resource arguments are displayed
as %variable% names, for example:
CreateDiskDevice ( %storvol_unc_name% , %host_name% , 0, READ_WRITE)
When selecting a speci fi c resource from an Editing Task menu, the resource names are presented in a
UNC format, or other format, as appropriate for the resource. If you enter a resource name from the
keyboard, you must use the appropriate format.
202
Jobs