Problem Note 40692: Reporting Java exceptions on MVS and UNIX platforms and when the graph type is Java
If you use the SAS® IT Resource Management Adapter Setup wizard to create and deploy report jobs on a z/OS or UNIX platform, you might encounter one or more of the Java exceptions shown below.
ERROR:,Java class generated an exception.
ERROR: Physical file does not exist,/tmp/xxxxx.png
java.lang.ArrayIndexOutOfBoundsException: Array index out of range:
ERROR:,Java class generated an exception.
ERROR: Physical file does not exist,/tmp/xxxxx.png
NOTE: The SAS System stopped processing this step because of errors.
This version of the applet does not support Box chart
Element Exception: Box Name: Box
Element Exception: Legend Name: Legend,
java.lang.ClassCastException:,com.sas.graphics.util.ods.visualize.Box incompatible with
com.sas.graphics.util.ods.visualize.Overlay
ERROR:,Java class generated an exception.
ERROR: Physical file does not exist,/tmp/xxxxx.png
TidyDateMapper: XXXXXX not recognized as a XXXXXX format.
java.lang.Error: Bad XXXXXX format
You can eliminate the errors by identifying the report definitions that cause the error and running them in a separate report job where the graph format is set to PNG. To do this, follow these steps:
- Identify all of the report definitions that caused the errors by searching the report job log for the specific Java errors shown above.
- For each error, search backward until you find the string that identifies the report definition that caused it.
- For example: /*---- Report: ReportDefinitionNameHere ----*/
- Use a SAS IT Resource Management client to make a copy of the report job that caused the errors.
- In the original report job, remove the report definitions that caused the errors.
- Open the report job and double-click the Gallery transformation to open the Properties window.
- Click the Report Definitions tab.
- Find the report definitions that caused the errors and click the Remove button to remove them from the list.
- Click OK to close the Gallery transformation.
- Save the report job.
- Redeploy the report job.
- In the copied report job, keep the report definitions that caused the errors, remove the others, and change the graph format to PNG.
- Open the report job and double-click the Gallery transformation to open the Properties window.
- Rename the transformation on the General tab.
- Verify the settings on the Server tab.
- Change the graph format override setting to PNG on the Report Parameters tab.
- Remove report definitions on the Report Definitions tab.
- Keep the report definitions that caused the errors.
- Remove the other report definitions by selecting them and clicking the Remove button.
- Click OK to close the Gallery transformation.
- Save the report job.
- Redeploy and rerun the report job.
Operating System and Release Information
| SAS System | SAS IT Resource Management | z/OS | 3.2 | 3.2 | 9.2 TS2M3 | 9.2 TS2M3 |
| 64-bit Enabled AIX | 3.2 | 3.2 | 9.2 TS2M3 | 9.2 TS2M3 |
| 64-bit Enabled HP-UX | 3.2 | 3.2 | 9.2 TS2M3 | 9.2 TS2M3 |
| 64-bit Enabled Solaris | 3.2 | 3.2 | 9.2 TS2M3 | 9.2 TS2M3 |
| HP-UX IPF | 3.2 | 3.2 | 9.2 TS2M3 | 9.2 TS2M3 |
| Linux | 3.2 | 3.2 | 9.2 TS2M3 | 9.2 TS2M3 |
| Linux for x64 | 3.2 | 3.2 | 9.2 TS2M3 | 9.2 TS2M3 |
| Solaris for x64 | 3.2 | 3.2 | 9.2 TS2M3 | 9.2 TS2M3 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2012-03-26 17:25:45 |
| Date Created: | 2010-08-25 20:32:37 |