|
|
|
|
|
Signal a scheduling event.
The SIGNAL command sends a signal to the SCHEDULE SERVER. This command is automatically added to the temporary command files created when ever a job is submitted into an execution queue. Once at the beginning of job to signal that the job has started and once at the end to signal that the job has completed. The signal operation is optional. If a job terminates (via a crash or other abrupt mechanism) this event is picked up and becomes the completion signal.
General Format
signal/job job_name [/qualifiers]
Alternate
sigjob job_name [-qualifiers]
Qualifier Summary
type of signal:
/completed (default)
/started
other qualifiers:
/status = number (default is 1)
/set_id = number (default of 0 implies all job sets)
general qualifiers:
/[no]log
/[no]confirm
/node = target_node
Examples
C:\> schedule signal first_of_three_jobs/started/log
signaled \bmossberg\first_of_three_jobs
Qualifiers
/confirm
/noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.
/hostname=host_name
The qualifier specifies what node (either local or remote) you want the operation performed on.
/completed
The COMPLETED qualifier sends a signal to the server that a job has successfully completed.
/log
/nolog
The LOG qualifier causes each completed operation to issue a note to the user.
/set_id
The SET_ID qualifier points to a designated job set. If no number is specified the default implies all job sets.
/started
The STARTED qualifier sends a signal to the server that a job is being executed.
/status
The STATUS qualifier indicates the success (odd) or failure (even) of a job execution.