Date: 05-28-2010 Subject: PATCH RELEASE 9.4B DATA Manager Files These release notes pertain to the following programs or files: SUNDM.EXE 9.4B 28 May 2010 9,4,2,500 SUNWSRV.DLL 9.4B 28 May 2010 9,4,2,500 *============================================================================== The following files have been changed as noted: ------------------------------------------------------------------------------- SUNDM - Modified the Data Manager to allow the SQLite database engine to be loaded and used as a driver using keywords from the Sundm CFG file. This change allows a PLB program to access the SQLite database engine by referencing user defined keywords in the runtime INI and the Data Manager CFG files. Example (1): PLBWIN INI keyword to access SUNDM: SOMEKEYDM=FILEMAN,127.0.0.1 SUNDM CFG keyword to access SQLite database engine: SOMEKEYDM=SQLite PLB Program sample: MYDB DBFILE DBCONNECT MYDB, "SOMEKEYDM;;c:\mypath\mydata.db","","" Example (2): PLBWIN INI keyword to access SUNDM: SOMEKEYDM=FILEMAN,127.0.0.1 SUNDM CFG keyword to access SQLite database engine: SOMEKEYDM=SQLite,c:\sundmpath\mydm.db PLB Program sample: MYDB DBFILE DBCONNECT MYDB, "SOMEKEYDM;;","","" - Corrected a GPF error that would occur when the following filter expression was being evaluated in a PLB READ operation. "colname LIKE '% %'" - Corrected a GPF error that would occur if a non-existing viewname was specified for VIEW keyword on an OPEN or PREP. - Corrected a problem where a READ FILE for a field using the column name syntax format would blank fill a data variable unexpectedly if the record size was shorter than a full record and this READ followed a previous partial IO READ that was terminated with a semi-colon. - Modified the UPDATE FILELIST to release a record lock that has been locked using a Secondary file in a FILELIST when using the SINGLE record lock mode. This corrects a problem where an UPDATE FILELIST was not releasing a record lock for a record just updated. - Corrected a problem when using record locking where one PLB program has a record locked to perform an AAM/ISAM UPDATE or DELETE operation and a second PLB program is in an AAM or ISAM read instruction waiting to lock the same record. The problem in this case was that the second PLB program could get an unexpected IO error or possibly get unexpected record data. The changes for this potential problem were diagnosed while implementing the UPDATE FILELIST correction as described above. The instructions affected by these changes are the Isam READ, READKS, and READKP as well as the AAM READ, READKG, and READKGP. - Corrected a problem where an AAMDEX instruction using a '-I' or '-R' option was causing an unexpected S13 error with a subcode 139 that indicated a bad AAM file name. - Corrected a problem with column IO where some column fields were not returning expected data when a file was opened with variable length records. ------------------------------------------------------------------------------- SUNDM REPLICATION SUPPORT - Added a replication message to the log file when checking for a primary rollover during the startup processing. This is to help clarify when the replication is entering a network validation sequence. -------------------------------------------------------------------------------