With this command you can display the version information of Database Manager. By specifying options, you can determine to which DBM server the DBM client should connect. And you can limit the version information displayed.
Since the version of the DBM server and therefore the Database Manager program are always the same as the version of the database software, you can also determine the version of the database software in this way.
You do not need to log on to Database Manager to execute this DBM command.
Nor do you require any server permission.
dbm_version [<option>]
<option> :: = -s | <version> | <build> | <os> | <instroot> | <logon> | <code> | <swap> | <unicode> | <instance> | <sysname> | <masking> | <replytreatment>
Option |
Description |
---|---|
Forces the DBMCLI client to connect to the DBM server of this installation. If you do not specify the -s option, the DBMCLI client connects to the DBM server of the highest available server installation on this computer. The information displayed then refers to this DBM server. |
|
<version> |
Version number of Database Manager |
<build> |
Identification number of Database Manager |
<os> |
Name of the operating system |
<instroot> |
Installation directory of the version-dependent database software, can only be determined by the system if you are connected to a database |
<logon> |
Indication whether an operating system logon has taken place |
<code> |
Character set used in Database Manager |
<swap> |
Swap type used in Database Manager |
<unicode> |
Query whether the Unicode character set is used by the database catalog |
<instance> |
Database type |
<sysname> |
Name of the operating system |
<masking> |
Queries whether the masking of special characters within a DBM command is supported |
<replytreatment> |
List of treatments applied to the current reply package |
OK
VERSION = <version_number>
BUILD = <build_number>
OS = <os>
INSTROOT = <dependent_path>
LOGON = <TRUE|FALSE>
CODE = <ASCII|UTF8>
SWAP = <swap>
UNICODE = (YES|NO)
INSTANCE = (OLTP|LVC|unknown)
MASKING =
REPLYTREATMENT =
Value |
Description |
---|---|
VERSION = <version> |
Version number of Database Manager |
BUILD = <build_number> |
Identification number of Database Manager |
<os> |
Name of the platform |
INSTROOT = <dependent_path> |
Installation directory of the version-dependent software |
LOGON = <TRUE|FALSE> |
Indication whether an operating system logon has taken place TRUE: Logged on FALSE: Not logged on |
CODE = <ASCII|UTF8> |
Character set used in Database Manager |
SWAP = <NO|FULL|HALF> |
Swap type used in Database Manager (internal representation of numeric values) NO: hihi-hilo-lohi-lolo FULL: lolo-lohi-hilo-hihi HALF: lohi-lolo-hihi-hilo |
UNICODE = <YES | NO> |
Character set used by the database catalog YES: UNICODE NO: ASCII |
INSTANCE = <OLTP|LVC|UNKNOWN> |
Database type OLTP: SAP MaxDB LVC: SAP liveCache Technology unknown: The database type cannot be determined. |
SYSNAME = <os> |
Name of the operating system |
MASKING |
Masking of special characters within a DBM command Possible values are: YES | NO YES: Masking is supported NO: Masking is not supported |
REPLYTREATMENT |
Comma-separated list of treatments, which are applied to the current reply package |
In the event of errors, see Reply Format.
Call Database Manager CLI, log on as the operator OLEG with the password MONDAY, connect to the database DEMODB, and display the version information of Database Manager:
>dbmcli -u dbadmin,secret -d demodb dbm_version
OK
VERSION = 7.7.06
BUILD = DBMServer 7.7.06 Build 001-113-186-093
OS = WIN32
INSTROOT = C:\Program Files\sdb\Demodb
LOGON = True
CODE = UTF8
SWAP = full
UNICODE = YES
INSTANCE = OLTP
SYSNAME = Windows XP
MASKING = YES
REPLYTREATMENT = none,zlib,auto
Glossary, Version