The utility creates reports in batch mode.
It can be called from the command line by using the following parameters:
UCYBDBRT -Xquery file [-CclientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type. -IINI file-Llanguage -Rreference date -S-Ooutput file-Tfile type]
All parameters are optional, except for the query file. A listShows entities in a grid view of all values and a description is provided in the document that describes the start parameters.
In batch mode, this utility reads the information for the evaluation reportA report provides more detailed information about a task's execution or a component. directly from the AE databaseA database is an organized collection of data including relevant data structures.. You can specify the parameters for the database in the corresponding configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. file UCYBDBRT.ini.
The following line shows an example. An evaluation report is created from the query defined for client 100 in the file jobtop10.d.xml.
UCYBDBRT -C0100 -XC:\AUTOMIC\Utilities\evaluation_reports\jobtop10.d.xml
The information that is provided in the report depends on the fields defined in your query. The fields shown below are available:
Field |
Description |
Definition |
Forecast |
Statistic |
---|---|---|---|---|
Archive 1 | First archive key. |
![]() |
![]() |
![]() |
Archive 2 | Second archive key. |
![]() |
![]() |
![]() |
Name of the workflow's Calendar objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task. |
|
|
|
|
Calendar in the schedule |
Name of the superordinate Schedule's Calendar object. |
|
![]() |
![]() |
Calendar keyword in the workflow |
Name of the calendar keywordThe attribute of a Calendar object that defines which days included in the calendar. in the workflow. |
|
|
|
Calendar keyword in the schedule |
Name of the superordinate schedule's calendar keyword. |
|
![]() |
![]() |
Changed by |
Name of the User object. |
|
|
|
Changed on |
Date of last object modification. Format: YYYY-MM-DD [HH:[MM:[SS]]] |
|
|
|
Created by |
Name of the User object. |
|
|
|
Earliest start time | Earliest start time in the format YYYY.MM.DD HH:MM:SS. |
![]() |
![]() |
![]() |
End time | End time in the format HH:MM:SS. |
![]() |
||
Expected end |
Expected end time in the format YYYY.MM.DD HH:MM:SS. |
|
|
|
Expected runtime in seconds. |
![]() |
|
![]() |
|
Expected start time |
Expected start time in the format YYYY.MM.DD HH:MM:SS. |
|
|
|
Host |
|
![]() |
|
|
Host type |
Job type. Allowed values: "BS2000", "GCOS8", "JMX", "MPE", "MVS", "NSK", "OA", "OS400", "R3", "SIEBEL", "UNIX", "VMS" and "WINDOWS" |
|
|
|
Int. account | Internal account. |
![]() |
![]() |
![]() |
Interval |
Interval of the Time-Event object. |
|
|
![]() |
Job content |
Text contained in the scriptA particular Automation Engine object type.. |
|
![]() |
|
Workflow |
Name of the superordinate workflow. |
|
|
![]() |
Last used on |
Date of last object usage. Format: YYYY-MM-DD [HH:[MM:[SS]]] |
|
|
|
Login object |
Name of the Login object in jobs. |
|
|
![]() |
Login information of the Login object in jobs. |
|
|
|
|
Object name |
Name of the object. |
|
|
|
Object type |
Short form of the object typeAn individual object is provided for the individual activities: There are User, UserGroup, Notification, Cockpit, CodeTable, Documentation, Event, Agent, FileTransfer, Group, Include, Job, Workflow, Calendar, Login, Client, RemoteTaskManager, Schedule, Script, Server, Sync, Variable and TimeZone objects (e.g.: JOBP) |
|
|
|
Output device (R3_ACTIVATE_REPORT) |
Name of the output device. |
|
|
![]() |
Report (R3_ACTIVATE_REPORT) |
Name of the report. |
|
|
|
Return code |
Return code of the taskAn executable object that is running. Tasks are also referred to as activities.. |
|
|
|
Number of the execution. |
|
|
|
|
Runtime |
Duration of the execution in seconds. |
|
|
|
SAP client |
Client in SAP in Login objects of jobs. |
|
|
|
SAP user |
Name of the SAP user in Login objects of jobs. |
|
|
|
Schedule |
Name of the superordinate Schedule objectIt starts executable objects periodically. A particular Automation Engine object type.. |
|
|
![]() |
Start time in the schedule |
Start time in the format HH:MM:SS. |
|
|
![]() |
Start time | Start time in the format HH:MM:SS. |
![]() |
||
Status |
For filter criteria: One or more system return codes are separated by commas (for example, 1900, 1920). In the analysis report: The long texts are output instead of the numbers (for example, ENDED_OK). |
|
|
|
Name of the Time-Event object. |
|
|
![]() |
|
Title | Title of the object. |
![]() |
![]() |
![]() |
Type of parentThere are different ways of activating objects. The originator of an activation is referred to as the superordinate task (parent). See also: Child; Children object | Object type of the parent object. |
![]() |
![]() |
![]() |
Variant (R3_ACTIVATE_REPORT) |
Name of the variant. |
|
|
![]() |
Version |
Version number of the object. |
|
|
|
See also:
Task Evaluations
Graphical Interface of the Reporting Tool
XML Files of Queries
Start Parameters
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |