For detailed instructions on using the CONTROL-M/EM Reporting Facility, see the CONTROL-M User Guide.
The following historical reports are available using the Reporting Facility:
■ SLA Analysis—presents a histogram displaying the number of services that completed late, on time, and did not complete, within a given time period.
■ History—lists the final status of each service during a given time period.
■ Details—lists the final status of specific services during specific dates, and details of their problematic jobs. The severity level of problematic jobs that are displayed depends on the settings of the ReportProblematicJobs system parameter.
By default the Details report shows all status changes of the service. You can select the Show final state only check box during report definition to limit this display to the final status only.
In addition to these historical reports, two additional reports cross-reference jobs and their related services:
■ Service-Jobs—lists jobs and their related services.
■ Jobs-Service—lists services and their related jobs.
These reports are only available for jobs that are currently active.
Generating reports using the Web Client or bim_report utility
You can also generate reports for services that have completed execution by
■ clicking Report in the BMC Batch Impact Manager Web Client
■ executing the bim_report utility from the command line (on both UNIX and Microsoft Windows)
NOTE
The number of days for which data is available for reports is determined by the value of the NumberOfReportDays system parameter (see page 115).
Generating reports using the Web Client or bim_report utility
These reports track changes to the status of a service, and include the following information:
■ the name of the service
■ the order date of the service
■ the original status of the service
■ the revised status of the service
■ the date and time that the status of the service changed
■ Remedy ticket number and status (if a ticket was issued)
To generate reports from the BMC Batch Impact Manager Web Client:
1 Click Report to display the Report window.
2 In the Report window, enter values for the fields that are described in Table 13.
3 Click Print. A report, similar to the sample in Figure 10 on page 117, is printed.
NOTE
The number of days for which data is available for reports is determined by the value of the NumberOfReportDays system parameter (see page 115).
Table 13 Fields used to generate reports Field Description
Show Service Events
Date and time criteria. Only services in this range are included in the report.
From Date Services running as of this date are included in the report.
Dates are specified in dd/mm/yyyy or mm/dd/yyyy format (depending on the value of the DateFormat system
parameter).
From Time Services running as of this time on the From Date are included in the report.
To Date Services running until this date are included in the report.
Dates are specified in dd/mm/yyyy or mm/dd/yyyy format (depending on the value of the DateFormat system
parameter).
To Time Services running until this time on the To Date are included in the report.
Filter by Service Name
Services that match the name in this field are included in the report.
Generating reports using the Web Client or bim_report utility
Figure 10 A Sample Report from the BMC Batch Impact Manager Web Client
To generate reports from the command line (bim_report):
At the command line, enter the following command:
-TIP
The bim_report utility can be run both on Microsoft Windows and UNIX operating systems from their respective command lines.
bim_report -U username -P password
[-O output file name]
[-N service name]
[-F from date]
[-T to date]
Table 14 bim_report parameters from the command line (part 1 of 2)
Parameter Description
-U username Name of the CONTROL-M/EM user running the report, for security purposes. Mandatory.
-P password Password of the CONTROL-M/EM user running the report, for security purposes. Mandatory.
-O output file name Name and full path of the output file that will contain the
generated report. Optional. If not specified, the report is displayed on the screen but is not saved in a file.
Generating reports using the Web Client or bim_report utility
-N service name Name of the service that should be listed in the report. Optional. If not specified, the report runs for all services.
-F from date Services whose order date (Odate) is the same as, or later than, this from date value are included in the report. The date and time format is DD/MM/YYYY_HH:MI:SS or
MM/DD/YYYY_HH:MI:SS format (depending on the value of the DateFormat system parameter). Optional.
If not specified, services whose order date was on the previous day or later are included in the report.
-T to date Services whose order date (Odate) is the same as, or earlier than, this to date value are included in the report. The date and time format is DD/MM/YYYY_HH:MI:SS or
MM/DD/YYYY_HH:MI:SS format (depending on the value of the DateFormat system parameter). Optional.
If not specified, services whose order date is the current date and time or earlier are included in the report.
EXAMPLE
This example is for Microsoft Windows:
bim_report -U emuser -P empass
-O D:\Temp\my_report.txt -N CD_service
-F 26/02/2004_08:34:00 -T 28/02/2004_23:34:00
Table 14 bim_report parameters from the command line (part 2 of 2)
Parameter Description
C h a p t e r
8
8
Managing exceptions for expected run time statistics
To determine if a critical service will finish on time, BMC Batch Impact Manager must compare the actual run time for each job to its expected run time.
You can set up BMC Batch Impact Manager to determine the expected run time from different sources, using a combination of previously compiled CONTROL-M
statistics, system parameters, and exceptions (manual overrides).
This chapter presents the following topics: