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.
The following steps provide an overview of how to install Mimer SQL for OpenVMS.
- Unpack the distribution file to a directory tree
To unpack the file, simply execute it. Note that the MIMER1001B.EXE file must reside in your current directory, so you may have to copy the file.
A new directory will be created in your current default directory. For example:$ COPY MIMER1001B.EXE somedisk: $ SET DEF somedisk: $ RUN MIMER1001B
For more information, see Unpacking the Mimer SQL Distribution File.
- Set-up the Mimer SQL Environment
Using MIMSETUP, you set up locations for programs, libraries, data files, documentation, etc., for users and applications. For example:$ @somedisk:[MIMER1001B]MIMSETUP SYS
For more information, see Setting-up the Mimer SQL Environment.
- (Optional) Install your Mimer SQL License Key
A default key, for test and development only, is automatically installed, that is, you can finish the installation without adding a key.
But, if you are going to put Mimer SQL into production you must install a run-time license.
See Installing the Mimer SQL License Key.
- (Optional) Add a MIMSETUP command in the SYSTARTUP_VMS.COM file
In order to set-up Mimer SQL each time the system boots, include the MIMSETUP command in the system startup file:
SYS$MANAGER:SYSSTARTUP_VMS.COM, for example:$ @disk:[MIMER1001B]MIMSETUP SYSTEM
When you have carried out the steps above, you are ready to create your first database, see Establishing a Database.
Unpacking the Mimer SQL Distribution File
The most common way of acquiring the Mimer SQL distribution for OpenVMS is to download it, in ZIP file format, from http://developer.mimer.com. The ZIP file is created using Info-ZIP.
Once downloaded, the file looks like an ordinary executable (*.exe) file, for example, the file containing Mimer SQL version 10.0.1B is named MIMER1001B.EXE.
Unpacking the ZIP File
To unpack the contents of the ZIP file, execute the file. Note that the MIMER1001B.EXE file must reside in your current directory, so you may have to copy the file.
The Mimer SQL distribution directory will be created under the current directory. For example:$ COPY MIMER1001B.EXE somedisk: $ SET DEF somedisk: $ RUN MIMER1001B
Note that you must download an executable file that matches your server platform, Alpha or Integrity. If you try to execute the wrong distribution file, you will get an error message.
Ensuring Correct File Protections
Note: The three consecutive dots in the "[...]" construction used in the OpenVMS command examples that follow, together with savesets, are an essential part of the command syntax. If they are omitted, all files on the distribution media will be assigned to a single directory and the Mimer SQL installation will fail.
The auto-extract facility may not always apply the correct file protections to the files it extracts.
Therefore, we recommend that you run the following commands to ensure that the correct file protections are applied to the files in the tree:$ SET FILE/PROT=(S:RWED,O:RWED,G:RE,W:RE) [MIMERxxxxx...]*.* $ SET FILE/PROT=(S:RWE,O:RWE,G:RE,W:RE) MIMERxxxxx.DIR
The Mimer SQL Directory Tree
Once you have successfully unpacked Mimer SQL, you can review the directory structure in which the Mimer SQL Version 10.0 software resides.
The name of the installation root directory in the tree contains the word `MIMER' and the version number of the product, for example: `MIMER1001B' (generally denoted as MIMERxxxxx).
The name of the root directory is unique for each Mimer SQL release. This makes it easier to install new versions without affecting any previous versions of the product.
For more information about the files installed, see Distributed Files.
Setting-up the Mimer SQL Environment
Before you can run Mimer SQL, you must carry out certain setup operations. These include defining locations for programs, libraries, data files and documentation for users and applications.
You set up Mimer SQL using the MIMSETUP command procedure. MIMSETUP defines the logical names needed to run Mimer SQL applications.
You can find the MIMSETUP command procedure in the Mimer SQL root directory.
Note: When running MIMSETUP, you may require some of the following privileges: SYSPRV, CMKRNL, SYSNAM, see Privileges for details.
The syntax for the MIMSETUP command is as follows:$ @disk:[MIMERxxxxx]MIMSETUP [-][lnm-table]
The parameter lnm-table specifies which logical name table to use when defining the logical names required to access a Mimer SQL installation.
If the parameter lnm-table is preceded by a hyphen (-), the MIMSETUP command procedure will remove the effects of any Mimer SQL setup previously performed for the specified table, including uninstalling shareable images.
Valid values for lnm-table are:
In general, we recommend that you execute MIMSETUP to update the SYSTEM logical name table so that the definitions are available to all users.
SYSTEM or GROUP
If you specify SYSTEM or GROUP, the following shared images will be installed if they are not installed already:
Therefore, for a Mimer SQL installation, you must perform a SYSTEM or GROUP level setup at least once in order to get these essential shared images installed. For more information, see Shared Images.
PROCESS or JOB
You can perform MIMSETUP at the PROCESS or JOB level to set up logical names that may be different to those available from the SYSTEM or GROUP level (no shared image installation is involved in a PROCESS or JOB level setup).
If you run MIMSETUP without specifying the lnm-table parameter, a PROCESS level setup is performed by default.
In order to run a SYSTEM-wide MIMSETUP, you must have SYSPRV, CMKRNL and SYSNAM privileges.
When logical names are defined in the SYSTEM table, they are defined in executive mode.
To run a GROUP-wide MIMSETUP, you must have SYSPRV and CMKRNL privileges.
System Startup Command File
Since all setups have to be re-executed each time the OpenVMS system is booted, we recommend that you enter the command(s) in the system startup command file: SYS$MANAGER:SYSTARTUP_VMS.COM.
For example:$ @disk:[MIMER1001B]MIMSETUP SYSTEM
Defining Logical names SYSTEM Wide
The following example defines logical names SYSTEM wide, that is, all OpenVMS users may access the Mimer SQL installation. Shareable images are installed.$ @SDEPT2:[MIMER1001B]MIMSETUP SYSTEM
Overriding the Default Definition of the Logical Names
The following example shows how any user can override the default definition of the logical names. This is useful when a user wants to test an alternative Mimer SQL installation. No shareable images are installed.$ @SDEPT2:[MIMER1001B]MIMSETUP
Removing a Mimer SQL Setup
The following example demonstrates how to remove a Mimer SQL setup which was previously made GROUP wide by running MIMSETUP (MIMROOT was defined by MIMSETUP). Shareable images are uninstalled.$ @MIMROOT:MIMSETUP -GROUP
Logical Names Defined by MIMSETUP
The MIMSETUP command defines the logical names listed below:
MIMCOMM Points to a native communication library for JDBC. MIMDB Logical name pointing to the Mimer SQL shareable library. Used when starting Mimer SQL applications. MIMDBP Logical name pointing to the MIMDBP image. Used when starting Mimer SQL applications. MIMDOC Points to the directory containing on-line documentation. MIMER_SQLHOSTS Points to the SQLHOSTS file which contains one entry for every accessible Mimer SQL database. Normally this logical name is set to SYS$SPECIFIC:[SYSMGR]SQLHOSTS.DAT. MIMEXAMPLES Points to the examples directory in the Mimer SQL distribution. MIMEXE Points to the directory containing executable programs in the Mimer SQL distribution. MIMLIB Points to the directory containing application libraries, CLD files, etc. MIMODBC Points to the Mimer ODBC shared library. MIMROOT A concealed logical name pointing to the root of the Mimer SQL distribution.
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
http://www.mimer.com/contact.asp?secID=175 or e-mail firstname.lastname@example.org.
Your representative will need to know the node name of the computer on which the Mimer SQL database server will run.
There are three ways of obtaining the node name:
- Use MIMSETUP, for example:$ @disk:[MIMERxxxxx]MIMSETUP
- If the OpenVMS node is part of a cluster, the scsnode parameter describes its name:$ WRITE SYS$OUTPUT F$GETSYI("SCSNODE")
- If the OpenVMS system is not clustered, the node name parameter may be blank. In this case, you should check the SYS$NODE logical name instead:$ SHOW LOG SYS$NODE
Receiving Your Run-time License Key
Your run-time license key and instructions for installing it will be e-mailed or faxed to you.
Usually, license key files are distributed via e-mail. 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
- Assuming that SET COMMAND MIMLIB:MIMER is done, see Setting the Command Style, enter the following:$ mimlicense /FILE=file_name.mcfg
For example, if the license key file you received was named 1234.mcfg, you would enter the following:$ mimlicense /FILE=1234.mcfg
The MIMLICENSE program is controlled by options specified on the command-line.
Adds a license key. Adds a license key from a .mcfg file. Deletes the specified key. Removes all keys. (Each key must be verified.) Lists the contents of the key file. Describes what the combined keys permits. Silent mode, i.e. execution with no output.
The Mimer SQL license keys are stored in the file:SYS$SPECIFIC:[SYSMGR]MIMERKEY.DAT
Removing a Mimer SQL Installation
Caution: If you plan to remove any Mimer SQL databases, see Removing a Mimer SQL Database before removing the Mimer SQL installation.
To remove a Mimer SQL installation:
- Check that no Mimer SQL applications or database servers are using the installation.
- Run the MIMSETUP command procedure to uninstall shared images and deassign logical names:$ disk:[MIMERxxxxx]MIMSETUP -SYSTEM
- Delete the Mimer SQL directory tree, for example:$ SET DEF disk: $ SET PROC/PRIV=BYPASS $ DELETE [.MIMERxxxxx...]*.*.* $ DELETE [.MIMERxxxxx...]*.*.* $ DELETE [.MIMERxxxxx...]*.*.* $ SET PROC/PRIV=NOBYPASS
- Note: You may have to issue the DELETE command more than once, because the DELETE command will not remove directory files unless they are empty.
- If 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.DAT.*
- If 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, remove the commands.
- If 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.
Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40