I have an executable job that runs a script job. The script job errors out. There is no entry in the job log except to say that the job has been disabled. I noticed that I can run the script job without a problem. Is there a change that we no longer need to call a script job from an executable job?

I think you just need to refresh the log view (View/Refresh menu)

The script job in your case runs as a separate process. Because of that it does not update log displayed on the main scheduler screen. It only writes to the job log file. When you refresh the view, all records should appear on the screen.

: I have an executable job that runs a script job. The script job errors out.
: There is no entry in the job log except to say that the job has been
: disabled. I noticed that I can run the script job without a problem. Is
: there a change that we no longer need to call a script job from an
: executable job?

: I think you just need to refresh the log view (View/Refresh menu)

: The script job in your case runs as a separate process. Because of that it
: does not update log displayed on the main scheduler screen. It only writes
: to the job log file. When you refresh the view, all records should appear
: on the screen.

Thought of that, I doesn't work. It just shows that the job was disabled with no error entry.

Do you have by any chance "do not log" option checked for that job?

: Thought of that, I doesn't work. It just shows that the job was disabled with
: no error entry.

: Do you have by any chance "do not log" option checked for that job?

No I have left everything as the default.

David, please post more details on this job and issue.
Exact command line you use to run the job.
The complete message in the job log file and 3 or 4 previous messages.
Does the script job actually run?
Are there job start/end messages in the job log?
Does the job run any notification actions before, after or on error events?
Is this sync or async job?

: No I have left everything as the default.

: I think you just need to refresh the log view (View/Refresh menu)
tororof9r9r9f0frokk

fofof9ofotoot.
foofoofogolgfpogoo
fof9fglglf
: The script job in your case runs as a separate process. Because of that it
: does notfff update log displayed on the main scheduler screen. It only writes
: to the job log file. When you refresh the view, all records should appear
: on the screen.
74747eheydududyue3748484884854
dffnfnmmfkm 40495480--_igitii