Domino Diva

If you have DAOS implemented on the IBM i (iSeries, AS/400) platform, you need to be aware of two issues you can run into.  Both issues are referenced in tech note 1398097. 

The first issue is related to the 'tell daosmgr prune x' command.  When this command is executed on the iSeries, it ignores the number of days passed in on the command and defaults to 0. 

The second issue affects reading of the daos.cfg file.  If there are more than 40,000 .NLO files in a single DAOS subdirectory, the daos.cfg file is not read correctly.

If you are using DAOS on the IBM i, you should contact support to obtain the proper hotfixes to avoid running into these two issues.

There are two new IBM i blogs I would like to share with you.  The first blog, You and i, is a blog where the IBM i product manager (Craig Johnson) and chief architect (Steve Will), share what is going on with IBM i along with the technical details on how it works and what sets it apart.  If you have ever wondered what Single Level Store is and why it makes the iSeries better, check out Steve's lastest blog post.

The other new blog, iCan, is written by Dawn May.  Dawn is the technical lead and business architect for IBM i.  The focus of her blog is to share features of the operating system.  I know from working with my customers that it's really hard for most customers to keep on top of all of the new enhancements added each release.  Dawn's blog will shed light on various features the system offers.

I hope you find these blogs helpful.

I have found DDM probes to be very helpful in analyzing Domino performance issues with agents without having to go to all of the work to manually instrument the code.  I wrote an article for IBM System i magazine detailing how I have used DDM probes to help identify and optimize agents that are large memory consumers.  Here is a link to the article "The Importance of DDM Probes".

I hope you find the article helpful.

I have been fortunate enough to have two of my session abstracts accepted for speaking at the Midwest Lotus User Group (MWLUG) conference that will be held in Chicago, IL August 27-28.  My two sessions are:

• Dust Off Your Servers with a Server Health Check
• Domino Performance Best Practices on System i

If you are looking for great Lotus education, I recommend you check out this conference.  The opening session is being done by Ed Brill and there are three tracks:

• Administration and infrastructure
• Application development
• Business development

I would like to extend a special thank you to Gregg Eldred for pinging me about the conference and encouraging me to submit some abstracts, thanks Gregg!

I was recently doing some performance work for a customer and noticed in analyzing their memory checks and memory dumps there was a memory leak.  The application that was causing the memory leak was using LS2J.  I contacted support, and they were able to confirm that the memory leak indeed existed when using LotusScript to call Java.  I checked with another customer that restarts a couple of their application servers every evening.  Sure enough, on those servers, they were executing LS2J code. 

Both of my customers are running on iSeries (AS/400, System i), and it appears this may be the only platform affected, although this is not 100% for sure.  If you use LS2J calls in your applications, I recommend you do memory dumps and memory checks to see if there is indeed a memory leak.  If you find a memory leak, here is the SPR number you can reference when calling the issue into support:

SPR #: AHOE7TPQKC  [SPR number has been corrected]
My customers that encountered the LS2J memory leak are running 7.0.3, 8.0.2, and 8.5.