The reports of Windows jobs have some special features.
Use the hostComputer, target system. specific Windows tab to specify when the jobAn Automation Engine object type for a process that runs on a target system.reportA report provides more detailed information about a task's execution or a component. should be stored in the databaseA database is an organized collection of data including relevant data structures. and/or in a file. It is also possible to define that a report should only be stored in case of an error.
The option Is generated by scriptA particular Automation Engine object type. serves programs whose outputs are supplied in files. If this specification has been activated, the job reports contain the program outputs.
With each job execution, an extra file is created for the job report. Use the attribute "FILENAME_SYSOUT" to retrieve these files' names which are composed of the individual run numbers (RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component .). The path for the job report can be set with the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. "UC_EX_PATH_JOBREPORT" and read with the script functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… GET_VAR. Finally, the retrieved information can be assigned to the program.
For 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#
Reports of Windows jobs show whether a particular job used a Windows Job object. The end of the AE Job Messenger then supplies different information:
For example: Without a Job objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task:
UCMDJP: *******************************************************************
UCMDJP: ** JOB 26181380 (ProcID:0000005796) ENDED AT 22.07.2004/15:02:10 **
UCMDJP: ** ------------------------------------------------------------- **
UCMDJP: ** USED: @ CPU **
UCMDJP: *******************************************************************
For example: With a Job object:
UCMDJP: *******************************************************************
UCMDJP: ** JOB 26181383 (ProcID:0000001416) ENDED AT 22.07.2004/15:03:09 **
UCMDJP: ** ------------------------------------------------------------- **
UCMDJP: ** USED: 0.188 CPU **
UCMDJP: ** 1154 PAGE FAULTS **
UCMDJP: ** 3 PROCESSES **
UCMDJP: *******************************************************************
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |