Database functions - Bench 1.1 ------------------------------ Hidden underneath Bench 1.1 is a dBASE-compatible database engine (Codebase ++, by Sequiter Software). This database engine is responsible not only for cataloging the tests, but also for keeping track of their results. In order for you to get the most out of Bench 1.1, it is important to understand how Bench 1.1 organizes the results it generates from the tests. In the Bench subdirectory, you will find five .DBF files and five .MDX files: TEST.DBF TEST.MDX TSTGROUP.DBF TSTGROUP.MDX MACHINE.DBF MACHINE.MDX RESULT.DBF RESULT.MDX SYSINFO.DBF SYSINFO.MDX The .DBF files are dBASE-compatible data files and the .MDX files are their respective index files. The MACHINE and RESULT files record information for the test machines. The MACHINE file stores data about a given system configuration. The information in this file is as follows: Machine ID : 8 characters Variant : 1 character Machine Name : 12 characters Machine Description : 225 characters The Machine ID and Variant are used to uniquely identify a machine and configuration. For example: Machine ID: ibm70 Variant: 0 could be used to identify an IBM PS/2 Model 70 configured to run without a disk cache while: Machine ID: ibm70 Variant: 1 could be used to identify the same machine with disk caching enabled. It is imperative to use meaningful Machine IDs when recording test results. When printing test results to a file, the output file name will take the form of: [MachineID].PR[V] where [V] is the Variant ID used for that unit's test run. "Machine Name" serves in Bench 1.1 as identifier for column headings in all of the test windows. Machine Description is a long description which can include notes about the system's components, any special configuration notes, or any special observations about the system's behavior while under test. The RESULT file is where all the results from the tests are stored. Provided with Bench 1.1 are result files from the following machines: IBM XT IBM AT Compaq Deskpro 386N IBM Model 70-A21 Compaq Deskpro 38625e IBM Model 90 (486-33) Every time a test is run, the result is immediately written to the database. This ensures that if there is a problem with any one test hanging the system or aborting the tests, the results from the rest of the test run aren't lost. Upon exiting the program, the exit dialog box asks you if you want to commit results to the database. Checking this box means that the results that are currently in the database will be permanently stamped with a date and time. This will permit these results to be recalled later on for comparison purposes. If you choose not to commit the results to the database, the next time you run the program, the first thing that will appear is a dialog that will remind you of uncommitted results in the database. You will be given four options at that time: use - use the results and bring them back for modifications/additions delete - delete the results from the database and then prompt for new machine information commit - date- and time-stamp the results and then prompt for new machine information exit - exit the program You should make backups of your database periodically. In the event that your database becomes corrupt or gets destroyed there are backup files containing only the default comparison machine data. When making your own backups, do not use the extensions .BKD or .BKX as they will conflict with the prestored backups. TO RESTORE THE DATABASE TO ITS ORIGINAL CONTENTS: Run the REINITDB batch file. You will be warned that your data is about to be destroyed. To cancel the procedure, hold down the Ctrl key and hit the Break key. (The word "Break" may appear on the front of this key on some keyboards.)