The procedures managed by the WhereScape scheduler require the following standards.
Parameters
The procedure must have the following parameters in the following order:
Parameter name | Input/Output | SQL Server/DB2 Type |
|---|---|---|
p_sequence | Input | Integer |
p_job_name | Input | Varchar(256) |
p_task_name | Input | Varchar(256) |
p_job_id | Input | Integer |
p_task_id | Input | Integer |
p_return_msg | Output | Varchar(256) |
p_status | Output | Integer |
The input parameters are passed to the procedure by the scheduler. If the procedure is called outside the scheduler then the normal practice is to pass zero (0) in the sequence, job_id and task_id. A description of the run can be passed in the job name and the task name is typically the name of the procedure.
The output parameters must be populated by the procedure on completion. The return_msg can be any string up to 256 characters long that describes the result of the procedures execution. The status must be one of the following values:
Status | Meaning | Description |
|---|---|---|
1 | Success | Normal completion |
-1 | Warning | Completion with warnings |
-2 | Error | Hold subsequent tasks dependent on this task |
-3 | Fatal Error | Hold all subsequent tasks |
The major task in integrating a procedure will be in adapting it to the WhereScape scheduler standards and workflow.