Construction own JOB report

Hello I would like to create with of a job with ftp file transfer "download" a state is indicated.

Unfortunately, it functions indicates only in the debug mode then the tool writes in a scheduler-YYYMMYY-TIME.log and creates a html report.
In the normally mode "job started and job finished" will use only indicated with Scheduler.logAddMessage is written it only in scheduler.log and not in the scheduler-YYYMMYY-TIME.log and is not evaluated in the html report.

Example:
Scheduler.logAddMessage('INFO', @V"job_id", '@V"job_name"','Download successfull);
Scheduler.logAddMessage('WARNING', @V"job_id", '@V"job_name"','no download');

Use LogAdMessageEx instead of LogAddMessage. It will do what you want.

it doesn't work
i have edit the job to logAdMessageEx

Scheduler.logAdMessageEx('WARNING', @V"job_id", '@V"job_name"','no download');

the scheduler.log error message
An error occurred while executing automation script: TypeError: logAdMessageEx is not a function.

With which comand can I pass to the scheduler message error state code?

I meant logAddMessageEx and I thought you are using 24x7 Scheduler Windows edition and using JAL script because you didn't say what you are running.

Now I know that you are running the Multi-platform Editor, have I known it earlier my response would be completely different.

	Quote:
	Scheduler.logAddMessage('INFO', @V"job_id", '@V"job_name"','Download successfull);

Here you got a syntax error - the last string is not closed, missing closing quote

	Quote:
	Scheduler.logAddMessage('WARNING', @V"job_id", '@V"job_name"','no download');

This seems to be ok.

Now
scheduler-YYYMMYY-TIME.log and scheduler.log have nothing directly to do with logAddMessage. The datetime file is created when the log file reaches certain size as controlled in the scheduler options. Basically when the log reaches certain point, the scheduler renames the old schedule.log file and starts a new one. You can control the turn-over size in the Options. The HTML reports are updated on each write to a log file, so that if configured properly, they should not be affected by the turn-overs.

And one more thing, do not abuse the logging feature, otherwise the performance will suffer and HTML logging will not work as expected. Only essential events, errors, and warnings should go to the log. If you have a bunch of jobs that run every minute each, first of all set them not to log regular events, for such jobs logging is pointless, creates a lot of "noise" making difficult to see/find important events in the logs written by other jobs. Secondary jobs running every minute or so should be converted to start-on-startup background jobs and run never ending loop jobs to avoid wasting precious system resources for each job start/stop and improve entire system scalability (less memory, less files, less CPU, less everything is needed)