Issue with the DAOS Estimator tool
Category
For people having issues with the DAOS estimator tool, the 8.5 forum is a good resource. IBM have posted a known issue and they are working on a fix.
"We are sorry you encountered a problem using the estimator.
A few other customers have seen this is as well. We believe that this is a bug opening a note (when MIME->CD converting message with a BinHex encoded attachment)
If this is the same problem we have seen, and NSD would show the hung thread in a mime conversion routine called by NSFNoteOpen. This bug was fixed in 8.03.
We will be posting an update to the estimator shortly which avoids this problem by not converting the mime portion of the message ( it should be faster as well)
It this does not seem like the same issue, take an NSD and send it to us."
For details, click here.
Update: A 1.1 release addressing this issue is now available for download. Click here
For people having issues with the DAOS estimator tool, the 8.5 forum is a good resource. IBM have posted a known issue and they are working on a fix.
"We are sorry you encountered a problem using the estimator.
A few other customers have seen this is as well. We believe that this is a bug opening a note (when MIME->CD converting message with a BinHex encoded attachment)
If this is the same problem we have seen, and NSD would show the hung thread in a mime conversion routine called by NSFNoteOpen. This bug was fixed in 8.03.
We will be posting an update to the estimator shortly which avoids this problem by not converting the mime portion of the message ( it should be faster as well)
It this does not seem like the same issue, take an NSD and send it to us."
For details, click here.
Update: A 1.1 release addressing this issue is now available for download. Click here
Comments
In this case the estimator will give bad results!! NSFNoteOpen will convert any MIME document to CD! And internally talking there are differences in the conversion: a mime document having an image is stored in an internal attachment and this internal attachment will be caught by DAOS.... while if you use NSFNoteOpen then the conversion will remove this $file.
Pls use NSFNoteOpenExt with the OPEN_RAW_MIME_PART flag...
Posted by dan At 11:13:58 On 27/01/2009 | - Website - |
Posted by Gary Rheaume At 14:23:24 On 27/01/2009 | - Website - |
Posted by Keith Ryan At 14:46:22 On 28/01/2009 | - Website - |
{ Link }
Posted by Paul Mooney At 11:20:59 On 27/01/2009 | - Website - |
I mean, it will work (no crash) but there will be plenty of Mime-To-CD conversion in the server side causing thousands of msgs in the console and consuming resources of the server CPU.
The worst part is not that, but the real problem is that when there is a Mime-To-CD conversion in memory, the document will internally loose attachments... for example a MIME document having one embedded image will contain an internal attachment and this attachment would be handled by DAOS in practice... once you do the conversion (because you used an old API) then this attachment is lost and you don't count it in the DAOS repository. So it will not give an accurate information.
Solution is to use the new API... it should take just 30 seconds.
It seems that this utility was developed in just one day.
Posted by dan At 11:43:47 On 27/01/2009 | - Website - |
Posted by dan At 11:45:43 On 27/01/2009 | - Website - |
Posted by Dan Rosato At 01:12:36 On 27/01/2009 | - Website - |
As a work around you could install 8.0.1, or 8.0.2, or 8.5? You do NOT need to upgrade your server to that release. The release just needs to be installed on the machine.
Problem: iSeries tightly binds dlls (service programs) to an explicit library. To support multi-versioning on iSeries, a wrapper libnotes was provided in the always present library QNOTES. All SDK applications (including DAOSEST) bind to this wrapper libnotes in QNOTES. This wrapper libnotes then determines the correct version of libnotes (be it 7.0.3, 8.0.2, 8.5,...) to forward the function call onto. The DAOSEST is using a nonstandard API (only on iSeries) and this API was not in our wrapper libnotes in 7.0.3. The 8.x versions of this wrapper contain this API.
Posted by Dan Rosato At 20:59:29 On 27/01/2009 | - Website - |
Posted by Kevin Kanarski At 16:43:51 On 27/01/2009 | - Website - |