In this section:
Log reports are stylized HTML format and appear in a separate browser window. You can search, print, or save the log report. The log report displays information according to your specifications in a separate browser window. One log record is produced for each scheduled job run in the specified time frame.
In this section:
Information about a schedule, such as date, time, execution status, and recipients of a distributed job, can be accessed by running a log report and checking the job status. For more information, see ReportCaster Console .
Log reports enable you to view information about a distributed job, such as whether or not the job executed successfully, when the scheduled output was distributed, in what format the distributed output was sent, and the method of distribution. Log reports are stylized HTML format and display in a separate browser window. You can search, print, or save the log report.
The log file accumulates information. You should periodically purge log records to manage the number of log reports stored in the Repository, as well as the performance of log report information that is displayed.
The list in the right panel provides basic information about the job execution, including the job ID, the time the job started running, the amount of time it took to complete the execution of the job, and the general status of the job. To view a full log report for a job, double-click the job in the job list.
Values from &ECHO variables and -TYPE commands in procedures appear in log reports. The &ECHO variable displays command lines as they execute in order to test and debug procedures. The -TYPE command enables you to comment and evaluate your code for informational and debugging purposes. For example, if the following procedure is scheduled using ReportCaster, it may produce a log report similar to the example that follows this procedure.
Note: The second -TYPE is on a single line within the report procedure (FEX).
-SET &ECHO='ALL'; -TYPE Regional Product Sales Forecast -TYPE Parameter RATE is passed into report to forecast potential sales growth -DEFAULT &RATE = .05; -DEFAULTH &WF_TITLE='WebFOCUS Report'; TABLE FILE GGSALES SUM DOLLARS COMPUTE GROWTH/D12.2= (DOLLARS * &RATE) + DOLLARS; AS 'Sales, Forecast' BY REGION BY PRODUCT ON TABLE PCHOLD FORMAT HTML ON TABLE NOTOTAL ON TABLE SET PAGE-NUM NOLEAD ON TABLE SET SQUEEZE ON ON TABLE SET EMPTYREPORT ON ON TABLE SET HTMLCSS ON ON TABLE SET HTMLENCODE ON ON TABLE SET STYLE * TYPE=REPORT, TITLETEXT=&WF_TITLE.QUOTEDSTRING,$ ENDSTYLE END
The following image shows an example of the log report.
Note: For more information about &ECHO variables, see Testing and Debugging a Dialogue Manager Procedure in the Developing Reporting Applications manual.
Another resource for tracking schedules is the schedule job status. The schedule status provides a list of scheduled jobs that are in the Distribution Server queue. Status information includes the schedule ID, the time it started running, and the status of the job.
To access the schedule status information, click the Log Reports tab, as shown in the following image.
For more information about job status, see Job Status.
The Schedule Log Options dialog box appears, as shown in the following image.
If you select Date, you will have the option to specify your search using start date and time and end date and time parameters.
The log reports that match your search criteria appear, as shown in the following image.
The log report first lists the job description for the record, which is the unique description identifier that you specified when you created the schedule. Underneath the Job Description, the left column of the log report includes the following information:
In the second column, the log report specifies messages consisting of the following:
The Basic Scheduling tool opens.
The Log Reports panel appears, as shown in the following image.
When viewing a log report, be aware of the following considerations.
Task and Report Names
The ReportCaster Log references WebFOCUS folders and procedures (FEXs) by their path and file names and not their descriptions.
ReportCaster cannot validate email addresses since email validation is performed by the mail server. The log report will include any email addresses validated by the mail server and returned to ReportCaster.
Burst Value: value is not in the database.
FILE filename SUCCESSFULLY DISTRIBUTED TO destination FOR burst value.