We upgraded to version 1.13.1 of both the Scheduler and YADE.
Now our file transfer jobs run with settings different to the profile in our XML settings file.
for example we have these settings:
But the Yade task runs with these values:
Mostly our tasks are triggered by folder-monitoring but a few times a day we run an extra time-scheduled order just to check that no files have been missed. Now these extra orders produce an error when there are no files ready for transfer.
SOSDExJSAdapterClass ended with error: com.sos.JSHelper.Exceptions.JobSchedulerException: SOSJADE_E_0100: No filename found which match the criteria as specified using the regular expression
It shouldn't be an error because we have specified "DisableErrorOnNoFilesFound = true".
See the attachments with our XML settings file, job definition and one of the task logs.
Screenshots
Last edit: Brendon 2019-11-26
The setting is read correctly when we use "force_files" in the xml Job Definition file.

<param name="force_files" value="false">
I guess it probably works if this setting is used in an INI formatted settings file.
We can use that as a work-around but our preference is to use the directive DisableErrorOnNoFilesFound in our XML configuration file: Eurofins_TransferSettings.xml (sourceforge.net)
Last edit: Brendon 2019-11-27
I noticed that when the XML configuration file is imported to the YADE editor of the JOC then it also reads DisableErrorOnNoFilesFound as empty even though this is correctly filled in the xml file.

Screehshot
Interestingly the import does correctly read the value of CheckSteadyCount as 30 and not 10 as when the job is executed so it appears the error happens differently for the two different settings.
Last edit: Brendon 2019-11-29
Hi Brendon,
I am able to reproduce the issue of boolean values with release 1.13.1 Windows x64 and a new change request has been created in our change management system for the same.
Please refer to the below URL for your reference:
Please refer JOC-796 for release date and updates.
Thanks and Best Regards
Anuj Mandloi
Last edit: AnujM 2019-12-05
It is nice that you can reproduce the problem with importing XML into the JOC and have fixed it.
My original report was about how the Job Scheduler Master runs jobs from an XML configuration file. It wrongly interprets the values of at least two settings:
It runs YADE with values of 10 and disabled = false respectively as seen in the output:
Have you been able to also reproduce these errors and fix them?
Last edit: Brendon 2019-12-05
Hi Brendon,
All the above issues you are facing relates to the newly created JIRA issue JOC-796 and will be solved in the next release 1.13.2. As there is an error in the current release 1.13.1 of JOC.
Thanks and Best Regards
Anuj Mandloi