***************************************************************** "relnotes.txt" for PRO/5(R) Revision 4.01 ***************************************************************** ================================================================= CONTENTS ================================================================= 1. NEW FEATURES/BEHAVIORS 2. WHAT'S FIXED/CHANGED 3. NOTES 4. KNOWN ISSUES 5. SUPPORT ================================================================= 1. NEW FEATURES/BEHAVIORS ================================================================= ------------------------------ NEW FEATURES/BEHAVIORS IN 4.01 ------------------------------ No new features in this release. ------------------------------ 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. o The SETTRACE verb now supports timestamping to aid in profiling BBx programs. Two new modes have been added to the verb - "TIMED", and "UNTIMED". TIMED causes the trace log to always include time stamps, even if it is being written to the console. UNTIMED suppresses the time stamps for trace logs that are being written to a file. When no valid mode is specified, the default behavior is to include time stamps in a log file but suppress them when logging to the console. o A profiling utility (_prof.bbx) has been added to the product distribution. This utility is a performance analysis tool which aids developers in optimizing their code. When combined with a timestamped SETTRACE output file, _prof.bbx can identify performance bottlenecks due to slow or inefficient code via a comprehensive set of timings and statistics. ------------------------------ NEW FEATURES/BEHAVIORS IN 3.11 ------------------------------ No new features in this release. ------------------------------ NEW FEATURES/BEHAVIORS IN 3.10 ------------------------------ o LICENSE PASS-THROUGH Licenses can now be issued and controlled for BBx applications in the same manner as BASIS products. This new FLEXlm license feature is managed through LCHECKIN and LCHECKOUT. o Added LISTING.MSB to the conversion utility suite. This program is used to aid in the conversion from MicroShare Basic to PRO/5. o PRO/5 was built against the 7.0g FLEXlm libraries. ------------------------------ 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. <== o NEW SETOPTS BYTE PRO/5 SETOPTS byte 8, bit $80$ now forces the FID() to report Mkeyed files as type $06$. When this bit is set, recoverable and 64-bit Mkeyed files are reported as standard Mkeyed files. In addition, recreating these file types using the INITFILE verb or the FILE verb in conjunction with the file's FID() will result in standard Mkeyed files. ------------------------------ 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. Any 2GB MKEYED dynamic files that are nearing the 2GB limit and you would like to allow them to continue to grow, you will need to convert them to a 64-bit MKEYED file. 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 4.01 --------------------- Anomaly in BACKGROUND verb. --------------------- FIXED/CHANGED IN 3.11 --------------------- Multi-user access to non-LFS files no longer issues !ERROR 60's for the 1x75 ports. --------------------- MREBUILD can now be used on SORT files --------------------- FIXED/CHANGED IN 3.10 --------------------- A READ RECORD on a channel opened to a socket now returns any available partial data instead of issuing an !ERROR=0 or 2. --------------------- The Basic Web Utility limits purges to old records instead of removing all session records. --------------------- BXRCV has been updated to handle MicroShare Basic specific program conversions. --------------------- _ddedit.utl now allows you to change a field type to variable length. --------------------- The following 95 QA memos have been fixed in this release: 02812 02895 02898 03413 03487 03498 03504 03524 03533 03555 03883 03971 03973 04050 04261 04276 04386 04404 04472 04758 05219 05544 06031 06104 06186 06366 06412 06426 06427 06428 06430 06432 06455 06456 06479 06498 06504 06516 06528 06533 06536 06562 06574 06583 06588 06617 06623 06674 06690 06695 06708 06709 06712 06722 06724 06725 06757 06773 06778 06780 06803 06821 06827 06828 06838 06858 06860 06861 06862 06892 06895 06898 06902 06922 06923 06933 06943 06970 06984 06999 07000 07007 07047 07050 07059 07094 07104 07117 07132 07140 07208 07226 07268 07270 07276 --------------------- FIXED/CHANGED IN 3.01 --------------------- PRO/5 now properly waits for a program specified in a printer alias EXECOFF mode to terminate before continuing. -------------------- 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. -------------------- "Nag" mode is the absence of a valid license file which halts the operation of the BASIS product. A message box appears randomly every 15-30 minutes reminding the user of the absence of a valid license. Pressing OK resumes the operation. -------------------- The LOCKMAX entry in the configuration file is now ignored. This value is now fixed at 7fffffff for 2GB files and is automatically adjusted to ffffffff for 4GB files. -------------------- Version 2.x has improved upon its detection and handling of corrupt files. It can now identify corrupted files more safely and easily, allowing you to find and fix the corruption in a timely manner. Previous versions of PRO/5 did not perform the extensive integrity verification that 2.x does, so consequently it would not report all instances of file corruption. After upgrading to PRO/5 2.x for the first time, you may encounter more !ERROR=7's which indicate that the files in question may be corrupt. This error does not indicate that there is more file corruption with PRO/5 2.x, but rather that it is able to more accurately determine the file's integrity and alert you of potential corruption. *** If you are upgrading to 2.x for the first time, *** *** from a version lower than PRO/5 2.0, we *** *** recommend you verify the integrity of your data *** *** files BEFORE installing version 2.x. *** -------------------- The default value for the maximum line length for the printer alias is 80. Earlier versions of PRO/5 had an undocumented default value of 132. -------------------- The DATE() and JUL() functions provide an easy method to store and manipulate four-digit years in a standardized way. For specifics on PRO/5's and Visual PRO/5's Year 2000 compliance, visit the BASIS web site at: http://www.basis.com/announcements/etc-19980508-y2k.html ================================================================= 4. KNOWN ISSUES ================================================================= The SELECT verb may not properly optimize on a WHERE clause that references an alternate index. ================================================================= 5. SUPPORT ================================================================= ===INTERNATIONAL=== If you purchased your BASIS product from a Distributor, Reseller, OEM, or any company outside the United States, 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. ===UNITED STATES=== Technical support is available to all U.S. customers directly from BASIS International Ltd. Refer to our technical support Web page, http://www.basis.com/support/index.html, for a listing of all our technical support services, including our knowledge base and other online resources. All domestic customers who purchase products from BASIS automatically receive thirty days of free telephone support per product serial number, activated upon the first phone call. BASIS analysts are available Monday through Friday, 8:00 AM - 5:00 PM, Mountain time. Free technical support is available via e-mail or e-Support (through our Web), however, these methods receive lower priority than telephone calls or voice mail messages. 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) l985-2002 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]