PMDF V6.7 Release Notes July 2015 This is a document containing a list of new fea- tures and bug fixes that have been made since PMDF V6.6. Software Version: PMDF V6.7 Operating System and Version: Solaris SPARC or In- tel V2.6, V8 or later; (SunOS V5.6, V5.8 or later); Red Hat En- terprise Linux 4 up- date 4 or later on x86 (or other com- patible Linux dis- tribution); OpenVMS VAX V6.1 or later; OpenVMS Alpha V7.0 or later; OpenVMS I64 V8.2 or later; Win- dows 2003 ii __________ Copyright ©2015 Process Software, LLC. Unpublished - all rights reserved under the copyright laws of the United States Process Software, LLC ("Process") makes no rep- resentations or warranties with respect to the con- tents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Process Software reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Process Software to notify any person of such revision or changes. Use of PMDF, PMDF-DIRSYNC, PMDF-FAX, PMDF-LAN, PMDF-MR, PMDF-MSGSTORE, PMDF-MTA, PMDF-TLS, PMDF- X400, PMDF-X500, PMDF-XGP, and/or PMDF-XGS soft- ware and associated documentation is authorized only by a Software License Agreement. Such license agree- ments specify the number of systems on which the software is authorized for use, and, among other things, specifically prohibit use or duplication of software or documentation, in whole or in part, except as authorized by the Software License Agree- ment. Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or as set forth in the Commercial Computer Software - Restricted Rights clause at FAR 52.227-19. The PMDF mark and AlphaMate is a registered all PMDF-based trademark of Motorola, Inc. trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries and are used under license. ALL-IN-1, Alpha AXP, cc:Mail is a trademark of AXP, Bookreader, cc:Mail, Inc., a wholly- DEC, DECnet, HP, owned subsidiary of Lotus I64, IA64, Integrity, Development Corporation. MAILbus, MailWorks, Lotus Notes is a registered Message Router, trademark of Lotus MicroVAX, OpenVMS, Development Corporation. Pathworks, PSI, RMS, TeamLinks, TOPS-20, Tru64, TruCluster, ULTRIX, VAX, VAX Notes, VMScluster, VMS, and WPS-PLUS are registered trademarks of Hewlett- Packard Company. iv AS/400, CICS, IBM, RC2 and RC4 are registered Office Vision, trademarks of RSA Data OS/2, PROFS, and Security, Inc. VTAM are registered trademarks of International Business Machines Corporation. CMS, DISOSS, OfficeVision/VM, OfficeVision/400, OV/VM, and TSO are trademarks of International Business Machines Corporation. dexNET is a registered Ethernet is a registered trademark of Fujitsu trademark of Xerox Imaging Systems of Corporation. America, Inc. FaxBox is a registered GIF and "Graphics Interchange trademark of DCE Format" are trademarks of Communications Group CompuServe, Incorporated. Limited. InterConnections InterDrive is a registered is a trademark of trademark of FTP Software, InterConnections, Inc. Inc. LANmanager and Memo is a trade mark of Microsoft are Verimation ApS. registered trademarks of Microsoft Corporation. MHS, Netware, and LaserJet and PCL are Novell are registered registered trademarks of trademarks of Novell, Hewlett-Packard Company. Inc. v PGP and Pretty Good Jnet is a registered Privacy are registered trademark of Wingra, Inc. trademarks of Pretty Good Privacy, Inc. Attachmate is a Pine and Pico are trademarks registered trademark of the University of and PathWay is a Washington, used by trademark of Attachmate permission. Corporation. PostScript is a Solaris, Sun, and SunOS registered trademark are trademarks of Sun of Adobe Systems Microsystems, Inc. Incorporated. SPARC is a trademark TCPware and MultiNet are of SPARC International, registered trademarks of Inc. Process Software. UNIX is a registered TIFF is a trademark of Aldus trademark of UNIX Corporation. System Laboratories, Inc. Gold-Mail is a Copyright (c) 1990-2000 trademark of Data Sleepycat Software. All Processing Design, rights reserved. Inc. libedit/editline is Copyright (c) 1992, 1993, The Regents of the University of California. All rights reserved. vi _______________________________________________________ Contents _______________________________________________________ CHAPTER 1 INSTALLATION OF PMDF V6.7 1-1 1.1 LICENSE DATE 1-1 1.2 GETTING HELP 1-1 1.3 RELEASE NOTES LOCATION 1-2 1.4 OBTAINING NEW FILES 1-2 _______________________________________________________ CHAPTER 2 INSTALLATION GOTCHAS 2-1 2.1 MINIMUM OPERATING SYSTEM VERSIONS 2-1 2.1.1 OpenVMS/Alpha _________________ 2-1 2.1.2 Windows _______________________ 2-1 2.2 COMPILED CONFIGURATIONS MUST BE RECOMPILED 2-2 2.3 PROGRAMS THAT USE THE PMDF API MUST BE RECOMPILED 2-2 2.4 RETIRED PMDF COMPONENTS 2-2 2.5 KNOWN ISSUES 2-3 _______________________________________________________ CHAPTER 3 NEW FEATURES 3-1 3.1 LONGER MESSAGE LINES SUPPORTED 3-1 _______________________________________________________ CHAPTER 4 RELEASE NOTES 4-1 4.1 LICENSING CHANGES 4-1 4.2 OPENVMS UTILITY FIXES 4-1 4.3 THIRD PARTY LICENSES 4-1 iii _______________________________________________________ 1 Installation of PMDF V6.7 This document contains installation gotchas and release notes for upgrading to PMDF V6.7 from V6.6 or V6.5. If you are upgrading from an earlier ver- sion of PMDF, please read the installation gotchas and release notes for all of the versions between your version and V6.7. Those release notes are avail- able on the Process Software web site. __________________________________________________________________ 1.1 License Date The release date for the PMDF V6.7 kit is: 1-JUL-2015 Check your PMDF licenses to make sure they are valid for this release. The release date contained in each license must be later than the release date of the kit. See the PMDF Installation Guide for your platform for more information about how PMDF licenses work. __________________________________________________________________ 1.2 Getting Help Contact your PMDF distributor or Process Soft- ware if you need assistance or have questions con- cerning the installation or configuration of PMDF. Process Software provides technical support if you have a current Maintenance Service Agreement [support@process.com; 800-394-8700 or 508-628-5074]. If you obtained PMDF from an authorized distrib- utor or partner, you receive your technical sup- port directly from them. Timely notices, point- ers to new PMDF images, and other PMDF news of in- 1-1 Installation of PMDF V6.7 Getting Help terest may also be found at the Process Software web site, www.process.com. __________________________________________________________________ 1.3 Release Notes Location The text version of these release notes is in- stalled on VMS in the SYS$HELP directory, and on UNIX and Windows in the PMDF documentation direc- tory. The postscript and PDF versions on all plat- forms are installed into the PMDF documentation di- rectory ( PMDF_ROOT:[DOC] on VMS, /pmdf/doc on UNIX, and C:\pmdf\doc on Windows). __________________________________________________________________ 1.4 Obtaining new files New files may be obtained from the anonymous FTP account on ftp.pmdf.process.com; use FTP to con- nect to the host ftp.pmdf.process.com and login as the user anonymous. Use your e-mail address as the login password. Move to the pmdf_67_patches subdirectory: ftp> cd pmdf_67_patches Patches will be located in platform-specific sub- trees, as follows: _______________________________________________ Platform_______Subdirectory____________________ Linux linux OpenVMS vms Solaris/SPARC solaris-sparc Solaris/x86 solaris-x86 Windows________windows_________________________ 1-2 _______________________________________________________ 2 Installation Gotchas Make sure you read the PMDF Installation Guide for your platform before starting the installation. Make sure you complete the Post-Installation Tasks for Upgrades or Post-Installation Tasks for New Sites in the installation guide after the installation. __________________________________________________________________ 2.1 Minimum Operating System Versions ___________________________ 2.1.1 OpenVMS/Alpha Starting with this release, the minimum version required for OpenVMS/Alpha systems is V7.0. If you have a version of Alpha VMS earlier than V7.0, you must upgrade to at least VMS V7.0 before you can install PMDF V6.6 or later. The minimum versions for the other VMS hardware platforms remain the same: OpenVMS/I64 V8.2 or Open- VMS/VAX V6.1. ___________________________ 2.1.2 Windows Starting with this release, Windows 2000 is no longer supported by PMDF. The minimum version is now Windows 2003. 2-1 Installation Gotchas Compiled Configurations Must Be Recompiled __________________________________________________________________ 2.2 Compiled Configurations Must Be Recompiled For all platforms, the format of the compiled configuration has changed as of PMDF V6.6. After installation, in order to use a compiled config- uration you must recompile your configuration. Con- figurations that were compiled by versions of PMDF prior to version 6.6 will no longer be recognized by PMDF. __________________________________________________________________ 2.3 Programs That Use The PMDF API Must Be Recompiled All site-maintained programs that use the PMDF API must be recompiled to work properly with PMDF V6.7, which changes the sizes of internal buffers used to support longer line lengths. __________________________________________________________________ 2.4 Retired PMDF components With the release of PMDF V6.7, the following op- tional components have been retired and are no longer distributed with PMDF. Note: If you have these packages installed, they will be removed when you install PMDF V6.7, as the V6.6 im- ages are not compatible with PMDF V6.7. o PMDF-FAX o PMDF-MR o PMDF-XGS o PMDF-X400 o PMDF-MB400 2-2 Installation Gotchas Known Issues __________________________________________________________________ 2.5 Known Issues o There is a longstanding problem on Unix plat- forms when using a compiled configuration. The problem occurs when the system manager performs a pmdf cnbuild while PMDF is running. This can cause some or all of PMDF's processes to crash. This is a design flaw in the way that compiled configurations are implemented on Unix. If you are experiencing this problem, Process Software's recommendation is to not use a com- piled configuration. The performance improve- ment with compiled configurations on Unix is not as dramatic as on VMS (since file I/O on Unix is usually much faster). Or, alternatively, if you decide to use a compiled configuration any- way, we recommend that you do not run cnbuild while PMDF is running. o The installation of PMDF on Windows 2003 does not correctly show the disk space required for each component on the "Select Components" screen. This information should be automatically gen- erated by InstallShield. The disk space required is as follows: o PMDF Base: 21096 K o PMDF Dirsync: 952 K o PMDF Documentation: 40120 K o PMDF LAN channels: 628 K o PMDF TLS: 1524 K 2-3 _______________________________________________________ 3 New Features __________________________________________________________________ 3.1 Longer message lines supported Historically, PMDF has always adhered to the SMTP RFCs with regard to message line lengths, impos- ing a limit of 1023 characters for any line. Over the years, more and more SMTP clients have ignored the RFCs, transmitting messages with lines much longer than 1023 characters (even in cases when they use quoted-printable, which was designed to allow longer lines while keeping within the 1023-character limit). PMDF V6.7 now supports message line lengths of up to 8192 characters. Previous versions of PMDF would truncate or try to wrap lines longer than the maximum-supported length. PMDF V6.7 will now re- ject any SMTP message containing lines longer than 8192 characters. Messages that are not quoted-printable but have lines longer than the RFC-mandated limit will au- tomatically be converted to quoted-printable by PMDF to keep the messages RFC-compliant. All of this will be transparent to the message recipient(s). Note: This change also affects any program that uses the callable PMDF API. All such programs will need to be recompiled so they use all the proper buffer sizes that PMDF expects and uses. If they were coded as documented, they use the symbol BIGALFA_SIZE de- fined in PMDF_COM:APIDEF.H (/pmdf/include/apidef.h 3-1 New Features Longer message lines supported on Linux), so a simple recompilation is all that is required. 3-2 _______________________________________________________ 4 Release Notes The following sections document the enhancements and bug fixes that have been made since PMDF V6.6. __________________________________________________________________ 4.1 Licensing changes 1. New license PAK checksums are used on Linux, So- laris, and Windows systems. PMDF V6.7 accepts license PAKs generated with both the older (pre- 2014 checksums) and the new checksum algorithms. __________________________________________________________________ 4.2 OpenVMS Utility Fixes 1. PMDF CNBUILD has been modified for OpenVMS I64 to properly return an error exit status if an error occurs. Previously, no error was indi- cated. CNBUILD now exis to DCL with a status of %X'10000002' if there are errors compiling the data. 2. A problem with PMDF MAIL where the negated ver- sion of some qualifiers, for example /NOSIGNA- TURE, wasn't being honored has been fixed. __________________________________________________________________ 4.3 Third Party Licenses Licenses for third party open source software that are included in the PMDF product are now avail- able in a new directory under the PMDF documenta- tion directory: o PMDF_ROOT:[DOC.3RDPARTY] on OpenVMS 4-1 Release Notes Third Party Licenses o /pmdf/doc/3rdparty on Unix platforms o \pmdf\doc\3rdparty on Windows 4-2