|
|
|
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.
Windows/OpenVMS Format:
signal/job job_name [/qualifiers]
UNIX/Linux Format:
sigjob job_name [-qualifiers]
/completed or -completed (default)
/started or -started
/status or -status = number (default is 1)
/set_id or -set_id = number (default of 0 implies all job sets)
/[no]log or -[no]log
/[no]confirm or -[no]confirm
/node or -node = target_node
Windows/OpenVMS:
Schedule> signal sal_reports /started/log
UNIX/Linux:
Schedule> sigjob sal_report -completed
/[no]confirm or -[no]confirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.
/hostname or -node =hostname
The qualifier specifies what node (either local or remote) you want the operation performed on.
/completed or -completed
The COMPLETED qualifier sends a signal to the server that a job has successfully completed.
/[no]log or -[no]log
The LOG qualifier causes each completed operation to issue a note to the user.
/set_id or -set_id
The SET_ID qualifier points to a designated job set. If no number is specified the default implies all job sets.
/started or -started
The STARTED qualifier sends a signal to the server that a job is being executed.
/status or -status
The STATUS qualifier indicates the success (odd) or failure (even) of a job execution.