. Kisco Home : products : WebReport/i : Support : Problem Reports .
.
Page last updated on October 2, 2017

The following is a list of problems reported for WebReport/i along with the solutions that we have developed for them. If you have a problem that is not covered here, ask us via E-mail and we'll address your problem.

Please note that where appropriate, WebReport/i is referred to as WebReport/400, which was its product name under earlier releases.

To register your E-mail address and receive automatic notification when this page is updated, CLICK HERE.


WebReport/i Problem Reports

Index:

WebReport/i Release 13 Problem Reports:


WebReport/i Release 12 Problem Reports:


WebReport/400 Release 11 Problem Reports:


WebReport/400 Release 10 Problem Reports:


WebReport/400 Release 9 Problem Reports:



WebReport/i Release 13 Problems:

WebReport/i automatic report routing is occasionally failing on our system.

We found that when automatic routing was used with the special *INT destination reference and the report format type was set to *RTF, then it could fail. This has now been corrected.

The fix is available as a PTF. This PTF can only be installed on a Release 13.21 version of WebReport/i. The correction is available in PTF package WRPTF1322. E-mail us and request the PTF package.


A destination filename is being truncated when using the *FTP option on the WREPORT command.

The destination filename in the WREPORT command supports 100 characters, but we found that under certain circumstance, the filename could get truncated to a shorter value. This has now been corrected.

The fix is available as a PTF. This PTF can only be installed on a Release 13.18 version of WebReport/i. The correction is available in PTF package WRPTF1319. E-mail us and request the PTF package.


When using the WRKWEBSPLF command, the F4 function is not working for date selections.

The WRKWEBSPLF command (option 4 on the MASTER menu) displays a list of spool files. When you start the command, you can set parameters to limit the displayed list to just certain spool files. One of the selection parameters is a date field. After the display of spool files starts, there is an F4 function key that lets you change the selection parameters. We found that the F4 function was not recognizing a new date parameter setting. This has now been fixed.

The fix is available as a PTF. This PTF can only be installed on a Release 13.16 version of WebReport/i. The correction is available in PTF package WRPTF1317. E-mail us and request the PTF package.


The IFS parameter on WREPORT is not working correctly.

Based on a report from a current customer, we found that the IFS parameter on the WREPORT command could get internally truncated to a character length less than the 100 characters provided by the command and the documentation. This has now been corrected.

The fix is available as a PTF. This PTF can only be installed on a Release 13.15 version of WebReport/i. The correction is available in PTF package WRPTF1316. E-mail us and request the PTF package.


While using the Report Intranet feature, we found that if the report being deployed has a blank in the filename, it cannot be retrieved from the web page.

We have identified this problem that was causing the report deployment to fail when the filename in the IFS contained a blank character. The web instance did not crash, but the report was not being retrieved.

The fix is available as a PTF. This PTF can only be installed on a Release 13.13 version of WebReport/i. The correction is available in PTF package WRPTF1314. E-mail us and request the PTF package.


I'm confused over the use of the term "HTML" in WebReport/i.

So were we, and for a long time. We have finally bit the bullet and implemented a terminology change to address this problem. When WebReport/i was originally brought to market, the term HTML could be applied to all sorts of web deployment of reports. Since that original start, the use of the product and that term have changed.

With this change, we have eliminated the concept of an "HTML Routing" and replaced it with the term "System Routing". In WebReport/i, this indicates that your report conversion will be processed on your IBM i system and stored on the system. Some additional processing may also take place like an FTP transfer to another server or an upload to Google Drive or Dropbox. Associated command text, screen text, menus and help text have now been updated. We have also updated the current documentation for the main user's guide as well as the guides for the Intranet Feature and the Google Drive Feature. The new documentation is now available at the Download page for WebReport/i

The fix is available as a PTF. This PTF can only be installed on a Release 13.11 version of WebReport/i. The correction is available in PTF package WRPTF1312. E-mail us and request the PTF package.


When using the *MAP option to burst and email a report, the right side of the report is incomplete.

After responding to a customer report for this problem, we found that the process was truncating reports that were wider than 210 print positions. This has now been raised to 250 print positions.

The fix is available as a PTF. This PTF can only be installed on a Release 13.00 version of WebReport/i. The correction is available in PTF package WRPTF1301. E-mail us and request the PTF package.



WebReport/i Release 12 Problems:

The email process is failing on a CPF0006 when using the *INT email address option.

We found a problem due to a recent update with the *INT email address option. The process can fail on a CPF0006 error code when extracting email addresses from the spool file content.

The fix is available as a PTF. This PTF can only be installed on a Release 12.29 version of WebReport/i. The correction is available in PTF package WRPTF1230. E-mail us and request the PTF package.


The spool file number field is shorter than what is allowed in IBM's OS.

A customer advised us about this and we decided to change WebReport/i so that it would be consistent with IBM's current specifications in the OS. This was not causing any customer issues, but the change will avoid potential issues in the future.

With this change, the current release of WebReport/i will only run on systems with IBM's OS level at 6.1 and higher.

The fixes are available as a PTF. This PTF can only be installed on a Release 12.29 version of WebReport/i. The correction is available in PTF package WRPTF1229. E-mail us and request the PTF package.


I am using a report map to burst and send a report, but it does not seem to be working.

A customer reported that they set up a report map, but when they processed the report, no email messages were sent. When checking this, we found a parameter length error in one of the processing modules that was causing it to look like it was successful, but no output was produced. This has now been corrected.

The fixes are available as a PTF. This PTF can only be installed on a Release 12.28 version of WebReport/i. The correction is available in PTF package WRPTF1228. E-mail us and request the PTF package.


Fix various minor issues - see details.

The following issues reported from customers have been addressed:

  1. An intermittent failure on a file named TXT in the QTEMP library has been correct.
  2. The merge lines process for *TXT, *RTF and *HTML conversions has been improved.
  3. An intermittent problem with the automatic router failing on a CPF3342/WEB0001 error message has been addressed.

The fixes are available as a PTF. This PTF can only be installed on a Release 12.26 version of WebReport/i. The correction is available in PTF package WRPTF1227. E-mail us and request the PTF package.


When sending a report as email, I sometimes get a CPF2130 error code in the EPRINTCL program.

We discovered that this error could happen very rarely when an email was sent and the message text was set to the special value of *NONE. This problem has now been corrected.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.25 version of WebReport/i. The correction is available in PTF package WRPTF1226. E-mail us and request the PTF package.


When I upload a PDF file to Google Drive, it is getting converted into a different format.

Google made a change in the upload API that we are using so that certain file types were getting changed during the upload process. We have made a change to the way we use the Google upload API to stop this from happening.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.22 version of WebReport/i. The correction is available in PTF package WRPTF1223. E-mail us and request the PTF package.


We are sometimes getting a CPF3342 in our custom CL program that emails spool files in *XLS format.

A customer reported this because they were not able to monitor for the error message in question and deal with it in their CL program. This problem happens when you try to email a spool file that is not in the system any longer or was never created in the first place. We have now updated our code so that when this happens, we issue our standard WEB0001 error code that can be monitored for in a user CL program.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.21 version of WebReport/i. The correction is available in PTF package WRPTF1222. E-mail us and request the PTF package.


When doing batches of report transfers to Google Drive, the process sometimes fails with MCH0601.

The Google API has implemented limits on token refresh processes. To compensate for this, we have reduced the number of token refreshes requested during a batch report transfer process.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.20 version of WebReport/i. The correction is available in PTF package WRPTF1221. E-mail us and request the PTF package.


We are not able to activate Google Drive on our system.

We discovered some changes to the Google Drive interface implemented by Google that were causing our account registration and validation process to fail. This has now been corrected and is working again once this new PTF fix is installed. Currently installed systems using Google Drive should not be affected unless the account has not been used from your IBM i system in a very long time. If this is the case, you may need to re-register and validate your account using the procedures outlined in the user's guide for the Google Drive feature.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.19 version of WebReport/i. The correction is available in PTF package WRPTF1220. E-mail us and request the PTF package.


We sometimes get a CPF0006 error when emailing a spool file in Excel format.

Based on a problem we found during testing here, we found that certain very complex conversions of spool files into Excel (*XLS) format could get this result. It was due to a command length factor that was too small. It has now been fixed for both the EREPORT and WREPORT commands.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.17 version of WebReport/i. The correction is available in PTF package WRPTF1217. E-mail us and request the PTF package.


When emailing a spool file in CSV format, the attachment name does not appear to support all the naming options.

We found that only the *GEN naming option was working correctly for CSV spool file conversions. We have now updated the software so that all naming options are supported as per the documentation.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.11 version of WebReport/i. The correction is available in PTF package WRPTF1212. E-mail us and request the PTF package.


When converting a spool file to Excel (XLS) format using a Report Model, it fails with the MCH0603 error code.

We found that when the Report Model file contained a large number of field definitions, then this could happen. It has now been fixed so that there is virtually an unlimited number of field definitions allowed.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.10 version of WebReport/i. The correction is available in PTF package WRPTF1211. E-mail us and request the PTF package.


When converting a spool file to Excel (XLS) format, some columns end up displaying as very wide in Excel.

After hearing from a customer on this issue, we were able to implement some additional controls to better control the width of numeric fields when an Excel file model is used.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.08 version of WebReport/i. The correction is available in PTF package WRPTF1209. E-mail us and request the PTF package.


When using the EREPORT command with the FILE parameter set to *NONE, there is a NULL.TXT attachment on the resulting email message.

Up to this point in time, this has been considered the way it works and "normal" behavior. We have had several customers, however, tell us that their users sometimes file this confusing and have trouble when they try to open the NULL.TXT file attachment. With this PTF, the NULL.TXT file will no longer be sent on these FILE(*NONE) uses of the EREPORT command.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.07 version of WebReport/i. The correction is available in PTF package WRPTF1208. E-mail us and request the PTF package.


EREPORT is failing when the JOBQ parameter is specified.

We found a segment of code that had not been properly updated for latest release of the software. It has now been corrected.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.00 version of WebReport/i. The correction is available in PTF package WRPTF1202. E-mail us and request the PTF package.


I am trying to install the Intranet feature, but it is failing with a device error.

We found that on some customers, a configuration difference could cause this to happen in the WWWINSTAL program. It has now been changed so that it will run correctly on all customer systems.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 12.00 version of WebReport/i. The correction is available in PTF package WRPTF1201. E-mail us and request the PTF package.



WebReport/400 Release 11 Problems:

I'm distributing reports using the *INT address with embedded addresses in the spool file, but it is failing with a CPF0006 error.

We found that for some customers, this could happen after a recent update to the software was released. The error appears like a bad parameter value in the joblog. This has now been corrected.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 11.13 version of WebReport/400. The correction is available in PTF package WRPTF1114. E-mail us and request the PTF package.


The file name showing from the HTML Index display is sometimes incorrect.

The file name showing on the first "list" of the index was sometimes showing an incorrect value when the file in question was stored in the *IFS. The detail display was always correct, this was just showing wrong on the list.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 11.12 version of WebReport/400. The correction is available in PTF package WRPTF1113. E-mail us and request the PTF package.


I'm converting a spool file to XLS format, but it fails when I try to set the page headings option to *NONE.

We found problems with the *NONE setting for both page headings and column headings in the EREPORT and the WREPORT commands. Both have now been corrected and work as documented.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 11.11 version of WebReport/400. The correction is available in PTF package WRPTF1112. E-mail us and request the PTF package.


I get a different PDF file result when running a spool file through the EREPORTM command.

Some time ago, the PDF conversion routine being used by the EREPORT command was changed, but that change was not extended into the EREPORTM command. With this change, we have made the two processes identical. We have also added the FONTSIZ and FONTTYP parameters for PDF conversions using the EREPORTM command.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 11.09 version of WebReport/400. The correction is available in PTF package WRPTF1110. E-mail us and request the PTF package.


I'm trying to delete multiple reports from the HTML Index, but the system only seems to process one at a time.

We found a problem that was causing this to happen. This has now been fixed and you can process multiple deletes at the same time when updating the HTML Index from option #3 on the MASTER menu.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 11.07 version of WebReport/400. The correction is available in PTF package WRPTF1108. E-mail us and request the PTF package.


When using the Report Intranet I don't see the selection box to bring up a report.

We discovered an incompatibility with the Report Intranet when used with certain versions of Microsoft's Internet Explorer (IE) web browser where the selection box was not getting rendered correctly. We have made adjustments in our software so that this now works as documented for these IE browsers.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 11.06 version of WebReport/400. The correction is available in PTF package WRPTF1107. E-mail us and request the PTF package.


When setting up the new Report Intranet, everything seems to work but when I try to bring up a report, the link fails.

We found a bad link included in the original release code for this feature. It has now been fixed.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 11.05 version of WebReport/400. The correction is available in PTF package WRPTF1106. E-mail us and request the PTF package.


The email address information stored in the USRDFNDTA field is not all being processed.

... and ...

I am seeing a logging error in the activity log, but no errors are happening with email report distributions.

... and ...

The TOID field is being rejected on the EREPORT command.

We found that the initial implementation code for picking up email address information from the USRDFNDTA field stopped processing after the first 50 characters. This has now been expanded to process all 255 characters available in this field.

We found that under the situation where a GROUP email address was processed in combination with an individual email address and the GROUP came first, then an erroneous error could get posted in the WebReport/400 activity log. This has now been corrected.

Due to a recent change in internal processing, certain TOID fields that contained special characters were not getting accepted correctly. This has now been fixed.

The fix for these problems is now available as a PTF. This PTF can only be installed on a Release 11.03 version of WebReport/400. The correction is available in PTF package WRPTF1104. E-mail us and request the PTF package.


One of my spool file conversions into Excel (*XLS) format fails with a CVT9994 error code.

We identified an intermittent problem with the Excel conversion routine. 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 11.02 version of WebReport/400. The correction is available in PTF package WRPTF1103. E-mail us and request the PTF package.


I am getting intermittent CPF0001 errors from the WebReport/400 automatic router.

Several customers have reported seeing this happen after upgrading to WebReport/400 Release 11. We have tracked down the issue and corrected it. Patches have already been provided to customers who experienced this issue. This PTF includes the fixes for all customers.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 11.01 version of WebReport/400. The correction is available in PTF package WRPTF1102. E-mail us and request the PTF package.


WebReport/400 Release 10 Problems:

Multiple customer problem reports.

After a recent upgrade to our PDF and XLS conversion software, several customer contacted us with issues. These include:

  1. A new "hint" screen is sometimes displayed when running a PDF conversion.
  2. The EREPORTM command fails sometimes when trying to send several reports in a single email process.
  3. The single email transmission fails on a parameter mismatch when using PDF security fields.

The fixes for these problems is now available as a PTF. This PTF can only be installed on a Release 10.21 version of WebReport/400. The correction is available in PTF package WRPTF1022. E-mail us and request the PTF package.


When using a pass phrase for a PDF security password, the conversion is failing.

We found that there was a problem when using a pass phrase for a PDF security password that had blank 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 10.20 version of WebReport/400. The correction is available in PTF package WRPTF1021. E-mail us and request the PTF package.


After installing the latest release (10.19), some email transmissions are going to incorrect email addresses.

Release 10.19 contained a new problem that could generate email messages to incorrect addresses when multiple destinations are used with automatic routing that have stacked address book references in them.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 10.19 version of WebReport/400. The correction is available in PTF package WRPTF1020. E-mail us and request the PTF package.


When converting a report into Excel format (XLS), some of the lines are getting processed as headings when they are not.

and ....

When using Address Book abbreviations stacked as email destinations, some of the addresses do not receive their email message.

We found that when the page and column headings were only produced on the first page and not repeated on subsequent pages in the spool file, then unpredictable results could happen. We have addressed this issue by adding a second page and column control parameter.

Also, we found that under certain circumstances, some destination email addresses were getting dropped when a large number of Address Book abreviations were stacked into a single email address parameter. The system has been modified to now correctly process all of the addresses when this is done.

The fix for these problems is now available as a PTF. This PTF can only be installed on a Release 10.18 version of WebReport/400. The correction is available in PTF package WRPTF1019. E-mail us and request the PTF package.


When updating the Email Automatic Routing Table, the copy function issues an error message.

We found that the copy function was sometimes issuing an error message even when the copy function was valid. The copy actually was taking place, but the error message seemed to indicate that it had failed. This has now been cleared up.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 10.17 version of WebReport/400. The correction is available in PTF package WRPTF1018. E-mail us and request the PTF package.


I get an error when trying to send a report that indicates that a data area in the WEBREPORT library is not available.

We found that under certain circumstances, a recent change to the product was leaving the CONTROL data area in the WEBREPORT library locked when it should not have been in a locked state. This could happen when using automatic routing with *INT internal destination email addressing.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 10.16 version of WebReport/400. The correction is available in PTF package WRPTF1017. E-mail us and request the PTF package.


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.


Various problem fixes.

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:

  1. The "Match Name" field in the Title Conversion Table now supports mixed case entry. This was requested by several customers who needed to be able to compare to mixed case *USRTDTA fields.
  2. A fix was made to the routine that sends email in *PDF format using email addresses stored within the spool file. It was failing on a parameter mismatch in a program call to program WEBRTREIN.
  3. A fix was made to program WEBRTREIN that was causing a command parameter error on a use of the EREPORT command.

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.


Our logo, which is implemented as a *PAGSEG, is not appearing on a spool file conversion of PDF format.

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.


While converting an AFPDS spool file to PDF format, I get an MCH3601 error.

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.


When using WebReport/400, a new user's task fails with message WEB0080.

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.


When emailing a spool file as *XLS, it fails with error CPF9897.

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.


I am having problems using the group address function.

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.


Sometimes, the &DATE-EXPR macro resolves to the wrong date.

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.


Not all activity is appearing in the activity log on my system.

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.


Error code MCH3401 is issued from the WEBRTR program.

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.


When sending a report as email, the report arrives with the last line missing.

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.


Automatic distribution of email using imbedded #EMAIL directives is failing intermitently.

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.


The first line is getting dropped on some CSV spool file conversions.

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 new EREPORTM command, not all spool files are getting processed for the ENDOPT parameter.

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.


Page breaks on my *TXT and *RTF reports are sometimes in the wrong place.

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.


I am getting an error code MCH0801 issued from program EPRINTU when using the WREPORT command.

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.


Contact Information
Kisco Information Systems
89 Church Street
Mt Kisco, New York 12983

Phone: (518) 897-5002 Fax: (518) 897-5003

E-mail your questions or suggestions: Support@Kisco.com

.
.
Kisco Information Systems 89 Church Street Saranac Lake, NY 12983
phone: 518.897.5002 | fax: 518.897.5003
sales@kisco.com about kisco kisco products product support kisco consulting services useful links