Explain the best way to capture a diagnostic dump of an ITM process in the Windows platform.
Windows 2003 and Windows 2008
Diagnosing The Problem
This technote explains how to install a Microsoft package to captures diagnostic dumps in the Windows system.
Windows Vista and Windows 7
For Vista and 7, the following Microsoft Knowledge entry explains what is needed. A dump can be created directly from Task Manager. In addition the ADPlus tool is referenced for some automatic captures of exception failures.
For Windows 2008 Enterprise Edition, the following Microsoft Knowledge entry explains what is needed - the ADPlus tool.
How to create a user-mode process dump file in Windows Server 2008
For previous Windows server levels the Microsoft User Mode Process Dumper is used to capture a diagnostic dump from a failing ITM process. It can also be run from the command line to take a diagnostic dump if you determine that a Windows application is looping or hung. This document explains how to install and use the tool.
The following URL:
is a Microsoft KnowledgeBase document which provides some documentation. The current level is 8.1 and was published in 2007. The references section contains a URL for downloading the installation file UserModeProcessDumper8_1_2929_5.exe. The level and file may change in the future, but the general process will likely be the same.
Start the installation by running the installation file. It starts by unZIPing some files into the default c:\kktools directory. After that, navigate to the c:\kktools\userdump8.1 directory and select the directory based on the correct architecture for the machine, which is usually x86 for most windows machines.
From the correct directory launch the setup.exe application.
During the install, you will make some choices. It is not necessary to enable the "Dump on Process Termination" feature, though it could be used for other types of failures which are not triggered by an exception. After the install, you should recycle the Windows server.
User dump is controlled via a control panel "Process Dumper":
Change the settings as needed; for example, you may want to set the dump file folder to c:\IBM\ITM\logs. If you want to capture a dump and continue, you will turn off the "Kill process after dumping" control.
There are several sorts of failures.
1) A crash - typically triggered by an exception.
2) A loop, CPU usage high but no productive work
3) A wait state, process not ended, no CPU usage and no productive work
4) Abnormal condition, such as process partly working but abnormal.
In all cases, the process dumper needs to be told what process to work on. On the "Process Monitoring" tab, click on New... and then enter the name of the process. For example, for TEMS it would usually be kdsmain.exe. For TEPS it would be KfwServices.exe. If you are unsure, IBM support will instruct what name to use.
To verify things are working, you should start up the process and take a sample dump. From a command line, enter
userdump -k <processname>
This will take a crash dump of the process. In this case the crash dump is created in the current directory.
For case (1) a crash, the preparatory work is complete. Start the process and wait.
For other cases, you will wait until the condition [loop/wait/abnormal] occurs and then issue the command line manually.
userdump -k <processname>
Now wait for the crash. It will create a .dmp file. At this point compress it and follow IBM Support instructions, which will usually be to send it to ECUREP along with the diagnostic logs.
Resolving The Problem
17 June 2018