The Mimer SQL distributed files are all located in a directory structure.
Root Directory Files
Default Mimer SQL license key. Command procedure that defines logical names and installs images, see Setting-up the Mimer SQL Environment. Contains the version number of the Mimer SQL distribution.
Documentation Files (MIMDOC9)
Mimer SQL Release Notes. JDBC usage guide. A short description of Mimer SQL and how to get started. The VMS guide. The Mimer SQL Engine documentation.
Example Files (MIMEXAMPLES9)
Example of a program written in embedded C that stores and retrieves binary data. Embedded C examples that demonstrates the use of dynamic SQL. Header file for the dynamic SQL example. Main program for the dynamic SQL example. Very simple embedded C example. Very simple embedded COBOL example. Very simple embedded FORTRAN example. Java example program using JDBC. Example of a program written in embedded C that calls a stored procedure. Same as FREQCALL.EC, but written in COBOL. Same as FREQCALL.EC, but written in FORTRAN. Contains a template for database parameters in single-user mode, see the Mimer SQL Engine System Management Handbook. Contains a template for the SQLHOSTS.DAT file.The actual SQLHOSTS file is pointed to by the MIMER_SQLHOSTS logical name (normally SYS$MANAGER:SQLHOSTS.DAT).Do not edit this template file. Example of a program written in embedded C that calls a stored procedure. Same as WAKECALL.EC, but written in COBOL. Same as WAKECALL.EC, but written in FORTRAN.
Executable Programs (MIMEXE9)
Program that executes SQL statements which are entered interactively or read from a command file. It is described in the Mimer SQL Engine User's Manual. Program that can check if a databank file is internally consistent. It is described in the Mimer SQL Engine System Management Handbook. Program that opens and restarts all databanks in a database. It is described in the Mimer SQL Engine System Management Handbook. The database server. Do not start this program directly, use MIMCONTROL to do this. Pre-processor for embedded SQL. Program to load the example database. Program converting old export files to the new mimload format. The MIMCONTROL command, which is used to control database servers,The MIMCONTROL Command. Program that can display status information for a database server. Application used to administrate the license key(s). Utility to load and unload data. Administration utility for Mimer Replication. Utility to bring two replicated Mimer systems back into sync. The program executed by the MIMTCP server, see The MIMTCP Server. Do not start this program directly. The PSM Debugger. For more information, see Running the PSM Debugger. Mimer Replication server. Program used to create the initial Mimer SQL system databank files in a database, described in the Mimer SQL Engine System Management Handbook. Procedure to manage MIMTCP processes.
Library Files (MIMLIB9)
Library with entries for backward compatibility. Library with entries for backward compatibility. Library with entries for backward compatibility. Library for shared memory communication in JDBC. Shareable library image containing the code for the Mimer SQL database client API, see Shared Images. Protected shareable library image containing code that performs secure and fast shared memory based communication with local database servers. Shareable library image containing code for running a Mimer SQL database in single-user mode. This library is mapped in dynamically when required. Command definitions for all the executable programs supplied with the Mimer SQL software. Options file used for linking Mimer SQL applications. JDBC 1 driver. JDBC 2 driver. JDBC 3 driver. C-definitions for Mimer ODBC specific descriptor attributes, working with 64-bit integers. ODBC driver library. Object file containing an xa_switch_t entry defining mimsqlxa, which is used when accessing the XA routines in Mimer SQL.
The Mimer SQL Engine distribution contains a number of shareable images which are located in the MIMLIB9 directory.
The shared images are installed by the MIMSETUP9 command procedure when defining logical names in the SYSTEM or GROUP name table.
Mimer SQL applications are linked with the shareable library MIMLIB9:MIMDB9.EXE.
When the application image is activated, the OpenVMS system locates the correct shareable image by using the logical name MIMDB9 (which MIMSETUP9 has defined as MIMLIB9:MIMDB9). This allows users to run applications with other versions of Mimer SQL by using the MIMSETUP9 procedure, without having to re-link the applications.
If you start an image that is installed with privileges or if you do not have read (R) access to the image file, OpenVMS will only use logical names defined in executive mode when activating shareable images. This is a security precaution that OpenVMS takes to avoid activating non-trusted shareable images together with trusted images.
Note: All logical names that MIMSETUP9 defines in the SYSTEM logical name table are defined in executive mode. This means that privileged or protected images will run the Mimer SQL version defined in the SYSTEM table even if there is another Mimer SQL version defined in one of the other tables!
Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40