História stránky

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 path

Creates 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 path

Creates a log database backup in the directory specified by the path parameter (Sybase SQL Anywhere and PostgreSQL platforms).

CFGSYNCHROAUTO ON/OFF

Enables/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_ARCHIVE

Checks 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/OFF

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

ENABLEAUTOSTARTPROCESSES

Since version v23.0

If the kernel was started with the /N parameter, i.e. so that it does not start processes, by calling this tell command, startup is turned on and kernel processes start.

Kotva

	instance
	instance

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_name

Shows 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, 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_name

Enables to display of 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 active instance is the one that connects to the D2000 Server process as first.
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_number

Enables 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_name

Broadcasts (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, and the message from the D2000 Server was sent.

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 serverName

Sets 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_PARAMS

Reloads 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_SECURITY

Sets the new configuration of Security Policy without restarting the D2000 System.

REPAIR_ARCHIVE

Checks 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 the 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.

Kotva

	restart
	restart

RESTART process_name

Stops 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

Kotva

	set_max_act_inst
	set_max_act_inst

SET_LOAD_BAL_MODE
process_name mode

Activates/deactivates Load balancing mode for D2000 Archiv (see the chapter Redundant archiving - Load balancing) or D2000 Kom (see the chapter Redundancy of communication process KOM) processes.

Example:
SET_LOAD_BAL_MODE SELF.ARC 1 - activates Load balancing mode for SELF.ARC process.
SET_LOAD_BAL_MODE SELF.KOM 1 - activates Load balancing mode for SELF.KOM 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 the D2000 system diagnostic purposes.

SHOW_DYNO_LIST idFirst idLast

The 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_LIST

Lists internal transactions of the D2000 system.

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

SHUTDOWN D2000

Stops the D2000 system.

SHUTDOWN RESTART_D2000

Restarts the D2000 system.

SHUTDOWN RESTART

Stops the D2000 system and restarts the operating system.

SHUTDOWN SHUTDOWN

Stop the D2000 system and shutdowns the operating system.

SHUTDOWN WINNT

Stops D2000 System and restarts the operating system.

Kotva

	start
	start

START process_name

Starts the specified process.

STDOUT output

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

Kotva

	stop
	stop

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]|HIBERNATE

It 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 acknowledgements (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 acknowledgements and it can interact with the TCP_NODELAY parameter.

Kotva

	xml_export_table
	xml_export_table

XML_EXPORT_TABLE

The configuration parts exported 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_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.

...

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.

...

the parameter before is not defined - for individual archive objects, there will be deleted all data that are older than the history depth (the parameter History depth) defined in the configuration of the objects,
the parameter before is defined - there will be deleted all data with the timestamps older than defined by the parameter before.

...

for Sybase - name of a depository database
for Oracle - number of depository tablespace
for PostgreSQL - number of a 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:

SCRIPT - script
PRIMARY - primary archive objects
STATISTIC - statistical archive objects
EVAL - calculated archive objects
ALL - all types of archive objects

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.

...

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.
Note 2: The slice number, except for ordinary values, supports special values:

value -1 means "all slices"
value -2 means "slice for current time"
value -3 means "previous time slice"
value -4 means "all slices older than current time slice"
value -5 means "only those archive objects that do not have time slices" (if time slices are configured only for structured archives, then only simple ones will be reorganized)

...

AlmostZero
ALMOST_ZERO

...

positive real number (e.g. 1e-10)

...

If the depositories are ON, the data older than the specified date will be read from the depository databases. This parameter can be used for checking if the depositories truly contain all data (e.g. after the patching by arcsynchro).
The value OFF deactivates the limitation.
When the limitation is active, every reading from the archive (in which the limitation is applied) produces the following note in the archive log file:
Start time for reading values from archive is before READ_ARCHIVE_DEPTH, limiting

...

Setting the periodicity of archive warnings about the low disk space (unless they are disabled using the DiskUsageWarning parameter).
See the description of the parameter DiskUsagePeriod.

...

IsoCacheDepth
ISOCACHE_DEPTH

...

a positive number (seconds)

...

The parameter is used to test depository data compression.

See the description of the parameter TrezorCompressKeep.

...

TrezorReadSegment0
TREZOR_READ_SEGMENT0

...

ON/OFF

...

Activation of monitoring of primary values that are older than the specified parameter. The following are monitored:

object values
values that come as old values (OLDVAL)
values entered or changed in HI
values inserted through INSERTARCHARR and UPDATEARCHVAL actions

Monitoring is deactivated by the OFF parameter.

...

WorkingHoursStart
WORKING_HOURS_START

...

non-negative integer number

...

WorkingHoursEnd
WORKING_HOURS_END

...

non-negative integer number

...

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.

...

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

...

start parameters of the process specified in the configuration of the archive process (if the archive process is run by process D2000 Server), or archive service (if the archive process is run by its own watchdog), or command-line parameters (if the archive process is run manually),
parameters for archive specified in Windows registry,
parameters stored directly in the archive database in the LOG_DATA table (see the parameter /CLD of arcsynchro utility),
specific parameters of the database (currently only for the Oracle platform).

...

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 running on the Windows platform as a service, the console output is disabled. Therefore if this functionality is required, it is necessary for a D2000 process to be started by D2000 Server without /X parameter.

...

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.
Note: The compression of a depository is possible if it is mounted for writing (see MOUNT_TREZOR command with WRITE parameter).

...

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.
Note: The decompression of a depository is possible if it is mounted for writing (see MOUNT_TREZOR command with WRITE parameter).

...

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.

...

] "BeginTime" ["EndTime"]

...

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 the category "SerialOverUDP Device Redundant", it need not be specified or must be equal to 1. For a line of 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:
LNALTERPATH L.MyLine ON 3
LNALTERPATH L.MyLine BACKUP 3
LNALTERPATH L.MyLine QUERY

...

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.

...

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:

IEC 60870-6 ICCP/TASE.2
IEC 870-5-101 (client, server, balanced mode)
IEC 870-5-104, IEC 870-5-104 Server
Modbus Client, Modbus Server
OPC UA Client

...

Return codes:

SUCCESS - changed address (the value of the I/O tag is invalid until it is read from the new address).
IGNORED - The 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:

...

Return codes:

SUCCESS - changed address,
IGNORED - The 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:

...

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.

...

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

...

Example of data replaying:
Time Stamp (TS) - blue color, current time (CT) - red color

begin_time	/NOW	Description
no	no	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
yes	no	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
yes	yes	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.

...

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).
The D2000 KOM process can be started up in replay mode only with the start parameter /Replay. It causes the process D2000KOM not to communicate with devices.

...

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

...

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.

...

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:

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

...

After receiving the command, the process writes, into its log file, information about:

...

¹ - script identification: text string uniquely identifying the running ESL scrip. It contains the object name (HOBJ)[instance number] unique numerical identifier.
Example: E.Script(728)[105]1872
(%GetSelfInstanceId, %GetSelfHBJ)

...

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.

...

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.

...

The command is used to determine the reason for calculating the eval tag that has the Calculation method parameter set to At change or Trigger value.

The command ensures (CALCINFO ON) that into the LOG file of the process will be continually written information about the reason for the calculation of the eval tag. The CALCINFO OFF command terminates the continuous log to the LOG file. It is used for the eval tags that have the Calculation Method parameter set to At change or Trigger value.

Record in the LOG file contains:

the identification of the object that caused the conversion and its value
the output value of the eval tag that was sent to the server

Parameters:

clcName - the name of eval tag

row - specifies a row number for a structured eval tag. If not specified, the replacement value is 0 and all rows will be tracked.

Example (the content of LOG file):

TELL command: CALCINFO ON P.OnSec

In the LOG file, there is a record that the information is about the calculation of the calculated P.OnSec object. The value of the object changed from HOBJ=20 (VALUE IN $20). Next, the individual attributes of the input value are displayed. Output value attributes are displayed after a row containing VALUE OUT content.

Blok kódu

CALCINFO: P.OnSec[ 0]
VALUE IN $20
GValTyp : INT (Integer)
Status : VALID
LimitStatus : INLIMIT
ProcAlarmStatus : NOALARM
ValTyp : INT
Flags : F,F,F,F,F,F,F,F,F,F,F,F,F,F,F,F
ValTime : 20.11.2017 16:39:59.000
AlarmTime : (null)
Value : 59
VALUE OUT
GValTyp : INT (Integer)
Status : VALID, NOACKVALUE
LimitStatus : INLIMIT
ProcAlarmStatus : NOALARM
ValTyp : CE
Flags : F,F,F,F,F,F,F,F,F,F,F,F,F,F,F,F
ValTime : 20.11.2017 16:39:59.001
AlarmTime : (null)
Value : 60

...

MONITOR_TRANS SHOW {ALL/<id>} [<file_path>]

MONITOR_TRANS ON <history_depth_sec>

MONITOR_TRANS OFF

MONITOR_TRANS RESET

...

Columns in the list:
- ID (transaction identifier)
- time, task, traceback (time the last operation within the group of identical ones, task, traceback in the internal code)
- comment, count (the last comment and the number of consecutive identical operations) (the identical operations has the same task and traceback)

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

...

Columns in the list:
- ID (auxiliary identifier of connection)
- logon_time, logon_task, logon_traceback (time of connection, task and traceback in internal code)
- logoff_time, logoff_task, logoff_traceback (time of disconnection, task, and traceback in internal code)
- comment (the last written comment for the given connection, e.g. traceback in ESL code)

Note: After starting DBManager, the monitoring is activated with the time-depth history of closed connections which is 3 hours (10 800 seconds).

...

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.

...

The command will cause the execution of the SQL statement DISCARD TEMPORARY in the PostgreSQL database with the specified name/ID on all connections, or on a specific one.

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.

...

GETOLDVAL remoteObjectMask "BeginTime" ["EndTime"] [NORECALC]

GETOLDVAL "remoteTagName[row]^item" "BeginTime" ["EndTime"] [NORECALC]

...

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:

reading row 10 - GETOLDVAL "RemoteTagName[10]" …
reading the column named Values - GETOLDVAL "RemoteTagName[0]^Values" …

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.

...

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

...

Instantly stops recording of values read from the GateWay Server. For details see the command description for the D2000 KOM process.

...

Info

title	Related pages:

D2000 Tell
Work with D2000 Tell

Strom stránky

Porovnávané verzie

Stará verzia 1

Nová verzia Aktuálny

Kľúč