The report parser log provides detailed status/diagnostic messages on report parsing, including the date and time of parsing and outcome. These messages are listed below, along with the likely problem and a suggested course of action.
When interpreting the messages below, bear in mind that anything with a "$" in front of it is a substitution variable. In the log messages, the "$" will be replaced by appropriate data. Also, note that "$@" is a special Perl variable which contains the underlying error from the operating system.
"Unable to open report configuration $reportconfig\n.$@"
Problem: A file named "$reportconfig" was downloaded, but no matching configuration file exists.
Solution: Either download a new file with the right name, or create a matching report configuration file. Re-download the report file.
"Invalid character '.' (period) in report id ($reportid)"
Problem: Periods are not allowed in report id names.
Solution: Edit the report configuration to remove the period. Re-download the file.
"Configuration filename and input filename do not match: Config says '$reportfilename', Filename is '$filename'"
Problem: As a double-check, the report configuration file contains the filename of the report as one of its elements. This message indicates that the report filename does not match the filename in the report configuration file.
Solution: Either edit the report configuration or re-download the file with the correct file name.
"No profile specified, using default (LANDSCAPE) for $reportid"
Problem: This is an informational message. It just reminds you that you have not specified a profile, which governs the layout of the report as a PDF document, so the default LANDSCAPE layout is being used.
Solution: If this is not the desired layout, delete the report (administrator interface), edit the report configuration, then re-download the report.
"Page keys are required for VBS authorization (report $reportID)."
Problem: You specified VBS authorization for the report, but did not include any page keys in the report definition.
Solution: In the report configuration wizard in the administrative interface, either change the report authorization to ALL, or add page keys. Re-download the report.
"Verification value mismatch: Report: $reportID Found: '$literal' Looking for: '$vervalue'"
Problem: In the report configuration file, you specified a verification value. The parser looked for this value at the specified location, and instead found another value.
Solution: Examine the report to make sure it is the correct report. If so, make sure that the indicated verification value exists in the report. If there is a mismatch, edit the report definition to correct the mismatch. Re-download the report.
"System date substituted for invalid date '$dateliteral'"
Problem: The date found on the report could not be parsed. The value found is indicated in the message.
Solution: Check the report to be sure it has the correct date value. If it does, verify the report configuration in the administrative interface. Delete and re-download the report if a valid date exists on the report, and you've fixed the report definition. Set the date row, column and length to 0 in the wizard if values do not exist.
"System time substituted for invalid time '$timeliteral'"
Problem/Solution: Same as above except TIME instead of DATE.
"Input file appears to be empty for report $reportid"
Problem: It looks like the downloaded file is empty.
Solution: Examine output of ftp on the host for errors or problems. Re-download the file.
"Warning: page too long on $overflow_counter pages for report $reportid."
Problem: The page length specified in the report configuration is too short.
Solution: Increase the page length to the proper value. Delete the report on the server and re-download from the mainframe.
"Warning: Report $reportid has no authorized user-level groups."
Problem: There is no user group that can access this report because the repository configuration has no default group, and no groups are specified in the report configuration.
Solution: Add a default group to the repository in the repository configuration wizard, or add a group or groups to the report configuration. In the administrator interface, add authorized groups to the report so this report is accessible by some user.