...
BACKUP [path] | Creates an archive database backup. If the parameter path is not specified, the backup will be performed into the directory, which is set in the archive configuration. Note: this command is supported for Sybase SQL Anywhere only. To back up Oracle/PostgreSQL/MsSql databases, use their respective utilities. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Executes recalcs of old values, which were redirected to the auxiliary calc task (see the RecalcImmediateDepth archive parameter), and then instead of being performed, they were stored to the file (see the DropOldRequests archive parameter). If path+filename is not specified, the file name_ARCHIV_DROPPED_CALCS.DAT will be processed by name.ARC and then renamed to name_ARCHIV_DROPPED_CALCS.DONE (if such a file exists, it will be deleted). Note: This command fails if the archive parameter DropOldRequests has value 1 because in this case the recalcs would be again stored to the file after being read. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| A command that must be run after the change of DataTableSlices parameter from value 1 to value 2 (i.e. after changing the time slices mode to time slices for structured archives only). The archive will transfer the archived values from time slices of simple archives to the original data tables and these time slices will be deleted. Note: for simple archives, from the start of the archive till the transfer of archived values to the original data tables, the archive will provide only data which are located in original data tables. Therefore this conversion is recommended only for systems with redundant archives and the archive performing conversion should be set as a passive instance. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
CRC path\filename mask from to [step] [PO] | Parameter checks the identity of data in instance archives. Creating the file with a CRC (checking sum) for archive objects that correspond to the mask for the entered time period. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
CRC_TREE path\filename name row col from to [step] | Parameter checks the identity of data in instance archives. Creating the file with CRC (checking sum) for archive objects that correspond to the mask for the entered time period. The calculation will be realized for the object that has been defined by parameter "name row col" and for all objects that influence its value. The optional parameter step (in hours) allows dividing the calculation for the time period into intervals. See the note to the CRC command. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DEL mask [before] | Deletes data from the archive database as follows:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Deletes data from the archive database without activation of dependent statistics evaluation (similar to the action DELETEARCHDATA). Time format is dd-mm-rrrr hh:mi:ss.mss. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DI ON/OFF | Debug Info - shows/hides internal debug information of the D2000 Archiv process (in the process window and in the D2000 Sysconsole process). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Debug Info for values - enables/disables displaying information about the evaluation of historical values with specified HOBJ or with the name matching the given mask. For structured historical values, you can specify the required structure item - column (if ROW=0) or row (if COL=0). Example: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DI ONREC/OFFREC HOBJ/mask [ROW [COL]] | Debug Info for values - recursive. The command extends the functionality of the previous commands with the possibility of showing / hiding the debug information for historical values that depend on specified historical values (e.g. minute averages). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sybase platform: The parameter path+trezor_name specifies the path and the name of the depository database to dismount. The * and ? characters for mask definition can be used in the depository database name. If more files match to entered mask, all these ones will be dismounted. For more information see the topic On-line access to data from depository databases. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DISMOUNT_TREZOR trezor_name [SEGMENT seg] DISMOUNT_TREZOR IdFrom IdTo [SEGMENT seg] | Oracle platform: The parameter Id or trezor_name defines the number (name) of the depository database to dismount. The name of the depository database is the name of the depository tablespace (e.g. MYAPP_TS_TREZOR15 or MYAPP_TS_TREZOR15_02) or the name of the tablespace's datafile (e.g. MYAPP_TS_TREZOR0015_S02_20040801.ORA). You can also dismount all depository databases (except the ones that are currently being filled) by using the parameter all. The parameters IdFrom and IdTo allow dismounting a sequence of depository databases. The parameter SEGMENT seg (where seg is the number of depository database segment) allows dismounting just the segment. Seg is the number between 0 and TrezorCountSegments. If the DISMOUNT_TREZOR command is used without the SEGMENT Seg parameter for depository database with segments enabled, the process D2000 Archiv attempts to dismount all segments of specified depository database/s. For more information see the topic On-line access to data from depository databases. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DISMOUNT_TREZOR IdFrom IdTo [SEGMENT seg] | PostgreSQL platform: The parameter Id defines the number of depository databases to dismount. You can also dismount all depository databases (except the ones that are currently being filled) by using the parameter all. The parameters IdFrom and IdTo allow dismounting a sequence of depository databases. The parameter SEGMENT seg (where seg is the number of depository database segment) allows dismounting just the segment. Seg is the number between 0 and TrezorCountSegments. If the command DISMOUNT_TREZOR is used without the parameter SEGMENT Seg for depository database segments enabled, the process D2000 Archiv attempts to dismount all segments of specified depository database/s. For more information see the topic On-line access to data from depository databases. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DP ON/OFF | Debug Pipe - shows/hides the course of communication with D2000 Server (only if the process window is displayed on the desktop). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Creates the file (defined by the parameter path+filename) containing SQL commands to delete tables, which are not used by the archive configuration. If the time slices are enabled, the file will contain also the commands to delete respective rows of the table ARC_SLICE, which contain information about the time slices corresponding to tables that are to be deleted. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Manual loading of archive cache (only available for isochronous cache mode) by reading values from the archive database. Archive cache loading can be also automatic after startup - for more information see the description of parameter IsoCacheAutoFill. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| For the selected object(s), their ClearTime is set to a value of several hours in the past, which means that a periodic delete of object's data should occur shortly - within a minute (unless it is disabled for some reason, e.g. if the time slices are enabled, it can depend on parameters DeleteInSlice0 and DeleteInSlices). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
UNFREEZE | FREEZE command causes the writing and calculating tasks of the archive stop processing the requests for a period freeze_seconds. Within this time, another task (deleting) will list the number of requests (primary and calculated) in the queues. After the elapsing of the freeze_seconds time, the processing of values will be restored. If the report_seconds parameter is entered, the deleting task continues to list the number of requests in the queues for this period. FREEZE command is primarily used for performance tests (testing the maximum speed for processing the requests under load). Before its use, you should realize that it does not influence reading from the archive, but during its execution, the writing to the archive (so the newest values are not available when reading) and the calculations are not executed for the freeze_seconds period. In redundant systems with 2 and more archives, we recommend executing the FREEZE command on a passive instance, so that the functionality of the archiving subsystem will not be affected. UNFREEZE command (without parameters) is used for aborting inactivity that was caused by the FREEZE command. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The parameter allows showing the list of depository databases used by the process D2000 Archiv. The contents of the list depend on the used platform - Sybase, PostgreSQL, or Oracle. Parameter id:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
LOAD_TREZOR path+filename [mask] [from] [to] | On-line depository database import (Sybase only) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sybase platform: The path+depository_name parameter defines the path and name of the depository database to be mounted. The name may contain "*" and "?" characters to define a mask. If more files match the specified mask, all these will be mounted. For more information see the topic On-line access to data from depository databases. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MOUNT_TREZOR trezor_name [SEGMENT seg] [WRITE] MOUNT_TREZOR IdFrom IdTo [SEGMENT seg] [WRITE] | Oracle platform: The parameter Id (trezor_name) defines the number (name) of a depository database to be mounted. The name of the depository database is the name of depository tablespace (e.g. MYAPP_TS_TREZOR15 or MYAPP_TS_TREZOR15_02) or the name of tablespace's datafile (e.g. MYAPP_TS_TREZOR0015_S02_20040801.ORA). The IdFrom and IdTo parametersallow mounting a sequence of depository databases. The SEGMENT Seg parameter (where Seg is the number of the depository database segment) allows mounting a single depository database segment. If the MOUNT_TREZOR command is used without the SEGMENT Seg parameter for depository database with segments enabled, the process D2000 Archiv attempts to mount on all segments of specified depository database/s. The parameter Write can be used to mount the depository database (s) for writing (for depository database synchronization through the Arcsynchro tool). For more information see the topic On-line access to data from depository databases. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MOUNT_TREZOR IdFrom IdTo [SEGMENT seg] [WRITE] | PostgreSQL platform: The parameter Id specifies the number of a depository database to be mounted. The parameter SEGMENT Seg (where Seg is the number of the depository database segment) allows mounting a single depository database segment. If the MOUNT_TREZOR command is used without the SEGMENT Seg parameter for depository database with segments enabled, the process D2000 Archiv attempts to mount on all segments of specified depository database/s. The parameter Write can be used to mount the depository database (s) for writing (for depository database synchronization through the Arcsynchro tool). For more information see the topic On-line access to data from depository databases. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
OPTIMIZE_QUEUE | Reduction of the number of calc requests in the archive queue. If for some reason, the number of requests in the archive queue has increased (for example, due to the arrival of old values from the communication), this TELL command can reduce duplicate requests. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Creates a file containing the descriptions of pending requests. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Recalculates the values in the statistical archive. Mask - defines the list of objects, which are to be recalculated. If the specific row and/or column of the structured archive is recalculated, it is possible to specify parameters Row and Col (if unspecified, their default value is 0, meaning "whole row/column"). The parameters <From, To> define a time interval to be recalculated. If the end time is not entered, the current time will be used. Time format is dd-mm-yyyy [hh[:mi[:ss[.mss]]]]. Optional parameter BACKGROUND puts the recalculation to the auxiliary calc task (see the archive parameter RecalcImmediateDepth). The parameter is recommended for long-lasting recalculation of historical values that are supposed to be performed in the background while the archive still continues archiving real-time data. Note: If the parameter RecalcTimeIntervalLimit has a non-zero value and the time interval <From, To> is longer than RecalcTimeIntervalLimit hours, the parameter BACKGROUND is mandatory, to ensure that the recalculation will be performed by auxiliary calc. This behavior is implemented as a protection against overloading the main task by recalculations. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Premature disconnection of the current depository database. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The command is used to force the reading of the last values of the specified objects from the archive database. Objects can be specified by name/mask and by type:
If e.g. in the test environment the inserting of values of script-filled archives is not possible, but these are inserted into the archive database by the arcsynchro utility, it is possible to execute this command after the insertion is completed (e.g. RELOAD_VALUES * STATISTIC). Subsequently, a read (e.g. of all script-filled archive objects) is performed and recalculations of archive objects that depend on the read objects can be initiated. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| If the time slices are activated, the command causes the archive to review all time slices of simple archive objects according to the defined HOBJ or mask and to delete the time slices without data. The command is used to clean up the archive database from empty time slices that were created due to the error of the archive. This error was repaired in the supported versions on June 8, 2015. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| On-line reorganization of archive database. The command compacts all archive tables (same as the Oracle command ALTER TABLE MOVE or the Sybase command REORGANIZE TABLE INDEX or the PostgreSQL command VACUUM - see the PG_ReorganizeSlice parameter). Note: For Oracle, PostgreSQL, and Sybase 8.0 (and above) platforms only. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| On-line reorganization of archive table of an object with specified HOBJ or with a name matching the specified mask. If the parameter tablespace is also defined, the given archive table will be moved to the specified tablespace. If time slices are on, all slices of one archive object will be reorganized/moved unless a slice number slice is specified. Note 1: The parameter tablespace can be used on Oracle and PostgreSQL platforms only.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
REORGANIZE ON | Enables the reorganization of the archive database (same as running the process D2000 Archiv with the /DBCY parameter). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
REORGANIZE OFF | Enables the reorganization of the archive database (same as running the process D2000 Archiv without the /DBCY parameter). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
REORGANIZE ACTIVE | Enables the reorganization of the archive database in the active mode only (same as running the process D2000 Archiv with the /DBCA parameter). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
REORGANIZE PASSIVE | Enables the reorganization of the archive database in the passive mode only (same as running the process D2000 Archiv with the /DBCP parameter). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
REORGANIZE SHRINK | Enables the alternate mode of the reorganization of the archive database - only for Oracle 10g and above (dame as running the process D2000 Archiv with the /DBCS parameter). Note: To enable the original mode, use the REORGANIZE MOVE command. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
REORGANIZE TableRowLimit rowLimit | On-line change of the parameter ReorganizeTableRowLimit is used for the automatic reorganization of the archive database. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
REORGANIZE TableTimeLimit timeLimit | On-line change of the parameter ReorganizeTableTimeLimit is used for the automatic reorganization of the archive database. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The command allows the user to change the dynamic cache size to speed up the calculation of statistical historical values while the process D2000 Archiv is still running. Note 1: The initial cache size can be specified by the parameter MaxCacheSize in the process D2000 Application Manager. Note 2: The command SET_CACHE also changes the value of the parameter MaxCacheSize in the registry. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
name_parameter value_parameter | The SET_OPTION command controls the following configuration and start-up parameters of the process D2000 Archiv:
Note: For parameters that are stored in the Registry database the SET_OPTION command will change the value of configuration parameters not only in the archive but also in the Registry database. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Shows dynamic information on the specified object (current value, last sent value, time of next calculation for periodically archived objects, time of periodic deleting, parameters, and content of cache) on the text console of the D2000 Archiv process. Note: The command is mainly intended for D2000 system diagnostic purposes. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| If the archive cache is enabled, the result is a list of top count historical values having the most values in the archive cache. For every value, the following properties are displayed: HOBJ, name, number of items, and time interval of values in the archive cache. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Shows configuration information of the process D2000 Archiv and archive database. This information covers:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Shows various information about the D2000 Archiv process and the archive database. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Creates the file path+filename with statistical information, i.e. number of values for individual historical values from the last n-hours. The path+filename file will be created by the D2000 Archiv process, so its naming is OS-dependent (e.g. D:\stat.txt on Windows, /tmp/stat.txt on Linux). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The command redirects the standard output to a new output. Example: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Deactivates a feature of the process D2000 - import of external data. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
STOP [NOQUEUE] | Stops the process D2000 Archiv. All unsaved values from the request queue are to be automatically stored on the disk and during the next start of the process, the values will be read from the disk. The current values of historical values are to be stored in the table SAVED_LAST_ROWS to quicken the next start of the process. If the NOQUEUE parameter is used, the unsaved values from the request queue will not be stored in the file (it speeds up stopping the process with a large number of unprocessed values). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
TIMESTAT START TIMESTAT RESTART TIMESTAT SHOW TIMESTAT SHOWLONG TIMESTAT SHOWSTART TIMESTAT STOP | Starts (START), stops (STOP), restarts (RESTART), shows (SHOW), shows and restarts (SHOWSTART) or shows the time statistics of reading task(s) in long time format, including the days (SHOWLONG). After starting the statistics, the database reading task(s) will start the measuring time, spent in various parts of the reading procedure. These values can be used for tuning by system specialists. Time statistics are displayed per reading task and if ReadThreadsCount > 1, also totals for all read tasks are shown. Note: When time statistics are on, reading from the archive may be several per cent slower due to time measuring. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PostgreSQL platform: The command is used to compress the data of existing depository databases. See the Depository Data Compression chapter for more information. The Id parameter specifies the number of a depository database whose data is to be compressed. The SEGMENT seg parameter, where seg is the number of the depository database segment (between 0 and TrezorCountSegments), allows you to compress a specific depository segment if depository segment creation is enabled. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PostgreSQL platform: The command is used to decompress the data of existing depository databases. See the Depository Data Compression chapter for more information. The Id parameter specifies the number of a depository database whose data is to be decompressed. The SEGMENT seg parameter, where seg is the number of the depository database segment (between 0 and TrezorCountSegments), allows you to compress a specific depository segment if depository segment creation is enabled. |
...
| Debug Info for values - enables/disables displaying information about the evaluation of:
| ||||||||||||||||||
DP ON/OFF | Debug Pipe - shows/hides the course of communication with the D2000 KOM (only if the process window is displayed on the desktop). | ||||||||||||||||||
GETKOMARCDEPTH | Gets the timestamp of the oldest data stored in the KOM Archive. | ||||||||||||||||||
] "BeginTime" ["EndTime"] | Reads historical values from a device - StationName station. The values from the specified interval will be read. The parameter EndTime is optional and if is not entered, the current time will be used. Time The time format ("BeginTime", "EndTime") is "dd-mm-yyyy hh:mi:ss". This feature is supported only by some communication protocols (Datalogger ESC8800, ESC8816, UNIP_TS ...). Warning: This is not a function of KOM Archiv but it is the reading values directly from a device! NORECALC parameter causes the archive to not execute the calculation of calculated archive objects, the values of which are calculated from the values acquired by this calling of a TELL commandTELL command. For some protocols (OPC DA, OPC HDA, and IEC 870-5-104, IEC 870-5-104 Server, IEC 870-5-104 Sinaut, OPC Data Access 2.05 & 3.0 Client, OPC Historical Data Access Client), a parameter mask "M:" can be used, which is used to read the archive values only for selected I/O tags which match the mask, from the StationName station. | ||||||||||||||||||
| The command allows switching between the primary (OFF or PRIMARY) and backup (ON or BACKUP) devices for lines of categories "SerialOverUDP Device Redundant", "SerialOverUDP Line Redundant", and "SerialOverUDP System&Line Redundant", or discovering the active device (QUERY). The active device is used to write UDP packets and packets received from it are processed. Data received from the inactive device is ignored. Similar functionality is also supported for lines of the "TCP/IP-TCP System Redundant" category - the TCP connection is connected to a primary or backup device. The third parameter (numbers 1-4) specifies the subline. For a line of category the category "SerialOverUDP Device Redundant", it need not be specified or must be equal to 1. For a line of category the category "SerialOverUDP Line Redundant", it can be equal to 1 (the device on the Primary line is set) or 2 (the device on the Secondary line is set). For a "SerialOverUDP System&Line Redundant" or "TCP/IP-TCP System Redundant" category line, it can be equal to 1 - 4 (the device on the Primary/Secondary line of the system A/B is set). If an active device is detected (QUERY) and the third parameter is not entered, all active devices are listed (1, 2, or 4 depending on the line type). The command is also applicable on the OPC UA Client line in the OPC Unified Architecture Data Access Client protocol for Client Type=Default. Using the command, it is possible to find out which of several specified hosts the D2000 KOM process is connected to (QUERY) or to force a connection to a specific one (ON, third parameter set to 1 .. N). The command is also applicable on RFC2217 Client, TCP/IP-TCP, and TCP/IP-TCP Redundant lines. With the help of the command, it is possible to find out which of several specified hosts the D2000 KOM process is connected to (QUERY, or QUERY PRIMARY/BACKUP) or to force a connection to a specific one (PRIMARY/BACKUP, third parameter set to 1 .. N). Examples of use: | ||||||||||||||||||
| The command can be used only for the lines of Serial (asynchronous serial lines) and RFC2217 Client categories. The command stops the communication (CLOSE) and disconnects the communication port. Then the port can be used by other programs, e.g. diagnostic or configuration tools. Stations on the line are to be in the Communication error state. The communication will be recovered either using the command LNSTAT OPEN or after restarting the whole communication process. | ||||||||||||||||||
LNTRACE DEC/HEX | Enables the decimal/hexadecimal format of line listening. The default format is hexadecimal. | ||||||||||||||||||
| Reads the values from KOM Archiv. There are transferred all old values from the specified interval. The parameter BeginTime is optional and if it is not entered, the data from all the whole history depth of KOM Archiv will be read there. The parameter parameter EndTime is optional and if it is not entered, the current time will be used. If the parameters BeginTime and EndTime are not defined, there only the unsent values will be sent just the values, which have not been sent. If at least the parameter parameter BeginTime is defined, there will be sent all values within the specified interval will be sent. Return codes:
| ||||||||||||||||||
| The command de-configures the object (line or station) and its descendants (stations, I/O tags) and reloads them. The command can be used to apply configuration changes that would otherwise require restarting the KOM process. The command is currently implemented for protocols:
| ||||||||||||||||||
| Resets the statistics of a given line/station - the system structured variable SV._System_LinePerformance / SV._System_LinePerformance. It is executed immediately but it will be visible after the process D2000 KOM sends new statistics to the process D2000 Server (periodically every 10 seconds). | ||||||||||||||||||
| Dynamic change of the I/O tag address. The parameter name specifies the I/O tag. It can be entered as the object name (e.g. "M.CoolantTemperature") or the object HOBJ (the syntax requires the character '$' before HOBJ, e.g. "$278"). The parameters address1 and address2 define the new I/O tag address. Change of address will be performed only in internal data structures of the KOM process. It is not sent, in a centralized way, to the server, i.e. changed address is valid until the restart of the KOM process. After this, the value from the initial configuration will be used again. Return codes:
Dynamic change of the I/O tag address is implemented only for a limited group of communication protocols: | ||||||||||||||||||
SETSTADDR StationName|StationHOBJ "address" | Dynamic change of station address. The first parameter specifies the station. It can be entered as the object name StationName (e.g. "B.Station") or station ID StationHOBJ. The "address" parameter defines its new address. Change of station address will be performed only in internal data structures of the KOM process. It is not sent, in a centralized way, to the server, i.e. changed address is valid until the restart of the KOM process. After this, the value from the initial configuration will be used again. Return codes:
Dynamic change of address is implemented only for a limited group of communication protocols: | ||||||||||||||||||
SHOW TAG TagName/TagHOBJ SHOW STATION StationName|StationHOBJ SHOW NAN | Enables debug information for the specified I/O tag/station. The command requires either the name or HOBJ of the I/O tag/station. The debug information is usable for D2000 System developers. The SHOW NAN command displays all I/O tags whose value (current, last telemetry, or last valid) is NaN (unspecified type). | ||||||||||||||||||
SHUTDOWN WINNT | Restarts the computer with the D2000 KOM process (the process must be running). | ||||||||||||||||||
| For the Microtel 700 protocol, it explicitly activates (ON) or deactivates (OFF) an alternative communication route for a station named StationName (e.g., "B.Station"). | ||||||||||||||||||
| Starts a data recording into a subdirectory (application directory) with the name dir_name_only. If the directory does not exist, it will be created. If this TELL command is run from the D2000 Server, firstly, the file dodm_values.dat containing the initialization values of DODM objects is recorded and then the D2000 Server will send this command to clients. Data are recorded within the time period <begin_time, end_time>. If <begin_time> is not set, data are recorded immediately. Example: These four data files (it relates to four hourly intervals) are the result of recording: Note: The TELL command uses "dd-mm-rrrr hh:mm:ss" format for the parameters of DateTime type. | ||||||||||||||||||
| Stops a data recording immediately, it is not necessary to wait for end_time. If the recording is not in progress, an error will be returned. Note: It is possible to start up this TELL command from the D2000 Server, as well as directly from the clients (currently only from the D2000 KOM and Gateway Client processes). | ||||||||||||||||||
| Starts a data replaying from a subdirectory (of application directory) with the name dir_name_only. If the directory does not exist, an error will be returned. If the command is run from the D2000 Server - at first, the dodm_values.dat file containing the initialization values of DODM objects will be recorded by the D2000 Server, and then the D2000 Server will send this command to the clients with /NOW parameter. It replays all data (in data files) with the time stamp >= begin_time. The timestamp of data represents a particular time from the recorded time period. The time of data replaying must be from the range of the recorded time period. Example of data replaying:
Note: This TELL command uses the "dd-mm-rrrr hh:mm:ss" format for the parameters of DateTime type. | ||||||||||||||||||
| Stops a data replaying immediately. If the replaying does not work, the error will occur. Note: There is possible to start up this TELL command from the D2000 Server, as well as directly from the clients (currently only from KOM client). | ||||||||||||||||||
STDOUT output | The command redirects the standard output to a new one. Example: | ||||||||||||||||||
STOP | Stops the D2000 KOM process. | ||||||||||||||||||
STSTAT COMERR/HARDERR StationName | The first form of the command enables the communication (the parameter START) or disables the communication (parameter STOP) with the StationName station. The station will get the StON (START) or StOFF (STOP) value. The second form of the command sets the station's value to a communication error (StComErr or StHardErr). This form can be used for some communication protocols (e.g. KNX protocol, MQTT Client) if there is an external way to detect the outage (e.g. the value of I/O tag serving as a watchdog doesn't come in time). | ||||||||||||||||||
| For protocols based on periodic polling of I/O tags (request-response protocols): the command generates one or several requests for priority reading of all I/O tags on a specified station. The Number parameter defines the number of requests, possible value is within 1...5. If the parameter is not specified, a single request will be generated. For protocols based on sending of changes (change-based protocols): the command generates one or several requests for the reading of all data. The command is implemented for a selected set of communication protocols:
|
...
SHOW_HANDLE [table/database/structure_definition HOBJ] or [table mask] | Shows information on open descriptors. For more information see the chapter DBManager - debugging. |
SHOW_CONNECT [database HOBJ [connect/transaction ID]] or [database mask [connect ID]] [DETAIL] | Shows information on open connections. For more information see the chapter DBManager - debugging. |
SET_WATCHDOG database_mask seconds [NONTRANS] | Switches on the monitoring of connections that perform SQL commands longer than the specified time seconds. This information can be used for the profiling of applications and for the detection of slow SQL commands. If a NONTRANS clause is specified, transactional connections are not monitored. After the long-running SQL is finished, detailed info about it is written to a log file. More information can be found in chapter D2000 DBManager - debugging. |
SET_WATCHDOG_QUEUE database_mask seconds [NONTRANS] | Switches on the monitoring of database actions that take longer to be processed (including waiting in queues of DBManager) than the specified time seconds. After such a database action is finished, detailed info about it is written to a log file. If a NONTRANS clause is specified, transactional connections are not monitored. More information can be found in chapter D2000 DBManager - debugging. |
MONITOR_TRANS SHOW {ALL/<id>} [<file_path>] MONITOR_TRANS ON <history_depth_sec> MONITOR_TRANS OFF MONITOR_TRANS RESET | The mechanism for monitoring of the transactions. Columns in the list: Note: After starting DBManager, the monitoring is switched off. |
MONITOR_CONNECTS SHOW {ALL/<id>} [<file_path>] MONITOR_CONNECTS ON <history_depth_sec> MONITOR_CONNECTS OFF MONITOR_CONNECTS RESET | Monitoring the connections. Columns in the list: Note: After starting DBManager, the monitoring is activated with the time-depth history of closed connections which is 3 hours (10 800 seconds). |
REFRESH_TABLES seconds | The command is intended for use on the PostgreSQL platform. It is used to close and reopen cursors used in page access to tables so they don't block table vacuuming if these cursors are open for too long. Typically, these are schemes with browsers, which are e.g. open for several days. The parameter seconds is the minimum age of the cursor in seconds to be reopened (e.g. 86400). |
TIME_STATISTICS database_mask [DETAIL] | Displays statistics of execution of individual database action types per-database or per-table (if a DETAIL parameter is specified). For more information see the chapter DBManager - debugging. |
REOPEN_CONNECT [database HOBJ [connect ID]] or [database mask [connect ID]] | The command allows you to close and reopen connections to the database that are not currently in use (there is no transaction in progress or a cursor in use). Note: This command was implemented to work with temporary tables in PostgreSQL. These are only dropped when the database connection ends, and while they exist, the data in them is not visible outside the database connection that inserted them, so they cannot be accessed by vacuum, and therefore internal transaction IDs (XIDs) can be exhausted if a connection is open for a long time. |
Kotva | ||||
---|---|---|---|---|
|
...
DI ON/OFF [HOBJ/mask] | Debug Info for alarm objects - enables/disables displaying the information about the evaluation of alarm objects with specified HOBJ or with the name matching the given mask. If neither neither HOBJ nor mask is specified, all alarm objects will be affected. | ||||||
| Shows dynamic information on the specified alarm object(s) on the text console of the process D2000 Alarm. Note: The command is mainly used for D2000 system diagnostic purposes. |
...
SHOW_TOPOLOGY HOBJ or topology_name [DETAIL] | Shows the information about topology. For more information - see Topology - Topology debugging chapter. |
DEBUG_TOPOLOGY HOBJ or topology_mask ON/OFF | Turns on/off writing out detailed information on topology evaluation. For more information - see the chapter Topology - Topology debugging. |
SHOW_ASYMETRIC TERMINALS or TRANSFORMERS [topology_mask] | Lists asymmetric Terminals or Transformers in the topology. For more information - see Topology - Topology debugging chapter. |
Kotva | ||||
---|---|---|---|---|
|
...
Gateway Client
GETOLDVAL remoteObjectMask "BeginTime" ["EndTime"] [NORECALC] GETOLDVAL "remoteTagName[row]^item" "BeginTime" ["EndTime"] [NORECALC] | Reads the values of the remote tag within a specified interval. If the EndTime parameter is not specified, the current time will be used as the default value. The time format ("BeginTime", "EndTime") is "dd-mm-yyyy hh:mi:ss". The command may be used for example after a failure or stoppage of the application, which the D2000 GateWay Client process belongs to. It allows transferring the values from the archive of the remote application to the archive of the application. The only requirement of the value transfer is that the values of corresponding objects have been stored in the archive of the remote application. The first form of the command reads all values transferred by specified remote tags (as well as structured objects). The second form of the command reads all the values of several objects according to the mask. The third form reads the values of a part of the structured object. The parameter item specifies a column of the destination structure (see the Destination structure parameter in the configuration of the remote tag) and it must be specified within quotes. When a single row (column) needs to be read, use the following:
The TELL command must always be executed in the transaction mode - the COMMAND action (within the D2000 System Console process, the command is automatically executed in the transaction mode). After the command is executed, the values that were transferred will be stored in the archive and the D2000 Archive automatically recalculates corresponding statistics. The NORECALC parameter can be set at the end of the GETOLDVAL. In this case, the statistic calculations will not be executed by the D2000 Archiv process. | ||||||
DI ON/OFF [HOBJ/mask] | Debug Info for remote objects - enables/disables displaying the information about processing the values of objects with specified HOBJ or with the name matching the given mask. Note:if the gateway client is run in a transparent gateway mode, use the TRGTW command to display debug information. | ||||||
| Shows dynamic information on the specified remote object(s) on the text console of the process D2000 Gateway. Note: The command is mainly used for D2000 system diagnostic purposes. | ||||||
TRGTW | Debug command for transparent gateway mode. The command lists the names of objects and their HOBJ on the local and remote systems. | ||||||
START_RECORD dir_name_only [begin_time] end_time | Starts recording of values read from theGateWay Server. For details see the command description for the D2000 KOM process. Note: Replaying of recorded values by the D2000 KOM process is possible if the GateWay Client was running in a transparent gateway mode during the recording. | ||||||
STOP_RECORD | Instantly stops recording of values read from the GateWay Server. For details see the command description for the D2000 KOM process. | ||||||
START_REPLAY dir_name_only [begin_time [/NOW]] or START_REPLAY dir_name_only /LOOP | Starts replaying of data recorded by command START_RECORD. For details see the command description for the D2000 KOM process. | ||||||
STOP_REPLAY | Instantly stops the replaying of data. For details see the command description for the D2000 KOM process. |
...