Home

 

Tracing Secure Sockets Layer (SSL) iKeyman and IKEYCMD functions

 

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

For UNIX:

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

For Windows:

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

To request IKEYCMD tracing, run the IKEYCMD command for your platform with the following –D flags.

For UNIX:

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

For Windows:

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 run time SSL trace is written: /var/mqm/trace on UNIX and <mqmtop>/trace on Windows. The trace files 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 take care when you transfer the files from system to system using FTP. The trace files are typically approximately 1 MB each.

On UNIX and Windows systems, we 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. We cannot format any of the SSL trace files; send them unchanged to IBM support.

 

Parent topic:

Tracing

fa15360_

 

Home