Porovnávané verzie

Kľúč

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

...

DEBUGWIN DEBUG/REQ/KOMARCThe Debug window of the process D2000 KOM displays:
  • DEBUG - trace communications with devices (implicit setting),
  • REQ - current processed communication request + requests in queue,
  • KOMARC - trace readings/writings into the archive file of KOM Archiv.
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 given mask,
  • all I/O tags on the stations with the names matching 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 oldest data stored in the KOM Archive.
Kotva
getoldval
getoldval
GETOLDVAL StationName [M:PointMask] [NORECALC] "BeginTime" ["EndTime"]
Reads historical values from a device - station StationName. The values from defined 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 does not execute the calculation of calculated archive objects, the values of which are calculated just from the values acquired by this calling of tell command. For some protocols (OPC DA, OPC HDA and IEC 870-5-104), there can be used a parameter of mask "M:", which is used to read the archive values only for selected I/O tags from the station StationName, which match the mask.
LNSTAT OPEN/CLOSE LineNameThe command can be used only for the lines of Serial category (asynchronous serial lines). 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. Default format is hexadecimal.
READKOMARC ["BeginTime"] ["EndTime"]Reads the values from KOM Archiv. There are transferred all old values from given 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 given 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
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 in each 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 defines the new I/O tag address.
Change of address will become evident only in internal data structures of KOM process. It is not sent, in a centralized way, to server, i.e. changed address is valid until restart of 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 till it is read from the new address).
  • IGNORED - process D2000 KOM does not support dynamic address change - licence limitation.
  • ERROR
    1. duplicate address
    2. point not found
    3. bad address format

Dynamic change of the I/O tag address is implemented only for limited group of communication protocols:

SETSTADDR name "address"Dynamic change of station address. The parameter name specifies station. It can be entered as the object name (e.g. "S.Stanica"). Parameter "address" defines its new address. Change of station address will become evident only in internal data structures of KOM process. It is not sent, in a centralized way, to server, i.e. changed address is valid until restart of process. After this, the value from the initial configuration will be used again.

Return codes:

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

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

SHOW TAG TagName/TagHOBJEnables debug information for given I/O tag. The command requires either the name or HOBJ of I/O tag. The debug information is usable for D2000 System developers.
SHUTDOWN WINNTRestarts the computer with the process D2000 KOM (the process must be running).

Kotva
start_record
start_record
START_RECORD dir_name_only [begin_time] end_time

Starts a data recording into subdirectory (application directory) with the name dir_name_only. If the directory does not exist, it will be created.
The start of tell command from D2000 Server - at first, the file containing the initialization values of DODM objects dodm_values.dat is recorded and then 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 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 record:
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: Tell command uses the format "dd-mm-rrrr hh:mm:ss" for the parameters of datetime type.
It is possible to start up this tell command from D2000 Server, as well as directly from the clients (currently only from KOM client).
Data are recorded into chosen subdirectory in application directory, in the form of data files representing 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 does not work, the error will occur.

Note: It is possible to start up this tell command from D2000 Server, as well as directly from the clients (currently only from KOM client).

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 subdirectory (application directory) with the name dir_name_only. If the directory does not exist, the error will occur.
The start of tell command from D2000 Server - at first, the file containing the initialization values of DODM objects dodm_values.dat is recorded and then D2000 Server will send this command to the clients with parameter /NOW.
It replays all data (in data files) with the time stamp >= begin_time. Time stamp of data represents the particular time from the recorded time period. Time of data replaying must be from the range of the recorded time period.

Example of data replaying:

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.

Time Stamp (TS) - blue color, current time (CT) - red color

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

Note: Tell command uses the format "dd-mm-rrrr hh:mm:ss" for the parameters of datetime type.
It is possible to start up this tell command from 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 D2000 Server, as well as directly from the clients (currently only from KOM client).

STDOUT outputThe command redirects the standard output to 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 process D2000 KOM.
Kotva
ststat
ststat
STSTAT START/STOP StationName
Enables the communication (the parameter START) or disable the communication (parameter STOP) on the station StationName. The station will get the value StON (START) or StOFF (STOP).
STWATCH StationName ["Number"]The command generates one or several requests for priority reading of all I/O tags on given station. It can be used only for some communication protocols (of request-response type). The parameter Number defines the number of requests, possible value is within 1...5. If the parameter is not defined, just one request will be generated.

...

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 profiling of applications and and for detection of slow SQL commands. If a NONTRANS clause is specified, transactional connections are not monitored.
Starting with version 10.1.39, 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 which 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>] / ON <history_depth_sec> / OFF / RESETMonitoring the transactions.

ON - activates the monitoring. <history_depth_sec> means a time-depth history of closed transactions.
OFF - deactivates the monitoring
RESET - resets the list of transactions (including the opened ones)
SHOW - shows either the list of transactions including the history (ALL), or the particular transaction (<id>) to a console or file <file_path> in csv format separated by ";"

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 switch off.
MONITOR_CONNECTS SHOW {ALL/<id>} [<file_path>] / ON <history_depth_sec> / OFF / RESETMonitoring the connections.

ON - activates the monitoring. <history_depth_sec> represents the time-depth history of closed connections.
OFF - deactivates the monitoring
RESET - resets the list of connections (including the opened ones)
SHOW - shows either the list of connections including the history (ALL), or the particular connection (<id>) to a console or file <file_path> in csv format separated by ";"

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).
TIME_STATISTICS database_mask [DETAIL]Displays statistics of execution of individual database action types per-database or per-table (if a parameter DETAIL is specified).
For more information see the chapter DBManager - debugging.

...