WebReport/400 Problem Reports

Index:

• 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 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.

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.

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.

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.

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.

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.

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.

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:

1. Delete any documents that may exist in the current WEBWORK folder
2. Delete the folder
3. Sign on under a user profile other than QSECOFR that has security officer authority and issue the command: CRTFLR WEBWORK
4. Then issue the command WRKFLR
5. Find the WEBWORK folder and key a '14' next to it
6. On the next screen, change the public authority to *ALL
7. Then, before leaving that screen, press F6 and add user profile QMSF with *ALL authority
8. Get back to an OS/400 command line by pressing ENTER to record all of the changes
9. End the QMSF job using the command: ENDMSF
10. Restart the QMSF job using the command: STRMSF MSGOPT(*CLEAR) NBRMSFJOB(1)

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:

1. The first parameter must be set to a valid Email address at a valid domain location.
2. The second parameter must show a text description of the sender. If there are any special characters in the name, try removing them.

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') 

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.

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.

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.

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.

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.)

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.

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.

Phone: (914) 241-7233 Fax: (914) 241-9140

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