| Feature | Test Result | Comment |
|---|---|---|
| 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 |
| API jobs with javascript | | not implemented |
| Shell jobs with javascript monitor | | not implemented |
| Shell jobs with java monitor | ||
JITL jobs | | |
| JobSchedulerExistsFile | | it seems, there is a problem getting parameters: 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)
|
Overview
Content Tools