Running SMS

In order for the tasks in a suite to be submitted and thus for the jobs to run there are some things that has to be done.

Page about start-up files.

General

SMS schedules tasks. Tasks are placed into families which in turn may be placed into families and/or suites. All these are called nodes. Nodes ungergo status changes and sometimes flags can be set to indicate various things. Running SMS successfully requires that suites are defined, played into SMS, suite is begun and thet SMS is restarted.

Status of a task

Each task in SMS has got a status. Status is the state in which the node is. In the following the background colour of the text reflects the status colour in XCdp.

The status of a task can vary as follows:

  1. After play(CDP) command the tasks are unknown
  2. After begin(CDP) command the tasks are either queued, complete, aborted or suspended. Suspened task means that the task really is queued but it must be resumed by user first.
  3. Once the dependencies are resolved the task is submitted by SMS. Now the status is or aborted (aborted, if SMSCMD failed.)
  4. If the submission was successfull once the job starts it should become active
  5. Before the job ends it may send other messages to SMS like
    smsevent set an event
    smsmeter change a meter
    smslabel change a label
    smsmsg send a message to sms-logfile
    smsmail send a mail message to user in SMS
  6. Job ends by becoming either complete or aborted by job ifself sending the message back to SMS.
  7. At any state user can suspend a task which means that it status is saved and a new status given is suspended

So the normal status change for a task is in this picture:

Status of a family or suite

The status of a family or suite is the most significat status of it's kids. While computing the status the real-status is used (that is if node is suspended it's saved status is used.

The status of the SMS itself can also be

Here is a table of the order of importance of the different statuses and some examples of the result of a status of the family depending on its kids.

Table of importance of the status
Unknown Least significant
Complete  
Queued  
 
Active  
Suspended 
Aborted Most importand for a task, family or a suite
Shutdown Only for SMS
Halted Most important, Only for SMS

Example of a small family, when tasks change status.

Status of a family
After begin command
archive anml
anpl
ansfc
obs
First job send
anpl
ansfc
obs
Second job send
archive anml
ansfc
obs
A few tasks running
archive anml
anpl
ansfc
One task aborts!
archive anml
anpl
ansfc
In the end, complete!
archive anml
anpl
ansfc
obs