|
|
Setting-up the Mimer SQL Environment
Before you can run Mimer SQL (also referred to as MIMER8), 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 MIMSETUP8 command procedure. MIMSETUP8 defines the logical names needed to run Mimer SQL applications.
You can find the MIMSETUP8 command procedure in the Mimer SQL root directory.
Note: When running MIMSETUP8, you may require some of the following privileges: SYSPRV, CMKRNL, SYSNAM, see Privileges for details.
MIMSETUP8 Syntax
The syntax for the MIMSETUP8 command is as follows:
$ @disk:[MIMERxxxxx]MIMSETUP8 [-][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 MIMSETUP8 command procedure will remove the effects of any Mimer SQL setup previously performed for the specified table, including uninstalling shareable images.
Valid Values
Valid values for lnm-table are:
In general, we recommend that you execute MIMSETUP8 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 MIMSETUP8 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 MIMSETUP8 without specifying the lnm-table parameter, a PROCESS level setup is performed by default.
Privileges
In order to run a SYSTEM-wide MIMSETUP8, 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 MIMSETUP8, 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.
$ @disk:[MIMER824A]MIMSETUP8 SYSTEMMIMSETUP8 Examples
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:[MIMER822A]MIMSETUP8 SYSTEMOverriding 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:[MIMER822A]MIMSETUP8Removing a Mimer SQL Setup
The following example demonstrates how to remove a Mimer SQL setup which was previously made GROUP wide by running MIMSETUP8 (MIMROOT8 was defined by MIMSETUP8). Shareable images are uninstalled.
$ @MIMROOT8:[000000]MIMSETUP8 -GROUPLogical Names Defined by MIMSETUP8
The MIMSETUP8 command defines the logical names listed below:
|
Upright Database Technology AB Voice: +46 18 780 92 00 Fax: +46 18 780 92 40 dbtechnology@upright.se |
|
|