With this command you can open the database parameter history and transfer the first block of the contents. The entries are displayed in reverse chronological order, that is, starting with the most recent and ending with the oldest entries.
You can restrict the parameters displayed by specifying options. If you enter several selection criteria, only the data for those parameters that correspond to all the criteria is displayed. You can also define which data should be displayed for the parameters selected.
Each parameter is displayed on a separate line with the details for all fields defined.
If the entries for the parameter history cannot be transferred in full, due to the limited size of the reply packet, you can display the remaining contents using param_gethistorynext.
You have the server permission ParamRead.
param_gethistory [NAME=<parameter_name>] [DATE=<yyyymmdd>] [GROUP=<group_list>] [STATE=<status_list>] [FIELDS=<field_list>]
<group_list>:: = <parameter_group>,<parameter_group>,...
<status_list>:: = <status>,<status>...
<field_list>:: = <field>,<field>,...
<field>:: = DATE | TIME | NAME | OLDVALUE | NEWVALUE | STATE | GROUP | COMMENT
Option |
Description |
---|---|
<parameter_name> |
Name of the database parameter If you do not specify a parameter name, the entries for all parameters in the history are displayed. |
<yyyymmdd> |
Date format (year, month, day) Only parameter changes since this date are displayed. If you do not specify a date, all entries in the history are displayed. |
<parameter_group> |
Parameter group Changes to database parameters, which belong to this group, are displayed. Possible values are: GENERAL | EXTENDED | SUPPORT GENERAL: general database parameters EXTENDED: special database parameters SUPPORT: support database parameters If you do not specify a parameter group, the parameter changes for all groups will be output. See also: Database Administration, Database Parameters |
<status> |
Database parameter status Possible values are: a | c | d a: active database parameters c: changed database parameters d: deleted database parameters If you do not specify a state, all parameter changes will be output. |
<field> |
Name of the field in the parameter history to be displayed You can display the following fields: DATE : date when the parameter was changed TIME: time when the parameter was changed NAME: parameter name NEWVALUE: new parameter value OLDVALUE: old parameter value STATE: the change status of the parameter GROUP: group to which the parameter is assigned COMMENT: comment, which you can enter when changing a parameter, or which is created by the system If you do not specify a field, all fields will be displayed. |
<hhmmss> |
Time format (hours, minutes, seconds) Only parameter changes since this time are displayed If you do not specify a time, all entries in the history are displayed. |
OK
<header_line>
<param_line>
<param_line>
...
Value |
Description |
---|---|
<header_line> |
Contains the names of the fields displayed. S stands for the STATUS of the data base parameter |
<param_line> |
Contains the values for the fields displayed in the <header_line>, the values are in the same column position as the field name in the <header_line>. Possible statuses are: a | c | d a: Active database parameter c: Changed database parameter d: Deleted database parameter |
Call Database Manager CLI in session mode, log on as the operator OLEG with the password MONDAY, connect to the database DEMODB:
>dbmcli –u OLEG,MONDAY –d DEMODB
dbmcli on DEMODB>
Display the parameter history for the parameter MaxDataVolumes:
dbmcli on DEMODB>param_gethistory NAME=MaxDataVolumes
OK
DATE TIME NAME NEWVALUE OLDVALUE S GROUP
20050503 00134126 MaxDataVolumes 32 64 A GENERAL
20050317 00141019 MaxDataVolumes 64 1 C GENERAL
20050317 00141013 MaxDataVolumes 1 C GENERAL
Display all changes to the database parameter MaxUserTasks with date, time and status:
dbmcli on DEMODB>param_gethistory NAME=MaxUserTasks FIELDS=DATE,TIME,STATE
OK
DATE TIME S
220050503 00105843 A
0050317 00141019 C
20050317 00141013 C
Database Administration, Log Files