Print this page.  If your browser doesn't allow JavaScript, right-click this page and choose Print from the popup-menu.        
Use Mimer V7 applications with Mimer SQL V9 on OpenVMS Alpha
Categories: Migration, System Management

First, please note! This guide only works for OpenVMS on the Alpha architecture. It does NOT work on the Integrity platform since no Mimer version 7 product is available there.

Mimer version 7 (V7) included a number of libraries and utilities that were not SQL-based. For example:

QL - Old Query Language
PG - Program Generator
FM - Forms Manager
SH - Screen Handler
RG - Report Generator
QF - Query by Forms
PI - Old API for Database Access

All development on these modules stopped more than ten years ago, and the Mimer SQL version 9 distribution does not include these modules.

However, the Mimer SQL Engine version 9 database (V9) server is still compatible with all the earlier tools. This document shows how you can use V7 modules such as QL, PG, SH and FM together with V9 on OpenVMS.


By using a special command procedure, MIMBUILD9.COM, together with a compatibility library (COMPAT.OBJ), you can add components from a Mimer V7 distribution to an existing V9 installation.

The command procedure is placed in the V7 distribution tree. It is very similar to the MIMBUILD command procedure used to build a V7 installation. The compatibility library should also be placed in the V7 distribution tree, next to the MIMBUILD9 command procedure.

MIMBUILD9 copies the old libraries into the V9 installation tree, and links the old modules (QL, PG, RG, etc) with the V9 database libraries.

A command file named MIMSETUP7.COM is created in the V9 root directory. This command file will redefine the MIMLIB7 and MIMEXE7 logical names to MIMLIB9 and MIMEXE9.

Some V7 components access data files by using the MIMLIB7 logical name. MIMER/PG starts code generator programs by using the MIMEXE7 logical name. By redefining these logical names, the old V7 installation is no longer used at all by the relinked programs.

The following picture shows an overview of the MIMBUILD9 environment:


The MIMBUILD9.COM command procedure and the COMPAT.OBJ file are copied to the [MIMAXP7] distribution tree. The MIMBUILD9 command procedure is used to build the V7 modules to the V9 installation that the logical name MIMROOT9 points to.

Please make sure that the correct V9 installation is set up by using the MIMSETUP9.COM command procedure.
$ SET DEF disk:[MIMAXP7]

Note that the MIMBUILD9 command procedure uses a configuration file named CONFIG.DAT which stores build options. If no such file is found in the V9 installation root directory, a new default file will be created. If you want to use an older configuration file from a V7 installation, simply copy it to the V9 root directory before running the MIMBUILD9 command procedure:

Now you can rebuild the V7 modules by running MIMBUILD9.COM:

Finally, the MIMLIB7 and MIMEXE7 logical names should be redefined by running the MIMSETUP7 command procedure. Supply a parameter that specifies the logical name table to use, in the same fashion as the MIMSETUP9 command procedure:


The old V7 components are installed in the V9 environment. All executable modules are relinked with the V9 database libraries. This allows the programs to access the V9 database server directly.

No V7 license key file (MIMKEY7) is needed for the clients. However, a LEVEL2 license must be present on the V9 server. Note that the default license file does not include a LEVEL2 license.

Libraries and option files are created in the MIMLIB9 directory. Earlier applications can be relinked by using exactly the same command that linked the application in the V7 environment. When the application is relinked, it will access the V9 database client library directly.

If the MIMSETUP7 command procedure is used, MIMLIB7 and MIMEXE7 are redefined to MIMLIB9 and MIMEXE9. The old V7 installation is no longer needed and can be removed if desired. However, you should keep the V7 distribution ([MIMAXP7]) to enable the V7 modules to be relinked.


In V7, there was one database library for single-user mode, and another for multi-user mode. In V9, there is only one database library that is capable of operating in both modes. Normally, a V9 application operates in multi-user mode, but by defining the logical name MIMER_MODE to SINGLE, the application can execute in single-user mode:

To distinguish between programs linked in single-user mode from the multi-user mode programs, an S or M suffix were added to the program names in V7. BSQL for single-user mode was called BSQLM. In V9, the need for S or M suffixes is no longer present, so the BSQL program is simply named BSQL.

However, to ensure maximum compatibility, the MIMBUILD9 command procedure will name the executable programs with suffixes, so the programs will be named QLM, PGM, CLM, etc.

Note that it is possible to edit the CONFIG.DAT file to request that single-user mode versions should be linked. If this is done, the MIMBUILD9 command procedure will create a program with an S suffix, but since there is only one kind of database server library in V9, the program with the S suffix will be an exact copy of the program with the M suffix. So it is recommended that no single-user version be linked. If you need to run a program in single-user mode, always redefine the MIMER_MODE logical name.

Upgrading a V9 installation

New V9 distributions come as new directory trees with new top-level names. When you upgrade Mimer SQL Engine version 9, it is recommended that you:

1) Install the new directory tree (for instance, [MIMER931A])

2) Copy the old configuration parameter file to the new V9 installation tree

3) Set up the new version:
$ @[MIMER921D]MIMSETUP9 -SYS     ! Deinstall V921D
$ @[MIMER931A]MIMSETUP9 SYS ! Install V931A

4) Rebuild the V7 modules to the new version tree:

5) Setup the V7 logical names:

Download MIMBUILD9.COM and COMPAT.OBJ (as an EXE file). Run the EXE file to access MIMBUILD9.COM and COMPAT.OBJ

Last updated: 2005-09-08


Powered by Mimer SQL

Powered by Mimer SQL