Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://blog.nashcom.de/nashcomblog.nsf/feed.rss

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <rss version="2.0"
  3. xmlns:dc="http://purl.org/dc/elements/1.1/"
  4. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  5. xmlns:admin="http://webns.net/mvcb/"
  6. xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  7. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  8. xmlns:wfw="http://wellformedweb.org/CommentAPI/">
  9. <channel>
  10. <title>Daniel Nashed&#8217;s Blog</title>
  11. <description>Domino on Linux/Unix, Troubleshooting, Best Practices, Tips and more ...</description>
  12. <link>http://blog.nashcom.de/nashcomblog.nsf/</link>
  13. <language>en-us</language>
  14. <lastBuildDate>Sat, 22 Apr 2017 11:13:16 +0200</lastBuildDate>
  15. <item>
  16. <title>Important Security Fix for IMAP</title>
  17. <pubDate>Sat, 22 Apr 2017 11:13:16 +0200</pubDate>
  18. <description>
  19. <![CDATA[
  20. In case you are running IMAP on a server that is reachable over the internet you should look into this fix ASAP. It might not be that critical for internal services. See details about this vulnerabi ...
  21. ]]>
  22. </description>
  23. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/important-imap-security-fix.htm</link>
  24. <category>IMAP</category>
  25. <dc:creator>Daniel Nashed</dc:creator>
  26. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/important-imap-security-fix.htm?opendocument&amp;comments</comments>
  27. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/important-imap-security-fix.htm</guid>
  28. <content:encoded><![CDATA[ <font size=2 face="sans-serif">In case you are running IMAP on a server that is reachable over the internet you should look into this fix ASAP.</font> <br /> <br /><font size=2 face="sans-serif">It might not be that critical for internal services.</font> <br /> <br /><font size=2 face="sans-serif">See details about this vulnerability here --> </font><a href="http://www.ibm.com/support/docview.wss?uid=swg22002280"><font size=2 color=blue face="sans-serif">http://www.ibm.com/support/docview.wss?uid=swg22002280</font></a> <br /> <br /><font size=2 face="sans-serif">All versions of Domino are affected!</font> <br /> <br />  ]]></content:encoded>
  29. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/important-imap-security-fix.htm</wfw:commentRss>
  30. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/important-imap-security-fix.htm?opendocument&amp;comments</wfw:comment>
  31. </item>
  32. <item>
  33. <title>NIFNSF Supported Maximum Size above 64 GB! -&gt; 1 TB is officially supported!</title>
  34. <pubDate>Fri, 21 Apr 2017 19:02:31 +0200</pubDate>
  35. <description>
  36. <![CDATA[
  37. After getting that question offline and having a discussion on my blog, I checked with IBM if they plan support NIFNSF sizes above 64 GB. Since it is kind of a database container and needs a database ...
  38. ]]>
  39. </description>
  40. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/nifnsf-supported-maximum-size-above-64-gb.htm</link>
  41. <category>NIFNSF</category>
  42. <dc:creator>Daniel Nashed</dc:creator>
  43. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/nifnsf-supported-maximum-size-above-64-gb.htm?opendocument&amp;comments</comments>
  44. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/nifnsf-supported-maximum-size-above-64-gb.htm</guid>
  45. <content:encoded><![CDATA[ <font size=2 face="sans-serif">After getting that question offline and having a discussion on my blog, I checked with IBM if they plan support NIFNSF sizes above 64 GB.</font><font size=3 face="sans-serif"> </font><font size=2 face="sans-serif"><br /> Since it is kind of a database container and needs a database handle someone could think that the maximum limit is also 64 GB.</font><font size=3 face="sans-serif"> </font><font size=2 face="sans-serif"><br /> That would give us at least 64 GB room for the NIF index -- which would be already a big improvement.</font><font size=3 face="sans-serif"> <br /> </font><font size=2 face="sans-serif"><br /> But from what I recall from some comments at Connect some years ago the maximum limit was not around 64 GB when they designed it.</font><font size=3 face="sans-serif"> <br /> </font><font size=2 face="sans-serif"><br /> On the other side it is difficult to test and such large view / folder index sizes. And you will not run into many situations where you need such a large size.</font><font size=3 face="sans-serif"> <br /> </font><font size=2 face="sans-serif"><br /> From what I heard, IBM is about to publish a supported official size for the NIFNSF indexs that is far beyond 64 GB. <br /> Stay tuned for the official statement. For now I can tell you that it will work above the 64 GB limit! </font><font size=3 face="sans-serif"><br /> </font><font size=2 face="sans-serif"><br /> On the other side a databases with that index size will reach other limits like application responsiveness issues because of the nature of complex views with many documents.</font><font size=3 face="sans-serif"> <br /> </font><font size=2 face="sans-serif"><br /> But it is good to know that it was designed to support larger sizes and also the counters in the database will continue to work as I have tested earlier for DAOS.</font><font size=3 face="sans-serif"> <br /> </font><font size=2 face="sans-serif"><br /> Once we get an official statement I will update my post and share the link.<br /> <br /> 25.04.2017 Update: <br /> <br /> The technical documentation has been updated --> </font><font size=2 color=blue face="sans-serif">https://www.ibm.com/support/knowledgecenter/SSKTMJ_9.0.1/admin/admn_moving_views_out_of_databases.html<br /> <br /> </font><font size=2 face="sans-serif">Here is the official statement for NIFNSF .NDX File size :-)</font> <br /> <br /><font size=3 face="sans-serif"><strong>".NDX files have a limit of 1 TB. The real determination of how large the views can grow is based on application responsiveness or if any other limits are reached before the 1 TB .NDX file limit is reached."</strong><br /> <br /> <br /> </font><font size=2 face="sans-serif">-- Daniel</font><font size=3 face="sans-serif"> </font>  ]]></content:encoded>
  46. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/nifnsf-supported-maximum-size-above-64-gb.htm</wfw:commentRss>
  47. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/nifnsf-supported-maximum-size-above-64-gb.htm?opendocument&amp;comments</wfw:comment>
  48. </item>
  49. <item>
  50. <title>Disclaimer Attachment Issue not yet fixed in IF1</title>
  51. <pubDate>Fri, 14 Apr 2017 20:28:40 +0200</pubDate>
  52. <description>
  53. <![CDATA[
  54. As Rob Kirkland commented in one of my last blog posted, the fix in IF1 does not solve the iusse. We both checked with IBM and got the reply that the SPR just changes back the default and disables th ...
  55. ]]>
  56. </description>
  57. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/disclaimer-attachment-issue-not-yet-fixed.htm</link>
  58. <category>FP</category>
  59. <dc:creator>Daniel Nashed</dc:creator>
  60. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/disclaimer-attachment-issue-not-yet-fixed.htm?opendocument&amp;comments</comments>
  61. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/disclaimer-attachment-issue-not-yet-fixed.htm</guid>
  62. <content:encoded><![CDATA[ <font size=2 face="sans-serif">As Rob Kirkland commented in one of my last blog posted, the fix in IF1 does not solve the iusse.</font> <br /> <br /><font size=2 face="sans-serif">We both checked with IBM and got the reply that the SPR just changes back the default and disables the change introduced in FP8 for Google calender integration.</font> <br /> <br /><font size=2 face="sans-serif">IBM is working on a fix hopefully makes it into FP9.</font> <br /> <br /><font size=2 face="sans-serif">So for now you should keep the notes.ini Parameter <strong>MIMEDisclaimersNoEncode=0</strong> disabled.</font> <br /> <br /><font size=2 face="sans-serif">Thanks to Rob to bring this up! </font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /><font size=2 face="sans-serif"><strong><br /> TPONAKFJLP</strong></font><font size=3> </font><font size=2 face="sans-serif"><br /> After upgrade to FP8, with disclaimers enabled, .pdf attachments have content-transfer-encoding of binary &nbsp; </font> <br /> <br />  ]]></content:encoded>
  63. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/disclaimer-attachment-issue-not-yet-fixed.htm</wfw:commentRss>
  64. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/disclaimer-attachment-issue-not-yet-fixed.htm?opendocument&amp;comments</wfw:comment>
  65. </item>
  66. <item>
  67. <title>Get Notes FP Version in &#64;Formulas </title>
  68. <pubDate>Wed, 12 Apr 2017 08:19:07 +0200</pubDate>
  69. <description>
  70. <![CDATA[
  71. In C-API and Lotus Script, Java developers the version information already shown for each FP. For example Lotus Script returns the full version string with session.NotesVersion. But if you want to ch ...
  72. ]]>
  73. </description>
  74. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/get-notes-fp-version-in-formulas.htm</link>
  75. <category>Feature Pack</category>
  76. <dc:creator>Daniel Nashed</dc:creator>
  77. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/get-notes-fp-version-in-formulas.htm?opendocument&amp;comments</comments>
  78. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/get-notes-fp-version-in-formulas.htm</guid>
  79. <content:encoded><![CDATA[ <font size=2 face="sans-serif">In C-API and Lotus Script, Java developers the version information already shown for each FP.</font> <br /><font size=2 face="sans-serif">For example Lotus Script returns the full version string with session.NotesVersion.</font> <br /> <br /><font size=2 face="sans-serif">But if you want to check the version information in @Formulas <strong>@Version</strong> will still return <strong>405</strong>.</font> <br /> <br /><font size=2 face="sans-serif">There is a new optional parameter which returns the Feature Pack version. </font> <br /><font size=2 face="sans-serif">So you use <strong>@Version</strong> to check the version and if it is 405 you check <strong>@Version(1)</strong> which will return <strong>8</strong> for Feature Pack 8.</font> <br /><font size=2 face="sans-serif">It is used in the new mail-template and will be updated for every new FP.</font> <br /> <br /><font size=2 face="sans-serif">@Version(1) returns 0 for older versions (I checked with a Notes 7 client to verify).</font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /> <br /> <br />  ]]></content:encoded>
  80. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/get-notes-fp-version-in-formulas.htm</wfw:commentRss>
  81. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/get-notes-fp-version-in-formulas.htm?opendocument&amp;comments</wfw:comment>
  82. </item>
  83. <item>
  84. <title>Notes/Domino 9.0.1 FP8 IF1 released</title>
  85. <pubDate>Tue, 11 Apr 2017 07:06:32 +0200</pubDate>
  86. <description>
  87. <![CDATA[
  88. Notes and Domino 9.0.1 FP8 IF1 has been shipped and there is also a separate fix for iNotes. All those IFs have the same version number but contain different SPRs! The most important IF is for the ...
  89. ]]>
  90. </description>
  91. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/notesdomino-9.0.1-fp8-if1-released.htm</link>
  92. <category>Notes</category>
  93. <dc:creator>Daniel Nashed</dc:creator>
  94. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/notesdomino-9.0.1-fp8-if1-released.htm?opendocument&amp;comments</comments>
  95. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/notesdomino-9.0.1-fp8-if1-released.htm</guid>
  96. <content:encoded><![CDATA[ <font size=2 face="sans-serif">Notes and Domino 9.0.1 FP8 IF1 has been shipped and there is also a separate fix for iNotes.</font> <br /> <br /><font size=2 face="sans-serif">All those IFs have the same version number but contain different SPRs! </font> <br /> <br /><font size=2 face="sans-serif">The most important IF is for the Domino Server. It fixes the disclaimer issue I reported before.</font> <br /><font size=2 face="sans-serif">And also the performance fix for the new feature NIFNSF which was introduced in in FP8.</font> <br /> <br /><font size=2 face="sans-serif">Be aware that NIFNSF is a server feature and not a client feature. It requires translog enabled on your server!<br /> Translog is not officially available on Notes clients.</font> <br /> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>Domino</strong></font> <br /> <br /><font size=2 face="sans-serif"><strong>YJIAAJ4MXV</strong></font> <br /><font size=2 face="sans-serif">Add new JNI wrappers to jNotes &nbsp; &nbsp; &nbsp; &nbsp;</font> <br /> <br /><font size=2 face="sans-serif"><strong>NNUZAG78H3</strong></font> <br /><font size=2 face="sans-serif">the tag includes some illegal characters, will be output not commentted as before. &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif"><strong>TPONAKFJLP</strong></font> <br /><font size=2 face="sans-serif">After upgrade to FP8, with disclaimers enabled, .pdf attachments have content-transfer-encoding of binary &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif"><strong>SWASAKELQ8</strong></font> <br /><font size=2 face="sans-serif">Perf issue w/ nifnsf enabled. &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif"><strong>LHEYAKALAH</strong></font> <br /><font size=2 face="sans-serif">Form Validation not working on an XPage &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>Notes </strong></font> <br /> <br /><font size=2 face="sans-serif"><strong>LHEYAKBJSQ</strong></font> <br /><font size=2 face="sans-serif">SSJS editor stops working in an NSF with a managed bean &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif"><strong>LHEYAKALAH</strong></font> <br /><font size=2 face="sans-serif">Form Validation not working on an XPage &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif"><strong>LHEYAKBJSQ</strong></font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; SSJS editor stops working in an NSF with a managed bean &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif"><strong>MDOYAKFPE2</strong></font> <br /><font size=2 face="sans-serif">XPages iNotes calendar control icons do not display the correct hover help text </font> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>iNotes</strong></font> <br /> <br /><font size=2 face="sans-serif"><strong>JJCMAKV3DT</strong></font> <br /><font size=2 face="sans-serif">iNotes "Starts With" window does not show when pressing any letter or number key <br /> <br /> </font>  ]]></content:encoded>
  97. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/notesdomino-9.0.1-fp8-if1-released.htm</wfw:commentRss>
  98. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/notesdomino-9.0.1-fp8-if1-released.htm?opendocument&amp;comments</wfw:comment>
  99. </item>
  100. <item>
  101. <title>Current Information about NIFNSF</title>
  102. <pubDate>Sat, 1 Apr 2017 00:42:31 +0200</pubDate>
  103. <description>
  104. <![CDATA[
  105. Domino 9.0.1 Feature Pack 8 introduced "NIFNSF" which allows to separate the view/folder index into a separate file. Let me try to summarized my current experience from my tests and from the field. ...
  106. ]]>
  107. </description>
  108. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/current-information-about-nifnsf.htm</link>
  109. <category></category>
  110. <dc:creator>Daniel Nashed</dc:creator>
  111. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/current-information-about-nifnsf.htm?opendocument&amp;comments</comments>
  112. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/current-information-about-nifnsf.htm</guid>
  113. <content:encoded><![CDATA[ <font size=2 face="sans-serif">Domino 9.0.1 Feature Pack 8 introduced "NIFNSF" which allows to separate the view/folder index into a separate file.</font> <br /> <br /><font size=2 face="sans-serif">Let me try to summarized my current experience from my tests and from the field.</font> <br /> <br /> <br /><font size=2 face="sans-serif">There are multiple benefits moving the index to a separate file.</font> <br /> <br /><font size=2 face="sans-serif"><strong>1. Backup Storage Reduction</strong></font> <br /> <br /><font size=2 face="sans-serif">First of all having the index in a separate file reduces the amount of data that you need to backup.</font> <br /><font size=2 face="sans-serif">For mail databases the index is around 10%. If you have DAOS enabled from the remaining data it's about 30%.</font> <br /><font size=2 face="sans-serif">So the backup time and backup storage in total is reduced.</font> <br /> <br /><font size=2 face="sans-serif"><strong>2. Size Limit of the data above 64 GB</strong></font> <br /> <br /><font size=2 face="sans-serif">The total size of a NSF is 64 GB. With DAOS enabled you can increase the logical size of a server based database by moving attachments to the DAOS store.</font> <br /><font size=2 face="sans-serif">For DAOS you can have external attachments up to 1 TB. Beyond that size the internal counters might overflow.</font> <br /> <br /><font size=2 face="sans-serif">But in some cases you still need more that 64 GB for NSF data and the view/folder indexes. With NIFNSF the limit is the 64 GB data in the NSF without the view/folder index.</font> <br /> <br /><font size=2 face="sans-serif"><strong>3. Performance</strong></font> <br /> <br /><font size=2 face="sans-serif">NIFNSF is intended to deliver better performance than having all data in a single NSF file.</font> <br /> <br /><font size=2 face="sans-serif">There is a current performance issue. For mail databases there should not be big difference.</font> <br /><font size=2 face="sans-serif">But for more complex views in applications the performance with NIFNSF might be not as good as without it.</font> <br /><font size=2 face="sans-serif">Tests have shown that it can take double the time. </font> <br /> <br /><font size=2 face="sans-serif">There is a pending fix that might be delivered with an IF for FP8 which should bring back the performance to almost the same as without NIFNSF.<br /> <br /> And for FP9 there is optimization planned to have better performance for concurrent operations. Those changes did not make it into FP8.</font> <br /> <br /><font size=2 face="sans-serif">So for now you might want to wait at least for an IF before enabling NIFNSF for complex applications.</font> <br /> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>-- Storage Location for NIFNSF --</strong></font> <br /> <br /> <br /><font size=2 face="sans-serif">There are multiple options to configure where to store the .NDX files which store the NIF data.</font> <br /><font size=2 face="sans-serif">What you choose depends on your environment,platform and your requirements.</font> <br /> <br /><font size=2 face="sans-serif">a.) Have NDX files stored next to your NSF files </font> <br /> <br /><font size=2 face="sans-serif">b.) Have NDX files stored in a separate folder in the data directory </font> <br /> <br /><font size=2 face="sans-serif">c.) Have NDX outside the data directory on the same disk</font> <br /> <br /><font size=2 face="sans-serif">d.) Have NDX stored on a separate disk</font> <br /> <br /><font size=2 face="sans-serif">There are no one size fits all recommendations. It really depends what storage situation and platform you are running on.</font> <br /> <br /><font size=2 face="sans-serif">If you can for example on Windows I would store NDX files at least outside the data directory.</font> <br /><font size=2 face="sans-serif">On Linux often without a new mount point you might not be able to move the NDX files outside the data directory, because often the data directory is a mount. </font> <br /> <br /><font size=2 face="sans-serif">If you need to increase your storage anyway because the NSF disk is full, having a separate disk (most of the times virtual disk) makes sense.,</font> <br /><font size=2 face="sans-serif">This is a good way for a clean new allocation and it will separate the I/O operations.</font> <br /> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>-- Enabling NIFSNSF on your Server --</strong></font> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>Translog</strong></font> <br /> <br /><font size=2 face="sans-serif">First requirement is that you are using transactions logging. Circular translog is perfectly OK for that.</font> <br /><font size=2 face="sans-serif">And translog is general recommendation for Domino anyway! For stability, fault recovery and also for performance!</font> <br /> <br /><font size=2 face="sans-serif"><strong>ODS 51 or higher</strong></font> <br /> <br /><font size=2 face="sans-serif">You will need at least ODS 51 for NIFSNSF. But I would recommend using ODS 52 for all databases on your server.</font> <br /> <br /><font size=2 face="sans-serif">notes.ini Create_R9_Databases=1 will ensure the ODS is updated the next time you run a copy-style compact.</font> <br /> <br /><font size=2 face="sans-serif"><strong>Notes.ini Settings</strong></font> <br /> <br /><font size=2 face="sans-serif">There are a couple notes.ini settings. The most important setting &nbsp;<strong>NIFNSFEnable=1 </strong>enables NIFNSF on your server.</font> <br /> <br /><font size=2 face="sans-serif">To store the NDX files in different locations (see options above) you can leverage <strong>NIFBasePath=path</strong> depending on your preferences.</font> <br /> <br /><font size=2 face="sans-serif">In addition if you want all new databases to be NIFNSF enabled there is another notes.ini setting <strong>CREATE_NIFNSF_DATABASES=1</strong> which will ensure that all new databases are automatically NIFNSF enabled.</font> <br /> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>-- Enabling NIFSNSF on a Database --</strong></font> <br /> <br /> <br /><font size=2 face="sans-serif">Once your server is NIFNSF enabled you can start enabling NIFNSF on your databases via compact.</font> <br /> <br /><font size=2 face="sans-serif">Please take care not to run the compact operation on all databases. We have seen customers who enabled NIFSNSF also on the DAOS catalog -- even the special database has no views.</font> <br /> <br /><font size=2 face="sans-serif">I would currently start with mail databases only! And you just specify the right mail directory.</font> <br /> <br /><font size=2 face="sans-serif">The normal recommendation is to use </font> <br /> <br /><font size=2 face="sans-serif"><strong>compact -c -NIFNSF ON mail/</strong></font> <br /> <br /><font size=2 face="sans-serif">This will enable the feature and also move existing indexes out of the NSF.</font> <br /><font size=2 face="sans-serif">But if the database is in use, the copy-style compact will not be possible.</font> <br /> <br /><font size=2 face="sans-serif">Instead you could enable NIFNSF on databases without copy-style compact and have a copy-style compact later on with either compact -c or leveraging the DBMT tool which you might have configured anyway.</font> <br /> <br /><font size=2 face="sans-serif">Once the database is on ODS 51 or higher and NIFNSF is enabled new indexes are created in the NDX file.</font> <br /><font size=2 face="sans-serif">But only the copy-style compact will move the views to the NDX file.</font> <br /> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>-- Checking NIFNSF --</strong></font> <br /> <br /> <br /><font size=2 face="sans-serif">You can check which databases are already NIFNSF enabled and there is also a way to see the size of the NDX. But this command shows all databases.</font> <br /> <br /><font size=2 face="sans-serif">The most useful commands shows all NIFNSF enabled databases.</font> <br /> <br /><font size=2 face="sans-serif"><strong>show dir -nifnsfonly</strong></font> <br /> <br /><font size=2 face="sans-serif">show only NIFNSF enabled databases</font> <br /> <br /><font size=2 face="sans-serif"><strong>show dir -nifnsf</strong></font> <br /> <br /><font size=2 face="sans-serif">show all databases with NDX files also</font> <br /> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>-- Maintaining Databases with NIFNSF enabled --</strong></font> <br /><font size=2 face="sans-serif"><strong><br /> </strong></font> <br /><font size=2 face="sans-serif">I have done some tests. Only with copy style compact the NDX will be compacted.</font> <br /><font size=2 face="sans-serif">Many customers are still using compact -B for an inplace, space reduction compact.</font> <br /> <br /><font size=2 face="sans-serif">There are also other reasons to leverage DBMT which is using copy style compacts and does use space pre-allocation to ensure the NSF is not allocated fragmented. </font> <br /> <br /><font size=2 face="sans-serif">The copy style compact will also shrink the NDX if needed. A compact -B did not free any space from the NDX file in my tests.</font> <br /> <br /><font size=2 face="sans-serif">However the free space in a NDX file should be still be reused if released from a purged view/folder index during normal runtime.</font> <br /> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>-- Tuning for NIFNSF --</strong></font> <br /> <br /><font size=2 face="sans-serif">A NDX file is a NSF file. The index data needs a container. Therefore if you are running a large server you have to make sure you have sufficient dbcache entries, because the NDX file will also need a cache entry.</font> <br /> <br /><font size=2 face="sans-serif">By default the dbcache handles depend on the size of the NSF Buffer Pool (which is 1024 MB for 64bit). The number of cache entries is around 3 times the buffer pool size in MB.</font> <br /> <br /><font size=2 face="sans-serif">3000 DbCache entries should be OK for most servers. But if your server is already on the limit you have to increase the limit.</font> <br /> <br /><font size=2 face="sans-serif">Here are the relevant server statistics from a current customer example:</font> <br /> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Database.DbCache.CurrentEntries = 4498</font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Database.DbCache.HighWaterMark = 4500</font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Database.DbCache.MaxEntries = 3000</font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Database.DbCache.OvercrowdingRejections = 15220</font> <br /> <br /><font size=2 face="sans-serif">Your CurrentEntries and HighWaterMark should be alwass below the MaxEntries.</font> <br /><font size=2 face="sans-serif">And the OvercrowdingRejections should be always zero!</font> <br /> <br /><font size=2 face="sans-serif">So in this case it would make sense to increase the number of cache entries to 6000 via:</font> <br /> <br /><font size=2 face="sans-serif">notes.ini <strong>NSF_DbCache_Maxentries=6000</strong></font> <br /> <br /><font size=2 face="sans-serif">&nbsp;</font>  ]]></content:encoded>
  114. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/current-information-about-nifnsf.htm</wfw:commentRss>
  115. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/current-information-about-nifnsf.htm?opendocument&amp;comments</wfw:comment>
  116. </item>
  117. <item>
  118. <title>CREATE_R9_LOG is not a valid notes.ini parameter and does not exist!</title>
  119. <pubDate>Fri, 24 Mar 2017 11:29:50 +0200</pubDate>
  120. <description>
  121. <![CDATA[
  122. After hearing this question twice a week I think it is time for a blog entry. There is a notes.ini parameter for the different ODS formats in different releases. The latest one you should use is Cre ...
  123. ]]>
  124. </description>
  125. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/create_r9_log-is-not-a-valid-notes.ini-parameter.htm</link>
  126. <category>Domino</category>
  127. <dc:creator>Daniel Nashed</dc:creator>
  128. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/create_r9_log-is-not-a-valid-notes.ini-parameter.htm?opendocument&amp;comments</comments>
  129. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/create_r9_log-is-not-a-valid-notes.ini-parameter.htm</guid>
  130. <content:encoded><![CDATA[ <font size=2 face="sans-serif">After hearing this question twice a week I think it is time for a blog entry.</font> <br /> <br /><font size=2 face="sans-serif">There is a notes.ini parameter for the different ODS formats in different releases. </font> <br /><font size=2 face="sans-serif">The latest one you should use is <strong>Create_R9_Databases=1</strong> to create databases with ODS 52.</font> <br /> <br /><font size=2 face="sans-serif">ODS 52 is needed for local databases which are encrypted (there was an underlying ODS issue that has been addressed in ODS 52).</font> <br /><font size=2 face="sans-serif">Also for hew new LargeSummary (16MB instead of 32KB per document) you need to be on ODS 52.</font> <br /> <br /><font size=2 face="sans-serif">But there is no new notes.ini parameter for the optimized aligned translog extends.</font> <br /> <br /><font size=2 face="sans-serif">The only parameter valid is still <strong>CREATE_R85_LOG=1.</strong></font> <br /> <br /><font size=2 face="sans-serif">I have dumped the string resources from the current binaries in 9.0.1 FP8 to double-check.</font> <br /> <br /><font size=2 face="sans-serif">There is no change for translog notes.ini parameters in Domino 9.0.1!</font> <br /> <br /><font size=2 face="sans-serif">Sounds like someone posted on his blog or added it to his presentation and others copied from there.</font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /> <br /><font size=2 face="sans-serif">libnotes.so:Create_R9_Databases</font> <br /><font size=2 face="sans-serif">libnotes.so:Create_R85_Databases</font> <br /><font size=2 face="sans-serif">libnotes.so:Create_R8_Databases</font> <br /><font size=2 face="sans-serif">libnotes.so:CREATE_R85_LOG</font>  ]]></content:encoded>
  131. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/create_r9_log-is-not-a-valid-notes.ini-parameter.htm</wfw:commentRss>
  132. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/create_r9_log-is-not-a-valid-notes.ini-parameter.htm?opendocument&amp;comments</wfw:comment>
  133. </item>
  134. <item>
  135. <title>Traveler 9.0.1.17 Relased with important bug fixes</title>
  136. <pubDate>Fri, 24 Mar 2017 09:12:07 +0200</pubDate>
  137. <description>
  138. <![CDATA[
  139. As posted before Traveler 9.0.1.16 had one issue that needed urgent attention. Push was not working when the mail-server had a short downtime. If you are on that release you should update asap. Ther ...
  140. ]]>
  141. </description>
  142. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-901-17-relased-with-important-bug-fixes.htm</link>
  143. <category>Traveler</category>
  144. <dc:creator>Daniel Nashed</dc:creator>
  145. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-901-17-relased-with-important-bug-fixes.htm?opendocument&amp;comments</comments>
  146. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-901-17-relased-with-important-bug-fixes.htm</guid>
  147. <content:encoded><![CDATA[ <font size=2 face="sans-serif">As posted before Traveler 9.0.1.16 had one issue that needed urgent attention. </font> <br /><font size=2 face="sans-serif">Push was not working when the mail-server had a short downtime.</font> <br /><font size=2 face="sans-serif">If you are on that release you should update asap.</font> <br /> <br /><font size=2 face="sans-serif">There are a couple of other fixes along with that ARPA included in 9.0.1.17. </font> <br /> <br /><font size=2 face="sans-serif">Just back from a couple of days of travel and installed it this morning. Looks good so far.<br /> <br /> </font> <table width=687 style="border-collapse:collapse;"> <tr valign=top height=8> <td width=102 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3><strong>APAR #</strong></font> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3><strong>Abstract</strong></font> <tr valign=top height=8> <td width=102 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO90889"><font size=3 color=blue><u>LO90889</u></font></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3>Invitee status not correct on mobile device if the invitee response is received in a non-syncing folder.</font> <tr valign=top height=8> <td width=102 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO91550"><font size=3 color=blue><u>LO91550</u></font></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3>Multiple ghost entries possible if adding invite to event that has outstanding updates pending.</font> <tr valign=top height=8> <td width=102 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO91723"><font size=3 color=blue><u>LO91723</u></font></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3>User may stop recieving updates to mobile device after mail server restarted and there is no backup mail server.</font> <tr valign=top height=8> <td width=102 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO91733"><font size=3 color=blue><u>LO91733</u></font></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3>Subject of mail replied to/forwarded from Windows 8 device may display incorrectly.</font> <tr valign=top height=8> <td width=102 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO91762"><font size=3 color=blue><u>LO91762</u></font></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3>IBM Traveler server may change case of Domino domain to all lower case when sending mail.</font> <tr valign=top height=8> <td width=102 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO91770"><font size=3 color=blue><u>LO91770</u></font></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3>Subject of new mail sent from Windows 8 device may display incorrectly.</font> <tr valign=top height=8> <td width=102 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO91819"><font size=3 color=blue><u>LO91819</u></font></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3>User may not be able to sync data to mobile device when the user's mail file name contains special characters.</font> <tr valign=top height=8> <td width=102 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO91870"><font size=3 color=blue><u>LO91870</u></font></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><font size=3>Wipe data option may be greyed out for iOS Verse client.</font></table> <br />  ]]></content:encoded>
  148. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/traveler-901-17-relased-with-important-bug-fixes.htm</wfw:commentRss>
  149. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-901-17-relased-with-important-bug-fixes.htm?opendocument&amp;comments</wfw:comment>
  150. </item>
  151. <item>
  152. <title>D9.0.1 FP8 Attachment Corruption Issue with Disclaimers</title>
  153. <pubDate>Tue, 21 Mar 2017 15:27:55 +0200</pubDate>
  154. <description>
  155. <![CDATA[
  156. There is an issue that has been reported about FP8. When using disclaimers attachments might be corrupted. IBM released a technote with details and is working on a fix. Feature Pack 8 contains an en ...
  157. ]]>
  158. </description>
  159. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/d9.0.1-fp8-attachment-corruption-issue-with-disclaimers.htm</link>
  160. <category></category>
  161. <dc:creator>Daniel Nashed</dc:creator>
  162. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/d9.0.1-fp8-attachment-corruption-issue-with-disclaimers.htm?opendocument&amp;comments</comments>
  163. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/d9.0.1-fp8-attachment-corruption-issue-with-disclaimers.htm</guid>
  164. <content:encoded><![CDATA[ <font size=2 face="sans-serif">There is an issue that has been reported about FP8. When using disclaimers attachments might be corrupted.</font> <br /><font size=2 face="sans-serif">IBM released a technote with details and is working on a fix. </font> <br /> <br /><font size=2 face="sans-serif">Feature Pack 8 contains an enhancement/fix to correctly send Google Calendar files.</font> <br /><font size=2 face="sans-serif">The fix is enabled by default and causes this corruption.</font> <br /> <br /><font size=2 face="sans-serif">You can still deploy FP8 and disable the feature/fix temporary via Notes.ini <strong>MIMEDisclaimersNoEncode=0</strong> on your SMTP outbound server.</font> <br /> <br /><font size=2 face="sans-serif">See this SPR #TPONAKFJLP / APAR &nbsp;#LO91828 for details</font> <br /><a href="http://www.ibm.com/support/docview.wss?uid=swg22000468"><font size=2 color=blue face="sans-serif">http://www.ibm.com/support/docview.wss?uid=swg22000468</font></a> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /> <br /> <br />  ]]></content:encoded>
  165. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/d9.0.1-fp8-attachment-corruption-issue-with-disclaimers.htm</wfw:commentRss>
  166. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/d9.0.1-fp8-attachment-corruption-issue-with-disclaimers.htm?opendocument&amp;comments</wfw:comment>
  167. </item>
  168. <item>
  169. <title>Traveler on Domino 9.0.1 FP8</title>
  170. <pubDate>Tue, 7 Mar 2017 23:51:34 +0200</pubDate>
  171. <description>
  172. <![CDATA[
  173. Domino 9.0.1 Feature Pack 8 has just shipped. If you are intending to update your Traveler Server to Domino FP8 you should be aware that you need at least Traveler 9.0.1.16 (which currently has an is ...
  174. ]]>
  175. </description>
  176. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-on-domino-9.0.1-fp8.htm</link>
  177. <category>Traveler</category>
  178. <dc:creator>Daniel Nashed</dc:creator>
  179. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-on-domino-9.0.1-fp8.htm?opendocument&amp;comments</comments>
  180. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-on-domino-9.0.1-fp8.htm</guid>
  181. <content:encoded><![CDATA[ <font size=2 face="sans-serif">Domino 9.0.1 Feature Pack 8 has just shipped.</font> <br /><font size=2 face="sans-serif">If you are intending to update your Traveler Server to Domino FP8 you should be aware that you need at least Traveler 9.0.1.16 </font> <br /><font size=2 face="sans-serif">(which currently has an issue reconnecting to a mail-server if it wasn't reachable --> see previous blog posts).</font> <br /> <br /><font size=2 face="sans-serif">If you still intend to update your server there are some important requirements. FP8 comes with Java 1.8 and Traveler is using that JVM.</font> <br /><font size=2 face="sans-serif">So it some changes are needed in the Traveler code to support the new JVM version.</font> <br /> <br /><font size=2 face="sans-serif">In addition for Traveler HA there are additional JDBC Requirements</font> <br /> <br /><font size=2 face="sans-serif">- If using DB2 server: In order to support Java 8 you must use DB2 JDBC Driver V10.5 FP7 (4.19.49) or higher, see technote 1983724 for details. </font> <br /> <br /><font size=2 face="sans-serif">- If using MS SQL server: In order to support Java 8 you must use sqljdbc42.jar file from MS JDBC 4.1 or later release. </font> <br /> <br /><font size=2 face="sans-serif">There is a new technote which contains links to the detailed technotes and also to the download sites</font> <br /> <br /><font size=2 face="sans-serif">--> &nbsp;</font><a href="http://www.ibm.com/support/docview.wss?uid=swg21999188"><font size=2 color=blue face="sans-serif">http://www.ibm.com/support/docview.wss?uid=swg21999188</font></a> <br /> <br /> <br /><font size=2 face="sans-serif">I updated my server to Domino 9.0.1 FP8 and Traveler 9.0.1.16 but you should probably wait for the fixed Traveler version before upgrading your server to FP8.</font>  ]]></content:encoded>
  182. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/traveler-on-domino-9.0.1-fp8.htm</wfw:commentRss>
  183. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-on-domino-9.0.1-fp8.htm?opendocument&amp;comments</wfw:comment>
  184. </item>
  185. <item>
  186. <title>Notes and Domino 9.0.1 Feature Pack 8 shipped</title>
  187. <pubDate>Tue, 7 Mar 2017 19:43:47 +0200</pubDate>
  188. <description>
  189. <![CDATA[
  190. Feature Pack 8 has shipped today including new templates. The new version comes with updated documentation for the Client, the Server and also for the Designer. For ADFS 3.0 there is brand new docume ...
  191. ]]>
  192. </description>
  193. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/notes-and-domino-9.0.1-feature-pack-8-shipped.htm</link>
  194. <category>Feature Pack 8</category>
  195. <dc:creator>Daniel Nashed</dc:creator>
  196. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/notes-and-domino-9.0.1-feature-pack-8-shipped.htm?opendocument&amp;comments</comments>
  197. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/notes-and-domino-9.0.1-feature-pack-8-shipped.htm</guid>
  198. <content:encoded><![CDATA[ <font size=2 face="sans-serif">Feature Pack 8 has shipped today including new templates.</font> <br /> <br /><font size=2 face="sans-serif">The new version comes with updated documentation for the Client, the Server and also for the Designer.</font> <br /><font size=2 face="sans-serif">For ADFS 3.0 there is brand new documentation that is not just in simple "cookbook" style. </font> <br /><font size=2 face="sans-serif">We had the opportinity to give feedback before it was released.</font> <br /> <br /><font size=2 face="sans-serif">Here is the main entries for the documentation.</font> <br /> <br /><font size=2 face="sans-serif">Beside Java 1.8 support, NIFNSF and large summary support there are a couple of other new stuff.</font> <br /> <br /><font size=2 face="sans-serif">XPages was not mentioned in the Domino development strategy session but XPages still gets attention and new functionality.</font> <br /> <br /><font size=2 face="sans-serif">Stay tuned for more information about FP8. Just installed the client update one minute ago...</font> <br /> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /> <br /> <br /><a href=http://www.lotus.com/ldd/fixlist.nsf/8d1c0550e6242b69852570c900549a74/26aa7417bb60f7df852580b40072af2d><font size=2 color=blue face="sans-serif">http://www.lotus.com/ldd/fixlist.nsf/8d1c0550e6242b69852570c900549a74/26aa7417bb60f7df852580b40072af2d</font></a> <br /> <br /> <br /><a href=https://www.ibm.com/support/knowledgecenter/SSKTMJ_9.0.1/admin/over_whats_new_in_fp8.html><font size=2 color=blue face="sans-serif">https://www.ibm.com/support/knowledgecenter/SSKTMJ_9.0.1/admin/over_whats_new_in_fp8.html</font></a> <br /> <br /><a href=https://www.ibm.com/support/knowledgecenter/SSKTWP_9.0.1/fram_newFP8_r.html><font size=2 color=blue face="sans-serif">https://www.ibm.com/support/knowledgecenter/SSKTWP_9.0.1/fram_newFP8_r.html</font></a> <br /> <br /><a href=https://www.ibm.com/support/knowledgecenter/SSVRGU_9.0.1/user/wpd_whatsnew_fp8_jan_2017.html><font size=2 color=blue face="sans-serif">https://www.ibm.com/support/knowledgecenter/SSVRGU_9.0.1/user/wpd_whatsnew_fp8_jan_2017.html</font></a> <br />  ]]></content:encoded>
  199. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/notes-and-domino-9.0.1-feature-pack-8-shipped.htm</wfw:commentRss>
  200. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/notes-and-domino-9.0.1-feature-pack-8-shipped.htm?opendocument&amp;comments</wfw:comment>
  201. </item>
  202. <item>
  203. <title>Travele 9.0.1.16 released with re-connect issue</title>
  204. <pubDate>Sun, 5 Mar 2017 16:26:41 +0200</pubDate>
  205. <description>
  206. <![CDATA[
  207. Traveler 9.0.1.16 has been released a while go with an issue that might impact you if you need to restart your mail servers. There is an APAR and there is already a hotfix available if you are alrea ...
  208. ]]>
  209. </description>
  210. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/travele-90116-released-with-re-connect-issue.htm</link>
  211. <category>Traveler</category>
  212. <dc:creator>Daniel Nashed</dc:creator>
  213. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/travele-90116-released-with-re-connect-issue.htm?opendocument&amp;comments</comments>
  214. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/travele-90116-released-with-re-connect-issue.htm</guid>
  215. <content:encoded><![CDATA[ <font size=2 face="sans-serif"><br /> Traveler 9.0.1.16 has been released a while go with an issue that might impact you if you need to restart your mail servers.</font><font size=3> </font><font size=2 face="sans-serif"><br /> There is an APAR and there is already a hotfix available if you are already on that release.</font><font size=3> </font><font size=2 face="sans-serif"><br /> If you are not on this release yet, you should wait for a new version!</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> There is also a work-around if you are on that release -- see below.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> 9.0.1.16 itself comes with a couple of bugfixes and preparation for Domino 9.0.1 FP8 which will introduce JVM 1.8.</font><font size=3> </font><font size=2 face="sans-serif"><br /> You will need to upgrade Traveler and will need a current JDBC driver. IBM said at Connect in SFO that there will be a detailed description as sonn 9.0.1 FP8 is released.</font><font size=3> <br /> <br /> <br /> </font><font size=2 face="sans-serif"><br /> LO91723: USERS STOP RECEIVING MAIL AFTER MAIL SERVER IS RESTARTED</font><font size=3> </font><font size=2 face="sans-serif"><br /> APAR status</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp;OPEN</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> Error description</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp;Traveler has a problem when all mail servers for a specific</font><font size=3> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp;user's goes down at one time and after the mail servers are</font><font size=3> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp;restarted users are able to synch data from the device, but no</font><font size=3> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp;new mails come down to the device. This was introduce in</font><font size=3> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp;9.0.1.16 fix pack.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp;The work around is to either do</font><font size=3> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp; - Tell Traveler Push Disable <UserId> and Tell Traveler Push</font><font size=3> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp;Enable <UserId> for each effected user or</font><font size=3> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp; - Restart IBM Traveler after the mail files have been</font><font size=3> </font><font size=2 face="sans-serif"><br />  &nbsp; &nbsp;restarted. Either of these approach will resolve the issue.</font><font size=3> <br /> <br /> </font>  ]]></content:encoded>
  216. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/travele-90116-released-with-re-connect-issue.htm</wfw:commentRss>
  217. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/travele-90116-released-with-re-connect-issue.htm?opendocument&amp;comments</wfw:comment>
  218. </item>
  219. <item>
  220. <title>Details about JVM 1.8 Update in Notes/Domino 9.0.1 FP8</title>
  221. <pubDate>Sun, 5 Feb 2017 23:30:51 +0200</pubDate>
  222. <description>
  223. <![CDATA[
  224. After my post I got a couple of offline and online questions about details for JVM 1.8 in the Notes Client. The release notes will be update but here is the comment from Scott in case you missed it i ...
  225. ]]>
  226. </description>
  227. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/details-about-jvm-1_8-update-in-notesdomino-901_fp8.htm</link>
  228. <category></category>
  229. <dc:creator>Daniel Nashed</dc:creator>
  230. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/details-about-jvm-1_8-update-in-notesdomino-901_fp8.htm?opendocument&amp;comments</comments>
  231. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/details-about-jvm-1_8-update-in-notesdomino-901_fp8.htm</guid>
  232. <content:encoded><![CDATA[ <font size=2 face="sans-serif">After my post I got a couple of offline and online questions about details for JVM 1.8 in the Notes Client.</font> <br /><font size=2 face="sans-serif"><br /> The release notes will be update but here is the comment from Scott in case you missed it in the comments.</font> <br /> <br /><font size=2 face="sans-serif">Thanks Scott for this detailed additonal information!!!</font> <br /> <br /> <br /> <br /><font size=2 face="Default MultiLingual">Java Upgrade to 1.8. <br /> </font> <br /><font size=2 face="Default MultiLingual">The Java run time environment provided with Domino has been upgraded to Java JRE version 1.8 to provide you with access to the latest features.<br />  <br /> - This is actually both Notes &amp; Domino. So the JRE will be 1.8 for both Notes &amp; Domino in 9.0.1 FP8. <br /> <br /> The preliminary fix list will be updated to state this. This was the first step. <br /> <br /> Designer will have 1.6 for compiling applications in FP8. But top of the list for the next FP is to upgrade the compiler in Designer to also use Java 1.8. </font> <br /> <br /><font size=2 face="Default MultiLingual">This will come with a number of other dependency upgrades:<br /> <br /> - Upgrading the version of Eclipse, SWT, OSGi for the Notes client &amp; Designer<br /> <br /> - Upgrading the version of OSGi for the Domino Server<br /> <br /> The work was big enough that it was separated into 2 Feature Packs. 901FP8 starts the work. <br /> <br /> Look for the session at IBM Connect 9am Wed Feb 22nd: Notes and Domino Roadmap</font> <br />  ]]></content:encoded>
  233. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/details-about-jvm-1_8-update-in-notesdomino-901_fp8.htm</wfw:commentRss>
  234. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/details-about-jvm-1_8-update-in-notesdomino-901_fp8.htm?opendocument&amp;comments</wfw:comment>
  235. </item>
  236. <item>
  237. <title>IBM Notes/Domino 9.0.1 Feature Pack 8 Preliminary Release Notice</title>
  238. <pubDate>Fri, 27 Jan 2017 15:57:33 +0200</pubDate>
  239. <description>
  240. <![CDATA[
  241. Today IBM released the first official information about Feature Pack 8 for Notes and Domino 9.0.1 The Preliminary Release Notice provides detailed information about the first feature pack which is c ...
  242. ]]>
  243. </description>
  244. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/new_features_nd901fp8.htm</link>
  245. <category>Domino 9.0.1</category>
  246. <dc:creator>Daniel Nashed</dc:creator>
  247. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/new_features_nd901fp8.htm?opendocument&amp;comments</comments>
  248. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/new_features_nd901fp8.htm</guid>
  249. <content:encoded><![CDATA[ <font size=2 face="sans-serif">Today IBM released the first official information about Feature Pack 8 for Notes and Domino 9.0.1 <br /> <br /> The Preliminary Release Notice provides detailed information about the first feature pack which is currently listed with status "gold candidate".<br /> <br /> </font><font size=2 color=blue face="sans-serif">http://www.lotus.com/ldd/fixlist.nsf/8d1c0550e6242b69852570c900549a74/26aa7417bb60f7df852580b40072af2d</font><font size=2 face="sans-serif"> </font> <br /><font size=2 face="sans-serif"><br /> Here are the release notes, with some comments from my side.</font><font size=2 color=blue face="sans-serif"> (comments in blue).</font><font size=2 face="sans-serif"> <br /> <br /> <strong><br /> Things to Note:</strong> </font> <ul> <li><font size=2 face="sans-serif"><strong>NBP replaced with ICAA - </strong>There is no NBP (Notes Browser Plugin) shipped with 9.0.1 FP8. This has been replaced with ICAA (IBM Client Application Access). For more information, see </font><a href=http://www.ibm.com/support/knowledgecenter/SS5SMW_1.0.1/topics/appacc_101_welcome.html><font size=2 color=blue face="sans-serif"><u>IBM Client Application Access V1.0.1 documentation</u></font></a><font size=2 face="sans-serif"> </font> </li><li><font size=2 face="sans-serif"><strong>Notes Client on Linux </strong>- There is no Notes client for Linux shipped with 9.0.1 FP8. This client platform has been discontinued and customers are encouraged to move to Windows or Mac. </font> </li><li><font size=2 face="sans-serif"><strong>Domino Server on Linux32 and AIX32 </strong>- There is no Domino Server for Linux32 and AIX32 shipped with 9.0.1 FP8. This server platform has been discontinued and customers are encouraged to move to the 64-bit platforms. Windows 32 bit remains a shipped and support platform. </font> </li><li><font size=2 face="sans-serif"><strong>Windows Server 2016 Support</strong> - (SPR #SVROAEPS4R)</font></li></ul><font size=2 color=blue face="sans-serif"><br /> It was an expected and announced move from the browser plugin to a stand-alone application because vanishing support for the type of plugins IBM is using.</font><font size=2 face="sans-serif"> <br /> </font><font size=2 color=blue face="sans-serif"><br /> Windows Server 2016 support is an important update for customers on the Windows platform. And Windows remains the only platform with 32bit support.<br /> Background is probably that applications like Sametime are still leveraging on the Windows 32bit Domino platform.</font><font size=2 face="sans-serif"> <br /> </font><font size=2 color=blue face="sans-serif"><br /> But for all other platforms including Linux moving to a 64bit only implementation only makes a lot of sense. For AIX customer should have moved already to native 64bit because of the limits of AIX segmented memory model.</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> For Linux most customers running mail and application servers and Traveler have already moved to native 64bit. </font><font size=2 face="sans-serif"><br /> </font><font size=2 color=blue face="sans-serif"><br /> The Linux client for SLED has been discontinued earlier. And there have been some discussions and rumors.</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> But dropping the Linux client support with FP8 completely was a surprise for me. </font><font size=2 face="sans-serif"><strong><br /> <br /> <br /> New Features in IBM® Domino® 9.0.1 Social Edition Feature Pack 8</strong><br /> The documentation in Knowledgebase will be updated with these new features to coincide with the ship date of 9.0.1 FP8<br /> <br /> 1) Optionally Move Views outside of NSF &nbsp;for Increased data store in NSF. <br /> This feature is useful for large databases and provides the following benefits:<br /> - A smaller database file size, to avoid reaching the 64GB limitation.<br /> - Faster database backup and restore.<br /> - Better performance by allowing concurrent access to database and views.<br /> </font><font size=2 color=blue face="sans-serif"><br /> This is a long awaited feature and brings a couple of benefits as mentioned in the release notes.</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> The feature can be enabled per database and the view index is stored in a separate file in either the same directory or in a complete different location (similar to the way FT index can be moved).</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> It allows storage optimization and has less contention. Also the fragmentation on the NSF disk will be reduced. And of course your backup solution does not need to backup index data (NIF).</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> The size of the view/folder index for a mail-databases are around 10% of the database size (that's before DAOS). With DAOS enabled the remaining size is 30-40% of the full database which means NIF is around 30% of the remaining NSF size.</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> That's a great improvement!</font><font size=2 face="sans-serif"> <br /> <br /> 2) Java Upgrade to 1.8. <br /> The Java run time environment provided with Domino has been upgraded to Java JRE version 1.8 to provide you with access to the latest features. <br /> </font><font size=2 color=blue face="sans-serif"><br /> The long waited update to Java 1.8 is shipping with FP8 :-)</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> This is the first step but the designer will hopefully be updated later this year to take benefit on new functionality for development of new application. </font><font size=2 face="sans-serif"><br /> <br /> <br /> 3) Optionally Increase Document Summary Data (SPR #AKNX64TLRS APARID: LO04193)<br /> You can increase the document summary data limit on Notes 9 databases to 16MB from 64K. (The size limit for a single field remains 32 K.)<br /> </font><font size=2 color=blue face="sans-serif"><br /> This feature is in discussion for a while and also a long waited new functionality. 64K for summary data not much but this was a difficult to change internal limitation.</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> Now with FP8 you can have up to 16MB summary data which is really an improvement for application developers!</font><font size=2 face="sans-serif"> <br /> <br /> 4) Add support for ADFS 3.0 and update the corresponding Cookbook instructions for configuration.<br /> </font><font size=2 color=blue face="sans-serif"><br /> ADFS 3.0 has been around for a while and is a much cleaner and straight forward implementation. It does not need IIS components and it build into the Windows server without extra download.</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> Also the administration and configuration is easier. Most customers looking into SAML today with Microsoft and other products are looking into ADFS 3.0.</font><font size=2 face="sans-serif"> </font><font size=2 color=blue face="sans-serif"><br /> So it was time to add ADFS 3.0 support. We implemented it for Web Federated Login for some customers and it worked well. Now we are getting official support!</font><font size=2 face="sans-serif"> <br /> </font><font size=2 color=blue face="sans-serif"><br /> Hopefully we get fully updated cook-books with cleaner and more detailed descriptions and background how to implement it. </font><font size=2 face="sans-serif"><br /> <strong><br /> <br /> New Features in IBM® Notes® 9.0.1 Social Edition Feature Pack 8</strong><br /> 1) Optionally Add Show Options: "Group By Date" And "Beginning Of Message", To Desktop Policy Settings (SPR #JSTN98BP3T APARID: LO75595)<br /> Administrators can add the notes.ini setting EnableGroupByDate=1 on mail servers to enable the Show > Group By Date option in all mail files.<br /> <br /> 2) Optionally Retain MIME formatting when forwarding or replying to internet messages<br /> A notes.ini setting is now available for Notes Standard clients to retain MIME message formatting when users reply to or forward messages received from the internet. Without this setting, MIME messages are converted to Notes Rich Text which can cause some MIME formatting to be lost.<br /> <br /> 3) Optionally Enable displaying internet addresses in mail and calendar documents<br /> You can enable internet addresses rather than Notes addresses to display in the Notes client mail and calendar. For example, display [email protected] rather than Samantha [email protected] To enable this feature, add the following setting to the notes.ini file on a Notes client $INETADDRESSFIXUP=1 <br /> </font><font size=2 color=blue face="sans-serif"><br /> Those changes in the Notes client show that there is still some development on the Notes client. <br /> Both features can make sense in many customer environments.</font><font size=2 face="sans-serif"> <br /> <br /> </font><font size=2 color=blue face="sans-serif"><br /> -- Daniel</font><font size=2 face="sans-serif"> </font>  ]]></content:encoded>
  250. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/new_features_nd901fp8.htm</wfw:commentRss>
  251. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/new_features_nd901fp8.htm?opendocument&amp;comments</wfw:comment>
  252. </item>
  253. <item>
  254. <title>Notes 9.0.1 FP7 IF1 released</title>
  255. <pubDate>Thu, 8 Dec 2016 15:59:38 +0200</pubDate>
  256. <description>
  257. <![CDATA[
  258. There is a new IF1 for the Notes Client. Now it begins to be more complicated. The client IF1 and the server IF1 for the Linux issue (see previous posts) have nothing to do with each other and contai ...
  259. ]]>
  260. </description>
  261. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/notes-9.0.1-fp7-if1-released.htm</link>
  262. <category>Notes Client</category>
  263. <dc:creator>Daniel Nashed</dc:creator>
  264. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/notes-9.0.1-fp7-if1-released.htm?opendocument&amp;comments</comments>
  265. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/notes-9.0.1-fp7-if1-released.htm</guid>
  266. <content:encoded><![CDATA[ <font size=2 face="sans-serif">There is a new IF1 for the Notes Client. Now it begins to be more complicated. </font> <br /><font size=2 face="sans-serif">The client IF1 and the server IF1 for the Linux issue (see previous posts) have nothing to do with each other and contain different SPRs.</font> <br /> <br /><font size=2 face="sans-serif">The most important fix is the issue we had with ID vault when the new port encryption is used.</font> <br /><font size=2 face="sans-serif">Given that the SPR is fixed in the client this looks like a client issue and not a server issue.</font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /> <br /><font size=2 face="sans-serif">Notes 9.0.1 Fix Pack 7 Interim Fix 1</font> <br /> <br /><font size=2 face="sans-serif">RGAUADUM59</font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Duplicate Attachment Icons When Using Ls Embedobject To Attach Files To A NotesRichTextItem &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif">BBSZAEEK8C</font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Notes User Id File Upload To Vault Failed If Port_enc_adv Parameter Is Enabled </font> <br />  ]]></content:encoded>
  267. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/notes-9.0.1-fp7-if1-released.htm</wfw:commentRss>
  268. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/notes-9.0.1-fp7-if1-released.htm?opendocument&amp;comments</wfw:comment>
  269. </item>
  270. <item>
  271. <title>Traveler 9.0.1.15 available with some important changes</title>
  272. <pubDate>Tue, 15 Nov 2016 19:14:58 +0200</pubDate>
  273. <description>
  274. <![CDATA[
  275. Traveler 9.0.1.15 has been released with some important fixes and also changes. The Release documentation has some interesting details. Here is the extract from the release documentation with some co ...
  276. ]]>
  277. </description>
  278. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.15-available-with-some-important-fixes.htm</link>
  279. <category>Traveler</category>
  280. <dc:creator>Daniel Nashed</dc:creator>
  281. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.15-available-with-some-important-fixes.htm?opendocument&amp;comments</comments>
  282. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.15-available-with-some-important-fixes.htm</guid>
  283. <content:encoded><![CDATA[ <font size=2 face="sans-serif">Traveler 9.0.1.15 has been released with some important fixes and also changes. The Release documentation has some interesting details.</font> <br /> <br /><font size=2 face="sans-serif">Here is the extract from the release documentation with some comments.</font> <br /> <br /><font size=2 face="sans-serif"><strong>What's New</strong></font> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>"Device wipe is no longer an option for iOS 10.x devices as support was dropped by Apple. You can still use the Wipe Traveler Data option."</strong></font> <br /> <br /><font size=2 face="sans-serif">For security reasons Apple disabled wipe over ActiveSync which is understandable. Before that change every server could wipe any device connected via ActiveSync.</font> <br /><font size=2 face="sans-serif">With this Apple side change Traveler could not delete the device any more and the status from the device was not interpreted correctly by the server.</font> <br /><font size=2 face="sans-serif">Traveler does now check if the device still supports the wipe (running iOS earlier than 10.x) and does only allow the Data Wipe over ActiveSync if the full wipe is not supported on the device.</font> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>"Yellow status message if the IBM Traveler server is not listed as a Trusted Server for an end user's mail server. This is required for future security and feature enhancements planned for 2017. The status message will include information about how to correct."</strong></font> <br /> <br /><font size=2 face="sans-serif">Sounds like IBM is planning a bigger change in 2017 for Traveler. I am curious what this higher security requirements are needed for. Trusted Servers are a quite high requirement which allow the Traveler servers to fully authenticate as any user on the mail server. It's much higher than just granting manager access to an individual mailfile. </font> <br /> <br /><font size=2 face="sans-serif">I have removed the Trusted Servers entry on my mail-server but I did not yet see the warning.</font> <br /> <br /><font size=2 face="sans-serif"><strong>"Database schema updates to improve data integrity.</strong></font> <br /> <br /><font size=2 face="sans-serif"><strong>Tablerepair tell command to support the above schema updates. A warning message will be displayed at startup if any of the schema updates were not applied with instructions to run the tablerepair command. The server will continue to function properly if no action taken.</strong></font> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>NOTE: IBM Traveler 9.0.1.15 does include a database schema update. Action may be required if you manually manage your database schema (this is not common). If you use auto schema updates (default behavior) there is no action required. See Updating the Enterprise Database for more information (</strong></font><a href=http://www.ibm.com/support/knowledgecenter/SSYRPW_9.0.1/UpdatingTheEnterpriseDatabase.dita><font size=2 color=blue face="sans-serif"><strong>http://www.ibm.com/support/knowledgecenter/SSYRPW_9.0.1/UpdatingTheEnterpriseDatabase.dita</strong></font></a><font size=2 face="sans-serif"><strong>)"</strong></font> <br /> <br /> <br /><font size=2 face="sans-serif">So this is an important information. This new version requires a schema change. If you are running stand-alone that should not cause any issues.</font> <br /><font size=2 face="sans-serif">If you have automatic schema update enabled the schema update should also happen automatically. <br /> And if you are switching from manual schema update to automatic schema update you should be careful. There is one ARPA fixed for DB2 and you should be aware of the default schema name differences for manual and automatic schema configuration.</font> <br /><font size=2 face="sans-serif">I guess with this schema change the issue has been discovered and the fix is that the NTS parameter with the schema name will be automatically set. </font> <br /><font size=2 face="sans-serif">(See -> </font><a href="http://www-01.ibm.com/support/docview.wss?uid=swg1LO90497"><font size=2 color=blue face="sans-serif">http://www.ibm.com/support/docview.wss?uid=swg1LO90497</font></a><font size=2 face="sans-serif"> for details).</font> <br /> <br /> <br /><font size=2 face="sans-serif">The fix-list contains some other important fixes! Check the fixlist link below for details.</font> <br /> <br /><font size=2 face="sans-serif">My server is already updated but I had not much time to test.</font> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>IBM Traveler Fixes 9.0.1.15</strong></font> <br /> <br /><a href="http://www.ibm.com/support/docview.wss?uid=swg21700212#90115"><font size=2 color=blue face="sans-serif">http://www.ibm.com/support/docview.wss?uid=swg21700212#90115</font></a> <br /> <br /><font size=2 face="sans-serif"><strong>IBM Traveler 9.0.1.15 Server Release Documentation</strong></font> <br /> <br /><a href="http://www.ibm.com/support/docview.wss?uid=swg21994070"><font size=2 color=blue face="sans-serif">http://www.ibm.com/support/docview.wss?uid=swg21994070</font></a> <br />  ]]></content:encoded>
  284. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/traveler-9.0.1.15-available-with-some-important-fixes.htm</wfw:commentRss>
  285. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.15-available-with-some-important-fixes.htm?opendocument&amp;comments</wfw:comment>
  286. </item>
  287. <item>
  288. <title>DNUG Domino Day 2016 in DUS und DNUG Comes to you in BER</title>
  289. <pubDate>Fri, 21 Oct 2016 13:13:55 +0200</pubDate>
  290. <description>
  291. <![CDATA[
  292. Auch in diesem Jahr haben wir wieder einen DNUG Event im Bereich Notes/Domino in Düssldorf. Und Anfang November hat Anett Hammerschmidt für unsere Fachgruppe einen halben Tag DNUG Comes To you mit ...
  293. ]]>
  294. </description>
  295. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/DNUG-domino-day-2016.htm</link>
  296. <category>DNUG</category>
  297. <dc:creator>Daniel Nashed</dc:creator>
  298. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/DNUG-domino-day-2016.htm?opendocument&amp;comments</comments>
  299. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/DNUG-domino-day-2016.htm</guid>
  300. <content:encoded><![CDATA[ <img  alt="DNUG &amp;#34;Domino Day&amp;#34; - Fachgruppen-Tag Notes/Domino/Verse" border="0" src="http://blog.nashcom.de/nashcomblog.nsf/dx/DNUG-domino-day-2016.htm/content/M2?OpenElement" /> <br /> <br /> <br /><font size=2 face="sans-serif">Auch in diesem Jahr haben wir wieder einen DNUG Event im Bereich Notes/Domino in Düssldorf.</font> <br /><font size=2 face="sans-serif">Und Anfang November hat Anett Hammerschmidt für unsere Fachgruppe einen halben Tag DNUG Comes To you mit anschließendem DNUG Stammtisch in Berliin.</font> <br /> <br /><font size=2 face="sans-serif">Bei beiden Events geht es um atkeulle Themen und Entwicklungen im Bereich Notes und Domino.</font> <br /><font size=2 face="sans-serif">Und es werden auch Kollegen von IBM vor Ort sein, mit denen man die aktuelle Strategie von IBM im Bereich Notes/Domino diskutieren kann.</font> <br /> <br /><font size=2 face="sans-serif">Ich hoffe viele von Euch auf einem der beiden Events begrüßen zu können.</font> <br /> <br /><font size=2 face="sans-serif">Anbei die Links zu beiden Veranstaltungen.</font> <br /> <br /><font size=2 face="sans-serif">Beide Tage sind für DNUG Mitglieder kostenlos . </font> <br /><font size=2 face="sans-serif">Aber auch Nicht-Mitglieder sind herzlich eingeladen (mit einem Kostenbeitrag am Domino Day).</font> <br /> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>DNUG "Domino Day" - Fachgruppen-Tag Notes/Domino/Verse</strong></font> <br /> <br /><font size=2 face="sans-serif">Donnerstag, 24. November in Düsseldorf</font> <br /> <br /><a href="https://www.eventbrite.de/e/dnug-domino-day-fachgruppen-tag-notesdominoverse-tickets-28526425306"><font size=2 color=blue face="sans-serif">https://www.eventbrite.de/e/dnug-domino-day-fachgruppen-tag-notesdominoverse-tickets-28526425306</font></a> <br /> <br /><font size=2 face="sans-serif"><strong>BERLIN - DNUG: Team Verse and Notes Domino Comes to You</strong></font> <br /> <br /><font size=2 face="sans-serif">Mittwoch, 2. November in Berlin</font> <br /> <br /><a href="https://www.eventbrite.de/e/berlin-dnug-team-verse-and-notes-domino-comes-to-you-tickets-28675598487"><font size=2 color=blue face="sans-serif">https://www.eventbrite.de/e/berlin-dnug-team-verse-and-notes-domino-comes-to-you-tickets-28675598487</font></a> <br /> <br /> <br />  ]]></content:encoded>
  301. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/DNUG-domino-day-2016.htm</wfw:commentRss>
  302. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/DNUG-domino-day-2016.htm?opendocument&amp;comments</wfw:comment>
  303. </item>
  304. <item>
  305. <title>IBM Champion Nomination 2016</title>
  306. <pubDate>Tue, 18 Oct 2016 11:07:09 +0200</pubDate>
  307. <description>
  308. <![CDATA[
  309. The IBM Champion program is a great way to thank active members of the community and also to help them in some way to continue their work for the community. The nomination is still open until Novembe ...
  310. ]]>
  311. </description>
  312. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-champion-nomination-2016.htm</link>
  313. <category>Champion</category>
  314. <dc:creator>Daniel Nashed</dc:creator>
  315. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-champion-nomination-2016.htm?opendocument&amp;comments</comments>
  316. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-champion-nomination-2016.htm</guid>
  317. <content:encoded><![CDATA[ <font size=2 face="sans-serif">The IBM Champion program is a great way to thank active members of the community and also to help them in some way to continue their work for the community. </font> <br /><font size=2 face="sans-serif">The nomination is still open until November 14th. So you still have time to nominate someone. Or renominate one of the current IBM Champions. </font> <br /> <br /><font size=2 face="sans-serif">See some details and official links below.</font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /><font size=2 face="sans-serif">"The IBM Champion program recognizes innovative thought leaders in the technical community — and rewards these contributors by amplifying their voice and increasing their sphere of influence. </font> <br /><font size=2 face="sans-serif">An IBM Champion is an IT professional, business leader, developer, or educator who influences and mentors others to help them make best use of IBM software, solutions, and services." </font> <br /> <br /><font size=2 face="sans-serif">So if there is someone you think how deserves it, here is the nomination form --> </font><a href="http://blog.nashcom.de/nashcomblog.nsf/dx/www.ibm.com/developerworks/community/profiles/dw/anonymous.jsp?id=2016"><font size=2 color=blue face="sans-serif">www.ibm.com/developerworks/community/profiles/dw/anonymous.jsp?id=2016</font></a> <br /> <br /><font size=2 face="sans-serif">For more details see --> </font><a href="https://www.ibm.com/developerworks/community/blogs/ibmchampion/entry/Nominate_an_IBM_Champion_Nominations_OPEN?lang=en"><font size=2 color=blue face="sans-serif">https://www.ibm.com/developerworks/community/blogs/ibmchampion/entry/Nominate_an_IBM_Champion_Nominations_OPEN?lang=en</font></a> <br /> <br />  ]]></content:encoded>
  318. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/ibm-champion-nomination-2016.htm</wfw:commentRss>
  319. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-champion-nomination-2016.htm?opendocument&amp;comments</wfw:comment>
  320. </item>
  321. <item>
  322. <title>IBM Domino 9.0.1 Fix Pack 7 Interim Fix 1 addresses critical issues affecting Domino 9.0.1 FP7 for Linux64 &amp; zLinux64</title>
  323. <pubDate>Fri, 14 Oct 2016 12:08:35 +0200</pubDate>
  324. <description>
  325. <![CDATA[
  326. As reported before on Linux64 there is a issue with the cluster replicator which has been addressed with IF1 (SPR #KBRNAEMPX2). Because of a change in FP7 that needed a recompile of the whole core inc ...
  327. ]]>
  328. </description>
  329. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-domino-9.0.1-fix-pack-7-interim-fix-1-addresses-critical-issues-affecting-domino-9.0.1-fp7-for-linux64-zlinux64.htm</link>
  330. <category></category>
  331. <dc:creator>Daniel Nashed</dc:creator>
  332. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-domino-9.0.1-fix-pack-7-interim-fix-1-addresses-critical-issues-affecting-domino-9.0.1-fp7-for-linux64-zlinux64.htm?opendocument&amp;comments</comments>
  333. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-domino-9.0.1-fix-pack-7-interim-fix-1-addresses-critical-issues-affecting-domino-9.0.1-fp7-for-linux64-zlinux64.htm</guid>
  334. <content:encoded><![CDATA[ <font size=2 face="sans-serif">As reported before on Linux64 there is a issue with the cluster replicator which has been addressed with IF1 (<strong>SPR #KBRNAEMPX2</strong>).</font> <br /><font size=2 face="sans-serif">Because of a change in FP7 that needed a recompile of the whole core including all components (<strong>SPR# KBRN9Q7EZW</strong>) but some files where missing in the installations.</font> <br /> <br /><font size=2 face="sans-serif">IBM has fixed the issue with 9.0.1 FP7 IF1 which is already available for download. I got it already yesterday for testing thru our PMR and it replaces the missing files.</font> <br /> <br /><font size=2 face="sans-serif">If you are running Domino on Linux64 with FP7 you should update your server asap to IF1.</font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /><font size=2 face="sans-serif">The this linke for additional information and download links</font> <br /> <br /><a href="http://www.ibm.com/support/docview.wss?uid=swg21992376"><font size=2 color=blue face="sans-serif">http://www.ibm.com/support/docview.wss?uid=swg21992376</font></a> <br /> <br /> <br /><font size=2 face="sans-serif">here is the list of files replaced by IF1</font> <br /> <br /><font size=2 face="sans-serif">rwxr-xr-x 1 root root &nbsp;33K Aug 18 16:42 billing</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root &nbsp;54K Aug 18 16:42 cldbdir</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root &nbsp;58K Aug 18 16:42 clrepl</font> <br /><font size=2 face="sans-serif">-r--r--r-- 1 root root 6.9K Sep 13 22:39 daosmgr.res</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root 160K Aug 18 16:42 decs</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root 408K Aug 18 16:42 libdcapi.so</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root 390K Aug 18 16:42 libdchtapi.so</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root 188K Aug 18 16:42 libdcrtapi.so</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root 300K Aug 18 16:42 libdecsext.so</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root 333K Aug 18 16:43 libdomws.so</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root 8.0K Aug 18 16:41 libhttprs.so</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root 230K Aug 18 16:42 liblsxlc.so</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root &nbsp;15K Oct 12 23:57 libndgts.so</font> <br /><font size=2 face="sans-serif">-rwxr-xr-x 1 root root 9.2K Aug 18 16:41 librshttp.so</font> <br /><font size=2 face="sans-serif">-r--r--r-- 1 root root &nbsp;11K Sep 13 22:39 smtp.res</font>  ]]></content:encoded>
  335. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/ibm-domino-9.0.1-fix-pack-7-interim-fix-1-addresses-critical-issues-affecting-domino-9.0.1-fp7-for-linux64-zlinux64.htm</wfw:commentRss>
  336. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-domino-9.0.1-fix-pack-7-interim-fix-1-addresses-critical-issues-affecting-domino-9.0.1-fp7-for-linux64-zlinux64.htm?opendocument&amp;comments</wfw:comment>
  337. </item>
  338. <item>
  339. <title>Domino 9.0.1 FP7 issue Notes User Id File Upload To Vault Failed If Port_enc_adv Parameter Is Enabled</title>
  340. <pubDate>Wed, 12 Oct 2016 12:45:24 +0200</pubDate>
  341. <description>
  342. <![CDATA[
  343. Alex Novak mentioned another issue with FP7 which might affect you in my blog comments. We only have the public description of the SPR and I assume only the ID Vault server communication is affected ...
  344. ]]>
  345. </description>
  346. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-fp7-issue-notes-user-id-file-upload-to-vault-failed-if-port_enc_adv-parameter-is-enabled.htm</link>
  347. <category>Security</category>
  348. <dc:creator>Daniel Nashed</dc:creator>
  349. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-fp7-issue-notes-user-id-file-upload-to-vault-failed-if-port_enc_adv-parameter-is-enabled.htm?opendocument&amp;comments</comments>
  350. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-fp7-issue-notes-user-id-file-upload-to-vault-failed-if-port_enc_adv-parameter-is-enabled.htm</guid>
  351. <content:encoded><![CDATA[ <font size=2 face="sans-serif">Alex Novak mentioned another issue with FP7 which might affect you in my blog comments. </font> <br /> <br /><font size=2 face="sans-serif">We only have the public description of the SPR and I assume only the ID Vault server communication is affected.</font> <br /> <br /><font size=2 face="sans-serif">SPR # BBSZAEEK8C APAR #LO90429.: Notes User Id File Upload To Vault Failed If Port_enc_adv Parameter Is Enabled</font> <br /> <br /><font size=2 face="sans-serif">So for now you should not enable the new AES encryption on your ID Vault server until this issue is fixed.</font> <br /> <br /><font size=2 face="sans-serif">Given the 3 issues I reported in the last days in my blog (one is only effecting Linux64) I would wait for the next IF that hopefully addresses all those issues if you did not deploy it yet.</font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br />  ]]></content:encoded>
  352. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/domino-9.0.1-fp7-issue-notes-user-id-file-upload-to-vault-failed-if-port_enc_adv-parameter-is-enabled.htm</wfw:commentRss>
  353. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-fp7-issue-notes-user-id-file-upload-to-vault-failed-if-port_enc_adv-parameter-is-enabled.htm?opendocument&amp;comments</wfw:comment>
  354. </item>
  355. </channel></rss>
  356.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//blog.nashcom.de/nashcomblog.nsf/feed.rss

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda