***************************************************************** "relnotes.txt" for PRO/5 Data Server(R) Revision 5.00 ***************************************************************** ================================================================= CONTENTS ================================================================= 1. NEW FEATURES/BEHAVIORS 2. WHAT'S FIXED SINCE 3. NOTES 4. KNOWN ISSUES 5. SUPPORT ================================================================= 1. NEW FEATURES/BEHAVIORS ================================================================= ------------------------------ NEW FEATURES/BEHAVIORS IN 5.00 ------------------------------ o A new SSL mode is available for use when communicating with an SSL-enabled PRO/5 or BBj client. o A new FCBDUPS keyword is available for use in the configuration file. This option, when used in combination with FCBCACHE, turns off an FCBCACHE feature that scans the prefix without performing any disk I/O to determine if a file is already in the FCB cache. o This product was built with the FLEXlm 9.2 libraries. BASIS recommends using this product with a 9.2 version or greater of the BASIS License Manager. ------------------------------ NEW FEATURES/BEHAVIORS IN 4.11 ------------------------------ No new features have been added. ------------------------------ NEW FEATURES/BEHAVIORS IN 4.10 ------------------------------ o The OPEN verb now supports a new PASSWD= mode option for recoverable multi-keyed files. This option protects records from being read or written by unauthorized utility programs. See the product documentation for additional information about the OPEN verb and the mkrecover utility. ------------------------------ NEW FEATURES/BEHAVIORS IN 4.00 ------------------------------ o The PRO/5 licensing model has been updated and now uses BBj licenses. This simplifies the licensing process because the same license is being used regardless of the product. ------------------------------ NEW FEATURES/BEHAVIORS IN 3.11 ------------------------------ No new features have been added. ------------------------------ NEW FEATURES/BEHAVIORS IN 3.01 ------------------------------ o IMPROVED MKEYED FILES PRO/5 now defaults to creating MKEYED files with 1024-byte nodes which provides greater search efficiency and file performance. Previous releases only utilized 1024-byte nodes when the length of an MKEYED file key exceeded 64 bytes. For existing MKEYED files, use the mrebuild utility to convert them to the larger node size. o IMPROVED DETECTION AND PREVENTION OF FILE CORRUPTION This version can detect file corruption better than past versions, so it may detect corruption and report an error=7 on a data file that seemed to work fine with an older version of PROGRESSION/4 or PRO/5. ==> Before using this version of PRO/5, please use the <== ==> accompanying utility "mrebuild" to rebuild all of <== ==> your data files to ensure their integrity. <== ------------------------------ NEW FEATURES/BEHAVIORS IN 3.00 ------------------------------ o 64-BIT FILE SUPPORT REPLACES 4GB SUPPORT In revision 3.00 of PRO/5, 4GB MKEYED file support has been replaced with support for 64-bit MKEYED files. If you currently have 4GB MKEYED files you will need to convert them to 64-bit MKEYED files by using the mrebuild utility. You will need to convert to 64-bit, MKEYED files any 2-GB, MKEYED dynamic files that you want to allow to grow beyond the 2-GB limit. o NEW CONVERSION UTILITY A stand-alone conversion utility has been provided with your PRO/5 software to generate a 64-bit MKEYED file from a 2 GB or 4 GB MKEYED file. The stand-alone file conversion utility, "mrebuild" can generate a 64-bit MKEYED file from an existing 2 GB or 4 GB MKEYED file. The generation of the 64-bit file is achieved without modification of the original file. Additionally, it can generate "highly recoverable" 2 GB or 64-bit MKEYED file. The recovery utility "mkrecover" has been modified to attempt to recover either a "highly recoverable" 2 GB or 64-bit MKEYED file. ================================================================= 2. WHAT'S FIXED/CHANGED ================================================================= --------------------- FIXED/CHANGED IN 5.00 --------------------- No new fixes or changes since revision 4.11 --------------------- FIXED/CHANGED IN 4.11 --------------------- No new fixes or changes since revision 3.11 --------------------- FIXED/CHANGED IN 3.11 --------------------- Multi-user access to non-LFS files no longer hangs. --------------------- MREBUILD can now be used on SORT files. --------------------- FIXED/CHANGED IN 3.01 --------------------- The BLM can now serve concurrent development and runtime licenses. -------------------- The last few bytes of a serial print job now print correctly. -------------------- Core dumps no longer occur on multiple, quickly executed OPENs and CLOSEs of a printer channel. -------------------- Problem with defunct processes that was specific to the DG/UX port has been fixed. -------------------- Error 16's no longer occur with BACKGROUNDed programs. -------------------- Hang Up signals which were occasionally being ignored are now honored. -------------------- A linefeed no longer occurs after the first Data Server OPEN(). -------------------- Closing a channel in a BACKGROUND program under SCO now works correctly. -------------------- Error 0 and file corruption problem that was specific to the DG/UX port has been fixed. -------------------- Opening an alias with a lock file no longer causes a core dump under DG-UX. ================================================================= 3. NOTES ================================================================= The mrebuild utility requires minimum available disk space equal to the size of the file(s) to be converted. -------------------- When parsing MODE= on an OPEN, PRO/5 now checks to ensure mode array bounds are not exceeded. An OPEN() verb now has 40 modes. -------------------- PRO/5 can now create files with a Data Server path in the prefix, without generating an error. ================================================================= 4. KNOWN ISSUES ================================================================= When using UNIX clients with the Windows NT Data Server, the clients cannot access files based on Windows NT drive letter designations (C:/, D:/, etc). The correct method is to have clients prefix to the Data Server, and configure the Data Server to handle pathing information via its config.bbx file. -------------------- UNIX clients can only create files through the Windows NT Data Server if the Windows NT Data Server is limited via DSKSYN or prefix to the single drive that the Data Server is installed on. ================================================================= 5. SUPPORT ================================================================= If you purchased your BASIS product from a distributor, reseller, or OEM, please contact them for technical support. They will either answer your question or will contact us on your behalf. German, Austrian and Swiss users should contact BASIS International Software GmbH. For a complete listing of our international distribution, please refer to http://www.basis.com/sales/index.html. Refer to our technical support Web page, http://www.basis.com/support/contacts.html, for a listing of all our technical support services, including our knowledge base and other online resources. For information about BASIS's Technical Support Policy, see http://www.basis.com/support/policy.html. BASIS Technical Support analysts are available Monday through Friday, 8:00 AM through 5:00 PM (Mountain Time) at 505.345.5021. Technical support is also available via e-mail at support@basis.com or via e-support at http://www.basis.com/support/. BASIS cannot process a request for technical support without a product serial number. PHONE -- 505.345.5021 E-MAIL - support@basis.com WEB ---- http://www.basis.com/support/ Also, refer to http://www.basis.com/support/contacts.html for additional information on how to contact Technical Support. When calling or sending a technical support question, please provide the following information: o The product serial number. o The name of the product and the product's version number. o A complete description of the problem, including the product error and the TCB(10) value, if available. Other pertinent information includes: o The operating system name, level and version. o Is the error consistently reproducible, or is it sporadic? o Is the error isolated to a specific machine or user? o Is this a new installation or has the system been in place and operating normally? o Is the problem network related/specific? ----------------------------------------------------------------- Copyright (C) 1985-2004 BASIS International Ltd. All rights reserved. BBx(R), Visual PRO/5(R), PRO/5(R), PRO/5 Data Server(R), GUIBuilder(R), ResBuilder(R), BASIS ODBC Driver(R), DDBuilder(R) and BBj(R) are registered trademarks of BASIS International Ltd. All other product names and brand names are service marks and/or trademarks or registered trademarks of their respective companies. [end of file]