Page last updated on February 17, 2010
The following is a list of problems reported for WebReport/400 along with the solutions that we
have developed for them. If you have a problem that is not covered here, ask us via
Index:
WebReport/400 Release 10 Problem Reports:
WebReport/400 Release 9 Problem Reports:
WebReport/400 Release 8 Problem Reports:
WebReport/400 Release 10 Problems:
When sending email from the WRKWEBSPLF list display, if I accidentally leave the
email address blank, I get a complicated error message returned that is confusing.
Several customers reported that this situation was very confusing for end users. This has now been
changed so that the list of spool files is shown again with an error message displayed at the bottom of
the screen. This is true when the email address is omitted or when the email address entered is in
an incorrect format.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 10.14
version of WebReport/400. The correction is available in PTF package WRPTF1015. E-mail us and request
the PTF package.
When I open an Excel file from WebReport/400, Excel reports that the file is corrupted
and it will not open.
and After running a process in WebReport/400, my session's local data area (LDA) is
changed.
We found that when an Excel file generated by WebReport/400 was opened on a PC running the new Win7
operating system, then you could get a message indicating that the file is corrupted. This has now been
fixed.
Also, we found that under certain situations, the session local data area could get altered by
WebReport/400. This too has been changed the the local data area contents will no longer be changed by
WebReport/400.
The fix for these problems is now available as a PTF. This PTF can only be installed on a Release 10.13
version of WebReport/400. The correction is available in PTF package WRPTF1014. E-mail us and request
the PTF package.
I have a front and back overlay specified in my spool file, but the back overlay
is not appearing in the converted PDF file.
We found a problem with the PDF conversion routine that was dropping the back overlay under certain
conditions. It has now been corrected with a replacement of the entire PDF conversion module.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 10.10
version of WebReport/400. The correction is available in PTF package WRPTF1011. E-mail us and request
the PTF package.
The EREPORT command fails when I specify a job name that contains a period.
The EREPORT and WREPORT commands were configured to not allow the period character in the field. This has
now been changed and the period will be accepted.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 10.09
version of WebReport/400. The correction is available in PTF package WRPTF1010. E-mail us and request
the PTF package.
My automatic routing process is terminating with a CPF0818 error.
We discovered that under certain circumstances, the automatic router could terminate with the CPF0818
error message. This has now been fixed.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 10.08
version of WebReport/400. The correction is available in PTF package WRPTF1009. E-mail us and request
the PTF package.
When I convert a spool file to *PDF format in the IFS, the USRDTA field does not
carry through to the internal document name list it does when sending email.
Based on a customer comment, we found that the logic for converting the TITLE(*USRDTA) parameter when
converting a spool file for storage in the IFS was incorrect. It has now been corrected to mirror the
way this is handled when emailing a spool file in *PDF format.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 10.06
version of WebReport/400. The correction is available in PTF package WRPTF1007. E-mail us and request
the PTF package.
I am getting the error code MCH0801 when converting a spool file into the IFS.
We found that release 10.04 of WebReport/400 contained a wrong program version. The correct program version
has now been included and is available with the PTF.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 10.04
version of WebReport/400. The correction is available in PTF package WRPTF1005. E-mail us and request
the PTF package.
WebReport/400 Release 9 Problems:
When converting a PCL spool file, the results are not lining up correctly.
For certain spool files that contain graphics created using PCL commands, we found that when certain
types of line graphics were used with curved ends, the curves were inverted causing the form alignment
to be off, even though the spool file print correctly on hard copy. This problem has now been fixed.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.31
version of WebReport/400. The correction is available in PTF package WRPTF932. E-mail us and request
the PTF package.
I am trying to use a color AFP overlay, but part of my spool file is getting
overlaid.
We found that with certain printer definitions, the color overlay can get applied in such a way that
portions of the spool file get get obscured or overlaid. This has now been corrected.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.30
version of WebReport/400. The correction is available in PTF package WRPTF931. E-mail us and request
the PTF package.
I added an XLS report model, but now it no longer appears on the display.
We found a problem with the XSL report model maintenance. The report model was created but the basic
record pointing to it was not saved. This has now been corrected.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.29
version of WebReport/400. The correction is available in PTF package WRPTF930. E-mail us and request
the PTF package.
When sending a report as a PDF, I found a line was missing from the report.
and When sending a report as a PDF, I found a line was missing from the report.
For the first problem, we found that in very rare situations when you are using an embedded #EMAIL
directive statement to distribute a spool file to multiple destinations, a situation could arise where a
line in the report could be dropped. When this happens, you will see that another line in the report
ends up getting duplicated. This problem has now been fixed.
For the second problem, we found that the program was ignoring the request for a report. This has
also been corrected.
The fix for these two problems is now available as a PTF. This PTF can only be installed on a Release 9.28
version of WebReport/400. The correction is available in PTF package WRPTF929. E-mail us and request
the PTF package.
When creating a *USER email routing, a new output queue is created.
When creating an email routing for the SEND2ME feature, a unique output queue is not needed. A customer
reported to us that WebReport/400 was creating these queues on their system and we found a problem in
the product that was causing this to happen. This PTF stops these user profile named output queues
from being created.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.26
version of WebReport/400. The correction is available in PTF package WRPTF927. E-mail us and request
the PTF package.
A new PTF is now available that addresses the following three issues in WebReport/400 along with one
new feature that is documented on the product updates page:
The fix for these problems is now available as a PTF. This PTF can only be installed on a Release 9.24
version of WebReport/400. The correction is available in PTF package WRPTF925. E-mail us and request
the PTF package.
Sometimes my application fails with an error when it is just a bad email
address that has been used.
Normally, WebReport/400 edits the email address to make sure that it is properly formed. When a bad
email address is found, an error entry is logged and that address is bypassed so that the application
does not get stopped with an error message. We found, based on feedback from a couple of customers,
that there was one situation where an error could be issued and processing would be suspended. We
have now tightened up the editting for email address form to avoid this problem.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.21
version of WebReport/400. The correction is available in PTF package WRPTF922. E-mail us and request
the PTF package.
When graphics placement was implemented this way, the graphic was getting dropped from the
output stream. This has now been corrected.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.19
version of WebReport/400. The correction is available in PTF package WRPTF920. E-mail us and request
the PTF package.
We identified a problem in our PDF conversion routine which has now been corrected. The entire
routine that converts spool files into PDF, CSV or XLS formats has now been updated. The new
routine not only corrects this error but improves the accuracy of the conversion.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.18
version of WebReport/400. The correction is available in PTF package WRPTF919. E-mail us and request
the PTF package.
The WEB0080 error is issued when WebReport/400 attempts to add a new user to the system directory, but
the user profile contains more than 8 characters. For releases of WebReport/400 up to this point, this
was resolved by having the customer perform a manual add for these profiles. With this PTF release,
WebReport/400 now deals with this situation gracefully and completes the directory addition without
failing.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.17
version of WebReport/400. The correction is available in PTF package WRPTF918. E-mail us and request
the PTF package.
We found that a certain customer systems running OS V5R4, the transmission process for the new *XLS
conversion format was failing with CPF9897. The text of the message refers to "reason code -107".
This appears to be a specification change in the OS on how IFS files are identified. We have now
coded a fix for this problem.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.16
version of WebReport/400. The correction is available in PTF package WRPTF917. E-mail us and request
the PTF package.
Based on customer feedback, we discovered a number of issues with the group email address function.
It would fail with certain large groups and with groups that had a high aggregate email length
factor. These have all been addressed now.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.15
version of WebReport/400. The correction is available in PTF package WRPTF916. E-mail us and request
the PTF package.
A problem with the resolution of this macro was found when it was used with the Automatic Routing
function in WebReport/400. A date prior to the current date could be shown instead of the correct
date.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.12
version of WebReport/400. The correction is available in PTF package WRPTF913. E-mail us and request
the PTF package.
We found that all activity was, in fact, getting logged, but some automatically routed processing
was getting logged with an incorrect date.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.11
version of WebReport/400. The correction is available in PTF package WRPTF912. E-mail us and request
the PTF package.
A problem was introduced into the WEBRTR program with PTF WRPTF910 that could cause this to happen
under certain error conditions. It has now been fixed.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.10
version of WebReport/400. The correction is available in PTF package WRPTF911. E-mail us and request
the PTF package.
Based on a customer report, we found that in the unusual situation where you are sending a report
in either *TXT format or *RTF format and line merging is specified AND the last line of the report
requires merging, that line was being omitted from the converted output report.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.09
version of WebReport/400. The correction is available in PTF package WRPTF910. E-mail us and request
the PTF package.
We found that when sending automatic email in *PDF format using imbedded #EMAIL directive statements
while an active printer session is attached to your job could result in message send failures.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.08
version of WebReport/400. The correction is available in PTF package WRPTF909. E-mail us and request
the PTF package.
We found that when all lines on a spool file were to be included for a CSV conversion, including all
report headings, then the very first line of each page was being dropped. This has now been corrected.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.07
version of WebReport/400. The correction is available in PTF package WRPTF908. E-mail us and request
the PTF package.
When using the EREPORTM command, we found that the initial version of this command only enforced
the ENDOPT parameter on the last of the multiple spool files processed. The PTF fixes this so that
the ENDOPT is processed against all of the spool files specified on the command.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.05
version of WebReport/400. The correction is available in PTF package WRPTF906. E-mail us and request
the PTF package.
We found that the new version code for extra wide reports that was introduced with version 9.04 had
this problem with it. This PTF corrects this issue along with a very intermittent problem with error
code MCH1202 being issued for when emailing a report.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.04
version of WebReport/400. The correction is available in PTF package WRPTF905. E-mail us and request
the PTF package.
WebReport/400 has now been updated so that this error code will no longer be issued.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 9.00
version of WebReport/400. The correction is available in PTF package WRPTF901. E-mail us and request
the PTF package.
WebReport/400 Release 8 Problems:
Some power users are deleting spool files while WebReport/400 is still processing
them, this causes an error in WebReport/400.
WebReport/400 has now been changed so that errors will not happen when a user deletes a spool file
while WebReport/400 is still processing it.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.14
version of WebReport/400. The correction is available in PTF package WRPTF815. E-mail us and request
the PTF package.
A customer reported getting an MCH0801 error when using the new EREPORTM command to send multiple
spool files as email in *PDF format. This has now been fixed.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.13
version of WebReport/400. The correction is available in PTF package WRPTF814. E-mail us and request
the PTF package.
Based on a customer problem report, we found that when a lot of destination email addresses were
stacked into a single TOINET parameter field, sometimes those addresses near the end of the string
were not getting processed. In the worst case, an error message could be issued indicating that
only a portion of the email address was being processed. This has now been corrected.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.12
version of WebReport/400. The correction is available in PTF package WRPTF813. E-mail us and request
the PTF package.
We found that sending a report as email in PDF format, the process would fail as described when
the TITLE parameter contained more than 50 characters. This has now been corrected.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.11
version of WebReport/400. The correction is available in PTF package WRPTF812. E-mail us and request
the PTF package.
When WebReport/400 was being used to send a report to an email address that is stored in the spool file,
WebReport/400 could fail under certain circumstances. The destination email address had to be referencing
and entry in the WebReport/400 Address Book and the file format had to be either *TXT or *RTF. The message
text on the failure refers to a reason code of -301 "negative response from SMTP server".
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.10
version of WebReport/400. The correction is available in PTF package WRPTF810. E-mail us and request
the PTF package.
Based on this customer's feedback, we found several areas of the HTML review process that were
not handling documents stored in the IFS correctly. The details of the IFS path were not showing
and the delete function was not actually removing the document file.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.09
version of WebReport/400. The correction is available in PTF package WRPTF809. E-mail us and request
the PTF package.
We discovered a problem that can happen when the size of the internet address field gets to be
longer than 210 characters. This has now been fixed and the full field length is now correctly
supported.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.07
version of WebReport/400. The correction is available in PTF package WRPTF807. E-mail us and request
the PTF package.
We found a problem with processing reports in PDF format with internally stored destination email
addresses using the #EMAIL directive statement. When the report had a width of more than 198
character positions, the rightmost information would be truncated. This has now been fixed along
with a related problem of not interpretting a CPI value of 16.7 correctly.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.05
version of WebReport/400. The correction is available in PTF package WRPTF806. E-mail us and request
the PTF package.
A customer using Microsoft Outlook reported that the text surrounding the expansion of the &TOLIST
macro that shows a list of destination email addresses in the body of the email was garbled and
poorly formatted. We found that some versions of Outlook, and other email clients, treat the fill
character equal sign that we were using as a special character. Changing the fill character to
another character resolved the problem.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.04
version of WebReport/400. The correction is available in PTF package WRPTF805. E-mail us and request
the PTF package.
I get a WEB0001 when attempting to send a report as email to an
internal list of email addresses.
We found a problem when attempting to process using the special *INT email destination address along
with a *PDF format conversion.
The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 8.00
version of WebReport/400. The correction is available in PTF package WRPTF801. E-mail us and request
the PTF package.
Contact Information
Phone: (518) 897-5002 Fax: (518) 897-5003
E-mail your questions or suggestions: 
To register your
E-mail address and receive automatic notification when this page is updated,
CLICK HERE.
WebReport/400 Problem Reports
Our logo, which is implemented as a *PAGSEG, is not appearing on a spool
file conversion of PDF format.
While converting an AFPDS spool file to PDF format, I get an MCH3601
error.
When using WebReport/400, a new user's task fails with message WEB0080.
When emailing a spool file as *XLS, it fails with error CPF9897.
I am having problems using the group address function.
Sometimes, the &DATE-EXPR macro resolves to the wrong date.
Not all activity is appearing in the activity log on my system.
Error code MCH3401 is issued from the WEBRTR program.
When sending a report as email, the report arrives with the last
line missing.
Automatic distribution of email using imbedded #EMAIL directives is
failing intermitently.
The first line is getting dropped on some CSV spool file conversions.
When using the new EREPORTM command, not all spool files are getting
processed for the ENDOPT parameter.
Page breaks on my *TXT and *RTF reports are sometimes in the wrong
place.
I am getting an error code MCH0801 issued from program EPRINTU when
using the WREPORT command.
MCH0801 when using the new EREPORTM command fixed.
Email reports are not getting delivered to all of the addresses specified.
WebReport/400 fails sometimes with a WEB0001 error when sending email.
When using the *INT option to extract and send a report via email using
an address stored in the spool file, WebReport/400 fails with a CPF9897 error.
The HTML Review option does not show the IFS path for my document.
I get an MCH0603 error when trying to update a set of destination
email addresses in the automatic routing table.
One report, with a very wide report width, it getting truncated when
sending it in PDF format using email addresses stored in the spool file.
When using the &TOLIST macro, there is garbled text in the list of
destination email addresses.
Kisco Information Systems
89 Church Street
Mt Kisco, New York 12983
Support@Kisco.com