Page History

Within the JITL features we have some jobs which are used to launch commands. One way to define the commands are in the parameter descriptionsvalues.  Another way is to define the statement in the script part of the job instead of the parameter command. All other needed parameters remain in the parameter part of the jobs.

In the case that a statement is defined in the script part and also a command parameter is given the command parameter is executed. To show this priority we define an illegal command parameter and the correct version within the script part. A second test without the command parameter shows the correct execution of the statement defined in the  script part.used.

We have these JITL jobs which are involved in this topic:

...

This job executes statements in a database. These can be database procedures or SQL statements

Error execution

Image Removed

This configuration causes the error: java.lang.Exception cannot be cast to com.sos.JSHelper.Exceptions.JobSchedulerException

Correctly executed

...

Configuration  in JOE

Image Modified

JITL Job JobSchedulerPLSQLJob

...

The job executes PL/SQL code for oracle Oracle databases

Error execution

Image Removed

 This configuration causes an error stop with : ERROR [main] (JobSchedulerPLSQLJob.java:109) - SQL Exception raised. Msg='ORA-00900: Ungültige SQL-Anweisung

Correctly executed

When the command parameter is deleted the job is executed correctly

Configuration  in JOE

Image Added

   Image Removed

JITL JobSchedulerSSHJob

...

For testing of this job the  free edition of copSSH is used.

Error execution

Image Removed

This configuration causes the error : (SOSSSHJob2.java:389) - stderr = bash: xyz: command not found

The correct command defined in the script part is not executed.

Correctly executed

Without the command parameter the job finished correctly.

Configuration  in JOE

Image Added

 Image Removed