| DYNAMIC_INFO | TELL command for the processes with the name *.EVH and *.HIS. This TELL command does not have any parameters. After receiving the command, the process writes, into its log file, information about: - list of all running instances of ESL scriptsFormat: ESL;ESL name ESL - text identifying the next information ESL name - script identification1 - registered text strings (GETACCESS action) Format: ACCESS;ESL name;String;time of GetAccess;bGlobal;userComment;status ACCESS - text identifying the next information XML - text identifying the next information REFOBJ - text identifying the next information DBCONNECT - text identifying the next information FIO - text identifying the next information CNT - text identifying the next information 1 - script identification: text string uniquely identifying the running ESL scrip. It contains the object name (HOBJ)[instance number] unique numerical identifier. |
| SHOW_TRANS_LIST idInstance | If idInstance = 0, the command shows both the list of all instances of events that are pending to finish the transaction and the list of transactions. If idInstance <> 0, the command shows the information about the particular instance (you can find the list of instances in the dialog window ESL Diagnostic Pack or by the TASK_STATUS command). |
| STATISTICS path+file | Writes data about the processor time consumption according to individual events into a file. |
| STDOUT output | The command redirects the standard output to a new one. Example: |
| TASK_STATUS path+filename | Writes currently executed lines of all the script running in a specified process into a file (*.EVH or *.HIS). The command also supplies the information about whether the ESL script is currently executing the external function. If yes, the file will contain the name of the function and the line number of the script calling the function. |
| ON_CHANGE_INFO [idInstance] | The command writes all active ESL ON CHANGE actions within the process to the log file. If the optional idInstance parameter is specified, only the actions of the given instance of the ESL script (idInstance described in the ESL Diagnostic Pack tab Event Instances) will be listed. |
...
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 | ||
|---|---|---|
| ||