SAP ABAP Data Element DB2ITRCLVL (ICLI trace level)

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DB-DB2 (Application Component) DB2 for z/OS
     ⤷ STU2 (Package) CCMS for DB2 for OS/390

Basic Data

Data Element	DB2ITRCLVL
Short Description	ICLI trace level

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	DB2NUMC01
Data Type	NUMC	Character string with only digits
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	Trace lev.
Medium	15	ICLI trace lev.
Long	20	ICLI SRV trace lev.
Heading	0

Documentation

Definition

Trace level to which the ICLI server is to be set.

If the system is set up with several ICLI servers, the trace level can only be set 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.

For optimal performance the trace should be switched off.

ICLI Server Trace levels:

• 1
  Developer trace: SQLCODE traceback.
  Should be used when doing test runs where you expect errors. For every non-zero SQLCODE, it will produce an SQLCODE trace, which shows the SQL statement producing the error and some previous statements. Performance impact is small since traces are written into memory and only dumped into the trace files when an error occurs. Traceback information can be very valuable when tracking down error situations.
  
• 2
  SQL trace of statements and parameter markers.
  Should be used if you want a list of all SQL statements that are executed and to find errors in input data to the R/3 database. Can also be used to get some timing values, because for each SQL statement a timestamp is written.
  
• 3
  Same as trace level 2 plus fetched data.
  In addition to the output of trace level 2, fetched data is also traced. This can help in analyzing errors which occur while retrieving data from the database. The amount of trace data is significantly higher than with trace level 2.
  
• 4
  Developer trace for internal use.
  Please switch only on request of IBM or SAP.
  
• 5
  Developer trace for internal use.
  Please switch only on request of IBM or SAP.
  
• 6
  Trace for Performance Monitor functions.
  Trace is only written when Performance Monitor (ST04) is used.

History

Last changed by/on	SAP	20070813
SAP Release Created in	710