You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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 set the command parameter is executed. For a test of this fact 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:

JITL Job JobSchedulerManagedDatabaseJob

Class name sos.scheduler.managed.JobSchedulerManagedDatabaseJob

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.scheduler.db.JobSchedulerPLSQLJobJSAdapterClass


JITL JobSchedulerSSHJob

Class name sos.scheduler.job.SOSSSHJob2JSAdapter


 

  • No labels