Hierarchy
⤷ BC-DB-DB2 (Application Component) DB2 for z/OS
⤷ STU3 (Package) Development Class for Database Monitor
Basic Data
Data Element | DB2ITRCSTA |
Short Description | Start the ICLI server trace |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FLAG | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Start |
Medium | 20 | Start trace |
Long | 30 | Start ICLI server trace |
Heading | 0 |
Documentation
Definition
If the system is set up with several ICLI servers, the trace can only be started for the ICLI server to which the application server that sent the request is connected. Note that all work threads of the ICLI server instance are affected.
Traces are written to the file ICLItrace.<ID>.<UNIQUE_ID> in the log directory of the ICLI server process, where <ID> is either the value <error_file_name> specified using the ICLI command line option -EFNAME <error_file_name> or the UNIX System Services process ID of the ICLI server process in decimal representation and <UNIQUE_ID> represents a unique identifier (last four bytes of the UNIX System Services thread ID converted to decimal representation). The log directory of the ICLI server is specified with the ICLI command line option -LOGDIR <log_dir>.
The files in the log directory of the ICLI server can be displayed using the 'Display trace' option on the 'ICLI server trace' panel of transaction ST04.
For more information, refer to the IBM documentation 'SAP R/3 on DB2 for OS/390: Planning Guide'.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 710 |