Checking Version Numbers
Middleware Client and Servers
The middleware products use shared libraries or ActiveX
depending on the product and operating system. One example
would be the file "3kodbc.dll" is the shared library used
by ODBC connections to Turbo Image and Eloquence on Windows.
On Unix systems this file would appear as "lib3kodbc.so".
The servers for the middleware products use executable
applications as appropriate for the operating system. On
Windows these files would be named in the case of ODBC "odbcsrvr.exe".
On Unix systems, they use the same format "odbcsrvr.exe".
|HP3000 - MPEiX
Use the VERSION system command as shown below. The version
number is found on the second line after SOM #1. This line
will begin with the (unmodified) application file name.
In the sample, this is "SERVER version 220.127.116.11".
VERSION C.70.00 Copyright (C) Hewlett-Packard 1987. All Rights Reserved.
@(#) HP30315 A.05.11 98/07/15 NRT0 Startup routine
SERVER - 18.104.22.168
TRACE - 22.214.171.124
NIF - 126.96.36.199
MAX STACK SIZE: 393216
MAX HEAP SIZE: 81920000
UNSAT PROC NAME:
LIBRARY SEARCH LIST:
If you are using a unsupported version, it may not report
the version number this way. You will need to use the commands
:SETVAR MSTRACE 7
(103634) SERVER-99: TRACE: Trace level = 7
(103634) SERVER-99: MiddleMan Listener, version 188.8.131.52,
(103634) SERVER-99: (c) Copyright, 1994 - 2007, Minisoft, Inc.
The version number is part of the delivered file name.
The supported installation procedures call for creating
symbolic links to standard (not version specific) names.
For example, the 184.108.40.206 Build 5 version of the ODBC server
for HPUX on an Itanium will have the file name "odbcsrvr.exe.22715-ia64-ELF32".
There will be a symbolic link to the file from "odbcsrvr.exe".
When requested by Minisoft support, please report the complete
Check the file properties of the driver dll or server
exe file. The version tab will contain the information needed.