| 5.16. Trace functionalities | ||
|---|---|---|
 | Chapter 5. Command language |  |
| 5.16. Trace functionalities | ||
|---|---|---|
| | Chapter 5. Command language | |
By typing the following command, an informative message about every trace command syntax will be shown.
[18:01:34] ABILIS_CPX:trace ??TRACE ACT Activate Tracer using saved values TRACE ACT PO:xx,yy,... [par:val] Activate Tracer on specified ports TRACE CLEAR Clear the current trace TRACE DELETE <file> Delete trace saved on disk in <file> file TRACE DISPLAY [par:val] Display trace of sent and received data TRACE DISPLAY EXTENDED [par:val] Display trace of all commands TRACE DISPLAY INFO Display trace informative header TRACE GET [X] Transfer trace using XMODEM-1K [ST: and/or LEN:] or [LAST:] TRACE GET Z [<file>] Transfer trace using ZMODEM [ST: and/or LEN:] or [LAST:] TRACE INACT Deactivate Tracer TRACE PARAM Display Tracer configured parameters, active parameters and the current Tracer state TRACE PARAM SAVE Save current Tracer parameters values TRACE PARAM SET par:val [par:val] Set Tracer parameters TRACE SAVE <file> Save trace on disk in <file> file TRACE START [par:val] Run Tracer TRACE STOP Stop Tracer
![[Tip]](../images/tip.png) | Tip |
|---|---|
Interesting chapter: Section 71.29, “How to trace the internal events for debugging purposes”. |
The trace act command activates the internal events trace function. By typing the command trace act ?, an informative message about trace activation syntax will be shown.
[18:01:34] ABILIS_CPX:trace act ?TRACE ACT Activate Tracer using saved values TRACE ACT PO:xx,yy,... [par:val] Activate Tracer on specified ports PO: Ports to be traced (max. 50) <Mandatory> SIZE: Tracer buffer size [3..262144 Kibyte] <Optional> DATA: Max event buffer size [10..2100 bytes] <Optional> CMD: Commands type [RSP, RSA, STD, CTIRSIG, FR-LMI, ALL] <Optional> LSN: SD/RV lsn to be traced [ALL, 0000..FFFE (Hex.)] <Optional> TYPE: SD/RV type to be traced [ALL, DATA, CHK, VOICE] <Optional> -M Force Tracer activation <Reserved>
If no parameter is specified, the following message is displayed:
“NO PARAMETER SPECIFIED: USING SAVED VALUES...”, so the
trace function is activated using the setting already saved through the
commands trace param set and trace param
save. The first one modifies the trace parameters that will be
used for further activations of the trace, while the second saves, in
the configuration file drivers.cfg, the parameters
previously activated.
The trace param command shows the parameters settings of the internal events trace and its working mode; the information shown will depend on the trace state.
Here's the meaning of parameters:
PO sets the list of ports (minimum 1,
maximum 50) which can be traced; their values must be in the
interval [0 - 999]. Ports to be traced, must be
“RUNNING”, if not, the following message will be
displayed “RES:xxx PORT NOT PRESENT OR NOT RUNNING” and
the trace function won't be activated; “xxx” stands for
the identifier of the not present or not running port. Refer to
Section 5.8.7, “D PSTACK” to have more
information about ports;
SIZE sets the maximum allocable memory size
for the trace function. If the parameter isn't specified, all the
available memory will be used by the system for trace activating,
except the needed quantity for system management. If the system
memory isn't enough for activating the trace function, it won't be
activated and the following message will be displayed “NOT
ENOUGH MEMORY TO RUN TRACE”;
DATA sets the maximum allocable memory size
for saving the single event, remaining optional parameters
CMD, LSN and
TYPE make possible the activation of filters on
the events traced.
| Tip |
|---|---|
it's possible to enable the automatic trace activation at system
start-up, if the parameter
|
The trace start command starts saving the events exchanged among the ports specified in the list, which has been defined during the trace activation (through the command trace act).
If in the command row isn't indicated any additional parameter,
the trace will start using the settings defined during its activation.
The following optional parameters can be specified
LSN, DATA,
TYPE, CMD. In this way trace
parameters setting may be edited again.
If the trace isn't active, the following message will be displayed “TRACE INACTIVE”. By typing the following command, an informative message about the command syntax and options will be shown.
[18:01:34] ABILIS_CPX:trace start ?TRACE START [par:val] Run Tracer DATA: Max event buffer size [10..2100 bytes] <Optional> CMD: Commands type [RSP, RSA, STD, CTIRSIG, FR-LMI, ALL] <Optional> LSN: SD/RV lsn to be traced [ALL, 0000..FFFE (Hex.)] <Optional> TYPE: SD/RV type to be traced [ALL, DATA, CHK, VOICE] <Optional>
The trace stop command stops tracing the events and stores the trace content in memory until the next trace start, through the command trace start or the deactivation of the function (command trace inact). If the trace isn't active, the following message will be displayed “TRACE INACTIVE”. If the trace function isn't running, the message “TRACE NOT RUNNING” will be displayed.
The trace get command transfers the content of the internal events trace, previously saved by Abilis CPX to a remote destination, by using the XModem-1k or ZModem protocol.
By default, the whole content of the trace, starting from the beginning of the saving, it's transferred. it's also possible, by using the proper optional parameter, to transfer only a part of the content:
If the trace buffer is empty or got empty by the command trace clear, the message “TRACE EMPTY” will be shown.
Before executing this command, the trace function has to be stopped, by using the command trace stop, otherwise the message “TRACE RUNNING” will be displayed. If the trace isn't active, the message “TRACE INACTIVE” will be shown.
The transfer procedure signals its availability to transfer the trace file by the message “READY TO SEND TRACE BUFFER...” When the transfer is completed the following message is shown: “TRACE BUFFER TRANSFER ENDED, PRESS <ENTER> TO CONTINUE...”, after pressing the <ENTER> button, an informative message, “TRACE BUFFER TRANSFER SUCCESSFULLY COMPLETED”, will be shown if it was successful.
[18:01:34] ABILIS_CPX:trace get ?TRACE GET [X] Transfer trace using XMODEM-1K [ST: and/or LEN:] or [LAST:] TRACE GET Z [<file>] Transfer trace using ZMODEM [ST: and/or LEN:] or [LAST:] X or Z Select the X or Z MODEM protocol (by default XMODEM is used) <file> Select the name of the file on the target host (ZMODEM protocol only) <Optional> ST: Trace buffer start value [in Kibyte] <Optional> LEN: Number of Kibyte to be transmitted, starting from the beginning of the Tracer buffer or from the "ST:" value <Optional> LAST: Number of Kibyte to be transmitted, starting from the end of the Tracer buffer <Optional>
The trace can also be transferred from the memory to a file with the command trace save <filename>. The file can be downloaded with the command file get and deleted from the disk with trace delete <filename>. For example:
[21:22:34] ABILIS_CPX:trace save trace.cpxCOMMAND EXECUTED[21:22:34] ABILIS_CPX:d iAbilis CPX - Ver. 8.0.2/STD - Build 3961.6 - Branch 8.0 - 01/04/2015 (c) 1994/2015 - Abilis ABILIS-ID: 800733 Free/Total Memory (in byte): 98,931,168/260,046,848 Free/Used/Total HD/CF space (in Kibyte): 99,150/25,298/124,448 File Version Date Time Size Note ------------------------------------------------------------------------------- CPX.RTB ....... 01/04/2015 20:33:34 5950919 DRIVERS.CFG v.8.0 22/04/2015 12:00:52 37888 Saved DRIVERS.BCK v.8.0 16/04/2015 11:45:02 36864 Ok CPX.LOG v.1.0 22/04/2015 13:40:12 51200 CPX.DBG v.1.1 16/04/2015 11:44:52 20480 CPX.XCP ....... 16/04/2015 11:44:48 51200 BSXXXI.BIN v.2.6 29/07/2014 12:53:40 109568 BSXXXV.BIN v.2.2 18/02/2013 11:14:12 108544 ESB2.BIN v.13.0 28/10/2004 19:38:20 17408 D1K.BIN v.312.9 07/06/2011 16:05:48 1024 D1C4F3.BIN v.312.9 07/06/2011 16:05:46 100352 D1C5F3.BIN v.312.9 07/06/2011 16:05:48 100352 D2K.BIN v.312.9 30/05/2008 19:31:16 1024 D2C4F3.BIN v.312.9 07/06/2011 16:05:48 102400 D2C4F6.BIN v.312.9 07/06/2011 16:05:48 102400 HFC2E4.BIN v.21.0 30/07/2009 10:57:22 16384 HFC2E8.BIN v.21.0 30/07/2009 10:57:22 16384 HFC3E4.BIN v.57.0 10/04/2012 19:24:34 83968 HFC3E8.BIN v.57.0 10/04/2012 19:24:34 83968 QPRI2B.BIN v.5.0 26/07/2011 18:58:14 17408 QPRI2E.BIN v.6.0 26/07/2011 18:58:14 17408 CTIHA2.BIN v.8.0 26/07/2011 18:58:14 18432 D64A.BIN v.33.22 02/11/2012 21:51:12 73728 D64V.BIN v.8.15 15/05/2012 12:52:26 143360 QPRIX.BIN v.33.0 16/04/2012 12:55:56 241664 OCTASIC.BIN v.16.0 18/06/2008 20:31:40 175104 WING-P.BIN v.1.0 08/02/2011 19:02:22 264192 SL-IT.BIN v.1.0 28/10/2004 19:38:20 1024 SRVSSL.CER ....... 28/10/2004 19:38:20 820 CLISSL.CER ....... 28/10/2004 19:38:20 820 SRVSSL.KEY ....... 28/10/2004 19:38:20 981 CLISSL.KEY ....... 28/10/2004 19:38:20 969 Other system relevant files: File Version Date Time Size Note ------------------------------------------------------------------------------- C:\LICENCE\LIC1-0000800733.TXT ....... 15/04/2015 12:52:44 349 C:\APP\CTI\ADDRBOOK\ADDRBOOK.DAT v.1.0 15/04/2015 12:58:20 140066 C:\APP\CTI\LCS\LCSTABLE.DAT v.1.0 22/04/2015 13:45:04 60066 C:\APP\DHCP\DHCP.BND v.1.0 16/04/2015 11:45:00 25600 C:\APP\DNS\BLACKLIST.DAT v.1.0 18/02/2015 19:02:52 66 Other files in 'C:\8-0-2': File Date Time Size Note ------------------------------------------------------------------------------- TRACE.CPX 22/04/2015 16:15:22 4829184
| Tip |
|---|---|
The automatic tracer saving feature can be activated, if the
parameter
|
| |  | |
| 5.15. Test functionalities |  | 5.17. DEBUG commands |