Scope
- Features are tested with respect to the
- Milestones
- TP1: Technical Preview with basic core functionality for use with shell scripts
- TP2: Technical Preview with fully featured functionality for replacement of the previous platform specific JobScheduler Agent
- RC1: Release Candidate with functionality to replace a previous standalone instance by Master/Agent instances.
Test Results
- The following test results have been recorded
| Feature | Test Result TP1 | Test Result TP2 | Comment |
|---|---|---|---|
Core Functionality | |||
| execution of shell jobs |  | ||
| stdout of shell jobs is logged as info | | ||
| stderr of shell jobs is logged | | stderr is logged as info, probably related to JS-1329 - Getting issue details... STATUS | |
| non-zero exit code is treated as error | | ||
| live output of log in JOC | | slow | |
| read order id with $SCHEDULER_ORDER_ID | | ||
| read job parameters as environment variables with $SCHEDULE_PARAM_ | | Works, but is case sensitive on Unix systems. Classic JobScheduler Agent works differently, seems to change all variables to upper case. | |
| read order parameters as environment variables with $SCHEDULE_PARAM_ | | Works, but is case sensitive on Unix systems. Classic JobScheduler Agent works differently, seems to change all variables to upper case. | |
| set order parameters using SCHEDULER_RETURN_VALUES | | ||
| kill a running task |  | process lost in JOC, but remote process is not killed | |
| file watching | | incoming files trigger a job chain, see JS-1300 - Getting issue details... STATUS | |
JobScheduler API | |||
| API jobs with javascript | | not implemented | |
| API jobs with java | | Yes, but with restrictions, see details below | |
| Shell jobs with javascript monitor | | not implemented | |
| Shell jobs with java monitor | | ||
| spooler_init() | | not called | |
| spooler_open() | | ||
| spooler_process() | | ||
| spooler_close() | | not called | |
| spooler_exit() | | ||
| spooler.create_variable_set | | ||
| spooler_task.params() | | ||
| spooler_task.order.params() | | ||
| Variable_set.set_value() | | ||
| Variable_set.var() | | ||
| Variable_set.merge() | | COM-80020009 scala.MatchError: sos.spooler.Variable_set@7fe373b5 (of class sos.spooler.Variable_set), method=call | |
| Variable_set.count() | | ||
| Variable_set.substitute() | | ||
| Variable_set.xml() | | ||
| Variable_set.set_xml() | | ||
| Log.info() (and all other log levels) | | ||
| Log.filename() | | ||
| Log.last() | | ||
| Log.set_level() | | ||
| Log.level() | | ||
| Log.log_file() | | ||
| Log.set_mail_on_error() | | ||
| Log.set_mail_on_success() | | ||
| Log.set_mail_on_process() | | ||
| Log.set_mail_on_warning() | | ||
| Log.start_new_file() | | COM-80020009 com.sos.scheduler.engine.minicom.types.COMException: COM-80020009 , method=call | |
| Job.set_delay_after_error(int,int) | | COM-80020009 scala.MatchError: 60.0 (of class java.lang.Double), method=call | |
| Job.set_delay_after_error(int,String) | | ||
| Job.clear_delay_after_error() | | ||
| Job.configuration_directory() | | ||
JITL Jobs | | ||
| JobSchedulerExistsFile | | There is a problem getting parameters. Possibly related to Variable_set.merge() JSJ_F_0010: error occurred in class sos.scheduler.file.JobSchedulerExistsFile : JSJ_E_0042: exception raised JSJ_F_0050: error occurred getting Parameters for job or order: sos.spooler.Variable_set@1540a68c (of class sos.spooler.Variable_set)
|