CA Test Data Manager

Broadcom documentation continues to identify CA Test Data Manager and current 4.11 support material. Its documented workflows include profiling, data masking, subset extraction and test-data provisioning; synthetic generation is described in vendor collateral.

Sources reviewed

When should you consider it?

Best suited to established enterprise and mainframe test-data workflows that need relationally intact subsets, masking and controlled provisioning.

Editorial fit assessment based on the sources below.

What are the limits?

Publicly reviewed feature descriptions span product versions and older collateral; validate supported connectors, components and entitlement for the specific installed release before making compatibility claims.

Which capabilities are documented?

Synthetic generationMainframe collateral · verify edition

De-identification / maskingDocumented · source

Subsetting / subset planningDocumented · source

Data virtualizationNot verified

Seeded replay, scopedNot verified

Documented means a cited vendor source describes this scoped capability. Not verified means the reviewed evidence cannot establish it. Neither is a hands-on test result.

How is it deployed and licensed?

Vendor material describes a central repository/web portal plus native execution engines; a mainframe edition executes tasks in a mainframe runtime. Exact architecture depends on edition and release.

No public list price was found in the reviewed vendor material; licensing/entitlements should be confirmed with Broadcom.

Sources and scope

CA Test Data Manager (Data Finder / Grid Tools)
Current Broadcom knowledge article references TDM Portal 4.11 and clarifies component-specific file masking behavior.
Source checked: 2026-10-01
CA Test Data Manager Key Scenarios
Vendor-described discovery/profiling, masking engines, referential integrity, subset extraction and test provisioning; service/message virtualization.
Source checked: 2026-10-01
CA Test Data Manager for the Mainframe
Mainframe runtime, masking/subsetting, synthetic generation and repository provisioning in vendor overview.
Source checked: 2026-10-01

What should you verify in a proof of concept?

Your database version, schema constraints and target formats.
The exact product, edition, deployment and license entitlements.
Your business assertions and the meaning of repeatability for your output.
A failed run, cleanup and a repeat run on controlled inputs.