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.
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.
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:
| 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 |
So the normal status change for a task is in this picture:
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.
| Unknown | Least significant |
| Complete | |
| Queued | |
| Submitted | |
| 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.
|
|
|
|
|
|