This table contains the list of jobs. The structure of the table is as follows:
Fields
Name |
Description |
Type |
Lg. |
Dec* |
Key |
ID |
Number used to uniquely identify the job. |
INTEGER |
9 |
0 |
1 |
NAME |
Job name (as displayed on the interface). |
VARCHAR |
50 |
0 |
|
TYPE |
Discriminant enabling the job type to be identified, to be used in tandem with the unicity parameter. |
VARCHAR |
50 |
0 |
|
UNICITY |
Execution unicity parameter. If it has the value '1', the job can only be run if no other job of the same type (see above) is currently active (regardless of the machines or queues concerned). |
SMALLINT |
4 |
0 |
|
PROFILE |
User that owns the job. |
VARCHAR |
30 |
0 |
|
CREATIONDATE |
Job creation date. |
TIMESTAMP |
4 |
0 |
|
ACTIVATIONDATE |
Job activation date (the job cannot be started before this date). Possible action: a user with management privileges for the job can modify this date. |
TIMESTAMP |
4 |
0 |
|
STARTDATE |
Job start date (>=ACTIVATIONDATE). |
TIMESTAMP |
4 |
0 |
|
STOPDATE |
Job end date (>STARTDATE). |
TIMESTAMP |
4 |
0 |
|
STATE |
Job state. Possible values: ' ' Job waiting to start 'C' Job completed without error 'E' Job completed with errors 'W' Job completed without errors, with warning 'S' Job suspended (cannot be started) 'R' Job currently running. Possible action: a user with management privileges for the job can change the state from "waiting" to "suspended" and vice versa. |
VARCHAR |
1 |
0 |
|
TARGETSERVER |
Name of the work station (machine running the job manager) that must incorporate the job. If this field is not filled in, any job manager can run the job. This field is reset when a job manager acquires the job. Possible action: a user with management privileges for the job can modify the name of the machine. |
VARCHAR |
250 |
0 |
|
QUEUEID |
Unique identifier of the queue. |
INTEGER |
9 |
0 |
|
PRIORITY |
Job priority, values from 1 (highest) to 5 (lowest). |
SMALLINT |
4 |
0 |
|
ARCHIVEFLAG |
Code indicating the job archiving mode. Possible values: ' ' No specific archiving, the job will be deleted directly by the user or during purging 'D' The job will be deleted after running if it completes normally 'A' Job is archived, it can only be deleted by direct action from the user |
VARCHAR |
1 |
0 |
|
MAXEXEC |
Maximum run time before an alert is generated |
INTEGER |
9 |
0 |
|
PGM |
Name of the program to be called to process the job. |
VARCHAR |
250 |
0 |
|
PARAM1 |
First parameter of the processing program. |
VARCHAR |
1024 |
0 |
|
PARAM2 |
Second parameter of the processing program. |
VARCHAR |
1024 |
0 |
|
* Decimals
Notes: the job execution program and its parameters are specified by the user that submits the job. Also, the job ID is sent via the command line so the job state can be updated and the execution report generated. The generated command line is as follows:
PGM "PARAM1" "PARAM2" ID
The execution program must update the job state (to 'C', 'E' or 'W') after running. If this is not done, the job manager will automatically set the state to 'E' and will record an error entry in the report.
At start up, the state of the jobs assigned to the machine will be checked (there must not be any jobs currently running).
Depending on the configuration, the Job manager may use different sets of tables, with or without schemas. For more information, see Deleting a schema.
