The "Scripted Report" Option functionality for Windows job

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

When using  "Scripted Report" options in his Windows jobs.

The jobs end "ENDED_OK - ended normally", but the reports fail with a "FAULT_OTHER" error.

Environment

Automatic Automation V 24.x
Windows Agent V 24.x

Resolution

Scripted report is not a tool writing the report to a file.

Explanation

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 as described in the List of Agent Variables, 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#

And the same is documented on out documentation page.

search for heading " Defining When and Where to Store Job Reports: Windows-Specific Options " from above documentation link.