Starting JNI trace

Use one of the methods described here to enable JNI trace.

Use one of the following methods to enable JNI trace:

  • Set the following environment variables before you start CICS Transaction Gateway:
    CTG_JNI_TRACE
    Use this environment variable to set the name of the JNI trace file. This environment variable only defines the name of the JNI trace file; it does not enable trace. JNI trace is output as plain text, and there is no requirement to use a particular extension for the file name.
    CTG_JNI_TRACE_ON
    Set this environment variable to YES (case-insensitive) to enable JNI trace when CICS Transaction Gateway is started.
  • While CICS Transaction Gateway is running, use the system administration functions. See Gateway daemon administration for details of how to enable JNI trace dynamically.

If the previous methods are not suitable, use one of the following methods:

  • For Java client applications running in local mode, use Java to launch your application and set the system property gateway.T.setJNITFile, as shown in the following example: 
    java -Dgateway.T.setJNITFile=filename application
    where
    • filename is the name of the file to which trace output is to be sent
    • application is the application to launch
  • When you start CICS Transaction Gateway, issue this command: 
    ctgstart -j-Dgateway.T.setJNITFile=filename
    where filename is the name of the file to which trace output is to be sent. If you do not specify a full path to the file, the location is /var/cicscli on UNIX and Linux or <product_data_path> on Windows.

You cannot enable JNI trace through the Configuration Tool.