Job Reports

When objects are executed, the system generates various types of reports that track what happened during execution. The execution of Job objects can generate extra reports. As a developer an object designer, you define when to generate them and where to store them on the platform-specific page of the Job definition. Some Job objects have extra reporting options.

Configuration Options Common to all Job Types

When you configure a Job, you define where to store the Job report and when to generate it in the Job Report section on the platform-specific page.

Where to Store the Report

You have two options. You can select one or both simultaneously:

Store to: Database means that when the Job has been executed, the process log available on the target system (on the Agent) is stored in the database.

When a Job has been executed on an Agent, the corresponding report is stored on the Agent computer. After the Automation Engine has written this data to the database, the report is automatically deleted from the Agent computer. If it cannot be deleted due to an error, the deletion process is not repeated and an error message is displayed.
Store to: File means that the process log is stored as a file on the target system (Agent).

When to Generate the Report

You have two options:

Generate: Always means that the process log of the operating system is always written.
Generate: On error only means that the process log is kept when an error occurs. Example, when the Job is canceled or aborted.

SQL Jobs

For SQL Jobs, you have the following additional option:

Add Agent Log: Activate this checkbox if you want also the agent messages on the execution of the job to be also included in the task.

Windows Jobs

The standard output (STDOUT) of Windows Jobs is written to the Job report. If you are using a program that cannot write to this standard output destination, you have two options:

External Output Files page

Specify any path of your choice to which the program should write the report.
Scripted Report option in the Windows page

This option is useful for programs whose outputs are supplied in files. If you activate it, the job reports contain the program outputs. You can assign the default output file to the program you are using.

With each job execution, a separate file is created for the job report. To retrieve the corresponding report file names, you can use the FILENAME_SYSOUT attribute. File names include the individual job's run numbers (RunID). To set the path for the job report, use the UC_EX_PATH_JOBREPOR variable and to read it, use the GET_VAR script function. You can then assign this information to the program you want to use.

Example:

:SET &job_report_path# = GET_VAR(UC_EX_PATH_JOBREPORT)
:SET &job_report_filename# = GET_ATT(FILENAME_SYSOUT)

isqlw -S PC1\SQL2000 -d TEST_DB -U sa -i c:\temp\test.sql -o &job_report_path#&job_report_filename#

For more information, see Output Pages.