Porovnávané verzie

Kľúč

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

...

DYNAMIC_INFOTELL 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 scripts
Format: 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
ESL name - script identification1
String - registered text string
time of GetAccess - time of string registration
bGlobal - flag defining the string to be global
userComment - comment
status - text "IN PROGRESS", if the global string has been registered, otherwise empty text ""

- list of all open XML documents (%XML_CreateDocument, %XML_OpenDocument)
Format: XML;ESL name;handle

XML - text identifying the next information
ESL name - script identification1
handle - unique numerical identifier of XML document; it is identical to handle which is used by functions %XML_* 

- list of objects that have been opened by function %OpenRefToObject
Format: REFOBJ;Esl Name;Synchro;Obj HOBJ;Obj Name;Open In Progress

REFOBJ - text identifying the next information
ESL name - script identification1
Synchro - value of parameter _bSynchro at calling of the function %OpenRefToObject
Obj HOBJ - unique identifier of opened object
Obj Name - unique name of opened object
Open In Progress - flag defining if the object is just being opened

- list of active database connections (by the DB_TRANS_OPEN, DB_CONNECT, PG_CONNECT, and SQL_CONNECT actions)
Format: DBCONNECT;ESL name;DB TRANS HANDLE;SUB CONNECT HANDLE;TYPE;OBJNAME;Prepared SQL Command;Last SQL Prepare; Comment

DBCONNECT - text identifying the next information
ESL name - script identification1
DB TRANS HANDLE - identifier of transaction connections (it is created by calling the DB_TRANS_OPEN action), or 0, if the connection is not transactional
SUB CONNECT HANDLE - identifier of connection (it is created by calling the DB_CONNECT, PG_CONNECT, or SQL_CONNECT actions)
TYPE - type of connection (SUB CONNECT HANDLE)
OBJNAME - object name, on which the connection is joining
Prepared SQL Command - flag of the existence of prepared SQL command
Last SQL Prepare - format of the last SQL command which has been prepared by calling the SQL_PREPARE action
Comment - the position where the SQL_PREPARE action was called

- list of files which have been opened by functions %FIO_*
Format: FIO;ESL name;file name

FIO - text identifying the next information
ESL name - script identification1
file name - filename

- list of created data containers (CNT_CREATE action)
Format: CNT;ESL name;handle;NR;valTyp;is array

CNT - text identifying the next information
ESL name - script identification1
handle - unique numerical identifier of data container
NR - number of elements
valTyp - a type of key which identifies the items in the data container uniquely
is array - flag determining whether the action CNT_CNVTOARRAY is applied on the respective data container

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

SHOW_TRANS_LIST idInstanceIf 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+fileWrites data about the processor time consumption according to individual events into a file.
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.

TASK_STATUS path+filenameWrites 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
calc
calc
D2000 CALC

...

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.

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 switched off.

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

MONITOR_CONNECTS ON <history_depth_sec>

MONITOR_CONNECTS OFF

MONITOR_CONNECTS RESET

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

REFRESH_TABLES secondsThe 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.

...