...
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. |
Kotva | ||||
---|---|---|---|---|
|
DP ON/OFF | Debug Pipe - shows/hides the information about communication with D2000 Calc (only if the process window is displayed on the desktop). | ||||||
RESET_STATISTICS | Resets the counters for evaluating the statistical data. | ||||||
STATISTICS path+file | Writes statistical data about individual I/O tags into a file. The file contains the following information: I/O tag name, number of recalculations and number of new values broadcasted into the system. The counters are reset while starting the process D2000 Calc or using the command RESET_STATISTICS. | ||||||
STDOUT output | The command redirects the standard output to new one. Example: | ||||||
CALCINFO ON|OFF clcName [row] | 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:
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.
| ||||||
| The command enables to compare the values of destination columns (of structured variables), configured in the eval tags, with the values that were calculated by D2000 Calc. When specifying the particular object of Structured variable type, for which the comparison should be done, the value of parameter DestId, or also ColIndex for the particular column, must be a non-zero. It is followed by the optional keywords from the list: Detail, Debug, Ignore_Time, ReCalc0s, ReCalc1m. You may find the detailed information in the document Checking values of destination columns. Note 1: This command is mainly used for diagnostic purposes in D2000 Systems. Note 2: Command is supported only in version D2000 V8.0.5. | ||||||
SHOW_DYN_INFO {Mask|HOBJ} [Row] | It enables displaying a configuration and the current status of a particular eval tag. The eval tag is defined as an input parameter either through its ID (HOBJ) or mask. If several eval tags match the mask, the first 20 tags will be displayed. If Row parameter is different than 0, it must be the eval tag, the values of which are written to a destination column of the structured variable. For common eval tags (those that have not a destination column) the Row parameter must be 0 or not specified. The log format is identical with the format [Calc], which is stated in the article Checking values of destination columns, Example 3. | ||||||
GET_SOURCE_VALUE HOBJ Row Col | It enables the displaying of the inputs into the calculation providing they are the inputs from the structured variables. The log format is identical with the format [DestVal] Checking values of destination columns, Example 3. Note: This command is mainly used for diagnostic purposes in the D2000 systems. |
...
SHOW_HANDLE [table/database/structure_definition HOBJ] or [table mask] | Shows information on open descriptors. For more information see the chapter DBManager - debugging. |
SHOW_CONNECT [database HOBJ [connect/transaction ID]] or [database mask [connect ID]] [DETAIL] | Shows information on open connections. For more information see the chapter DBManager - debugging. |
SET_WATCHDOG database_mask seconds [NONTRANS] | Switches on the monitoring of connections that perform SQL commands longer than the specified time seconds. This information can be used for the profiling of applications and for the detection of slow SQL commands. If a NONTRANS clause is specified, transactional connections are not monitored. 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 that take longer to be processed (including waiting in queues of DBManager) than the specified time seconds. After such a database action is finished, detailed info about it is written to a log file. If a NONTRANS clause is specified, transactional connections are not monitored. More information can be found in chapter D2000 DBManager - debugging. |
MONITOR_TRANS SHOW {ALL/<id>} [<file_path>] MONITOR_TRANS ON <history_depth_sec> MONITOR_TRANS OFF MONITOR_TRANS RESET | The mechanism for monitoring of the transactions. Columns in the list: Note: After starting DBManager, the monitoring is switched off. |
MONITOR_CONNECTS SHOW {ALL/<id>} [<file_path>] MONITOR_CONNECTS ON <history_depth_sec> MONITOR_CONNECTS OFF MONITOR_CONNECTS RESET | Monitoring the connections. Columns in the list: Note: After starting DBManager, the monitoring is activated with the time-depth history of closed connections which is 3 hours (10 800 seconds). |
REFRESH_TABLES seconds | The command is intended for use on the PostgreSQL platform. It is used to close and reopen cursors used in page access to tables so they don't block table vacuuming if these cursors are open for too long. Typically, these are schemes with browsers, which are e.g. open for several days. The parameter seconds is the minimum age of the cursor in seconds to be reopened (e.g. 86400). |
TIME_STATISTICS database_mask [DETAIL] | Displays statistics of execution of individual database action types per-database or per-table (if a DETAIL parameter is specified). For more information see the chapter DBManager - debugging. |
...