COOL Product Suite ================== Sterling Software Customer Support 800-246-5151, 972-801-7900 Sterling Software Order Help Desk

888-801-6300 or 972-801-6300. Support web page at http://www.cool.sterling.com/support. Introduction ============ This is release 5.0 of COOL:Biz and COOL:Xtras Webview. This file contains important information you should know before working with COOL:Biz and/or COOL:Xtras Webview in Windows 95, Windows 98, or Windows NT 4.0. New Features ============ Some of the new features in COOL:Biz are the following: A new where-used tab on the property sheet of an object AMD text formatting options Auto-Recruitment of Data Autostart routine for Webview Copy Extended Property Definitions Create an Administrative KM file Create Subset Subordinate Files ERD rules for determining a complete model and a new transform feature Migrate Extended Property Definitions Spell Check capabilities for many different languages Synchronization of DFD keys and ERD identifiers Undo Redo Updated Objects Summary Preview list before a merge A Biz 5.0 New Features guide is now in Acrobat format (.PDF) in the ...\COOL\Help directory. Setting Up Spell Check ---------------------On the COOL:Biz Setup dialog box you can specify the dictionary for the language in which you are working. The following files are stored in the SPELLCHECK directory on the COOL:Biz CD. If you want to use a spell checker other then English, you need to copy both the *.tlx and the *.clx file into your Winnt32/System directory and then type these file names into the Main Dictionaries box on the COOL:Biz Setup dialog box. For example if you want to use the French spell checker, you would type the following in the Main Dictionaries box: sscefr.tlx,sscefr2.clx Use the following table to determine what files to use. For British English use sscebr.clx,sscebr2.clx These files are copied into WINNT32/SYSTEM32 during the COOL:Biz install. For Danish use ssceda.tlx,ssceda2.clx For Dutch use sscedu.tlx,sscedu2.clx

For For For For For For For For

Finnish use sscefi.tlx,sscefi2.clx French use sscefr.tlx,sscefr2.clx German use sscege.tlx,sscege2.clx Italian use ssceit.tlx,ssceit2.clx Norwegian use sscenb.tlx,sscenb2.clx Portuguese use sscepo.tlx,sscepo2.clx Spanish use sscesp.tlx,sscesp2.clx Swedish use sscesw.tlx,sscesw2.clx

The following objects are no longer accessible from COOL:Biz. Component Component Specification Interaction Type Collaboration Collaboration State Machine J Package Spec Package Instance (Object Instance) COOL:Biz has one additional diagram - Class Diagram. Multi-User Environment Issues ============================= When upgrading to this new release, you need to upgrade all of your users to COOL:Biz 5.0 or deadlock errors may occur during multi-user sessions. This is to ensure the integrity of the data, object reuse, and multi-user edits and reviews. To ensure optimal performance of the COOL products in a multi-user environment, it is advisable not to run any batch operations such as generating external reports, importing and exporting, file merging, and some OLE operations when multiple clients are accessing the server because the other clients may receive messages about the server being busy. To aid performance in a multi-user environment, the client PCs and server PC should have adequate CPU speed, memory, and available disk space. The number of other applications being run should be kept to a minimum. It is recommended that the server PC have a minimum of 128 MB of RAM. If you are prompted to log in to the ObjectStore server when you open the tools, the Authentication parameter may be set wrong. Start the Object Store Setup program and select the Yes radio button when prompted to change parameters. Change the Authentication parameter to NONE and continue. Large import/export operations on multi-user .KM files should be scheduled for off-peak hours if possible. Import/export operations (e.g. Import from BML, Export to BML) are performed within a transaction boundary. Other transactions are forced to wait until the import/export operation is complete. This process can take from 30 minutes to several hours depending on the size of the file and the speed of your machine. Therefore, other sessions and other users may be impacted. Migration ========= Relationships created to object types unique to Spex/Jex will not migrate to COOL:Biz Release 5.0.

Important Information on Making Backups, Copies, Archives, ========================================================== and ODI Utilities ================= Rules ----Do not use DOS or Windows Explorer to make copies of your KM files. Always use the Copy option on the File menu in COOL:Biz. Using the Copy option on the File menu in COOL:Biz assures that the .KM file will be in a consistent state. A DOS or Windows Explorer copy does not take into account the portion that may be resident in memory. A recommended strategy for making backups is to export periodic .BML files. These can easily be imported into a .KM file of the same release or next release when necessary. An added benefit of this strategy over storing copies of .KM files is that corruption in a .KM file may not be discovered until after damage prevents an export to BML. When you use the Export to BML option in Model Manager, any graphics/OLE annotations are stored in a .BMG file. Keep the .BML and .BMG files together in case you need to restore the .KM file. If you are interested in automated backups, there are ObjectStore commands that you can use. The syntax is: OSSVRCHKPT <host name> OSCP <source .KM><target .KM> The first command checkpoints the server; the second Command copies the .KM file inside a transaction boundary. The target.KM is the one that can be restored at a later date. Running the OSCOMPACT Utility ----------------------------The purpose of running the OSCOMPACT utility is to remove deleted space in the database, segments, or clusters. This usually results in better database performance. To run the OSCOMPACT utility, you must first delete the internal KM file dictionary. You will, of course, have to reconstruct the internal dictionary before you will be able to use the KM file again. To delete the dictionary, in MS-DOS go to the directory where you store your km files. Type the following command: C:\COOL\EXE\patch -ddict <abc.km> Then run OSCOMPACT. Then create and fill the dictionary by typing the following command: C:\COOL\EXE\patch -fdict <abc.km>

Product Limitations and Restrictions ==================================== The COOL Directory Structure is Fixed. The directory used to install the COOL products should not be moved after the installation is complete. If you want to move or rename the directory you need to complete the following steps. If you store your KM files within the COOL directory, the first step is to copy all of your KM files to a new directory. The second step is to use the ADD/REMOVE feature in Windows NT, Windows 95, or Windows 98 to remove the product. After this process is complete, delete the current COOL directory and re-install to the new directory. Drawing Size Limitations -----------------------Due to limitations in the size of the drawing space used to create diagrams, there are some limits on the number of graphics objects that can be included in a single diagram. These are not strict limits and may vary depending on the size of the objects you create in the diagram. Diagrams have a limit of approximately 250 objects drawn horizontally and 250 objects drawn vertically. Preferred Object Naming Conventions ----------------------------------Do not use colons (:), commas(,) or backslash (\) characters in object names. Use of these characters in object names confuses the object path names that are viewed in dialogs and in the report list that is passed to customized reports. Usage of these characters in object or diagram names may cause unpredictable results in third party programs and custom reports. Do not end object names in a backslash (\). Using a backslash as the last character of an object name will cause errors when merging two .KM files. Setting the Defaults for Information Types -----------------------------------------There is no default Style, Precision, or Scale for Information Types. You need to set the Information Type and System Data Type built-in values for Style, Precision, and Scale. Although the dialog initially displays the VARCHAR length to 20, this information is not recorded in the model until you specifically record a style, precision, and scale for the information type object. Authentication Error on Windows NT ---------------------------------After installing COOL products on a Windows NT machine that does not have network capabilities, an authentication error

may occur when you try to use the tools. If this error occurs, do the following: 1. 2. 3. 4. 5. From the Control Panel, Click the System icon. Click on the Environment tab. Complete the Variable entry field, with OS_AUTH Complete the Value field, with 12. Click Set. The User Environment Variables list box should now include OS_AUTH=12.

Connecting to a Network Server ============================== If you want to access files located on a remote server, simply make sure the remote path is mapped locally and that COOL:ServerNT is installed on the server. The local schema, which is installed with COOL products on the client machine, provides access to both local and remote .KM files provided that you have enabled access to remote schemas in COOL Biz Setup. If you choose to select the Remote Schema radio button to point to the schema on the remote server for performance reasons, terminate all COOL applications, the ObjectStore Cache Manager, and Server Services before starting Setup. Remember to terminate them in the proper order: applications, Cache Manager, and then the ObjectStore Server. In the Schema Pathname entry field, you can enter the full pathname (relative to a local device mapping) of the schema directory on the remote server or use the Browse button to locate it. Keep in mind that it is not necessary to point to a remote schema to use a remote .KM file, however, wherever the schema resource runs, memory management may become a consideration. You will typically find performance improvements using the remote schema. If the Local Schema radio button is selected, the local schema will be used to read the remote .KM file. Troubleshooting... ================== Server stops running during a transaction (for example, a power outage). Changes to the transient portion of the .KM file that was resident in memory will be lost. When the server is restarted however, the log file is re-applied automatically. If the server administrator needs to clear space used by the log file, the server should be checkpointed and ODI services should be shut down prior to re-initializing the log file. Applications terminate with miscellaneous memory errors. -------------------------------------------------------When you display a diagram in `scale to fit' mode, a new Font resource must be created for each scale factor used to display

the diagram. Since a new scale factor is computed for each edit to the diagram, a large number of scale factors and thus Fonts can be required. Scale to fit mode is useful for displaying the entire diagram in order to see an overview of the diagram. However, you should not use this mode as the default when you are editing the diagram. You should select a limited number of scale factors (i.e. 75%, 100%, and 125%) and toggle between them as required. Tips for drawing publishable diagrams: If the audience for the diagram will eventually view the diagram using a web browser, OLE Client, or a report generated from Biz, it is generally a good idea to try to draw the diagram using 100% scale factor. Use a true type font. Try to draw the diagram such that you can see all of the diagram with very little scrolling required. If you can see and read everything in the 100%, full-size, diagram, then you are more likely to have a diagram that will display well in an OLE client, in a Webview browser client, or in an HTML or customizable report. Using this technique does limit the amount of objects that you can have in one diagram. However, you can use diagram links to provide quick navigation to related topics. Use diagram folders to form logical groupings of related diagrams. Building diagrams with large numbers of objects that span multiple pages is perfectly acceptable to COOL:Biz. However, larger diagrams will require more scrolling and may not display as well in a generated report or OLE Client. Diagrams in Webview ------------------In the BML version of Webview, the labels for diagonal arcs display horizontally. Unable to open the application schema file. ------------------------------------------When you attempt to open an existing file or create a new file while running COOL applications that access .KM files, the ObjectStore server must also open the application schema file. If you receive an error message that states "Cannot open the application schema," you must terminate the application and run the Setup program. Select the local or remote (remote drives must be mapped locally) directory where the schema files are located. The schema files are located in the SCHEMA directory under the root where COOL products were installed, i.e. ...\COOL\SCHEMA. When selecting the location of the application schema files, there are several things you should consider. In order to open a .KM file, you must have an ObjectStore server application running on the machine that contains the physical drive where the .KM file is stored. You must also have an ObjectStore server application running on the machine where the schema is located. If you are running locally, that is, all .KM files reside on your local machine, then the default installation settings should be used. This will execute the ObjectStore server on your local machine and will also access the schema from the

local installation. Connection to Server is Broken -----------------------------When you can no longer communicate with the server, you can troubleshoot the situation by looking for the following conditons: 1. Excessive network traffic may be causing a delay in the communications path 2. You may have suspended the local application to execute a different application 3. The PC is running low on virtual memory and/or disk space. To resolve this situation, restart COOL:Biz and reconnect to the remote server. If this problem is persistent and the local client application disconnects from the server soon after the connection is established (a file is opened), this may be a TCP/IP problem. TCP/IP -----If you can successfully "ping" your server (TCP/IP command), but you cannot successfully "ossvrping" (found in the ObjectStore bin directory), add SET OS_NETWORK=O4NETNSM.DLL,O4NETTCP.DLL to the environment variable settings on both the client and the server. In Windows 95 these settings are found in the OS_AUTO.BAT file. On an NT workstation, you will add these settings in the System icon on the Control Panel. This OS_NETWORK variable is used to force a communication protocol other than the default one specified in the Network settings of the machine. If a communication to a server is to be established and the server has a different default than yours, you need to specify this OS_NETWORK setting. Failure to provide the O4NETNSM.DLL before the preferred one may result in the application crashing the first time you open a database after you log on to the machine. Setting Communications Protocols in Webview ------------------------------------------This release of COOL:Biz and COOL:Xtras Webview uses ObjectStore 5.1. It provides additional functionality and corrective enhancements, including support for Windows 98 and Windows NT Service Pack 4. However, this release also eliminates support for NetBIOS as a communications protocol between clients and the COOL Server NT. As in release 4.1, clients must use the TCP/IP protocol for client to server communications. Shutting Down ObjectStore Services ==================================

When you install this release of COOL:Biz, you will be prompted to shutdown ObjectStore Services. When you Click the Shutdown Services button, the installation program takes care of this task for you. If you need to shutdown ObjectStore for any other reason, follow these steps: For NT, select the ObjectStore Server and Cache Manager entries in Control Panel/Services and select Stop. For Windows 95, from the DOS prompt, type OSSVRSHTD <machine name> to shutdown the server. Type OSCMSHTD <machine name> to shutdown the Cache Manager. When you shut down a server, make sure you close any open .KM files first.

Un-installing COOL Products =========================== Deleting the COOL directory does not undo all of the effects of the installation. If you want to remove the COOL products from your machine, use the Add/Remove Programs feature in Windows NT 4.0 or Windows 95. This feature will uninstall your last installation of COOL products. After you uninstall the COOL:Biz, it is recommended that you remove Objectstore from your machine by using the Objectstore Uninstall program. The last step in this process is to delete the COOL and ODI directories. Did you know... =============== ...that embedded OLE objects have significant file overhead. Diagrams that are annotated using embedded rather than linked OLE objects must maintain both the OLE data and a bitmap copy of the object's display image in the COOL .KM file. Embedded OLE objects are contained entirely within the file and can not be accessed outside of COOL products. Linked OLE objects are maintained in application specific Files and can be accessed by those applications outside of COOL products. Embedded Microsoft Paintbrush objects require significant file space because Paintbrush creates a full page bitmap regardless of the actual size of the drawing elements. Microsoft Draw can be used to generate similar graphics images with significantly less overhead. Creating diagram annotations with formatted text should be done with the "Text Annotation" feature. If you choose to use an OLE object for annotations you should use Microsoft Draw rather than a word processor such as Microsoft Word. Word requires more system resources to execute which makes it more cumbersome (and slower) to execute as an OLE server.

Known Issues ============== When exporting a .KM file to BML, do not include ".EXP" in your file name because an invalid export file extension error may occur if your machine is not configured to accept the long path name. While Merging .KM files, if you receive the error message, "The Sender already sends "Name of Data Flow" to that Receiver", answer "Yes" to the message and ignore it. When you initially open a Data Flow Diagram, invoke the "Refresh Diagram Contents" option from the Diagram menu. This will insure that all pertinent information is displayed within the context. 10138478: In Webview when using Netscape, the GIF diagram does not always load correctly. If the diagram frame is small enough to display the horizontal and vertical scrollbars this condition occurs and the frame window is left blank. If the frame is large enough to hold the GIF without using both scrollbars, then the diagram displays correctly. 10138845 : Reconcile fails with a 'Parse Error' message when an OrdAssociationClassArc/OrdAssociationTypeArc is created in the subordinate.