DS_PENDING_JOB
This is the main table used by Broadcast Agent, and contains all the properties of each scheduled task.
Name | Null ? | Type | Values |
BATCH_ID | NOT NULL | int10 | This is the batch identifier. Each task has a different BATCH_ID. This batchId is unique for each task in a security domain. It is computed from the OBJ_M_MAGICID table. "SELECT M_MAGIC_N_ID FROM OBJ_M_MAGICID WHERE M_MAGIC_C_NAME='BATCH'" is the SQL sentence that allows to get the ID of the next task. |
DOCUMENT_ID | NOT NULL | int10 | This is the document identifier. Two tasks can have the same DocumentID (for example, when you perform a Run now command, the new task entry will have a different BatchID but the same DocumentID). |
PRC_ID | char(10) | This is the End-user module process ID that is launched on the server machine. | |
USER_SUBMIT_ID | NOT NULL | int10 | This is the sender identifier (the end-user that performed the Send to document Agent command). It references a value in the OBJ_M_ACTOR table . |
PRIORITY | NOT NULL | int10 | This is the task priority. (High is 3, Normal is 2 and Low is 1). It can be modified at any time by editing the task properties. |
FREQUENCY | NOT NULL | int10 |
This is the task frequency, combined with the
Overwrite mode. (It is a Combined field). It can be
modified at any time by editing the task properties. |
DAY_TIMING | NOT NULL | int10 | This is used to store information about the task execution period. |
BEGIN_TIME | int10 | This is used to store information relative to the scheduling. For example, it stores the hour :minutes chosen when submitting a document that is Weekly. | |
BEGIN_DATE | int10 | This is the date on which the job will be considered as being eligible. | |
START_DATETIME | int10 | This is the date on which the task started on the server machine. | |
END_DATETIME | int10 | This is the date on which the task ended on the server machine. | |
SUBMIT_DATETIME | NOT NULL | int10 | This is the date on which the task was submitted on the client machine. |
EXPIRATION_DATE | int10 | This date indicates when the task will be converted to the status Expired. | |
JOB_STATUS | int10 | indicates whether the job is successful,
failed,... Success = 0, Failure = 1, Waiting = 2, Running = 3, Suspended = 4, Retrying (1)=1001, Retrying (2)=1002, Retrying (3)=1003, Retrying (4)=1004, Retrying (5)=1005, Expired=1006 |
|
JOB_ERROR | int10 | Code that indicates what is the error: The value is further translated into an error message. Example : The value 4 is translated to Error executing script. | |
DOCSERVER_ID | int10 | This is the Broadcast Agent Server ID. It references a user in the OBJ_M_ACTOR table (field M_ACTOR_N_ID). | |
JOB_SCRIPT | char(254) |
This is used to know what type of actions will be executed
on the document. The values are separated by commas. |
|
JOB_DESC | char(254) | This is the job description initially filled when submitting the document. | |
JOB_DATA | char(70) | This column contains the encrypted value of the BOPASS variable defined at the submission time in the end-user module. This column is used only when the user is defined in 'No password checking' mode at the supervisor level (however, when submitting a document, this column is systematically filled). This column can be updated from the end-user module console (tools\console). If a user submits two document in the same session, the JOB_DATA column will not have the same value (even though at the submission time, the variable BOPASS did not change) because it depends also on the BATCHID column. This column is only updated at the document submission time. | |
IP_ADDRESS | char(254) | This column contains the name of the machine where the scheduler was running and the name of the machine where the task was processed (the machine where BOManager is running ). | |
ERROR_TEXT | char(254) | This column contains the full error description. | |
VERSION | int10 | This column contains the version number of the submitter (end-user module, etc). | |
IN_NAME_OF | int10 | This column indicates the mode used to refresh the document (refresh with the profile of the submitter, which is the default, or refresh with the profile of the recipient. This column is only updated at document submission time. | |
JOB_PLATFORM | int10 | In a heterogeneous cluster, this value determines whether the task will be executed on an NT node or a UNIX node. See the table below. It is also used for the retry mechanism for tasks which fail on UNIX and are then tried on NT, as described below. |
VERY IMPORTANT : All dates stored on the repository are stored in UTC format, beginning at December 15th in 1970 (that is, one second later than 23 :59 :59 December 14th 1970).