Mimer SQL Documentation TOC PREV NEXT INDEX

Mimer SQL Developer Site

Running Mimer SQL Applications

This chapter describes how to run applications in the Mimer SQL Engine environment.

It covers information that applies to the utilities included in the Mimer SQL Engine installation as well as to applications that may have been created to access a Mimer SQL database.

This chapter also describes:

Executing Mimer SQL Utilities

This section describes the various ways an application can be executed under OpenVMS and also describes how to set up the Mimer SQL-supplied utilities to use UNIX-style or OpenVMS-style command-line flags.

Using the DCL command RUN

The DCL command RUN can be used as follows:


You cannot specify any flags or other input parameters on the command-line when you use the RUN command.

Some of the Mimer SQL-supplied programs allow parameters and options to be supplied via logical names, e.g. MIMER_DATABASE to supply a database name and MIMER_MODE to define the database access mode.

See documentation for the programs in the Mimer SQL System Management Handbook for specific details.

Using OpenVMS Command Definitions

You can set up the programs supplied by Mimer SQL so that they can be run by specifying the program name followed by the VMS-style command line flags and parameters.

You do this by defining the Mimer SQL programs as DCL command verbs.

Use the following OpenVMS command to define all the Mimer SQL-supplied programs as DCL command verbs:


Example using OpenVMS-style command-line arguments:


You can un-define a DCL command by issuing the following command:

 $ SET COMMAND/DELETE=command-name

Caution: Take care when using this DCL command, because any DCL command verb can be un-defined.

Using the DCL$PATH Logical Name

The DCL$PATH logical name defines a list of directories in which the OpenVMS operating system will look when trying to locate the executable for a specified program name.

Utilities started this way accept UNIX-style command options.

Note: If you set-up a Mimer SQL-supplied utility as a DCL command verb, the UNIX-style command-line flags and parameters are not used, even if MIMEXE9 is included in DCL$PATH.

In order for the utilities supplied by Mimer SQL to be run by specifying the utility name followed by the UNIX-style command line flags and parameters, you must include the MIMEXE9 directory in the directory list defined in DCL$PATH.

If there are other directories containing executables for programs that are to be run this way, those directories must also be included in the directory list defined in DCL$PATH.

For example, the following DCL$PATH definition:

 $ DEFINE DCL$PATH MIMEXE9,disk:<directory.app>

will allow the utilities supplied by Mimer SQL to be run by specifying the utility name followed by the UNIX-style command line flags and parameters.

It will also allow all programs found in the specified application directory to be run by specifying the program name.

Example using UNIX-style command-line flags:

 $ bsql -s testdb

Running the PSM Debugger

You can use the Mimer SQL PSM Debugger for debugging PSM procedures that are stored in the Mimer SQL database server. The PSM debugger is written in Java and requires a Java 2 environment.

Since the Debugger accesses the Mimer SQL server by using the TCP protocol, you can execute the Debugger on any machine that has adequate Java support, such as a Windows or Linux machine.

If you want to execute the PSM debugger on the OpenVMS platform, you must first make sure that the Java 2 environment is active.

You can display the current Java version using the following command:


If you need to install a newer Java version on OpenVMS, you can download the installation kit from the following site:

Starting the PSM Debugger

To start the PSM debugger, use the following command:


More information about the PSM debugger can be found in the included on-line help file.

Selecting a Mimer SQL Installation

A host computer can have several versions of the Mimer SQL database system installed simultaneously.

Access to a specific version is done through logical names (MIMEXE9, etc.). Since the major version number (currently 9) is included in the logical names, Mimer SQL version 7, version 8 and version 9 can run concurrently without any interference.

If several versions of Mimer SQL Engine version 9 are installed, you can use the MIMSETUP9 command procedure to specify exactly which version a program should work with.

Normally, you do a system wide definition of the logical names. However, you can specify another Mimer SQL version by running the MIMSETUP9 command procedure and specifying a GROUP, JOB or PROCESS logical name definition (see MIMSETUP9 Syntax for details on MIMSETUP9).

Note: When starting a database server, any JOB or PROCESS logical names will not be inherited by the database server process. The database server will use the Mimer SQL version specified in the GROUP or SYSTEM logical name tables.

Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40
Mimer SQL Documentation TOC PREV NEXT INDEX