PAGE IN PROGRESS
Within the JITL features we have some jobs which are used to launch commands. One way to define the commands are in the parameter descriptions. Another way is to define the statement in the script part of the job instead of the parameter command.
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.
We have these JITL jobs which are involved in this topic:
Class SOSSSHJob2JSAdapter, ( used in job JobSchedulerSSHJob )
JITL Job JobSchedulerManagedDatabaseJob
Class name: sos-berlin.com/doc/JITL/JobSchedulerManagedDatabaseJob.xml
This job executes statements in a database. These can be database procedures or SQL statements
Error execution
This configuration causes the error: java.lang.Exception cannot be cast to com.sos.JSHelper.Exceptions.JobSchedulerException
Correctly executed
After the deletion of the command parameter the statement defined in the script part is executed correctly.
JITL Job JobSchedulerPLSQLJob
Class name sos-berlin.com/doc/JITL/JobSchedulerPLSQLJob.xml
The job executes PL/SQL code for oracle databases
Error execution
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
JITL JobSchedulerSSHJob
Class name sos-berlin.com/doc/JITL/SOSSSHJob2JSAdapter.xml
Error execution
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.