I updated to V3.3. And changed the properties of a JAL script to use the new Advanced features of the ‘ALL Day’ job submission option which works great.
However if I re-start the scheduler, the job disables, and in edit mode the validation button disables.
If I change the job to another schedule, i.e. ‘Daily/Weekly’, the job remains enabled.
Is there a limit to the number of characters a JAL script can contain? As this seems to me why the validation button disables after re-starting.

Check the job log file. There should be some message explaining why the job was disabled, unless you do it programmatically.

Anyway, I don't see how all this could be related to the disabled validation button. Nor the JAL script size should affect that.

: I updated to V3.3. And changed the properties of a JAL script to use the new
: Advanced features of the ‘ALL Day’ job submission option which works
: great.
: However if I re-start the scheduler, the job disables, and in edit mode the
: validation button disables.
: If I change the job to another schedule, i.e. ‘Daily/Weekly’, the job remains
: enabled.
: Is there a limit to the number of characters a JAL script can contain? As
: this seems to me why the validation button disables after re-starting.

: Check the job log file. There should be some message explaining why the job
: was disabled, unless you do it programmatically.

The job is set using the wizard. I can save the scheduler and all looks fine, the job stays enabled. If I re-start the scheduler it disables with no messages to the job file.
Not only does the job disable, the queue re-sets to default, detached unchecks itself, and the advanced entrys for start and end time go back to zero.
: Anyway, I don't see how all this could be related to the disabled validation
: button. Nor the JAL script size should affect that.
So the disabling of validation is a separate problem.

Are you sure the job database file gets saved? Is the file located on a network drive?

Do you have a 24x7 service running in the background? Does the service have "automatically save changes on exit" option turned on in the Tools/Options?
Do you have jobs that change properties programmatically? This can lead to the in some situations (concurrency) when the service overrides job database file and you loose your changes.

Try creating a new job using Job Wizards "copy properties of existing job" option. Please let me know how the new job behaves before and after the restart.

: The job is set using the wizard. I can save the scheduler and all looks fine,
: the job stays enabled. If I re-start the scheduler it disables with no
: messages to the job file.
: Not only does the job disable, the queue re-sets to default, detached
: unchecks itself, and the advanced entrys for start and end time go back to
: zero.
: So the disabling of validation is a separate problem.