Tool to capture Datacap environment information
Enhance Datacap debugging with a new support tool to capture the Datacap environment information and output the captured list of files to the DatacapInfo.txt file.
About this task
The DatacapInfo executable tool captures the following information to a log file labeled, DatacapInfo.txt to assist in problem debugging:
- Datacap build information
- General machine information, such as the operating system and the number of cores
- Important registry settings
- A list of every file in the Datacap directory. If the file is a DLL, it includes the version number of the file
Procedure
The DatacapInfo.exe file is located in the \Datacap\support\DatacapInfo folder.
- Launch the DOS prompt, change the directory to the folder containing the DatacapInfo.exe file. Example: \Datacap\support\DatacapInfo folder.
- Run DatacapInfo.exe in the DOS command line to capture the Datacap installed files during a recent interim fix installation against all operating system drives.
- Press any key to end the DatacapInfo.exe tool when the message appears in the DOS command prompt window. By default, the tool will create a log file in the current folder. See the steps below to change the name and location of the log file.
- Upload the DatacapInfo.txt to the case.

Running the DatacapInfo.exe tool on several Datacap directories and machines
By default, the DatacapInfo tool will capture the files from the directory where Datacap was installed. This is typically C:\Datacap. It is possible that multiple directories and machines are used in a Datacap installation. For example, while the base product may be installed in C:\Datacap or D:\Datacap, applications could be installed on other drives, such as a shared drive Z:, effectively splitting the Datacap installation for a single machine.
It is common to have separate machines for a large Datacap installations. One machine could be a server machine with Taskmaster Server installed, while another machine could have Rulerunner installed and a third machine could have the Datacap clients. When IBM Datacap support asks for the information gathered using the DatacapInfo tool, capturing all of these drives is important for problem diagnosis.
If Datacap server is installed on D:\drive and the applications are installed on a shared Z:\ drive, run the DatacapInfo tool for each root directory by using the following sample.
datacapinfo.exe "log:c:\CollectDatacapFiles\datacapServer.txt" "dir:D:\Datacap"datacapinfo.exe "log:c:\CollectDatacapFiles\datacapApplications.txt" "dir:Z:\Datacap"If there is a separate machine for Rulerunner, then use a similar approach to capture the installation on that machine, giving it a unique log file name.
Additional parameters to use with the DatacapInfo.exe tool
syntax: [log:<logfile>] [dir:<searchdir>] [skipfpdir] [nowait] [nogroups] [/?]
- logfile
- The location to create the log file. If not specified, it is created in the current directory that contains the DatacapInfo tool.
- searchdir
- The base directory to scan. If not specified, it scans the Datacap install directory.
- skipfpdir
- If specified, any and all directories called "fingerprint" will not be listed in the log file. This flag can be enabled to prevent the capture of large fingerprint directories.
- nowait
- If specified, the application will exit without waiting for a keypress.
- nogroups
- If specified, does not list groups that have permissions to the root directory.
- /?
-
Displays syntax information only for the DatacapInfo tool. Use by itself to display the syntax guide in the command window.
Sample syntax: [log:<logfile>] [dir:<searchdir>] [skipfpdir] [nowait] [nogroups] [/?]
Example
C:\Datacap\support\DatacapInfo>Datacapinfo "log:c:\temp\DatacapinfoRulerunnerMachine.txt" "dir:C:\Datacap" skipfpdir
The sample syntax runs DatacapInfo.exe tool to output the datacap.txt file to the c:\temp folder, capturing the Datacap installed files from the C:\Datacap folder in its entirety, skips the fingerprint directory, exits the DatacapInfo tool application when done without waiting for user to initiate a keypress, and will not list groups that have permissions to the root directory.