WebReport/400 : Problem Reports



.	Kisco Home : products : WebReport/400 : Support : Problem Reports		.
.		Page last updated on April 24, 2008 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 E-mail and we'll address your problem. To register your E-mail address and receive automatic notification when this page is updated, CLICK HERE. WebReport/400 Problem Reports Index: WebReport/400 Release 9 Problem Reports: When creating a USER email routing, a new output queue is created. Various problem fixes - see details below. Sometimes my application fails with an error when it is just a bad email address that has been used. 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. WebReport/400 Release 8 Problem Reports:* Some power users are deleting spool files while WebReport/400 is still processing them, this causes an error in WebReport/400. 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. I get a WEB0001 when attempting to send a report as email to an internal list of email addresses. WebReport/400 Release 7 Problem Reports:* I get a CPF3303 when attempting to run WREPORT and create 400 format output to the IFS or a shared folder. When converting a very large report to RTF format, part of the report at the end is missing. Converting my DBCS spool file to PDF produces some incorrect output. When using the WREPORT command to create an PDF file, the BMARKACT parameter appears to be ignored. When using the WREPORT command to create an HTML file in the IFS, I get a WEB0056 error, but I have specified the REPLACE(YES) parameter. I am getting a CPFA097 error when trying to send a report as an Email attachment. The WebReport/400 Message Monitor is sometimes reporting an incorrect message ID in the Email that is sent. WebReport/400 Release 6 Problem Reports: When using the FILE(NONE) option to send Email without a spool file attachment, WebReport/400 fails. Two small problems fixed with RTF formatting and overprint merge processing. I am getting an error when creating 400 format files on my system. I am getting a CPF0001 when trying to use the WREPORT command to create a local copy of a report in CSV format. After upgrading to Release 6.09 of WebReort/400, I am getting a CPA0702 error. I am getting errors CPF0001 and MCH0802 when sending reports to internally specified addresses in PDF format. I get a TCP5105 error in the QMSF job when trying to send email. I get a CPF3429 error in program KPDFINTCL. My IPDS spool file converts to PDF correctly for the first page, but the second and subsequent pages are turned at an odd angle. The WEBRTR job fails following a period of very high email utilization. After upgrading to OS/400 V5R2, my email no longer goes out and I'm getting a message indicating that message relaying is blocked. I get a WEB0001 (spool file not found) error when sending a report as a PDF attachment, but I can see that the spool file is actually there on my system. We are getting a CPF0001 from program PRTFMTCL when trying to convert a spool file to Acrobat (PDF) format. When sending email in PDF format using the imbedded email directive statement, I am getting an MCH0603 error message. WebReport/400 Release 5 Problem Reports: When trying to delete a spool file from the WRKWEBSPLF command, I get a CPF0001 error. When I send an Email using an address from the WebReport/400 address book, sometimes the QMSF job fails. Sometimes a report recipient sees a long string of question marks in the text of an email. When using imbedded email directives with a PDF attachment format, the right side of each page is being truncated. I get an MCH1210 from program EPRINTCL when trying to send an Email report. Outbound Email stops on an intermittent basis, when I check it, I find that MSF has shut down. When sending a PDF attachment using the INT option, I get an MCH0802 error message. After installing WebReport/400 PTF WRPTF508, I get a CPFA097 error in the automatic router job WEBRTR. When running WebReport/400 on my V4R4 machine, the QMSF job fails with error code TCP5105 and a reason code of 3405. The new FROMID parameter on email transmissions is sometimes reset to the default value. I'm sending PDF attachments, but the BOOKMARK setting does not seem to be working. When trying to send a PDF report using the INT address option, the optional message text is getting lost. I am getting a CPF0001 error from program EPRINTCL. WebReport/400 Release 4 Problem Reports: The WRKWEBSPLF command does not work correctly immediately folllowing our upgrade to OS/400 V5R1. WebReport/400 has been working fine, but now no email is being received. WebReport/400 fails when using the Merge Overprint and Internal Email options together. When using WebReport/400 functions EREPORT or WREPORT an specifying a CURRENT spool file, CPF0001 errors occur. When sending a report as E-mail, sometimes a line on the report has information shifted to the left and does not line up correctly. When running a PDF conversion to be stored in the IFS, the file name is getting truncated. I am getting a CPF0001 from the automatic router function running in the EREPORT subsystem. I get error message CPF0001 when converting a report into Acrobat Format (PDF) for local deployment in the IFS. I converted a report to HTML and placed it in the IFS, but when I access it, the file appears to be empty. When I send a report in Acrobat format (PDF), the Acrobat Reader hangs up while reading the file with an "Error 14". When I send E-mail, everything looks like it works OK but I find several CPF8A83 error messages in the QMSF joblog indicating that the user is "Not authorized to access ..." a document in folder WEBWORK. After upgrading from WebReport/400 Release 2 to Release 3, email looks like it is being sent but it never arrives. When I try to send Email to an Internet Address, WebReport/400 fails with a CPF0818 error. Sometimes when converting a report to HTML, it fails with an LBE7207 error. I sent a report as Email. Everything looked like it was sent OK, but a CPI9046 error is issued after a short pause, and the Email is never delivered. When I try to send a report as Email, it fails with error code CPFA097. When I try to send a report as Email, it fails with error code CPF3429. I just installed WebReport/400 and when I try to send a report as an Email message, I'm getting an error message of IWS1612. When I email a large report, it arrives as multiple messages and the text is garbled. When I send a large report, I get an error message on a workfile when it appears to fill up. WebReport/400 Release 9 Problems:* *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: 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. 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. 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. 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. MCH0801 when using the new EREPORTM command fixed. 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. Email reports are not getting delivered to all of the addresses specified.* 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. WebReport/400 fails sometimes with a WEB0001 error when sending email. 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 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.** 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. The HTML Review option does not show the IFS path for my document. 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. I get an MCH0603 error when trying to update a set of destination email addresses in the automatic routing table. 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. 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. 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. When using the &TOLIST macro, there is garbled text in the list of destination email addresses. 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. WebReport/400 Release 7 Problems: *I get a CPF3303 when attempting to run WREPORT and create 400 format output to the IFS or a shared folder.** Based on customer information, we found that the 400 format file conversion was not working correctly when run on systems with OS/400 V5R2 or newer installed. The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 7.16 version of WebReport/400. The correction is available in PTF package WRPTF717. This PTF also includes a minor improvement to the PDF conversion capabilty when processing Chinese language (font) doublebyte character spool files. E-mail us and request the PTF package. When converting a very large report to RTF format, part of the report at the end is missing.* We found an artificial size limitation in the RTF conversion process that caused it to fail when a spool file had more than 99,999 print lines. This has now been increased to 9,999,999 print lines. The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 7.15 version of WebReport/400. The correction is available in PTF package WRPTF716. This PTF also includes a product enhancement. E-mail us and request the PTF package. Converting my DBCS spool file to PDF produces some incorrect output. The recently introduced ability to process DBCS spool file into PDF documents was initially based on Japenese test documents. When extended to include Chinese documents, we found several problems with certain fonts. This has now been corrected. A fix for this problem is now available as a PTF. This PTF can only be installed on a Release 7.14 version of WebReport/400. The correction is available in PTF package WRPTF715. E-mail us and request the PTF package. When using the WREPORT command to create an PDF file, the BMARKACT parameter appears to be ignored. We found that under certain conditions, the BMARKACT parameter was not being enforced and was always defaulting to the SHOW value. A fix for this problem is now available as a PTF. The PTF changes the WREPORT process to correctly recognize the BMARKACT parameter and enforce it. The PTF also restores a PGM object that was incorrectly removed from the WEBREPORT library by an earlier PTF install process. The missing PGM object is named @@ED0213. This PTF can only be installed on a Release 7.13 version of WebReport/400. The correction is available in PTF package WRPTF714. E-mail us and request the PTF package. When using the WREPORT command to create an HTML file in the IFS, I get a WEB0056 error, but I have specified the REPLACE(YES) parameter.** Based on a customer complaint, we found a problem when converting a spool file to an HTML file in the IFS. If you specified REPLACE(YES) and a copy of the file was already in the IFS location, the error would happen incorrectly. This has now been fixed to work as documented. A fix for this problem is now available as a PTF. The PTF correctly identifies the IFS file to be replaced and does not cause an error to happen. This PTF can only be installed on a Release 7.08 version of WebReport/400. The correction is available in PTF package WRPTF709. E-mail us and request the PTF package. I am getting a CPFA097 error when trying to send a report as an Email attachment.* This problem can happen when an eariler Email send failed for some other reason and, in so doing, left a named attachment file behind in the WEBWORK folder in the IFS root directory. You can correct for this by using the command WRKLNK WEBWORK and looking in the folder using option 5. Check for the named attachment file and delete it. Once this is done, you can resume sending Email using that named attachment option. A better, long term, fix for this problem is now available as a PTF. The PTF looks for the named attachment before processing and removes it, thereby avoiding the issue. This PTF can only be installed on a Release 7.04 version of WebReport/400. The correction is available in PTF package WRPTF705. E-mail us and request the PTF package. The WebReport/400 Message Monitor is sometimes reporting an incorrect message ID in the Email that is sent. We found that sometimes the wrong MSGID parameter was being set. It has now been fixed. A fix for this problem is now available as a PTF. This PTF can only be installed on a Release 7.03 version of WebReport/400. The correction is available in PTF package WRPTF704. E-mail us and request the PTF package. WebReport/400 Release 6 Problems: *When using the FILE(NONE) option to send Email without a spool file attachment, WebReport/400 fails. We found that due to some recent changes in the way email messages are transmitted, this feature no longer worked correctly. We have now corrected the problem. A fix for this problem is now available as a PTF. This PTF can only be installed on a Release 6.14 version of WebReport/400. The correction is available in PTF package WRPTF615. This PTF also includes some new features. You can see information about the new features on the updates page. E-mail us and request the PTF package. Two small problems fixed with RTF formatting and overprint merge processing. Customers reported two minor problems to us. One had to do with certain reports with line lengths between 73 and 80 positions that were coming up with line wrap when processing in RTF format. The other problem caused some data to be lost on the very last line of a report that required overprint line merge process. A fix for both of these problems is now available as a PTF. This PTF can only be installed on a Release 6.13 version of WebReport/400. The correction is available in PTF package WRPTF614. E-mail us and request the PTF package to correct this problem. I am getting an error when creating 400 format files on my system.* When the 400 file format was specified when emailing a spool file, it could sometimes fail when the customer had OS/400 V5R1 or higher installed. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.11 version of WebReport/400. The correction is available in PTF package WRPTF612. E-mail us and request the PTF package to correct this problem. I am getting a CPF0001 when trying to use the WREPORT command to create a local copy of a report in CSV format.** We found a problem with the local CSV conversion that could cause a CPF0001. You will find this error code preceded by a CPF0094 in the joblog. This can happen when storing the output in a FLR or IFS destination. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.10 version of WebReport/400. The correction is available in PTF package WRPTF611. E-mail us and request the PTF package to correct this problem. After upgrading to Release 6.09 of WebReort/400, I am getting a CPA0702 error.* This problem was introduced to WebReport/400 with the release of version 6.09 (PTF WRPTF609) and can happen when sending email using the internal #EMAIL statements imbedded in the spool file. The problem happens only when sending TXT or RTF attachments. The CPA0702 is preceeded in the joblog with a CPF9897 error that shows a reason code of -301. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.09 version of WebReport/400. The correction is available in PTF package WRPTF610. E-mail us and request the PTF package to correct this problem. I am getting errors CPF0001 and MCH0802 when sending reports to internally specified addresses in PDF format. We identified and corrected both of these problems with the internal routing on PDF email processing. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.08 version of WebReport/400. The correction is available in PTF package WRPTF609. E-mail us and request the PTF package to correct this problem. I get a TCP5105 error in the QMSF job when trying to send email. Several customers using WebReport/400 under V5R2 reported problems with the TCP5105 error and reason code 3405 when trying to use WebReprt/400 to send email in either Text or Rich Text Format. After working with IBM support, we could not come to either an explanation or even a reason for these errors. To get customers back up and working, we made a change to WebReport/400 so that it no longer uses the Mail Server Framework in OS/400, effectively bypassing the problem. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.08 version of WebReport/400. The correction is available in PTF package WRPTF609. E-mail us and request the PTF package to correct this problem. *My IPDS spool file converts to PDF correctly for the first page, but the second and subsequent pages are turned at an odd angle. A customer reported this problem to us and we found an obscure programming problem in the spool to PDF conversion routine. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.05 version of WebReport/400. The correction is available in PTF package WRPTF606. E-mail us and request the PTF package to correct this problem. I get a CPF3429 error in program KPDFINTCL. We found that when you attempted to process an empty spool file, this error could happen. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.07 version of WebReport/400. The correction is available in PTF package WRPTF608. E-mail us and request the PTF package to correct this problem. My IPDS spool file converts to PDF correctly for the first page, but the second and subsequent pages are turned at an odd angle.* A customer reported this problem to us and we found an obscure programming problem in the spool to PDF conversion routine. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.05 version of WebReport/400. The correction is available in PTF package WRPTF606. E-mail us and request the PTF package to correct this problem. The WEBRTR job fails following a period of very high email utilization. We found that on some customer systems, the settings of certain system values could cause this to happen when the job message queue fills up. To correct for this, we have changed the application to that it now uses a unique job description which will prevent this from happening. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.02 version of WebReport/400. The correction is available in PTF package WRPTF603. E-mail us and request the PTF package to correct this problem. After upgrading to OS/400 V5R2, my email no longer goes out and I'm getting a message indicating that message relaying is blocked. OS/400 V5R2 implements a new and easier method of SMTP relay control. If you are experiencing this problem, it is because the SMTP Attributes on your system have been updated since to prevent SMTP mail relaying. If this was done to prevent unapproved use of the mail server on your AS/400, then you will have to make some changes to your SMTP configuration to allow WebReport/400 to work. First, you will have to allow some message relaying on your system by specifying the following change to your SMTP Attributes: CHGSMTPA ALWRLY(LIST) Then, you will have to authorize your iSeries-AS/400 system as an approved user of the SMTP server on your system. This is done using the ADDSMTPLE command with the ACCEPT option to enter one entry to your accepted relay list that specifies the IP address of your AS/400. For example, if your AS/400 IP address is 100.101.102.103, then the command would be: ADDSMTPLE TYPE(ACCEPT) INTNETADR('100.101.102.103') SUBNETMASK('255.255.255.255') The setting of the subnet mask guarantees that only the stated IP address will be allowed to relay. This will permit WebReport/400 mail to leave your AS/400 but no other mail will be permitted to relay off your system. I get a WEB0001 (spool file not found) error when sending a report as a PDF attachment, but I can see that the spool file is actually there on my system.* When sending a report as a PDF attachment, sometimes the WEB0001 error can be misleading. The most common reason for this happening is when you are using a named attachment (the ATTNAME parameter) but the attachment name already exists in the webwork folder. This can happen when an earlier email operation fails before it has completed, leaving the file in place. You can verify this situation by examining the joblog for the failing job. Search for the presence of a CVT9004 error in the joblog that comes prior to the WEB0001 message. If you see that CVT9004, this confirms the above problem description. Recovery from this is fairly simple. Use the WRKLNK command from an OS/400 command line and find the webwork folder. Use option 5 to display the contents of the folder and locate the attachment that is currently stored there. When you find it, delete it using the option 4. Once it has been deleted, your email send should then work correctly. We are getting a CPF0001 from program PRTFMTCL when trying to convert a spool file to Acrobat (PDF) format. A customer reported this problem to us. When running the WREPORT function, the CPF0001 from program PRTFMTCL at line 51300 of the program was issued. A fix for this is now available as a PTF which prevents the program from failing. This PTF can only be installed on a Release 6.01 version of WebReport/400. The correction is available in PTF package WRPTF602. E-mail us and request the PTF package to correct this problem. When sending email in PDF format using the imbedded email directive statement, I am getting an MCH0603 error message. We found a problem with this function when an email directive statement is used that does not conform to the rules set forth in the documentation. A failure can occur. A fix for this is now available as a PTF which will prevent the program from failing. This PTF can only be installed on a Release 6.00 version of WebReport/400. The correction is available in PTF package WRPTF601. E-mail us and request the PTF package to correct this problem. WebReport/400 Release 5 Problems: When trying to delete a spool file from the WRKWEBSPLF command, I get a CPF0001 error. We found a problem with this function when used on a system running OS/400 level V5R1 or higher. A fix for this is now available as a PTF which now performs the spool file delete correctly. This PTF can only be installed on a Release 5.16 version of WebReport/400. The correction is available in PTF package WRPTF517. E-mail us and request the PTF package to correct this problem. When I send an Email using an address from the WebReport/400 address book, sometimes the QMSF job fails. Based on a customer report, we found that when an abbreviation is used from the WebReport/400 address book and that abbreviation contains 10 characters (the maximum allowed), then a problem in WebReport/400 was causing an incorrect destination Email address to be used. A fix for this is now available as a PTF which replaces the null characters with blanks. This PTF can only be installed on a Release 5.15 version of WebReport/400. The correction is available in PTF package WRPTF516. E-mail us and request the PTF package to correct this problem. (Note, this Email also contains several new features.) Sometimes a report recipient sees a long string of question marks in the text of an email. When sending reports as either text or RTF attachments via automatic routing, if you used the option for no email message text (NONE), WebReport/400 was inadvertently sending a string of null characters as part of the message text. Some email clients, most notably Lotus Notes, were showing these as question marks. A fix for this is now available as a PTF which replaces the null characters with blanks. This PTF can only be installed on a Release 5.14 version of WebReport/400. The correction is available in PTF package WRPTF515. E-mail us and request the PTF package to correct this problem. When using imbedded email directives with a PDF attachment format, the right side of each page is being truncated.* We discovered an artificial line length limit was being imposed in the routine that processes PDF reports with the internal email directives. I was limited to 132 column reports. A fix for this is now available as a PTF which increases the line width to 198 columns. This PTF can only be installed on a Release 5.13 version of WebReport/400. The correction is available in PTF package WRPTF514. E-mail us and request the PTF package to correct this problem. I get an MCH1210 from program EPRINTCL when trying to send an Email report. A customer who is a very heavy user of the WebReport/400 E-mail features reported this to us. We found an internal message counter that was not checking for overflow and was causing the MCH1210 error to occur. A fix for this is now available as a PTF. This PTF can only be installed on a Release 5.11 version of WebReport/400. The correction is available in PTF package WRPTF512. E-mail us and request the PTF package to correct this problem. Outbound Email stops on an intermittent basis, when I check it, I find that MSF has shut down. Customers have periodically reported this problem to us since WebReport/400 was initially introduced. Over this time, we have finally determined that this was happening when an invalid email address is passed from WebReport/400 to the OS/400 Mail Server Framework (MSF). An invalid email address is one that does not conform to standard email conventional structure. An example of this would be a blank address, an address that does not contain any @ sign or one that has no period (dot) following the @ sign. This can be a serious problem since when the MSF shuts down, all outbound email traffic from WebReport/400 will stop until the situation is detected and MSF is restarted. To help stop this from happening, Kisco has added validation code to edit the destination email address just before passing an email off to the OS/400 MSF component. If an illegal destination email address is used, the message will be skipped and a log entry will be posted to the WebReport/400 activity log. The fix for this is now available as a PTF. This PTF can only be installed on a Release 5.10 version of WebReport/400. The correction is available in PTF package WRPTF511. E-mail us and request the PTF package to correct this problem. *When sending a PDF attachment using the INT option, I get an MCH0802 error message. After distributing PTF WRPTF509 to several customers, a customer reported this problem back to us. We have now traced the problem and corrected it. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 5.09 version of WebReport/400. The correction is available in PTF package WRPTF510. E-mail us and request the PTF package to correct this problem. Note, this PTF also includes several new features for WebReport/400. After installing WebReport/400 PTF WRPTF508, I get a CPFA097 error in the automatic router job WEBRTR. After distributing PTF WRPTF508 to several customers, a customer reported this problem back to us. We have now traced the problem to a release incompatibility when running the new version of WebReport/400 under OS/400 V5R1 or higher. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 5.09 version of WebReport/400. The correction is available in PTF package WRPTF508. E-mail us and request the PTF package to correct this problem. When running WebReport/400 on my V4R4 machine, the QMSF job fails with error code TCP5105 and a reason code of 3405.** This problem only seems to affect customers running WebReport/400 under V4R4. Later releases appear to be OK. The error being reported is due to an authority issue in the WEBWORK shared folder. You can correct for this situation using the following procedure: Run the WRKLNK command. Find the QDLS entry and type a 5 next to it. Find the WEBWORK entry and type an 9 next to it. On the top line, type option 1 and press ENTER. On the next screen, enter a user profile name other than QSECOFR that has security office authority. For "New Data Authorities", enter RWX and for "New Object Authorities" enter ALL. Press ENTER. This will return you to the Work with Authority screen. If there is an entry shown for QSECOFR, use option 4 to delete it. Place a 2 next to the PUBLIC entry and press ENTER. For "New Object Authorities", enter ALL and press ENTER. Return to the command line, then run the WRKDIRE command. Check to make sure that the user profile that you specified in step 5 above appears in the directory. If not, create a new entry for the user profile using all default settings. Once all of these changes have been made, you should recycle your MSF and SMTP jobs by ending them and restarting them. The new FROMID parameter on email transmissions is sometimes reset to the default value. We found that under certain circumstances, when sending a report attachment in Acrobat format, the FROMID parameter was not being enforced as requested by the user. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 5.05 version of WebReport/400. The correction is available in PTF package WRPTF506. E-mail us and request the PTF package to correct this problem. I'm sending PDF attachments, but the BOOKMARK setting does not seem to be working. We found that when you sent PDF attachments using the INT internal email directive option, the BOOKMARK and BMARKACT parameters were not being enforced. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 5.04 version of WebReport/400. The correction is available in PTF package WRPTF505. E-mail us and request the PTF package to correct this problem. When trying to send a PDF report using the INT address option, the optional message text is getting lost.** A customer reported this problem to us and we found that there was a problem that was causing the optional message text to get dropped when a value other than the DFT value is used. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 5.03 version of WebReport/400. The correction is available in PTF package WRPTF504. E-mail us and request the PTF package to correct this problem. I am getting a CPF0001 error from program EPRINTCL.* We found a problem that was causing a CPF0001 when WebReport/400 was used to send email using imbedded fax directives with the PDF option from the CURRENT job. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 5.02 version of WebReport/400. The correction is available in PTF package WRPTF503. E-mail us and request the PTF package to correct this problem. WebReport/400 Release 4 Problems: The WRKWEBSPLF command does not work correctly immediately folllowing our upgrade to OS/400 V5R1. Due to an engineering change made by IBM in OS/400 V5R1, a problem has cropped up in WebReport/400. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 4.14 version of WebReport/400. The correction is available in PTF package WRPTF415. E-mail us and request the PTF package to correct this problem. WebReport/400 has been working fine, but now no email is being received. If you have been using WebReport/400 for a while to send E-mail and it stops working all of a sudden, we have found that the most common reason for this is because of a failure in the Mail Server Framework within OS/400. You can check this by running the following command on your system: WRKACTJOB SBS(QSYSWRK) This command will display the active tasks in the QSYSWRK subsystem on your system. Look for a job named QMSF. If it is not there, then the Mail Server Framework has probably failed. We recommend the following sequence to restart the Mail Server Framework: Restart QMSF using the following command: STRMSF NBRMSFJOB(1) After restarting it, wait about 30 seconds and then check the QSYSWRK subsystem again. If the QMSF job is gone again, then restart it again using the following command: STRMSF MSGOPT(RESET) NBRMSFJOB(1) Wait another 30 seconds and check it again. If it is gone again, then do one more restart using the following command: STRMSF MSGOPT(CLEAR) NBRMSFJOB(1) The last restart should work regardless of what was wrong. If you get to this point, however, then any pending emails that you had waiting to go out will get deleted. We have found that more Mail Server Framework failures happen when a very corrupted e-mail address is used to send a message. Typically, these are e-mail addresses that fail to contain a @' character. WebReport/400 fails when using the Merge Overprint and Internal Email options together. When using both the Merge Overprint feature and the Internal Email Addressing feature to send E-mail, a problem was causing WebReport/400 to fail with an error message. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 4.12 version of WebReport/400. The correction is available in PTF package WRPTF413. E-mail us and request the PTF package to correct this problem. *When using WebReport/400 functions EREPORT or WREPORT an specifying a CURRENT spool file, CPF0001 errors occur. A problem was found that was causing certain parameters on internal OS/400 commands to be set incorrectly. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 4.11 version of WebReport/400. The correction is available in PTF package WRPTF412. Note that this same PTF also includes a new feature for automatic system directory enrollment. E-mail us and request the PTF package to correct this problem. When sending a report as E-mail, sometimes a line on the report has information shifted to the left and does not line up correctly. A problem was found that was causing blank truncation on a very intermittent basis. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 4.10 version of WebReport/400. The correction is available in PTF package WRPTF411. E-mail us and request the PTF package to correct this problem. When running a PDF conversion to be stored in the IFS, the file name is getting truncated.* We found a problem that could happen when the file name in the IFS was longer than 12 bytes. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 4.09 version of WebReport/400. The correction is available in PTF package WRPTF410. E-mail us and request the PTF package to correct this problem. I am getting a CPF0001 from the automatic router function running in the EREPORT subsystem. We discovered a problem with this process that was inadvertently introduced with release level 4.08. This problem can happen after installing version 4.08 or after PTF package WRPTF408 has been installed. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 4.08 version of WebReport/400. The correction is available in PTF package WRPTF408. E-mail us and request the PTF package to correct this problem. *I get error message CPF0001 when converting a report into Acrobat Format (PDF) for local deployment in the IFS. We discovered a problem with this process and have corrected it. This affects local conversions for PDF files when the output is specified for the IFS. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 4.05 version of WebReport/400. The correction is available in PTF package WRPTF406. E-mail us and request the PTF package to correct this problem. I converted a report to HTML and placed it in the IFS, but when I access it, the file appears to be empty. We discovered a problem with this process and have corrected it. This affects local conversions for HTML, TXT and RTF file when the output is specified for the IFS. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 4.04 version of WebReport/400. The correction is available in PTF package WRPTF405. E-mail us and request the PTF package to correct this problem. When I send a report in Acrobat format (PDF), the Acrobat Reader hangs up while reading the file with an "Error 14".** We discovered a problem that can corrupt the Acrobat files being generated from WebReport/400 when they are sent as E-mail attachments. The problem is very intermittent and only happens on larger reports. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 4.03 version of WebReport/400. The correction is available in PTF package WRPTF404. E-mail us and request the PTF package to correct this problem. When I send E-mail, everything looks like it works OK but I find several CPF8A83 error messages in the QMSF joblog indicating that the user is "Not authorized to access ..." a document in folder WEBWORK. This problem only happens when you are using WebReport/400 on a system set to security level 30 or higher. The problem stems from the fact that the work folder WEBWORK is created when the product is installed. When WebReport/400 is used on a system at security level 30 or higher, WebReport/400 has a problem working with documents in this folder because it is owned by the special user profile QSECOFR. We have developed a solution to this problem. Please take the action steps listed here to correct for this situation: Delete any documents that may exist in the current WEBWORK folder Delete the folder Sign on under a user profile other than QSECOFR that has security officer authority and issue the command: CRTFLR WEBWORK Then issue the command WRKFLR Find the WEBWORK folder and key a '14' next to it On the next screen, change the public authority to ALL Then, before leaving that screen, press F6 and add user profile QMSF with ALL authority Get back to an OS/400 command line by pressing ENTER to record all of the changes End the QMSF job using the command: ENDMSF Restart the QMSF job using the command: STRMSF MSGOPT(CLEAR) NBRMSFJOB(1) When all of these changes have been made, WebReport/400 will have proper access to documents in the WEBWORK folder. After upgrading from WebReport/400 Release 2 to Release 3, email looks like it is being sent but it never arrives.* WebReport/400 Release 3 requires that user profiles QUSER, QMSF and QSECOFR (and QDIRSRV if you are running OS/400 V4R4 or higher) be registered in your system directory. Use the WRKDIRE command to check for this. If they are not there, then they must be added (use your system name for the location). This is needed for WebReport/400 to have proper access to the IFS on your system. After each change that you make, we recommend that you end the Mail Server Framework (ENDMSF) and then restart it (STRMSF) using the CLEAR option. If this does not cure the problem, use the WRKFLR command and locate the WEBWORK folder. Use option 14 to check the authority setting for the folder. Public should have ALL access rights. If you are still having problems, go to the INSTALL menu in library WEBREPORT and run option #9 (Update WebReport Default Settings - WEBSET). Check the following items: The first parameter must be set to a valid Email address at a valid domain location. The second parameter must show a text description of the sender. If there are any special characters in the name, try removing them. If none of the above suggestions help, contact Kisco Information Systems support staff for assistance. When I try to send Email to an Internet Address, WebReport/400 fails with a CPF0818 error. We found a problem that can cause this when you upgrade from Release 2 to Release 3 of WebReport/400. The problem is caused by a data area not getting setup correctly to work with Release 3. You can correct this problem by entering the following command on your AS/400: CHGDTAARA DTAARA(WEBREPORT/CONTROL (152 5)) VALUE('00001') Once this change is made, the error will stop occurring. Sometimes when converting a report to HTML, it fails with an LBE7207 error. We discovered a problem with this when you select to convert the report into a Source File and also specify an index creation. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 2.04 version of WebReport/400. The correction is available in PTF package WRPTF205. E-mail us and request the PTF package to correct this problem. I sent a report as Email. Everything looked like it was sent OK, but a CPI9046 error is issued after a short pause, and the Email is never delivered. This error code is issued when the system directory entry for the recipient is not configured correctly. Check the setup for the recipient using the WRKDIRE command. Check the setting for the value "Preferred address", it should be set to a value of 3' for "SMTP Name". This is the normal cause for this error situation. When I try to send a report as Email, it fails with error code CPFA097. This error code is issued when the user profile of the sender is not in the system directory. All users that send reports as Email must be enrolled in the system directory. Use the WRKDIRE command to review the contents of the directory. Users can be enrolled by using the 1' option from this directory display. When I try to send a report as Email, it fails with error code CPF3429. This error code indicates that the spool file you are trying to process is not an SCS (character-based) print spool file. WebReport/400, in its current release form, only processes SCS spool files. I just installed WebReport/400 and when I try to send a report as an Email message, I'm getting an error message of IWS1612. We discovered that early releases of WebReport/400 contained a CL command that was not supported by OS/400 when Client Access/400 is not installed as a part of the system. A fix for this has been developed and is now available as a PTF. This PTF can only be installed on a Release 2.01 version of WebReport/400. The correction is available in PTF package WRPTF202. E-mail us and request the PTF package to correct this problem. (Note: If you have CA400 installed, this PTF is not required. The next time you receive a release upgrade from us, the change will be included.) When I email a large report, it arrives as multiple messages and the text is garbled. This problem is caused by the way the AS/400 handles large MIME attachments. You can correct for this problem several different ways depending on the level of OS/400 on your system. For V4R5 or higher, run the following command: CHGPOPA MSGSPLIT(NOMAX) For V4R2 - V4R4, run the following command: CHGPOPA MSGSPLIT(2048) Note:* the above must be done, even if you are NOT using the OS/400 POP server function. For V4R1 or lower, use the following information taken from the IBM AS/400 service website: IBM AS/400 Support Line Technical Document Document Number: 10280308 Functional Area: AS/400 Mail Subfunctional Area: POP3 Sub-Subfunctional Area: General Product: TCP/IP FOR OS/400 - TCP/IP FOR OS/400 37 (5716TC100) TCP/IP UTILITIES (5769TC100) TCP/IP CONN UTILITY (5763TC100) Release: V3R7M0; V4R1M0 Document Title: Large MIME Messages Are Split into Multiple E-Mails Document Description: Many AS/400 mail users send SMTP, MIME-formatted messages often referred to as Internet mail. On the AS/400 system, these messages can be generated from many different sources including the AS/400 SNDDST command, PC applications that use Client Access MAPI (such as Lotus Mail R4.5), any POP3 application (such as Eudora, Microsoft Windows 95 Inbox, and so on), Domino for AS/400 MTA-attached users, and OfficeVision/400 users. Problem: The AS/400 system may split a large MIME message into multiple e-mails. This is a normal function and documented in the SMTP/MIME specifications. However, the receiving mail platform must also support reassembling the split messages. If it does not, the single e-mail appears as multiple e-mails. We have encountered several mail servers and/or mail gateways that do not support this function. This includes such products as: Lotus Domino Message Transfer Agent (MTA) running on non-AS/400 platforms and Microsoft Exchange SMTP/MIME Gateway. Circumvention: It is now possible to completely disable the Message Split function on R320, R370, and later systems. To disable Message split, create a special data area. On the OS/400 command line, type the following: CRTDTAARA DTAARA(QUSRSYS/QTMSNOSPLT) TYPE(CHAR) Press the Enter key. Note: R320 and R370 systems must first apply the following PTF to enable this feature: R320 SA68679 SF46243 R370 SA59873 SF46242 No special PTFs required for R410 or later Caution: Creation of partial/split notes is required by SMTP/MIME standards for notes over 2Meg in size. Using this circumvention limits the size of the note that can be sent. When I send a large report, I get an error message on a workfile when it appears to fill up.* The file size parameters for the work files have now been corrected and WebReport/400 will now process reports of any size. The correction is available in PTF package WRPTF105. E-mail us and request the PTF package to correct this problem. 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

WebReport/400 Problem Reports