A detailed trace mechanism is provided for the ECI resource adapter. Trace is useful when problem solving for applications that use the CICS® resource adapters.
The CICS resource adapters support four levels of trace:
|0||No trace messages|
|1||Exception tracing only (default level)|
|2||Exception and method entry/exit trace messages|
|3||Exception, method entry/exit and debug trace messages|
To provide more control over tracing, these system properties are available:
|com.ibm.connector2.cics.tracelevel||Overrides the deployed trace level for the resource adapters without having to redeploy or deploy another CICS resource adapter.|
|com.ibm.connector2.cics.dumpoffset||The offset into a byte array at which a hex dump will start.|
|com.ibm.connector2.cics.dumplength||The maximum length of data displayed in a hex dump.|
|com.ibm.connector2.cics.outputerr||Declaring this directive sends trace output to standard error, if no other trace location has been specified either by the JEE server, or by the application developer working in a nonmanaged environment. In other circumstances the provided logwriter takes precedence.|
These are JVM System properties that can be passed to the JVM on startup. The com.ibm.connector2.cics.tracelevel option is equivalent to the managed environment property "tracelevel" that is set as a custom property on the connection factory.
When you deploy the CICS resource adapters into your environment, security restrictions are set up to allow access to the local file system for the purpose of writing trace files.
Access is given to the IBM/ctg directory in your home directory.
Therefore, when setting the name and path of the trace file in your JEE environment, use a location under this directory structure to store your trace. Otherwise the resource adapters will not have security permissions to write to the file.