Administration Guide > Utilities > AE DB Reporting Tool > Creating Evaluation Reports

 Creating Evaluation Reports

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.

Calendar in the workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."]

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 runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start).

Expected runtime in seconds.

Expected start time

Expected start time in the format YYYY.MM.DD HH:MM:SS.

 

 

Host

Name of the agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host in jobs.

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: userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management.

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..

 

 

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 .

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).

 

Time eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase.

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