Distributed Files

The Mimer SQL distributed files are all located in a directory structure.

Root Directory Files


File Name	Description
DEFAULTKEY.MCFG	Default Mimer SQL license key.
MIMSETUP.COM	Command procedure that defines logical names and installs images, see Setting-up the Mimer SQL Environment.
VERSION.DAT	Contains the version number of the Mimer SQL distribution.

Documentation Files (MIMDOC)


File Name	Description
MIMJDBEN.PDF	JDBC usage guide.
MIMSQLEN.PDF	The Mimer SQL documentation.
MIMVMS.PDF	The VMS guide.
README.TXT	A short description of Mimer SQL and how to get started.
RELNOTEN.PDF	Mimer SQL Release Notes.

Example Files (MIMEXAMPLES)


File Name	Description
BLOBSAMP.EC	Example of a program written in embedded C that stores and retrieves binary data.
DSQL.EC	Embedded C examples that demonstrates the use of dynamic SQL.
DSQL.H	Header file for the dynamic SQL example.
DSQLSAMP.C	Main program for the dynamic SQL example.
EXAMPLE.EC	Very simple embedded C example.
EXAMPLE.ECO	Very simple embedded COBOL example.
EXAMPLE.EFO	Very simple embedded FORTRAN example.
EXAMPLE.JAVA	Java example program using JDBC.
FREQCALL.EC	Example of a program written in embedded C that calls a stored procedure.
FREQCALL.ECO	Same as FREQCALL.EC, but written in COBOL.
FREQCALL.EFO	Same as FREQCALL.EC, but written in FORTRAN.
SINGLEDEFS.DAT	Contains a template for database parameters in single-user mode, see the Mimer SQL System Management Handbook.
SQLHOSTS.DAT	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.
WAKECALL.EC	Example of a program written in embedded C that calls a stored procedure.
WAKECALL.ECO	Same as WAKECALL.EC, but written in COBOL.
WAKECALL.EFO	Same as WAKECALL.EC, but written in FORTRAN.

Executable Programs (MIMEXE)


File Name	Description
BSQL.EXE	Program that executes SQL statements which are entered interactively or read from a command file. It is described in the Mimer SQL User's Manual.
DBC.EXE	Program that can check if a databank file is internally consistent. It is described in the Mimer SQL System Management Handbook.
DBOPEN.EXE	Program that opens and restarts all databanks in a database. It is described in the Mimer SQL System Management Handbook.
DBSERVER.EXE	The database server. Do not start this program directly, use MIMCONTROL to do this.
ESQL.EXE	Pre-processor for embedded SQL.
EXLOAD.EXE	Program to load the example database.
EXPTOLOAD.EXE	Program converting old export files to the new mimload format.
MIMCONTROL.EXE	The MIMCONTROL command, which is used to control database servers,The MIMCONTROL Command.
MIMINFO.EXE	Program that can display status information for a database server.
MIMLICENSE.EXE	Application used to administrate the license key(s).
MIMLOAD.EXE	Utility to load and unload data.
MIMREPADM.EXE	Administration utility for Mimer Replication.
MIMSYNC.EXE	Utility to bring two replicated Mimer systems back into sync.
MIMTCP.EXE	The program executed by the MIMTCP server, see The MIMTCP Server. Do not start this program directly.
PSMDEBUG.JAR	The PSM Debugger. For more information, see Running the PSM Debugger.
REPSERVER.EXE	Mimer Replication server.
SDBGEN.EXE	Program used to create the initial Mimer SQL system databank files in a database, described in the Mimer SQL System Management Handbook.
TCPCONTROL.COM	Procedure to manage MIMTCP processes.

Library Files (MIMLIB)


File Name	Description
LR.OLB	Library with entries for backward compatibility.
LRU.OLB	Library with entries for backward compatibility.
MDR.OLB	Library with entries for backward compatibility.
MIMCOMM.EXE	Library for shared memory communication in JDBC.
MIMDB.EXE	Shareable library image containing the code for the Mimer SQL database client API, see Shared Images.
MIMDBP.EXE	Protected shareable library image containing code that performs secure and fast shared memory based communication with local database servers.
MIMDBS.EXE	Shareable library image containing code for running a Mimer SQL database in single-user mode. This library is mapped in dynamically when required.
MIMER.CLD	Command definitions for all the executable programs supplied with the Mimer SQL software.
MIMER.OPT	Options file used for linking Mimer SQL applications.
MIMJDBC1.JAR	JDBC 1 driver.
MIMJDBC2.JAR	JDBC 2 driver.
MIMJDBC3.JAR	JDBC 3 driver.
MIMODBC.EXE	ODBC driver library.
MIMODBC.H	C-definitions for Mimer ODBC specific descriptor attributes, working with 64-bit integers.
MIMSQLXA.OBJ	Object file containing an xa_switch_t entry defining mimsqlxa, which is used when accessing the XA routines in Mimer SQL.

Shared Images

The Mimer SQL distribution contains a number of shareable images which are located in the MIMLIB directory.

The shared images are installed by the MIMSETUP command procedure when defining logical names in the SYSTEM or GROUP name table.

Mimer SQL applications are linked with the shareable library MIMLIB:MIMDB.EXE.

When the application image is activated, the OpenVMS system locates the correct shareable image by using the logical name MIMDB (which MIMSETUP has defined as MIMLIB:MIMDB). This allows users to run applications with other versions of Mimer SQL by using the MIMSETUP 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 MIMSETUP 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!