Tracing Secure Sockets Layer (SSL) iKeyman and iKeycmd functions

How to request iKeyman and iKeycmd tracing.

To request iKeyman tracing, execute the iKeyman command for your platform with the following -D flags.

For Windows UNIX and Linux® systems:


strmqikm -Dkeyman.debug=true -Dkeyman.jnitracing=ON

To request iKeycmd tracing, run the iKeycmd command for your platform with the following -D flags.

For Windows UNIX and Linux systems:


runmqckm -Dkeyman.debug=true -Dkeyman.jnitracing=ON

iKeyman and iKeycmd write three trace files to the directory from which you start them, so consider starting iKeyman or iKeycmd from the trace directory to which the runtime SSL trace is written: /var/mqm/trace on UNIX and Linux systems and MQ_INSTALLATION_PATH/trace on Windows. MQ_INSTALLATION_PATH represents the high-level directory in which WebSphere MQ is installed. The trace files that iKeyman and iKeycmd generate are:

ikmgdbg.log: Java related trace
ikmjdbg.log: JNI related trace
ikmcdbg.log: C related trace

These trace files are binary, so they must be transferred in binary transfer mode when they are transferred from system to system using FTP. The trace files are typically approximately 1 MB each.

On UNIX, Linux, and Windows systems, you can independently request trace information for iKeyman, iKeycmd, the runtime SSL functions, or a combination of these.

The runtime SSL trace files have the names AMQ.SSL.TRC and AMQ.SSL.TRC.1. You cannot format any of the SSL trace files; send them unchanged to IBM® support. The SSL trace files are binary files and, if they are transferred to IBM support via FTP, they must be transferred in binary transfer mode.