The MIMBUILD8.COM command procedure is copied to the [MIMAXP7] distribution tree. The procedure will build the V7 modules to the V8 installation that the logical name MIMROOT8 points to.
Please make sure that the correct V8 installation is set up by using the MIMSETUP8.COM command procedure.
$ @disk:[MIMER822A]MIMSETUP8 SYS
$ COPY somewhere:MIMBUILD8.COM disk:[MIMAXP7]
$ SET DEF disk:[MIMAXP7]
Note that the MIMBUILD8 command procedure uses a configuration file named CONFIG.DAT which stores build options. If no such file is found in the V8 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 V8 root directory before running the MIMBUILD8 command procedure:
$ COPY disk:[MIMER7]CONFIG.DAT MIMROOT8:
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 MIMSETUP8 command procedure:
$ @MIMROOT8:MIMSETUP7 SYS
The old V7 components are installed in the V8 environment. All executable modules are relinked with the V8 database libraries. This allows the programs to access the V8 database server directly.
No V7 license key file (MIMKEY7) is needed for the clients. However, a LEVEL2 license must be present on the V8 server. Note that the default license file does not include a LEVEL2 license.
Libraries and option files are created in the MIMLIB8 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 V8 database client library directly.
If the MIMSETUP7 command procedure is used, MIMLIB7 and MIMEXE7 are redefined to MIMLIB8 and MIMEXE8. 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 V8, there is only one database library that is capable of operating in both modes. Normally, aV8 application operates in multi-user mode, but by defining the logical name MIMER_MODE to SINGLE, the application can execute in single-user mode:
$ DEFINE MIMER_MODE SINGLE
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 V8, 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 MIMBUILD8 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 MIMBUILD8 command procedure will create a program with an S suffix, but since there is only one kind of database server library in V8, 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 V8 installation
New V8 distributions come as new directory trees with new top-level names. When you upgrade Mimer V8, it is recommended that you:
1) Install the new directory tree (for instance, [MIMER841…])
2) Copy the old configuration parameter file to the new V8 installation tree
$ COPY [MIMER823]CONFIG.DAT [MIMER841]
3) Set up the new version:
$ @[MIMER823]MIMSETUP8 –SYS ! Deinstall V823
$ @[MIMER841]MIMSETUP8 SYS ! Install V841
4) Rebuild the V7 modules to the new version tree:
$ SET DEF [MIMAXP7]
5) Setup the V7 logical names:
$ @[MIMER841]MIMSETUP7 SYS