The jobs sos.scheduler.job.JobSchedulerSSHJob and sos.scheduler.managed.JobSchedulerManagedDatabaseJob can both use a "command" parameter

Current Situation

• If both jobs are used in a job chain then the parameter command cannot be used as an order parameter due to disambiguity.
• If this parameter is identified as a job node parameter then it will be removed having passed the job node.

Resolution
The following alternative solutions are available:

1. Rename the parameter to ssh_command. This solution is downwardly compatible.
2. Use node parameters
3. Use the name of the job and/or the job status for additional information, like a namespace. Example
   • JobSchedulerSSHJob.command=dir
   • JobSchedulerSSHJob:700.command=dir
     This will be possible when JITL-165 is approved.
4. Instead of using a parameter you could add the respective SSH or SQL command to the <script> element as stated in the article How to add commands to JITL Jobs