Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Kotva
audit_info
audit_info
AUDIT_INFO [REINIT [USER|RESGROUP]]
The command without parameters writes out the status of monitoring or storing of auditing information (see also Object Group - monitoring changes in configuration).
Parameter REINIT USERS causes the writing of the current configuration of all objects of *User* type into the monitoring database.
Parameter REINIT RES_GROUP causes the writing of the current configuration of necessary objects of *Object group* type into the monitoring database.
In any object type is not stated in the command, both types of objects will be written into the monitoring database.
BACKUP SYSCFG pathCreates a configuration database backup in a directory specified by the path parameter (Sybase SQL Anywhere and PostgreSQL platforms).
Note: The backup can be influenced by the setting of ConfigBackUpTimeout parameter.
BACKUP LOGFILE pathCreates a log database backup in the directory specified by the path parameter (Sybase SQL Anywhere and PostgreSQL platforms). 
CFGSYNCHROAUTO ON/OFFEnables/disables the automatic synchronization of configuration databases after a new SBS (standby server) is connected.

Note 1: The command can be applied to the HOT server only.
Note 2: The synchronization can be influenced by the setting of the parameter ConfigSynchroTimeout.
CHECK_ARCHIVEChecks a value type consistency between the primary archive object and the archive one and shows the errors (writes it into the log). The error is if the value type of the primary archive object is different from the value type of historical value.
Kotva
deploy_java_shared
deploy_java_shared
DEPLOY_JAVA_SHARED

If some files - the external and user libraries for Java, placed in directory %lt;appldirgt;/java/shared are changed, the D2000 Server will send these files to all running clients.

DI ON/OFF

DI /E+dbginfo

DI /E-dbginfo

Debug Info - shows (DI ON)/ hides (DI OFF) internal debug information of D2000 Server (in the process window and in the process D2000 Sysconsole).

The command allows show/hide viewing debug information by category as the SysConsole user interface allows.

Example 1: Show debug information

DI /E+DBG.CFG_RQ

Example 2: Hide debug information

DI /E-DBG.CFG_RQ

DP ON/OFFDebug Pipe - enables/disables the displaying of the communication of the D2000 Server with client processes (only if the D2000 Server's window is displayed on the desktop).
INSTANCE SET|GET ACTIVE|PREFERRED|USABLE ...

It is used to determine and set the active instance, preferred instance, and instance mode in a load-balancing mode.

INSTANCE GET PREFERRED process_nameShows the number of the preferred process instance.
Kotva
set_pref_inst
set_pref_inst
INSTANCE SET PREFERRED process_name instance_number

Sets a preferred process instance.
It is used to set the preferred archive if the archives run as an instance (for more information see the chapter Redundant archiving). By default, the instance with a minimal number is active.
This parameter can be used also for setting up the D2000 KOM process (for more information see the chapter Redundancy of communication process KOM).

The command writes the number of the preferred instance into the system registers:

HKEY_LOCAL_MACHINE\Software\Ipesoft\D2000V70\cfg_Meno_Aplikacie\Kernel\SELF.ARC_PreferredActiveInstance

Warning: If the preferred value is 0, the process instances are not switched actively while the terminated active instance is started. I.e. when some active instance is finished, other another existing instance will be a new active instance. If there are more process instances, the active one will be that with the minimum instance number. This process instance remains active even if another one is started (it had to be active before termination).

Incorrect termination of the active and preferred instances may change the preferred process instance. If the active instance crashes while another instance is operating, it becomes a new preferred active instance (with the minimum number).

INSTANCE GET ACTIVE process_nameEnables to display the number of the active process instance.
Kotva
set_act_inst
set_act_inst
INSTANCE SET ACTIVE process_name instance_number

Sets the active instance of a given process.
The parameter is used for setting up the active instance of the archive process if all the instances are running as instances (for more information see the chapter Redundant archiving). By default, the instance with a minimal instance number is active.
This parameter can be used also for setting up the D2000 KOM process (for more information see the chapter Redundancy of communication process KOM).

The command switches the active instance of the process.

INSTANCE GET USABLE process_name instance_numberEnables to display '1' if a process of a given instance is active in load-balancing mode. If not, then '0'.
Kotva
set_inst_usable
set_inst_usable
INSTANCE SET USABLE process_name instance_number 1|0
Sets the instance of the process as active or passive in Load balancing mode (see the chapter Redundant archiving - Load balancing).


MESSAGE Message_Text process_nameBroadcasts (sends) a text message to client processes. The process name can be entered as a mask (e.g. *.HIP - for all processes D2000 HI). If the return code is Success, it contains the number of clients, the message from the D2000 Server was sent to.
LIC_PostponeLicWrnToUsers
0 až 240 [hod], default 24
Delay of license warnings for common users. The administrators of D2000 will get the license warning always and immediately.
LIC_DoNotAllowConsoleOverLimit
0|1, default 0
When setting 1, the system will not allow connecting consoles (HI) over the scope of the license.
LIC_DoNotAllowSysProcOverLimit
0|1, default 0
When setting 1, the system will not allow the system processes (CALC, EVENT, KOM,...) over the scope of the license.
RD_SET_HOT serverNameSets the HOT server in the redundant system. The parameter serverName is the name of the server within the redundant group.
Kotva
refresh_licence
refresh_licence
REFRESH_LICENCE
On-line refresh of the information about the license range (from file LicenceRun.code or LicenceDev.code) and information about the network clients (from file ConsolesInfo.txt). It enables changing the license range without any need to stop the system - as well as re-reading the list of network clients after it has been manually edited.

Note 1: In redundant systems, it is necessary to replace the files LicenceRun.code or LicenceDev.code on all redundant servers.
Note 2: In redundant systems, it is necessary to modify the file ConsolesInfo.txt only on the active (HOT) server. The changes will be transferred to all SBS servers.
Note 3:
The information about the license is sent to the client processes when connecting to D2000 Server. For that reason, if the change of license affects even other processes than D2000 Server, they must be restarted. For example, when a user adds a new communication protocol, it influences the D2000 CNF process. To enable this protocol in D2000 CNF, it must be restarted. Also, when adding a new communication station and I/O tags with the given protocol to the D2000 KOM process, it must be restarted.
RELOAD_PARAMSReloads all parameters for D2000 Server (except the parameters for saving the monitoring database to the depository) from the registry (Windows) or from the configuration file (Linux) without restarting the D2000 system.
RELOAD_SECURITYSets the new configuration of Security Policy without restarting the D2000 System.
REPAIR_ARCHIVEChecks the consistency of value type between the object being archived and the historical value. If some error occurs, it will be repaired immediately and information will be written into the log. The error is if the value type of the object being archived is different from the value type of historical value.

Kotva
repository
repository
REPOSITORY INIT [path]

Initialize the path to the repository. If the directory does not exist, a new one will be created. If there is a repository on a given path, this one will be used for storing object history. History capturing must be disabled.

REPOSITORY DISCONNECT

Remove setup path to the repository. History capturing must be disabled.

REPOSITORY ON|OFF

Enable/disable history capturing. A path to the repository must be set. 

RESTART process_nameStops the given process and then starts it correctly.

Note: If the process is stopped (Stop or Crash status), the command just starts it.

Kotva
set_load_bal_mode
set_load_bal_mode
SET_LOAD_BAL_MODE
process_name mode
Activates/deactivates Load balancing mode (see the chapter Redundant archiving - Load balancing).

Example:
SET_LOAD_BAL_MODE SELF.ARC 1 - activates Load balancing mode for SELF.ARC process.
Kotva
show_access_list
show_access_list
SHOW_ACCESS_LIST

The command writes the list of the names registered by the GETACCESS action within the application (with the keyword PUBLIC) into the text console and to the log file (kernel.log) of the D2000 Server process.
The list contains the owner of the registered name as follows:
computer_name;process_name;event_name/activepicture_name

Example:
ACCESS LIST BEGIN
GETACCESS : "RegisteredName" is locked by : ComputerName;SELF.EVH;E.EventName
GETACCESS : "RegisteredName2" is locked by : ComputerName;ComputerName.HIP;S.PictureName
ACCESS LIST END

SHOW_ARC_STAT
process_name
Shows the statistical information about the running instances of the archive - the maximum number and sum of the read requests that are being processed.
Kotva
show_config
show_config
SHOW_CONFIG
Shows configuration information of the process D2000 Server.
This information covers:
  • start parameters of process D2000 Server,
  • configuration parameters of D2000 system installation common for all applications,
  • parameters of process D2000 Server specified in Windows registry (specific for running application),
  • in redundant systems parameters of redundancy specified in Windows registry (specific for running application),
  • parameters specific for ODBC and OCI versions of process D2000 Server.
  • detailed information on the number and structure of the tags
    For Structured Variables: Object Name; the number of tags; the number of tags according to the methodology into the version D2000 V11
    ;D2RECORD;SV.DaE_Export_Head; 0; 11
    For Structured Eval Tags: Object Name; the number of tags;
    ;CLC_VAL Struct;P.TASK_SUM_Pending; 13

    Summary information on the contribution to the total number of tags for each object types:
    Number of tags for structured variables from V11 and to V11
    ;D2RECORD;Summary V11+; 9126
    ;D2RECORD;Summary OLD; 49044

    Number of tags for structured eval tags
    ;CLC_VAL Struct;Summary; 314

    Number of tags for eval variables
    ;CLC_VAL;; 98
    Number of tags for I/O tags
    ;POINT;; 25
    Number of tags for user variables
    ;USER_VAR;; 2095
    Number of tags for remote objects
    ;REM_OBJ;; 2
    The total number of application tags
    ;TOTAL TAGS;; 11510

Note: By comparing the information, obtained by this TELL command, it is possible to find out whether D2000 Server processes in a redundant group are configured identically, resp. if any parameter was omitted during the migration of the application server.
Kotva
show_dyn_info
show_dyn_info
SHOW_DYN_INFO object_name or HOBJ

Shows dynamic information on the specified object (list of objects that dynamically or statically use the object) on the text console of the D2000 Server process.

Note:
The command is intended to be used mainly for D2000 system diagnostic purposes.

SHOW_DYNO_LIST idFirst idLastThe command dumps the list of current dynamic objects (ID and object name) to the text console of the process based on the defined interval.

Note: The command is mainly intended for diagnostic purposes.
SHOW_TRANS_LISTLists internal transactions of the D2000 system.

Note: The command is intended to be used mainly for D2000 System diagnostic purposes.

SHUTDOWN D2000Stops the D2000 system.
SHUTDOWN RESTARTStops the D2000 system and restarts the operating system.
SHUTDOWN SHUTDOWNStop the D2000 system and shutdowns the operating system.
SHUTDOWN WINNTStops D2000 System and restarts the operating system.
START process_nameStarts the specified process.
STDOUT outputThe command redirects the standard output to a new output specified by output.

Example:
D2000 on OpenVMS platform: STDOUT "_TNA2:" (output is redirected to the terminal _TNA2:)
D2000 on Windows platform: STDOUT C:\output.txt (output is redirected to the file output.txt)

Note: If a D2000 process is run on the Windows platform as a service, the console output is disabled.

STOP process_name [FORCE]It stops a process. When using the optional parameter FORCE, the termination of the process will be forced.
*SUSPEND* SLEEP [WAKEUP yyyy-mm-ddThh:mi:ssZ]|HIBERNATEIt causes the operating system to switch into sleep mode (SLEEP) or hibernation (HIBERNATE). If the OS switches into sleep mode, the user may define a time of its automatic awakening by the parameter WAKEUP yyyy-mm-ddThh:mi:ssZ, where yyyy-mm-ddThh:mi:ssZ defines UTC time of awakening. The string must be in ISO 8601 format (http://sk.wikipedia.org/wiki/ISO_8601).

Example: *SUSPEND SLEEP WAKEUP 2015-02-11T12:00Z* - causes putting the computer to sleep and automatic awakening at noon, February 11th, 2015 (UTC).
Kotva
tcp_no_delay
tcp_no_delay
TCP_NO_DELAY process_name|process_mask [FALSE|TRUE|QUERY]
It enables, disables, or queries the delay of data transfer between the D2000 Server process and the client connected via TCP/IP protocol. Setting the parameter TCP_NO_DELAY to TRUE disables TCP delay before sending TCP packets (setsockopt function with parameter TCP_NODELAY - see Nagle's algorithm). The delay improves the efficiency of TCP/IP networks by reducing the number of packets that need to be sent over the network. On the other hand, if the communicating partners wait for each other's response (e.g. remote procedure calls between two EVENT processes or between HI and EVENT), this delay can significantly slow down the execution of scripts and other interactions.
By default, TCP delay is on (TCP_NO_DELAY = FALSE).
This TELL command is intended only for tuning and debugging purposes.

Note 1: When registering a TCP/IP client, the process D2000 Server queries the value of parameter TCP_NO_DELAY, and, depending on this value, it does or does not change the parameter TCP_NO_DELAY for client connection. This value is then sent to the client, which also changes the TCP_NODELAY parameter of its TCP connection to the server.
Warning: In the current implementation, the TCP_NO_DELAY command does not cause any change in the setting on the client's side!
Note 2: Besides the TCP_NO_DELAY parameter, there is also another parameter that influences sending TCP delayed acknowledgments (it can be set on OpenVMS and *nix system by calling sysconfig -r inet tcpnodelack). This parameter induces a 200 ms delay before sending TCP acknowledgments and it can interact with the TCP_NODELAY parameter.
Kotva
xml_export0
xml_export0
XML_EXPORT
Warning: Since the version V8.00.001, the command is not supported.

XML file(s) export from the directory, which is defined by the parameter path, together with the following parameters:

  • Path –  defines the directory where the objects will be exported; required parameter.
    It must contain the complete path, e.g. c:\XML. The path must exist. If it does not exist, the export is not allowed.
    Instead of a fixed path, the user can select the default directory - by entering the value "*" into the parameter.
    The default directory is placed in "[APP_DIR]\XML_EXPORT", where APP_DIR defines the application directory, e.g. c:\D2000\D2000.APP\application_name\XML_EXPORT" ".
  • Mask – defines the mask, which corresponds to the list of objects that are to be exported; the required parameter.
  • optional settings of XML_SETTINGS

The path for the file export on VMS must be written in Unix format.

Correct syntax: /DKB0/d2000/d2000-app/RIS_ROVE/XML/ mask
Incorrect syntax: DKB0:[d2000.d2000-app.RIS_ROVE.XML] mask - this syntax is not supported, export ends with an error.

Kotva
xml_export_table
xml_export_table
XML_EXPORT_TABLE 
The configuration parts export to the XML files, which is not part of the object configuration.
The parameters: [Path, FileName, TableName].
  • Path - defines the path for saving the configuration.
  • FileName - defines the name of the output file. E.g. for the "systemtxt" file, a file with the name "systemtxt.xml" is created.
  • TableName - defines the table of the database, from which the configuration is to be exported.
    TableName can acquire the following values: SYS_COLORS, SYSTEM_TEXT, TRANS_MASKA, DICTIONARY, LANGUAGES, LOGDEF, NAME_RULES.

Warning: Extension ".xml" is added automatically, do not explicitly specify it.

Kotva
xml_import0
xml_import0
XML_IMPORT
Warning: This command is not supported for OpenVMS.

XML file(s) import of a specific file or of all XML files from specified directory, depending on path_to_dir / path_to_file parameter:

path_to_dir - directory name with XML files (eg D:\temp). Note - the directory is searched for xml files recursively.

path_to_file - absolute path to the XML file (eg D:\temp\H.Sec.xml)

For this TELL command to be executed, a configuration key must be present!.

The path for the file import on VMS should be entered in Unix format.
Correct syntax: /DKB0/d2000/d2000-app/RIS_ROVE/XML/
Incorrect syntax: DKB0:[d2000.d2000-app.RIS_ROVE.XML] - this syntax is not supported, import of directory containing XML files ends with an error

The import of one file supports both records:
Correct syntax: /DKB0/d2000/d2000-app/RIS_ROVE/XML/file.xml
Correct syntax: DKB0:[d2000.d2000-app.RIS_ROVE.XML]file.xml

Note: The command belongs to the "security" TELL commands. I.e., it can be activated only from interactive processes with configuration key or from process D2000 Event Handler.

Kotva
xml_import_table
xml_import_table
XML_IMPORT_TABLE
Import of the configuration parts that are not part of the object configuration from XML files.
The parameter [Path, FileName, TableName[, CleanTable]]
  • Path - defines the path from which the configuration will be read.
  • FileName - defines the name of the input file without XML extension. For example, "systemtxt" for the file with the name "systemtxt.xml".
  • TableName - defines the table of the database to which the configuration is to be imported.
    TableName can acquire the following values: SYS_COLORS, SYSTEM_TEXT, TRANS_MASKA, DICTIONARY, LANGUAGES, LOGDEF, NAME_RULES.
  • CleanTable - defines whether the table in the database will be cleaned before import.
    This parameter is optional, the default value is FALSE.
    The parameter can acquire two values: TRUE - clean table, FALSE - the table is updated.

The initialization of the TELL command is conditioned by using the configuration key.

Note: The command belongs to the "security" TELL commands. I.e., it can be activated only from interactive processes with configuration key or from process D2000 Event Handler.

Kotva
xml_settings
xml_settings
XML_SETTINGS
Warning: Since the version V8.00.001, the command is not supported.

Sets the parameters for XML_IMPORT and XML_EXPORT commands.

The command without parameter displays the default parameters of the D2000 Server.

Kotva
xml_update
xml_update
XML_Update
Partial update of the objects by XML from the directory, which is defined by parameter Path.
The parameter:
[path_to_dir / path_to_file]

Note: The command belongs to the "security" TELL commands. I.e., it can be activated only from interactive processes with configuration key or from process D2000 Event Handler.

...

Kotva
kom_di
kom_di
DI ON/OFF HOBJ/mask

Debug Info for values - enables/disables displaying information about the evaluation of:
  • I/O tag with specified HOBJ,
  • all I/O tags on the station with specified HOBJ,
  • I/O tags with the name matching the given mask,
  • all I/O tags on the stations with the names matching the given mask.
DP ON/OFFDebug Pipe - shows/hides the course of communication with D2000 KOM (only if the process window is displayed on the desktop).
GETKOMARCDEPTHGets the timestamp of the oldest data stored in the KOM Archive.
Kotva
getoldval
getoldval
GETOLDVAL StationName [M:PointMask] [NORECALC] "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 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 command. For some protocols (OPC DA, OPC HDA, and IEC 870-5-104), 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.

Kotva
lnalterpath
lnalterpath
LNALTERPATH LineName ON|OFF [1|2|3|4]

The command allows switching between the primary (OFF) and backup (ON) devices for the "SerialOverUDP Device Redundant", "SerialOverUDP Line Redundant" and "SerialOverUDP System&Line Redundant" line categories. The active device is used to write UDP packets and packets received from it are processed. Data received from the inactive device is ignored.

The third parameter (numbers 1-4) specifies the subline. For a line of category "SerialOverUDP Device Redundant", it need not be specified or can be equal to 1. For a line of 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" category line, it can be equal to 1 - 4 (the device on the Primary/Secondary line of the system A/B is set).

Example of use: LNALTERPATH L.MyLine ON 3

Kotva
lnstat
lnstat
LNSTAT OPEN/CLOSE LineName

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/HEXEnables the decimal/hexadecimal format of line listening. The default format is hexadecimal.
READKOMARC ["BeginTime"] ["EndTime"]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 history depth of KOM Archiv will be read there. The 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 will be sent just the values, which have not been sent. If at least the parameter BeginTime is defined, there will be sent all values within the specified interval.

Return codes:

  • SUCCESS - transaction successful, data transfer to the system finished,
  • IGNORED - the process D2000 KOM is not running in the mode of KOM Archiv,
  • ERROR - invalid parameters (time format: dd-mm-yyyy hh:mi:ss), wrong sequence of entered times - BeginTime > EndTime.

Kotva
reload
reload
RELOAD StationName | StationHOBJ | LineName | LineHOBJ

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:

Kotva
resetperf
resetperf
RESETPERF LineName/StationName

Resets the statistics of 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).

Kotva
setptaddr
setptaddr
SETPTADDR name "address1" "address2"

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:

  • SUCCESS - changed address (the value of the I/O tag is invalid until it is read from the new address).
  • IGNORED - D2000 KOM process does not support dynamic address change for the specified protocol.
  • ERROR
    1. duplicate address
    2. point not found
    3. bad address format

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:

  • SUCCESS - changed address,
  • IGNORED - D2000 KOM does not support a dynamic change of address for the specified protocol,
  • ERROR
    1. object not found
    2. invalid number of parameters

Dynamic change of address is implemented only for a limited group of communication protocols:

SHOW TAG TagName/TagHOBJ
SHOW NAN
Enables debug information for the specified I/O tag. The command requires either the name or HOBJ of the I/O tag. 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 WINNTRestarts the computer with the D2000 KOM process (the process must be running).

Kotva
stalterpath
stalterpath
STALTERPATH StationName ON|OFF

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").

Kotva
start_record
start_record
START_RECORD dir_name_only [begin_time] end_time

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:
Data files, recorded by the TELL command:
START_RECORD DirName "01-12-2008 08:22:27" "01-12-2008 11:02:07"

These four data files (it relates to four hourly intervals) are the result of recording:
KOM-SELF_2008_12_01_08.dat < 01-12-2008 08:22:27 ; 01-12-2008 09:00:00 >
KOM-SELF_2008_12_01_09.dat < 01-12-2008 09:00:00 ; 01-12-2008 10:00:00 >
KOM-SELF_2008_12_01_10.dat < 01-12-2008 10:00:00 ; 01-12-2008 11:00:00 >
KOM-SELF_2008_12_01_11.dat < 01-12-2008 11:00:00 ; 01-12-2008 11:02:07 >

Note: The TELL command uses "dd-mm-rrrr hh:mm:ss" format for the parameters of DateTime type.
It is possible to initialize this TELL command from the D2000 Server, as well as directly from the clients (currently only from the D2000 KOM and Gateway Client processes).
Data are recorded into the specified subdirectory in the application directory, where a separate data file is created for every hourly time period.

Kotva
stop_record
stop_record
STOP_RECORD

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).

Kotva
start_replay
start_replay
START_REPLAY dir_name_only [begin_time [/NOW]]
or
START_REPLAY dir_name_only /LOOP

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:
Time Stamp (TS) - blue color, current time (CT) - red color

begin_time/NOWDescription
nono
  • data are replayed immediately
  • if CT = 02-12-2008 14:11:02, data are replayed from TS >= 01-12-2008 09:11:02
  • if CT = 02-12-2008 14:33:55, data are replayed from TS >= 01-12-2008 08:33:55
yesno
  • if begin_time = 01-12-2008 08:27:27, data are replayed from time so that this time corresponds with a shift from hour
  • if CT = 02-12-2008 14:11:02, data are replayed from TS >= 01-12-2008 08:27:27, when CT = 02-12-2008 14:27:27
  • if CT = 02-12-2008 14:33:55, data are replayed from TS >= 01-12-2008 08:27:27, when CT = 02-12-2008 15:27:27
yesyes
  • if begin_time = 01-12-2008 08:27:27, the command finds the nearest time (time stamp) so that data could be replayed immediately
  • if CT = 02-12-2008 14:11:02, data are replayed from TS >= 01-12-2008 09:11:02
  • if CT = 02-12-2008 14:33:55, data are replayed from TS >= 01-12-2008 08:33:55
In this situation, also data, recorded before TS, are replayed. This data are replayed at the beginning.


If /LOOP is used, data replaying will be again started automatically. It can be stopped by the STOP_REPLAY command.

Note: This TELL command uses the "dd-mm-rrrr hh:mm:ss" format for the parameters of DateTime type.
It is possible to start this TELL command from the D2000 Server, as well as directly from the clients (currently only from KOM client).
Process D2000 KOM can be started up in replay mode only with the start parameter /Replay. It causes, the process D2000KOM does not communicate with devices.

Kotva
stop_replay
stop_replay
STOP_REPLAY

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 outputThe command redirects the standard output to a new one.

Example:
D2000 on OpenVMS platform: STDOUT "_TNA2:" (output is redirected to the terminal _TNA2:)
D2000 on Windows platform: STDOUT C:\output.txt (output is redirected to the file output.txt)
Note: See a note for STDOUT command for D2000 Archiv.

STOPStops the D2000 KOM process.

Kotva
ststat
ststat
STSTAT START/STOP StationName

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.

Kotva
stwatch
stwatch
STWATCH StationName ["Number"]

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:

  • BACnet (sends ReadProperty, ReadPropertyMultiple, and Subscribe messages depending on the configuration of I/O tags)
  • DNP3 (sends requests for reading of all configured Poll Classes specified in configuration of station parameters and for reading of values of all objects with "Explicit read" enabled)
  • IEC 60870-6 ICCP/TASE.2 (sends requests for reading values of all I/O tags)
  • IEC 61850 (sends requests for reading values of all I/O tags)
  • IEC 870-5-101 (sends Interrogation Command/Counter Interrogation Command depending on station protocol parameters)
  • IEC 870-5-104 (sends Interrogation Command/Counter Interrogation Command depending on station protocol parameters)
  • IEC 870-5-104 Server (sends Interrogation Command/Counter Interrogation Command depending on station protocol parameters)
  • IEC 870-5-104 Sinaut (sends Interrogation Command/Counter Interrogation Command depending on station protocol parameters)
  • OPC Data Access (sends requests for synchronous reading values of all I/O tags)
  • OPC UA (sends requests for reading values of all I/O tags)

...