Broadcom Mainframe Databases

Name: Broadcom Mainframe Databases
Brand: Broadcom
Rating: 3.7 (10 reviews)

Leader

Broadcom provides semiconductors and infrastructure software for global organizations’ complex, mission-critical needs

Est 1961|Valuation $1764B

LinkedIn 446K|Website|Web traffic 4.0M|FTEs 33,000|HQ Palo Alto, California, US

Published Oct 9, 2026

01Common complaints

1. Net-new application development where mainframe DBMS choice is flexible - If an organization is not already using Datacom/IDMS, standardizing on IBM Db2 for z/OS may reduce long-term skills risk and improve ecosystem alignment. 2. Organizations pursuing mainframe exit - If the strategic objective is platform exit, substantial investment in Datacom/IDMS modernization may not align with migration goals; prioritize migration approaches (CDC/replication, data virtualization) and application refactoring. 3. Teams that require a SaaS-like vendor experience for procurement and support - If procurement, entitlement, and support portal friction is a major operational concern, buyers should stress-test vendor processes early (for example, trial access, support SLAs, entitlement workflows). Public discussions suggest these processes can be challenging in parts of the broader Broadcom portfolio. 4. DevOps-first Db2 schema automation where another vendor is entrenched - If an organization already uses BMC AMI DevOps for Db2 or comparable CI/CD integrations, switching to Broadcom’s tooling may not justify disruption without clearly demonstrated migration benefits.

Deal disqualifiers

Organizations that require transparent, self-serve pricing and rapid procurement.
Organizations lacking mainframe operational maturity where a lightweight mainframe DBMS deployment is not practical.

Publicly acknowledged limitations / documentation-driven constraints

SOC reports for Datacom: Broadcom knowledge-base materials indicate SOC reports are not provided for some mainframe products, which can present audit friction.
Lifecycle and compatibility data behind login: Detailed lifecycle dates (GA/EOS) and comprehensive compatibility matrices may require access to Broadcom support portals, which can slow diligence.

Scale limitations

No public definitive scale breakpoints were identified. Reviews suggest Datacom has been used with large datasets; buyers should validate scalability with workload-relevant benchmarks.

Roadmap visibility

Roadmaps and detailed product plans are often shared in Broadcom events and user-group sessions; detailed commitments are not always publicly published.

02Why they buy

Distinctive characteristics supported by available evidence

Stability and long operational usage: multiple user reviews and community commentary describe long-term operational deployments and continuity.
API-based modernization options: Broadcom documents a strategy for exposing mainframe capabilities through REST APIs and integration portals, enabling hybrid access patterns.

Areas where competitors have advantages

Db2 engine ecosystem: IBM Db2 for z/OS has broader native platform integration and an extensive skills ecosystem.
DevOps and change automation: Some competitors emphasize CI/CD integrations and governance features for schema change automation.

Why customers chose Broadcom mainframe databases/tooling

Common drivers reported in reviews and in public positioning include:

Perceived stability and long operational history.
Ability to handle high-volume transaction processing in regulated industries.
Installed-base continuity; some organizations retain these products because of historical use.

03Field reports

Note: Mainframe DBMS products typically have fewer public reviews than mainstream cloud software. Available reviews tend to come from long-tenured users.

Review platforms (G2, PeerSpot) — positives

On G2, some reviewers characterized Datacom as particularly valuable, citing reliability, scalability, and performance for large workloads and noting transaction-processing capability.
PeerSpot reviews emphasize perceived product reliability, scalability (including support for large tables), and long-term operational stability; reviewers report being able to implement requested functionality without major database incidents.

Review platforms — negatives / concerns

- G2 reviewer critiques summarize complexity, substantial costs associated with mainframe environments, resource intensity, and concerns about vendor changes (acquisitions/mergers). These summaries are directional and should be validated with primary reviews. - PeerSpot reviewers identify areas for improvement such as integration with open systems, modernization and security auditing features, and operational issues like installation sizing guidance that did not match some real-world deployments.

Community/social sentiment (Reddit) — support & vendor friction

While not always specific to Datacom/IDMS, community sentiment about Broadcom in system administration communities includes negative reports related to licensing and support experiences following acquisitions. Examples include complaints about portal access, entitlement delays, and support responsiveness. Some users report positive support interactions, but recurring reports of delays and bureaucratic processes could affect procurement risk perception. Interpretation caution: Commentary about other vendors and broader Broadcom portfolio experiences may not directly reflect Mainframe Software Division support quality, but they can influence buyer risk assessments.

Why some customers leave or avoid

Application modernization and platform exit are common structural reasons to move away from Datacom/IDMS; replatforming typically requires extensive application re-engineering rather than simple database migration.
Vendor and process friction reported in communities—such as licensing and renewals complexity and support portal issues—are cited as procurement concerns.

Vendor-published modernization and automation examples

Broadcom publishes examples and use cases demonstrating Db2 tooling and modernization patterns: - Database Analyzer for Db2 for z/OS is presented as automating utility scheduling and execution using Db2 Real-Time Statistics to reduce manual work. The described benefits are vendor-authored and not independently verified in public materials. - Broadcom’s Mainframe Integration Portal and REST API strategy are described as a modernization approach for exposing mainframe capabilities through centralized APIs and integrations with tooling such as Zowe. Critical evaluation: These examples are consistent with plausible operational improvements, but hard metrics (for example, verified time saved, CPU reduction, or incident reduction) are generally not independently validated in vendor-published content. Buyers should request primary metrics and validation relevant to their specific workloads.

Analyst / commissioned metrics caution

Broadcom’s "Mainframe Insights" pages include reported metrics (for example, specific percentage improvements) attributed to commissioned research. Treat such figures as vendor-supported claims: use them as hypotheses and request methodology, sample size, and relevance to Datacom/IDMS specifically.

04Best fit

Company size

Typically very large enterprises (organizations ranging from large enterprises to those with tens of thousands of employees), and government agencies where mainframe systems are core infrastructure.

Industries

Financial services (banking and insurance)
Telecommunications
High-transaction retail
Government and public sector

Roles and personas

Decision makers: mainframe platform owners, enterprise architects, CIO/CTO organizations, procurement
End users: mainframe DBAs (Datacom/IDMS/Db2), systems programmers, application teams (COBOL/PL/I/Assembler), security and audit teams

Pain points addressed

Maintaining mission-critical workload stability
Minimizing downtime and improving operational automation
Enabling hybrid access to mainframe data via standardized interfaces (for example, REST APIs)

Great-fit qualification criteria

Organizations already running Datacom and/or IDMS that intend to modernize access and operations without full replatforming.
Organizations running Db2 for z/OS seeking vendor tooling aligned with Broadcom’s ecosystem and tooling integrations.

05The pitch

What the product does (core value proposition)

"Broadcom Mainframe Databases" is a portfolio label rather than a single SKU; it generally refers to Broadcom’s mainframe database engines together with associated database tooling. The portfolio commonly includes: - Datacom / Datacom/DB (formerly CA Datacom/DB) — a proprietary relational DBMS used as a system-of-record on IBM mainframes (z/OS and z/VSE). Broadcom describes Datacom as a database designed for high performance and availability for large, long-lived enterprise workloads, with modernization features such as SQL, server connectivity, and REST APIs. - IDMS (CA IDMS / rebranded as IDMS) — a long-running mainframe database family supporting both relational SQL and network (CODASYL) navigational DML, with an integrated data dictionary and application server/TP monitor capabilities. - Database tooling for IBM Db2 for z/OS — Broadcom sells Database Management Solutions for Db2 for z/OS (and sub-suites like admin/utility tooling), focused on administration, performance monitoring, schema management, and backup/recovery automation, increasingly via web UIs, REST APIs, and VS Code extensions. Broadcom's stated modernization goals for this portfolio include: - Continued operational stability for mission-critical transaction processing. - Integration between mainframe systems and hybrid environments via REST APIs and standardized tooling (for example, Zowe ecosystem integrations).

Target market and market positioning

Primary buyers: Large enterprises and public sector organizations with existing mainframe estates (banks, insurers, telcos, government agencies) running long-lived applications.
Positioning: Broadcom’s public materials emphasize maintaining mainframe system-of-record deployments while providing modernization paths through APIs and newer management interfaces rather than complete replacement.

Get a comprehensive analysis of Broadcom Mainframe Databases including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 9, 2026

01Common complaints

Net-new application development where mainframe DBMS choice is flexible
- If an organization is not already using Datacom/IDMS, standardizing on IBM Db2 for z/OS may reduce long-term skills risk and improve ecosystem alignment.
Organizations pursuing mainframe exit
- If the strategic objective is platform exit, substantial investment in Datacom/IDMS modernization may not align with migration goals; prioritize migration approaches (CDC/replication, data virtualization) and application refactoring.
Teams that require a SaaS-like vendor experience for procurement and support
- If procurement, entitlement, and support portal friction is a major operational concern, buyers should stress-test vendor processes early (for example, trial access, support SLAs, entitlement workflows). Public discussions suggest these processes can be challenging in parts of the broader Broadcom portfolio.
DevOps-first Db2 schema automation where another vendor is entrenched
- If an organization already uses BMC AMI DevOps for Db2 or comparable CI/CD integrations, switching to Broadcom’s tooling may not justify disruption without clearly demonstrated migration benefits.

Deal disqualifiers

Organizations that require transparent, self-serve pricing and rapid procurement.
Organizations lacking mainframe operational maturity where a lightweight mainframe DBMS deployment is not practical.

Publicly acknowledged limitations / documentation-driven constraints

SOC reports for Datacom: Broadcom knowledge-base materials indicate SOC reports are not provided for some mainframe products, which can present audit friction.
Lifecycle and compatibility data behind login: Detailed lifecycle dates (GA/EOS) and comprehensive compatibility matrices may require access to Broadcom support portals, which can slow diligence.

Scale limitations

No public definitive scale breakpoints were identified. Reviews suggest Datacom has been used with large datasets; buyers should validate scalability with workload-relevant benchmarks.

Roadmap visibility

Roadmaps and detailed product plans are often shared in Broadcom events and user-group sessions; detailed commitments are not always publicly published.

02Why they buy

Distinctive characteristics supported by available evidence

Stability and long operational usage: multiple user reviews and community commentary describe long-term operational deployments and continuity.
API-based modernization options: Broadcom documents a strategy for exposing mainframe capabilities through REST APIs and integration portals, enabling hybrid access patterns.

Areas where competitors have advantages

Db2 engine ecosystem: IBM Db2 for z/OS has broader native platform integration and an extensive skills ecosystem.
DevOps and change automation: Some competitors emphasize CI/CD integrations and governance features for schema change automation.

Why customers chose Broadcom mainframe databases/tooling

Common drivers reported in reviews and in public positioning include:

Perceived stability and long operational history.
Ability to handle high-volume transaction processing in regulated industries.
Installed-base continuity; some organizations retain these products because of historical use.

03Field reports

Note: Mainframe DBMS products typically have fewer public reviews than mainstream cloud software. Available reviews tend to come from long-tenured users.

Review platforms (G2, PeerSpot) — positives

On G2, some reviewers characterized Datacom as particularly valuable, citing reliability, scalability, and performance for large workloads and noting transaction-processing capability.
PeerSpot reviews emphasize perceived product reliability, scalability (including support for large tables), and long-term operational stability; reviewers report being able to implement requested functionality without major database incidents.

Review platforms — negatives / concerns

G2 reviewer critiques summarize complexity, substantial costs associated with mainframe environments, resource intensity, and concerns about vendor changes (acquisitions/mergers). These summaries are directional and should be validated with primary reviews.
PeerSpot reviewers identify areas for improvement such as integration with open systems, modernization and security auditing features, and operational issues like installation sizing guidance that did not match some real-world deployments.

Community/social sentiment (Reddit) — support & vendor friction

Interpretation caution: Commentary about other vendors and broader Broadcom portfolio experiences may not directly reflect Mainframe Software Division support quality, but they can influence buyer risk assessments.

Why some customers leave or avoid

Application modernization and platform exit are common structural reasons to move away from Datacom/IDMS; replatforming typically requires extensive application re-engineering rather than simple database migration.
Vendor and process friction reported in communities—such as licensing and renewals complexity and support portal issues—are cited as procurement concerns.

Vendor-published modernization and automation examples

Broadcom publishes examples and use cases demonstrating Db2 tooling and modernization patterns:

Database Analyzer for Db2 for z/OS is presented as automating utility scheduling and execution using Db2 Real-Time Statistics to reduce manual work. The described benefits are vendor-authored and not independently verified in public materials.
Broadcom’s Mainframe Integration Portal and REST API strategy are described as a modernization approach for exposing mainframe capabilities through centralized APIs and integrations with tooling such as Zowe.

Critical evaluation: These examples are consistent with plausible operational improvements, but hard metrics (for example, verified time saved, CPU reduction, or incident reduction) are generally not independently validated in vendor-published content. Buyers should request primary metrics and validation relevant to their specific workloads.

Analyst / commissioned metrics caution

04Best fit

Company size

Typically very large enterprises (organizations ranging from large enterprises to those with tens of thousands of employees), and government agencies where mainframe systems are core infrastructure.

Industries

Financial services (banking and insurance)
Telecommunications
High-transaction retail
Government and public sector

Roles and personas

Decision makers: mainframe platform owners, enterprise architects, CIO/CTO organizations, procurement
End users: mainframe DBAs (Datacom/IDMS/Db2), systems programmers, application teams (COBOL/PL/I/Assembler), security and audit teams

Pain points addressed

Maintaining mission-critical workload stability
Minimizing downtime and improving operational automation
Enabling hybrid access to mainframe data via standardized interfaces (for example, REST APIs)

Great-fit qualification criteria

Organizations already running Datacom and/or IDMS that intend to modernize access and operations without full replatforming.
Organizations running Db2 for z/OS seeking vendor tooling aligned with Broadcom’s ecosystem and tooling integrations.

05The pitch

What the product does (core value proposition)

Datacom / Datacom/DB (formerly CA Datacom/DB) — a proprietary relational DBMS used as a system-of-record on IBM mainframes (z/OS and z/VSE). Broadcom describes Datacom as a database designed for high performance and availability for large, long-lived enterprise workloads, with modernization features such as SQL, server connectivity, and REST APIs.
IDMS (CA IDMS / rebranded as IDMS) — a long-running mainframe database family supporting both relational SQL and network (CODASYL) navigational DML, with an integrated data dictionary and application server/TP monitor capabilities.
Database tooling for IBM Db2 for z/OS — Broadcom sells Database Management Solutions for Db2 for z/OS (and sub-suites like admin/utility tooling), focused on administration, performance monitoring, schema management, and backup/recovery automation, increasingly via web UIs, REST APIs, and VS Code extensions.

Broadcom's stated modernization goals for this portfolio include:

Continued operational stability for mission-critical transaction processing.
Integration between mainframe systems and hybrid environments via REST APIs and standardized tooling (for example, Zowe ecosystem integrations).

Target market and market positioning

Primary buyers: Large enterprises and public sector organizations with existing mainframe estates (banks, insurers, telcos, government agencies) running long-lived applications.
Positioning: Broadcom’s public materials emphasize maintaining mainframe system-of-record deployments while providing modernization paths through APIs and newer management interfaces rather than complete replacement.

Get a comprehensive analysis of Broadcom Mainframe Databases including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →