This enhancement offers benefits for troubleshooting, identifies reasons for breaks in the workflow and assists in root-cause analysis. 

To troubleshoot the issue where a task's XML file is overwritten with the previous task's XML file during processing by RuleRunner (RR) services in IBM Datacap, an enhanced configurable RR registry setting is available in the latest Datacap 9.1.9 fix pack.

Enabling the registry setting is diagnostic only-it does not remediate any known defects; It can in some instances, assist in isolating contributing factors by logging detailed XML content before and after task execution.

Use Case

When the RuleRunner registry setting Dump DCO Files is enabled, the contents of the task's XML file - both before and after the task is executed - are written to the RuleRunner logs.

This allows IBM Datacap developers and support teams to compare the XML structure and data at different stages of execution, helping to identify anomalies such as:

• Unexpected overwrites
• Missing or duplicated nodes
• Task execution order issues

Instructions to enable / disable the registry setting on the Rulerunner server machines. 

§  Close the Datacap applications, and RR server services.  

§  Under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Datacap\Rulerunner\Misc

§  Create a DWORD (32-bit) value "Dump DCO Files" and assign a value of 1.

§  Restart RR services.

§  Reproduce the issue and upload the collected rulerunner logs to the case.  

§  Disable the registry setting.

Example: TravelDocs Application

When using the TravelDocs application, enabling the RuleRunner registry setting Dump DCO Files causes the contents of the DCO (Document Control Object) files to be logged at several key points during task execution.

This includes:

• Before the task begins processing
• After the task is completed
• Any intermediate stages where the DCO is modified

This visibility is especially useful in custom applications because it often involves complex document hierarchies and multiple task stages, making it easier to trace where and how the XML content changes.

Before a task is executed

In addition to the XML logging provided by the Dump DCO Files registry setting, the RuleRunner log now includes the process ID (PID) for the thread executing each task. For example:

After identifying the Process ID (PID) in the RuleRunner logs, you can open Windows Task Manager on the RuleRunner machine to confirm which instance of RRProcessor.exe is associated with that PID.

------------------------------
Paula Prusty
------------------------------

Hi Paula,

I was happy to see this enhancement so I immediately tried it with a custom app we have in Datacap 9.1.9 IF07 but unfortunately it doesn't work for me. Searching the RRS Logs for the words "dump" and "process id" returns no hits.

I checked the registry entry and restarted the machine, but that made no difference. I have also tested with TravelDocs. What am I doing wrong?

Many thanks,

Shaun

------------------------------
Shaun McDowall

Original Message:
Sent: Tue August 12, 2025 01:48 PM
From: Paula Prusty
Subject: What's New: Datacap Rulerunner Server Services now writes out the contents of the workflow tasks and the rulerunner process ID numbers to the logs.

This enhancement offers benefits for troubleshooting, identifies reasons for breaks in the workflow and assists in root-cause analysis. 

To troubleshoot the issue where a task's XML file is overwritten with the previous task's XML file during processing by RuleRunner (RR) services in IBM Datacap, an enhanced configurable RR registry setting is available in the latest Datacap 9.1.9 fix pack.

Enabling the registry setting is diagnostic only-it does not remediate any known defects; It can in some instances, assist in isolating contributing factors by logging detailed XML content before and after task execution.

Use Case

When the RuleRunner registry setting Dump DCO Files is enabled, the contents of the task's XML file - both before and after the task is executed - are written to the RuleRunner logs.

This allows IBM Datacap developers and support teams to compare the XML structure and data at different stages of execution, helping to identify anomalies such as:

• Unexpected overwrites
• Missing or duplicated nodes
• Task execution order issues

Instructions to enable / disable the registry setting on the Rulerunner server machines. 

§  Close the Datacap applications, and RR server services.  

§  Under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Datacap\Rulerunner\Misc

§  Create a DWORD (32-bit) value "Dump DCO Files" and assign a value of 1.

§  Restart RR services.

§  Reproduce the issue and upload the collected rulerunner logs to the case.  

§  Disable the registry setting.

Example: TravelDocs Application

When using the TravelDocs application, enabling the RuleRunner registry setting Dump DCO Files causes the contents of the DCO (Document Control Object) files to be logged at several key points during task execution.

This includes:

• Before the task begins processing
• After the task is completed
• Any intermediate stages where the DCO is modified

This visibility is especially useful in custom applications because it often involves complex document hierarchies and multiple task stages, making it easier to trace where and how the XML content changes.

Before a task is executed

In addition to the XML logging provided by the Dump DCO Files registry setting, the RuleRunner log now includes the process ID (PID) for the thread executing each task. For example:

After identifying the Process ID (PID) in the RuleRunner logs, you can open Windows Task Manager on the RuleRunner machine to confirm which instance of RRProcessor.exe is associated with that PID.

------------------------------
Paula Prusty
------------------------------

Hi Paula,

I was happy to see this enhancement so I immediately tried it with a custom app we have in Datacap 9.1.9 IF07 but unfortunately it doesn't work for me. Searching the RRS Logs for the words "dump" and "process id" returns no hits.

I checked the registry entry and restarted the machine, but that made no difference. I have also tested with TravelDocs. What am I doing wrong?

Many thanks,

Shaun

------------------------------
Shaun McDowall

Original Message:
Sent: Tue August 12, 2025 01:48 PM
From: Paula Prusty
Subject: What's New: Datacap Rulerunner Server Services now writes out the contents of the workflow tasks and the rulerunner process ID numbers to the logs.

This enhancement offers benefits for troubleshooting, identifies reasons for breaks in the workflow and assists in root-cause analysis. 

To troubleshoot the issue where a task's XML file is overwritten with the previous task's XML file during processing by RuleRunner (RR) services in IBM Datacap, an enhanced configurable RR registry setting is available in the latest Datacap 9.1.9 fix pack.

Enabling the registry setting is diagnostic only-it does not remediate any known defects; It can in some instances, assist in isolating contributing factors by logging detailed XML content before and after task execution.

Use Case

When the RuleRunner registry setting Dump DCO Files is enabled, the contents of the task's XML file - both before and after the task is executed - are written to the RuleRunner logs.

This allows IBM Datacap developers and support teams to compare the XML structure and data at different stages of execution, helping to identify anomalies such as:

• Unexpected overwrites
• Missing or duplicated nodes
• Task execution order issues

Instructions to enable / disable the registry setting on the Rulerunner server machines. 

§  Close the Datacap applications, and RR server services.  

§  Under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Datacap\Rulerunner\Misc

§  Create a DWORD (32-bit) value "Dump DCO Files" and assign a value of 1.

§  Restart RR services.

§  Reproduce the issue and upload the collected rulerunner logs to the case.  

§  Disable the registry setting.

Example: TravelDocs Application

When using the TravelDocs application, enabling the RuleRunner registry setting Dump DCO Files causes the contents of the DCO (Document Control Object) files to be logged at several key points during task execution.

This includes:

• Before the task begins processing
• After the task is completed
• Any intermediate stages where the DCO is modified

This visibility is especially useful in custom applications because it often involves complex document hierarchies and multiple task stages, making it easier to trace where and how the XML content changes.

Before a task is executed

In addition to the XML logging provided by the Dump DCO Files registry setting, the RuleRunner log now includes the process ID (PID) for the thread executing each task. For example:

After identifying the Process ID (PID) in the RuleRunner logs, you can open Windows Task Manager on the RuleRunner machine to confirm which instance of RRProcessor.exe is associated with that PID.

------------------------------
Paula Prusty
------------------------------

Hi Shaun,

Yes thanks for enabling the registry.  As Duke asked I see you have enabled the registry setting.  Please can you share your rulerunner log on with full logging enabled so I can see if the task xml's contents is dumped in there.  

Hi Paula,

I was happy to see this enhancement so I immediately tried it with a custom app we have in Datacap 9.1.9 IF07 but unfortunately it doesn't work for me. Searching the RRS Logs for the words "dump" and "process id" returns no hits.

I checked the registry entry and restarted the machine, but that made no difference. I have also tested with TravelDocs. What am I doing wrong?

Many thanks,

Shaun

------------------------------
Shaun McDowall

Original Message:
Sent: Tue August 12, 2025 01:48 PM
From: Paula Prusty
Subject: What's New: Datacap Rulerunner Server Services now writes out the contents of the workflow tasks and the rulerunner process ID numbers to the logs.

This enhancement offers benefits for troubleshooting, identifies reasons for breaks in the workflow and assists in root-cause analysis. 

To troubleshoot the issue where a task's XML file is overwritten with the previous task's XML file during processing by RuleRunner (RR) services in IBM Datacap, an enhanced configurable RR registry setting is available in the latest Datacap 9.1.9 fix pack.

Enabling the registry setting is diagnostic only-it does not remediate any known defects; It can in some instances, assist in isolating contributing factors by logging detailed XML content before and after task execution.

Use Case

When the RuleRunner registry setting Dump DCO Files is enabled, the contents of the task's XML file - both before and after the task is executed - are written to the RuleRunner logs.

This allows IBM Datacap developers and support teams to compare the XML structure and data at different stages of execution, helping to identify anomalies such as:

• Unexpected overwrites
• Missing or duplicated nodes
• Task execution order issues

Instructions to enable / disable the registry setting on the Rulerunner server machines. 

§  Close the Datacap applications, and RR server services.  

§  Under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Datacap\Rulerunner\Misc

§  Create a DWORD (32-bit) value "Dump DCO Files" and assign a value of 1.

§  Restart RR services.

§  Reproduce the issue and upload the collected rulerunner logs to the case.  

§  Disable the registry setting.

Example: TravelDocs Application

When using the TravelDocs application, enabling the RuleRunner registry setting Dump DCO Files causes the contents of the DCO (Document Control Object) files to be logged at several key points during task execution.

This includes:

• Before the task begins processing
• After the task is completed
• Any intermediate stages where the DCO is modified

This visibility is especially useful in custom applications because it often involves complex document hierarchies and multiple task stages, making it easier to trace where and how the XML content changes.

Before a task is executed

In addition to the XML logging provided by the Dump DCO Files registry setting, the RuleRunner log now includes the process ID (PID) for the thread executing each task. For example:

After identifying the Process ID (PID) in the RuleRunner logs, you can open Windows Task Manager on the RuleRunner machine to confirm which instance of RRProcessor.exe is associated with that PID.

------------------------------
Paula Prusty
------------------------------

Hi Paula,

I was happy to see this enhancement so I immediately tried it with a custom app we have in Datacap 9.1.9 IF07 but unfortunately it doesn't work for me. Searching the RRS Logs for the words "dump" and "process id" returns no hits.

I checked the registry entry and restarted the machine, but that made no difference. I have also tested with TravelDocs. What am I doing wrong?

Many thanks,

Shaun

------------------------------
Shaun McDowall

Original Message:
Sent: Tue August 12, 2025 01:48 PM
From: Paula Prusty
Subject: What's New: Datacap Rulerunner Server Services now writes out the contents of the workflow tasks and the rulerunner process ID numbers to the logs.

This enhancement offers benefits for troubleshooting, identifies reasons for breaks in the workflow and assists in root-cause analysis. 

To troubleshoot the issue where a task's XML file is overwritten with the previous task's XML file during processing by RuleRunner (RR) services in IBM Datacap, an enhanced configurable RR registry setting is available in the latest Datacap 9.1.9 fix pack.

Enabling the registry setting is diagnostic only-it does not remediate any known defects; It can in some instances, assist in isolating contributing factors by logging detailed XML content before and after task execution.

Use Case

When the RuleRunner registry setting Dump DCO Files is enabled, the contents of the task's XML file - both before and after the task is executed - are written to the RuleRunner logs.

This allows IBM Datacap developers and support teams to compare the XML structure and data at different stages of execution, helping to identify anomalies such as:

• Unexpected overwrites
• Missing or duplicated nodes
• Task execution order issues

Instructions to enable / disable the registry setting on the Rulerunner server machines. 

§  Close the Datacap applications, and RR server services.  

§  Under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Datacap\Rulerunner\Misc

§  Create a DWORD (32-bit) value "Dump DCO Files" and assign a value of 1.

§  Restart RR services.

§  Reproduce the issue and upload the collected rulerunner logs to the case.  

§  Disable the registry setting.

Example: TravelDocs Application

When using the TravelDocs application, enabling the RuleRunner registry setting Dump DCO Files causes the contents of the DCO (Document Control Object) files to be logged at several key points during task execution.

This includes:

• Before the task begins processing
• After the task is completed
• Any intermediate stages where the DCO is modified

This visibility is especially useful in custom applications because it often involves complex document hierarchies and multiple task stages, making it easier to trace where and how the XML content changes.

Before a task is executed

In addition to the XML logging provided by the Dump DCO Files registry setting, the RuleRunner log now includes the process ID (PID) for the thread executing each task. For example:

After identifying the Process ID (PID) in the RuleRunner logs, you can open Windows Task Manager on the RuleRunner machine to confirm which instance of RRProcessor.exe is associated with that PID.

------------------------------
Paula Prusty
------------------------------

My bad, it needs to be decimal.

Hi Paula,

I was happy to see this enhancement so I immediately tried it with a custom app we have in Datacap 9.1.9 IF07 but unfortunately it doesn't work for me. Searching the RRS Logs for the words "dump" and "process id" returns no hits.

I checked the registry entry and restarted the machine, but that made no difference. I have also tested with TravelDocs. What am I doing wrong?

Many thanks,

Shaun

------------------------------
Shaun McDowall

Original Message:
Sent: Tue August 12, 2025 01:48 PM
From: Paula Prusty
Subject: What's New: Datacap Rulerunner Server Services now writes out the contents of the workflow tasks and the rulerunner process ID numbers to the logs.

This enhancement offers benefits for troubleshooting, identifies reasons for breaks in the workflow and assists in root-cause analysis. 

To troubleshoot the issue where a task's XML file is overwritten with the previous task's XML file during processing by RuleRunner (RR) services in IBM Datacap, an enhanced configurable RR registry setting is available in the latest Datacap 9.1.9 fix pack.

Enabling the registry setting is diagnostic only-it does not remediate any known defects; It can in some instances, assist in isolating contributing factors by logging detailed XML content before and after task execution.

Use Case

When the RuleRunner registry setting Dump DCO Files is enabled, the contents of the task's XML file - both before and after the task is executed - are written to the RuleRunner logs.

This allows IBM Datacap developers and support teams to compare the XML structure and data at different stages of execution, helping to identify anomalies such as:

• Unexpected overwrites
• Missing or duplicated nodes
• Task execution order issues

Instructions to enable / disable the registry setting on the Rulerunner server machines. 

§  Close the Datacap applications, and RR server services.  

§  Under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Datacap\Rulerunner\Misc

§  Create a DWORD (32-bit) value "Dump DCO Files" and assign a value of 1.

§  Restart RR services.

§  Reproduce the issue and upload the collected rulerunner logs to the case.  

§  Disable the registry setting.

Example: TravelDocs Application

When using the TravelDocs application, enabling the RuleRunner registry setting Dump DCO Files causes the contents of the DCO (Document Control Object) files to be logged at several key points during task execution.

This includes:

• Before the task begins processing
• After the task is completed
• Any intermediate stages where the DCO is modified

This visibility is especially useful in custom applications because it often involves complex document hierarchies and multiple task stages, making it easier to trace where and how the XML content changes.

Before a task is executed

In addition to the XML logging provided by the Dump DCO Files registry setting, the RuleRunner log now includes the process ID (PID) for the thread executing each task. For example:

After identifying the Process ID (PID) in the RuleRunner logs, you can open Windows Task Manager on the RuleRunner machine to confirm which instance of RRProcessor.exe is associated with that PID.

------------------------------
Paula Prusty
------------------------------

This enhancement offers benefits for troubleshooting, identifies reasons for breaks in the workflow and assists in root-cause analysis. 

To troubleshoot the issue where a task's XML file is overwritten with the previous task's XML file during processing by RuleRunner (RR) services in IBM Datacap, an enhanced configurable RR registry setting is available in the latest Datacap 9.1.9 fix pack.

Enabling the registry setting is diagnostic only-it does not remediate any known defects; It can in some instances, assist in isolating contributing factors by logging detailed XML content before and after task execution.

Use Case

When the RuleRunner registry setting Dump DCO Files is enabled, the contents of the task's XML file - both before and after the task is executed - are written to the RuleRunner logs.

This allows IBM Datacap developers and support teams to compare the XML structure and data at different stages of execution, helping to identify anomalies such as:

• Unexpected overwrites
• Missing or duplicated nodes
• Task execution order issues

Instructions to enable / disable the registry setting on the Rulerunner server machines. 

§  Close the Datacap applications, and RR server services.  

§  Under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Datacap\Rulerunner\Misc

§  Create a DWORD (32-bit) value "Dump DCO Files" and assign a value of 1.

§  Restart RR services.

§  Reproduce the issue and upload the collected rulerunner logs to the case.  

§  Disable the registry setting.

Example: TravelDocs Application

When using the TravelDocs application, enabling the RuleRunner registry setting Dump DCO Files causes the contents of the DCO (Document Control Object) files to be logged at several key points during task execution.

This includes:

• Before the task begins processing
• After the task is completed
• Any intermediate stages where the DCO is modified

This visibility is especially useful in custom applications because it often involves complex document hierarchies and multiple task stages, making it easier to trace where and how the XML content changes.

Before a task is executed

In addition to the XML logging provided by the Dump DCO Files registry setting, the RuleRunner log now includes the process ID (PID) for the thread executing each task. For example:

After identifying the Process ID (PID) in the RuleRunner logs, you can open Windows Task Manager on the RuleRunner machine to confirm which instance of RRProcessor.exe is associated with that PID.