Installing Mimer SQL

This chapter describes how to install the Mimer SQL software on OpenVMS. It also documents how to remove a Mimer SQL installation.

Overview

•Execute the distribution file to obtain the installation files

•Use PRODUCT INSTALL to install Mimer SQL

•Add commands in SYS$MANAGER:SYSTARTUP_VMS.COM, SYS$MANAGER:SYSHUTDWN.COM and SYS$MANAGER:SYLOGIN.COM

•Execute SYS$COMMON:[MIMERxxxxx]SETUP.COM to define Mimer commands for this process

•Install your Mimer SQL license key

Execute the distribution file to obtain the installation files

The software is distributed as a self-extracting ZIP file. To unpack the ZIP file, just execute it. The installation files will be extracted and placed in the current directory.

$ RUN MIMER-I64VMS-MIMER1106A.ZIPEXE

UnZipSFX 6.00 of 20 April 2009, by Info-ZIP (http://www.info-zip.org).

  inflating: MIMER-I64VMS-MIMER1106A-U1100-6A-1.PCSI$COMPRESSED  

Use PRODUCT INSTALL to install Mimer SQL

Use the command PRODUCT INSTALL to install Mimer SQL, just like any other layered product. Please note that the product name includes the version number which is unusual. New versions of Mimer will have new version numbers in the product name which will make all versions of Mimer to appear as different products. This allows multiple versions to be installed at the same time on a machine. The user can select any version by running its SETUP command procedure.

$ PRODUCT INSTALL MIMER1106A

 

Performing product kit validation of signed kits ...

%PCSI-I-CANNOTVAL, cannot validate SIV$DKA300:[PER.SLASK]MIMER-I64VMS-MIMER1106A-U1100-6A-1.PCSI$COMPRESSED;1

-PCSI-I-NOTSIGNED, product kit is not signed and therefore has no manifest file

 

The following product has been selected:

   MIMER I64VMS MIMER1106A U11.0-6A       Layered Product

 

Do you want to continue? [YES]

 

Configuration phase starting ...

 

You will be asked to choose options, if any, for each selected product and for

any products that may be installed to satisfy software dependency requirements.

 

Configuring MIMER I64VMS MIMER1106A U11.0-6A

 

* This product does not have any configuration options.

 

Execution phase starting ...

 

The following product will be installed to destination:

   MIMER I64VMS MIMER1106A U11.0-6A       DISK$I64SYS:[VMS$COMMON.]

 

Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...90%...100%

 

The following product has been installed:

   MIMER I64VMS MIMER1106A U11.0-6A       Layered Product

 

MIMER I64VMS MIMER1106A U11.0-6A

 

   Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:

       @SYS$STARTUP:MIMER$STARTUP_1106A

   Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:

       @SYS$STARTUP:MIMER$SHUTDOWN_1106A

 

   Users need to add the following lines to their login command procedure:

       $ @SYS$SYSROOT:[MIMER1106A]SETUP VMS

Add commands in system startup files

As instructed by the PRODUCT INSTALL command, you should add commands to execute Mimer startup and shutdown procedures.

The procedure SYS$STARTUP:MIMER$STARTUP_1106A installs required shareable images. Add a command to do this in SYS$MANAGER:SYSTARTUP_VMS.COM.

The procedure SYS$STARTUP:MIMER$SHUTDOWN_1106A deinstalls shareable images. Add a command to do this in SYS$MANAGER:SYSHUTDWN.COM.

Any process that is running Mimer SQL must execute the SETUP command procedure for the version of Mimer SQL it wants to use. By adding the SETUP command in SYS$MANAGER:SYLOGIN.COM, a default SETUP is provided for all processes. This makes it easier to manage a version upgrade of Mimer SQL since the command is in a central place.

Execute SYS$COMMON:[MIMERxxxxx]SETUP.COM for this process

To continue using the newly installed Mimer SQL product in the current process you should execute the SETUP procedure.

$ @SYS$SYSROOT:[MIMER1106A]SETUP VMS

MIMER version 11.0.6A Beta Test Jun 29 2021 Rev 35581

Node name: SIV VMS IA64

 

An alternative is to log out and log in again. The new process should have executed the SYS$MANAGER:SYLOGIN.COM procedure where you have added the SETUP command.

The SETUP procedure is described further in section The Mimer SQL SETUP command procedure.

Install your Mimer SQL license key

Mimer requires a license key to be installed. Use the MIMLICENSE command to administrate Mimer licenses. A license for testing purposes is included in the Mimer distribution and can be reached by the logical name MIMER$EXAMPLES.

The MIMLICENSE command is described further in section Installing the Mimer SQL License Key.

$ MIMLICENSE /FILE=MIMER$EXAMPLES:DEFAULTKEY.MCFG

 

Mimer SQL License Manager  Version 11.0.6A Beta Test

Copyright (C) Mimer Information Technology AB. All rights reserved.

 

License key file: SYS$SPECIFIC:[SYSMGR]MIMERKEY_IA64.DAT

 

Number Expires    Version Module       Users Netusers

------ ---------- ------- ------------ ----- --------

   -6 2022-01-31 11.0    Beta test                   *** test and development

                         Mimer SQL       10       10

                          Imm restart

                          XA          

 

Key file updated

 

Note: The database server must be restarted to enable the new key settings

The Mimer SQL SETUP command procedure

Use the SETUP command procedure in the top directory of a particular Mimer installation to define logical names and commands for the current process. For example:

$ @SYS$SYSROOT:[MIMER1106A]SETUP VMS

MIMER version 11.0.6A Beta Test Jun 29 2021 Rev 35581

Node name: SIV VMS IA64

 

The parameter to SETUP specifies what style of commands you wish to use. You can also clear any definitions made by a previous SETUP command.

@SYS$SYSROOT:[MIMER1106A]SETUP VMS

This command specifies that Mimer version 11.0.6A should be used. Logical names are defined in the process logical name table. Mimer commands are defined in VMS style (like: MIMCONTROL/START).

Note that if you create a subprocess (by using the SPWAN command), the command definitions will not be active in the there. Use the SETUP command again in the subprocess.

If no parameter is given to the SETUP procedure, VMS will be assumed.

@SYS$SYSROOT:[MIMER1106A]SETUP UNIX

This command specifies that Mimer version 11.0.6A should be used. Logical names are defined in the process logical name table. Mimer commands are defined in UNIX style (like: mimcontrol --start).

UNIX command definitions will be transferred to any subprocess you start with the SPAWN command.

@SYS$SYSROOT:[MIMER1106A]SETUP CLEAR

Clears all logical names and command definitions made by an earlier invocation of the SETUP procedure.

Logical Names Defined by SETUP

The SETUP command defines the logical names listed below

Installing the Mimer SQL License Key

Mimer SQL for OpenVMS is free for development and evaluation. A development and evaluation license key is included in the Mimer SQL distribution and is automatically installed.

This means that, as long as you use Mimer SQL for development and/or evaluation, you can set up a complete Mimer SQL environment and work with Mimer SQL without adding any additional license keys.

Mimer SQL for OpenVMS in Production

If you want to use Mimer SQL in production, you must purchase a valid run-time license key and then install it. Please contact your local Mimer SQL representative, see https://www.mimer.com/contact/, or send an e-mail to info@mimer.com.

Node Name

Your representative will need to know the node name of the computer on which the Mimer SQL database server will run.

To obtain the node name, use SETUP:

$ @SYS$SYSROOT:[MIMERxxxx]SETUP

Receiving Your Run-time License Key

Your run-time license key and instructions for installing it will be e-mailed to you.

When you receive the file, save it in an accessible directory.

The MIMLICENSE Utility

You use the MIMLICENSE utility to administrate the license key file. You can add, remove and update keys using MIMLICENSE.

You can also use MIMLICENSE to list and describe the contents of the key file.

Note:When entering the Mimer SQL license key, you must have appropriate access to the key file.

Adding a License Key using MIMLICENSE

To add a license key

1Assuming a SETUP with VMS-style commands, enter the following:

$ mimlicense /FILE=file_name.mcfg

 

For example, if the license key file you received was named mimerkey1234.mcfg, you would enter the following:

$ mimlicense /FILE=mimerkey1234.mcfg

MIMLICENSE Syntax

The MIMLICENSE program is controlled by options specified on the command-line.

The Mimer SQL license keys are stored in the file:

SYS$SPECIFIC:[SYSMGR]MIMERKEY.DAT

Removing a Mimer SQL Installation

To remove a Mimer SQL installation:

1Check that no Mimer SQL applications or database servers are using the installation.

2Remove the selected Mimer SQL version by using the PRODUCT REMOVE command:

$ PRODUCT REMOVE MIMER1106A

 

The following product has been selected:

   MIMER I64VMS MIMER1106A U11.0-6A       Layered Product

 

Do you want to continue? [YES]

 

The following product will be removed from destination:

   MIMER I64VMS MIMER1106A U11.0-6A       DISK$I64SYS:[VMS$COMMON.]

 

Portion done: 0%...20%...30%...40%...50%...60%...70%...80%...90%...100%

 

The following product has been removed:

   MIMER I64VMS MIMER1106A U11.0-6A       Layered Product

 

3If there are no other Mimer SQL installation trees in the system, you may want to delete the SQLHOSTS file and the Mimer SQL license key file:

$ DELETE SYS$SPECIFIC:[SYSMGR]SQLHOSTS.DAT.*

$ DELETE SYS$SPECIFIC:[SYSMGR]MIMERKEY_IA64.DAT.*

 

4If you have added any Mimer SQL-related commands to the OpenVMS startup file SYS$MANAGER:SYSTARTUP_VMS.COM, or the OpenVMS shutdown file SYS$MANAGER:SYSHUTDWN.COM, or the OpenVMS system login file SYS$MANAGER:SYLOGIN.COM, remove these commands.

5If you have added any database-specific commands to the system startup file SYS$MANAGER:SYSTARTUP_VMS.COM, or the shutdown file SYS$MANAGER:SYSHUTDWN.COM, you should remove them.