ReportCaster

In this section:

The following are documentation enhancements for ReportCaster:

Totals that display in the subfoot of a report are incorrect when the report also issues a WHERE TOTAL and is burst and distributed by ReportCaster. This problem occurs with Reporting Server Releases 7.7.03, 7.7.04, and 7.7.05. Contact Customer Support to request the fix for Reporting Server Release 7.7.03. This problem is fixed in Reporting Server Release 7.7.04 Gen 789 and 7.7.05 Gen 124.
The HTML ODP Format is not supported on z/OS.
When WebFOCUS is installed on a 64-bit machine with a Linux OS, an attempt to logon to the ReportCaster interface may fail when the ReportCaster repository is an Oracle database and the Oracle driver fails to find the locale. A workaround is to use an alternate version of the Oracle driver or add -Duser.country=US (or other country) in the Application Server system setting.
You can create users in Managed Reporting using up to 128 characters. ReportCaster does not support User IDs that are greater than 48 characters. If you create a user in Managed Reporting with more than 48 characters and attempt to assign ReportCaster privileges to that user, you will encounter compatibility errors.
The Scheduling Tool Template has been revised to include LibraryFTPCustom1 as an additional template option.
An administrator creating or maintaining a schedule in ReportCaster 7.7.01 erroneously had the ability to use the Save As function to save a schedule under a different user. In Version 7 Release 7.02 and later, this has been corrected and schedules can only be saved under the original owner.
The length of the Notification Email string has been increased from 75 to 255. However, the Javadoc has not yet been updated to reflect this change.

ReportCaster Applet Interface JVM Issue

The toolbar icons on the ReportCaster Developer and Administrator (applet) interface are incorrectly spaced when the user browser is configured to use Sun Microsystems JVM Versions 1.5_08 and higher on Windows 2000 and Windows 2000 Server, and with JVM Versions 1.5_07 and higher on Windows 2003 Server. This is a documented problem in the Sun Microsystems Release Notes, which are found at:

http://www.oracle.com/technetwork/java/javase/releasenotes-142123.html

Sun Microsystems is tracking a number of related reported problems in this area. The main bug ID number is 6349010. The bug ID number that specifically references JVM 1.5_08 is 6234686. Although the description information on these problems states that it is for Windows XP, the problem within the ReportCaster applet interface is only occurring on Windows 2000 and 2003. This is not a problem if the user browser is running on Windows XP.

Evaluation has been performed with the Sun Microsystems JVM 1.6 Version and this ReportCaster applet toolbar button issue has been confirmed not to occur with Windows XP, 2000, and 2003. This is a cosmetic issue and does not impact ReportCaster functionality.

Top of page

Opening Excel Files Using Outlook Web Access Mail Client

There is a known issue opening Excel files distributed by e-mail to an Outlook® Web Access mail client due to Outlook attachment blocking. For more information about Outlook Web Access attachment blocking, go to the following URL:

http://support.microsoft.com/kb/555001.

The alternative for this issue is to zip the Excel file(s) before distribution. For information on zipping scheduled output, see the ReportCaster End User's Manual.

Top of page

Opening Excel and PDF Files Distributed by ReportCaster to Managed Reporting for WebSphere 6.1

You cannot open Excel and PDF reports in Internet Explorer if the reports were distributed to Managed Reporting on a WebSphere 6.1 application server configured with Java 1.5.

This problem does not occur with the following:

Internet Explorer using the Tomcat application server
Firefox browser

Top of page

Distributing Scheduled Output Using SFTP

When distributing scheduled output using SFTP, you must specify the fully-qualified domain name.

Top of page

Issues When Using Informix

When ReportCaster is configured with Informix, the error java.net.UnknownHostException occurs when a schedule is run and the mail server specified is invalid.

Top of page

Web Browser Issues

The following are Web Browser issues when using ReportCaster:

When using the Firefox browser to access the ReportCaster API Help from the WebFOCUS Online Help, a Page not found error message displays. You must change the URL in the Firefox browser address window from:
```
ibi_html/javaassist/intl/EN/help/..\..\..\..\..\javadoc\rcaster\help\index.html
```
to:
```
ibi_html/javadoc/rcaster/help/index.html
```
The ReportCaster Scheduling Wizard that opens from Dashboard is not resizable in Internet Explorer. It is resizable in Firefox.
When using the Firefox browser, you are unable to see multiple entries in the Distribution List. The Distribution List Destination column does not scroll to show all characters for values that exceed the display width of the Destination column.

Top of page

Help Option in Email Address Search Dialog

The Help option from the Email Address Search dialog does not display online help. The alternative is to use the online help Index and enter Address Search in the keyword entry field to locate and view the online help information for Address Search.

Top of page

Opening ODP Reports in the Library

Under certain conditions, you may receive a Siteminder authentication prompt when you attempt to open an On Demand Paging (ODP) report in the Report Library by clicking the report in the left pane of the Library interface. (This prompt does not appear when you open the report in a separate window, that is, when you select the report and click the Open icon.)

If you receive the Siteminder authentication prompt, enter the requested information, then the report will open in the right pane of the Library interface.

Top of page

Secondary Run Interval Ignored When Schedule Updated

When a schedule is updated, the next run time is recalculated based only on the primary run interval. This means that if a schedule that includes a secondary run interval is updated before the secondary schedule is able to run, then the secondary run interval is ignored and the NEXTRUNTIME is calculated based on the primary interval.

For example, a schedule exists that is set to run daily at 2:00 PM with a secondary run interval of every 10 minutes from 2:00 PM to 3:00 PM. When the schedule runs at 2:00 PM, the NEXTRUNTIME is reset to run at 2:10, which honors the secondary run interval. If this schedule is updated at 2:03 PM, the NEXTRUNTIME is recalculated to be 2:00 PM the next day, rather than 2:10 PM on the current day.

WebFOCUS