CasePoint OS/2 2.0 Release Notes Important Installation Notes ---------------------------- CasePoint OS/2 is an OS/2 Presentation Manager program that can be installed to OS/2 version 2.11 and above. CBR Express OS/2 is not yet available, but CBR Express/Windows can be used to build and maintain case bases for CasePoint OS/2. CBR Express/Windows can be run under WIN-OS2. When performing a re-installation of CasePoint onto a network, ensure that the Overwrite Files option is selected in the Install program. The Install program provides support for removing CasePoint from disk and the Workplace Shell. This is maintained by storing installation details for this release on disk. If you remove the created Inference CBR2 folder or the contents of the CasePoint directory, outside of the Install program, then errors may occur on subsequent re-installations of CasePoint. RDM Installation: 1. If CBR Express and CasePoint will be run on the same machine at the same time, make sure that the "tafpath" variable in the file CBRX.INI for CBR Express and CBRX.OS2 for CasePoint, points to the same directory. 2. If CasePoint will be installed on a network, all users must be given full rights to the TAF directory. This is the directory specified by the "tafpath" variable in the CBRX.OS2 file. Full access is required because RDM will attempt to create, read, write, and delete the transaction log files in this directory for all users. Without full access, users will experience locking problems. SQL Installation: 1. CasePoint 2.0 provides database support for both Oracle 6 and Oracle 7. CasePoint is currently configured to use ora7o32.dll and coreo32.dll which are distributed with CasePoint. Important notes about upgrading from CasePoint 1.3 to 2.0 --------------------------------------------------------- General Notes CasePoint now has Rule Support, allowing users to create rules to automatically answer questions from either description terms or answers to prior questions. See Inference's Adding Rules to CasePoint document for more information. CasePoint now supports Relevance Feedback, which allows users to select a retrieved case, and force it to be the case matched against, effectively allowing the user to find cases similar to the selected case. CasePoint now supports Maximal Discrimination Question Ordering, or Strata Ordering, which orders questions more intelligently than the standard question ordering algorithm. In the preference dialog there is a Strata check box and a Stratum percent field, which specify whether Strata Ordering should be used and how large the Stratum should be. The Search menu contains a single menu item for Text Browse, Additional Information, as opposed to a separate item for each object type. At start-up, CasePoint now remembers whether a user was viewing actions or cases, and automatically comes up with that view when a case base is opened. CasePoint can now be launched in a minimized or maximized state. This is controlled with the -r command line option, which takes the values min or max as appropriate. If the -g command line option is specified as well, this is taken to be the restore position. ToolBook files used for graphic browse can now reside in any directory found in the path. New functions have been added to provide even more information about the case base. These functions allow a cooperating application to retrieve information about actions and questions for a given case. The additions of these functions complete the API for retrieving information about the data in the case base. Please see the CasePoint Application Programming Interface Guide for more information about these functions. Internationalization (European character set support) in CasePoint has been added. The following DDE commands were consolidated into existing commands and have been removed from the CasePoint 2.0 API documentation. Support for these in the CasePoint API is maintained for backwards compatibility purposes, but their use is discouraged. The obsolete DDE commands are: getAbsenceWeight getDescriptionWeight getQuestionAnswer getSelectedCB setAbsenceWeight setDescriptionWeight setQuestionAnswer setQuestionIDAnswer setSelectedCB The 'ConfirmOnClose' preference option has been added. If set, CasePoint 2.0 prompts the user before closing a case base. SQL Notes CasePoint 2.0 permits the bypassing of the user password prompt when creating or opening case bases residing in RDBMS tables such as DB2/2, SYBASE or Oracle. This is accomplished by referencing in the cbrx.os2 file an encrypted version of the password entered by the user via a password encryption utility. If the password found is not valid, CasePoint will present the usual dialog box to the user for entry of a different password. This is done to accommodate sites using CBR products on multiple servers with different passwords. CasePoint 2.0 now supports SYBASE System 10 resident case bases. The version number of the SQL Server containing the case bases is dynamically determined without any user intervention. However, some configuration modifications are necessary regarding the ISQL scripts used to create the case base tables. See the corresponding CBR Express or CasePoint 2.0 RDBMS Enabler for details. CasePoint 2.0 now supports data access to and from Oracle 7 servers via the Oracle 7 OCI (Oracle Call Interface) which considerably improves performance over the Oracle 6 OCI used in the past for accessing Oracle 7 servers. The version number of the Oracle Server containing the case bases is dynamically determined without any user intervention. Connectivity to Oracle 7 servers is now supported for both the SQL*Net V1 and V2 protocols. If CasePoint 2.0 will be used with Oracle 6 or 7 servers, you must make sure that the Oracle 7 version of the client software (e.g., ORA7O32.DLL) is installed. Contact Oracle Corporation for ordering details if you do not have this. If you are using FTP Software PC/TCP to connect to an Oracle 6 or 7 server, two versions of SQL*Net for Windows are supported (or newer): for those using SQL*Net V1, 1.1.7.10.4 and for those using V2, 2.0.15.0.3. Some older versions of SQL*Net V1 and V2 are known to have problems and we do not recommend their use with CasePoint 2.0. CasePoint 2.0 features a dramatic improvement in search performance for SQL resident case bases over the CasePoint 1.3 release. This improvement is primarily achieved by caching cases, questions and actions whenever possible to reduce database accesses. DB2/2 Conversion program The conversion utility that was supplied with 1.3 which migrated case bases from a Raima Data Manager format database to a DB2/2 database has been replaced with a general import utility. The new utility has the capability of creating case bases in any of the supported databases in either SQL or Raima Data Manager format. It uses as its primary input a case base definition file which is created by the CBR Express export function. Problems Corrected in CasePoint 2.0 ----------------------------------- General Bug Fixes A number of problems regarding question ordering in the search window have been corrected. The previous release of CasePoint would display a maximum of 100 questions. This limit has been removed. Several minor problems with saving unresolved search cases in the Standard Version have been corrected. In the Standard Version, unresolved searches can now be saved via either clicking on the icon, clicking on the pull- down menu item, or using the keyboard shortcut. Toolbar buttons will now display a status line message describing their functionality, when they are pressed. Ampersands in lieu of underscores now appear in case, question and action titles in the search window and the Text Question dialog box. The SQL and RDM versions of CasePoint no longer display the Questions and Answers Fields if an open case base does not contain any questions. Browse Windows are no longer hidden after opening. CasePoint no longer renumbers Search Windows when a case base is closed. Focus is now retained on the selected action or case while displaying actions (via Ctrl+A) and cases (via Ctrl+K). CasePoint now accepts numeric answers with the decimal sign set to comma instead of period (to accommodate European users). The showSQLErrors and showSQLWarnings options set in CBRX.OS2 now display SQL errors and warning messages. CasePoint now inserts a / between the title and the description of a relevant case displayed in the description field. DDE Fixes DDE command [getError(X)] now returns error code 8 ("The parameter X is out of range") if X is less than 0 or greater than 23. DDE command setAnswer now returns error code 18 ("Invalid answer for this question") if the answer to a Yes|No question is invalid. DDE command appendAnswer can now append up to 256 characters to an answer. CasePoint now matches answers set via the DDE command setAnswer regardless whether the answers are upper or lower case. Searching using DDE now works and the correct scores calculated when running CasePoint minimized. Known Problems in CasePoint 2.0 ------------------------------- A CBID with trailing spaces causes CasePoint to display the error message, "Unable to find file". To avoid this, remove the trailing spaces. Unresolved cases cannot be saved to a file in a root directory. RDM transaction log files are created in the current working directory, normally the CasePoint directory, and not in the directory specified by the tafpath variable. Differences between CasePoint OS/2 and CasePoint/Windows -------------------------------------------------------- CasePoint OS/2 runs as a native 32-bit application under OS/2 Presentation Manager, as opposed to 16-bit under Windows. CasePoint OS/2 supports extended filename formats for the High Performance File System in addition to the FAT file system. CasePoint OS/2 supports the loading of case bases built using the Windows version of CBR Express. Support for an OS/2 version of CBR Express will be provided in future releases. The CasePoint OS/2 extended browse facility can call programs in multiple environments: Presentation Manager programs including CMD and REXX files, Windows programs running under WIN-OS2, and DOS programs from the DOS box. File associations for the extended browse facility in CasePoint OS/2 are defined in a CasePoint specific file, and must be set up by the user. To use this facility you must create a text file called ASSOC.OS2, which contains a header line containing the text [Extensions] followed by the list of file extensions that are to be associated with programs. These should be one per line, as follows : [Extensions] txt=e.exe ^.txt bmp=iconedit.exe ^.bmp cbd=c:\casepnt\casepnt.exe ^.cbd This file must be placed in the same directory as the CasePoint program. To change existing graphic browse entries, so that they make use of file association, use CBR Express to edit the graphic browse field and remove the name of the program executable from the page field. Then, specify the name of the file that is to be passed as a parameter to the target program. The current version of CasePoint OS/2 supports case bases to be held in a RDM format database, DB2/2, Oracle or SQL Server. Screen attributes are different for OS/2 and Windows. OS/2 Presentation Manager screen co-ordinates are based on 'bottom left' but Windows is based on 'top left'. This affects the start up parameter to set the application position and size, and the DDE window geometry calls for the CasePoint API. For CasePoint OS/2, ToolBook browses will start from the first page, not from the name or number of a specific page. The CasePoint Preferences file is named CBRX.INI under Windows, and CBRX.OS2 under OS/2. As there is currently no OS/2 version of CBR Express, case bases to be stored in DB2/2 must be created using the import program supplied with CasePoint OS/2. The text in the title bar of CasePoint may be changed by editing the resource file and replacing the text of the resource IDS_TITLE_CAPTION. Refer to the CasePoint Application Programming Interface Guide for further details of this customization. CasePoint OS/2 DDE Client application examples are now provided in C and WordPerfect for OS/2. The C example is called CLIENT.EXE (the C source file is CLIENT.C and a batch file COMPILE.CMD is provided to generate CLIENT.EXE). The WordPerfect example is a macro called DDESAMP.WCM. Both examples are provided as source files so that the contents may be modified. Further details of the examples are provided in the CasePoint Application Programming Interface User's Guide. UserIDs entered into the Preferences dialog may consist of up to six alphanumeric characters. Under Windows, the limit is seven.