IBM Hourglass

Name: IBM Hourglass
Brand: IBM

IBM HourGlass is a system-level clock and date simulation tool for IBM Z (z/OS) that returns simulated date/time values to applications without modifying application code, enabling controlled testing of end-of-period, time-zone, and future-date scenarios.

Est 1911|Valuation $213.9B|Raised $85.3B

LinkedIn 19.8M|Website|Web traffic 18.9M|FTEs 287,000|HQ Armonk, NY

Published Aug 24, 2026

01Common complaints

1. Cross-platform time simulation requirements - If applications and workflows span z/OS and distributed systems and synchronized virtual time is required across platforms, a cross-platform time-simulation product may be more appropriate. 2. Feasible code refactoring to abstract time - When the organization can refactor applications to centralize time calls behind an interface or use dependency injection/time providers, system-level time interception may be avoidable. This approach may be impractical for large COBOL estates but can be viable for modernized components. 3. Need for transparent public pricing and abundant peer reviews - HourGlass is niche and quote-based, with limited presence on mainstream review platforms. Organizations requiring extensive third-party validation may find evaluation more difficult. 4. Requirement for a broad DevOps testing platform - HourGlass addresses a specific need (date/time simulation). Organizations prioritizing end-to-end automated testing, pipeline integration, and test virtualization should evaluate integrated testing suites and consider time simulation as a complementary capability.

Deal disqualifiers (poor fit)

No significant z/OS footprint
Predominantly distributed or microservices environments requiring synchronized time simulation across platforms
Organizational risk posture that excludes system-level tooling in shared environments

Publicly documented limitations and constraints

Platform constraint: Core product is z/OS-only.
Prerequisites and low-level requirements: APF authorization; memory usage in ECSA; supported z/OS and middleware versions.
Compatibility currency: IBM maintenance notes indicate specific PTF requirements for certain middleware versions, reinforcing the need for ongoing currency management.

Roadmap and future features

No clear public roadmap with dates was found for HourGlass.
IBM’s ideas portal contains enhancement requests (for example, requests for program interfaces), but these are not equivalent to a committed roadmap.

Scale limitations

Not explicitly quantified in public materials; likely constrained by standard z/OS operational boundaries and considerations related to time interception in shared environments.

02Why they buy

Features referenced in IBM documentation

- IBM documentation indicates that HourGlass can simulate dates and times for many workloads without requiring application code changes. - It offers an alternative to dedicated test LPARs and frequent IPLs for the purpose of date/time testing. - The product integrates with z/OS ecosystem components (CICS, IMS, Db2) and provides control elements and a repository for managing simulations. - IBM documentation references simulation up to the end of year 2099 on supported z/OS levels.

Where competitors may have an advantage

Softdate emphasizes broader operating-system coverage and cross-platform time synchronization, which may suit hybrid architectures.
Modern testing suites (e.g., BMC AMI DevX Total Test) focus on CI/CD integration and broader automated testing capabilities and may be prioritized by teams seeking comprehensive testing platforms.

03Field reports

Reality check on review availability

IBM HourGlass is a specialized mainframe tool and does not appear to have meaningful review coverage on mainstream SaaS review sites (G2, TrustRadius, Capterra, PeerSpot) under this exact product name. Searches returned other IBM products rather than HourGlass.

Community / practitioner references (proxy evidence)

Because direct review pages are scarce, this analysis relies on practitioner references where HourGlass appears as part of real-world mainframe workflows. Practitioner reference (usage context): - A COBOL career discussion references performing “hours of Hourglass testing,” implying date/time simulation testing is a known activity in legacy/mainframe environments (example: community discussion thread). Third-party product listings and reseller summaries describe the product with claims consistent with IBM’s documentation: control center, security controls by programmer/job group, the ability to run simultaneous tests with different system dates, and support for CICS/IMS. These listings do not constitute independent user validation but indicate common use cases.

What customers likely choose it for (inferred from vendor docs and practitioner context)

Testing hard date boundaries (month end, year end, time zone differences).
Avoiding dedicated LPARs or frequent IPLs that disrupt shared environments.
Coordinating time simulation across subsystems such as CICS, IMS, and Db2.

Why some customers might avoid it (inferred)

Limited public peer reviews and a niche profile may lead teams to develop internal abstractions for time or choose cross-platform suites for multi-environment needs.
Some organizations may avoid system-level time interception due to governance or operational risk concerns.

Availability of case studies

No public, detailed IBM-published customer case studies for HourGlass with named customers and quantified metrics were located during this research.

What IBM publishes (documentation-based scenarios)

IBM documentation and presentations describe scenarios such as:

Testing time-sensitive code without dedicated LPARs or frequent IPLs.
Supporting major subsystems (Db2, IMS, CICS, COBOL) and sysplex synchronization (described in older release materials).

Critical evaluation: These are vendor-authored materials and do not provide independently verified ROI or quantified defect-reduction metrics.

04Best fit

Company sizes

Typical fit: Large enterprises operating IBM Z in production.
Practical range: Enterprise-scale organizations with substantial headcount and significant revenues, though smaller regulated institutions running IBM Z can also fit.

Industries

Financial services (banking, payments)
Insurance
Government
Healthcare payers and providers with legacy systems
Retail, airlines, and transportation with high-volume transaction processing

Roles and personas

Decision makers: IBM Z platform owners, mainframe engineering leadership, QA and test leadership
Influencers: CICS/IMS/Db2 administrators, z/OS systems programmers, release managers
End users: Test engineers executing batch and online test suites; developers validating date-bound logic

Pain points addressed

Reducing production incidents arising from date/time logic (billing cycles, interest calculations, eligibility windows, batch cutoffs)
Reducing the need for dedicated test partitions or LPARs solely for time testing
Increasing confidence in deployments around critical calendar events

Qualification criteria (good fit)

Significant portfolio of time-sensitive z/OS applications that use system date/time services
Need to test multiple date/time scenarios quickly and repeatedly
Adequate change-control discipline and platform skills to govern time simulation

05The pitch

What the product does (core value proposition)

IBM HourGlass is a system-level clock/date simulation tool for IBM Z (z/OS) that enables teams to test time-sensitive mainframe applications by returning simulated dates and times to applications without changing application code or creating a separate environment. IBM describes it as a tool to reduce risk in scenarios such as end-of-month, end-of-quarter, time zone transitions, and future-date testing. IBM’s product documentation states: - Simulation of arbitrary date/time values (documentation references support for dates well into the long-term future on supported z/OS levels). - Avoiding operational steps such as re-IPLing or modifying runtime JCL for many scenarios. - A control-center style interface and control elements for managing test scenarios.

Target market and positioning

- Primary buyers/users: Mainframe platform teams; QA and testing teams supporting z/OS workloads; operations teams coordinating test windows; CICS/IMS/Db2 middleware administrators. - Typical environment: Enterprises with long-lived z/OS applications (financial services, insurance, government, healthcare, retail, etc.) where time-based logic is high-risk. - Positioning: A specialized z/OS testing utility for date/time simulation testing, intended to support reliability testing of mission-critical applications.

Get a comprehensive analysis of IBM Hourglass including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Aug 24, 2026

01Common complaints

Cross-platform time simulation requirements
- If applications and workflows span z/OS and distributed systems and synchronized virtual time is required across platforms, a cross-platform time-simulation product may be more appropriate.
Feasible code refactoring to abstract time
- When the organization can refactor applications to centralize time calls behind an interface or use dependency injection/time providers, system-level time interception may be avoidable. This approach may be impractical for large COBOL estates but can be viable for modernized components.
Need for transparent public pricing and abundant peer reviews
- HourGlass is niche and quote-based, with limited presence on mainstream review platforms. Organizations requiring extensive third-party validation may find evaluation more difficult.
Requirement for a broad DevOps testing platform
- HourGlass addresses a specific need (date/time simulation). Organizations prioritizing end-to-end automated testing, pipeline integration, and test virtualization should evaluate integrated testing suites and consider time simulation as a complementary capability.

Deal disqualifiers (poor fit)

No significant z/OS footprint
Predominantly distributed or microservices environments requiring synchronized time simulation across platforms
Organizational risk posture that excludes system-level tooling in shared environments

Publicly documented limitations and constraints

Platform constraint: Core product is z/OS-only.
Prerequisites and low-level requirements: APF authorization; memory usage in ECSA; supported z/OS and middleware versions.
Compatibility currency: IBM maintenance notes indicate specific PTF requirements for certain middleware versions, reinforcing the need for ongoing currency management.

Roadmap and future features

No clear public roadmap with dates was found for HourGlass.
IBM’s ideas portal contains enhancement requests (for example, requests for program interfaces), but these are not equivalent to a committed roadmap.

Scale limitations

Not explicitly quantified in public materials; likely constrained by standard z/OS operational boundaries and considerations related to time interception in shared environments.

02Why they buy

Features referenced in IBM documentation

IBM documentation indicates that HourGlass can simulate dates and times for many workloads without requiring application code changes.
It offers an alternative to dedicated test LPARs and frequent IPLs for the purpose of date/time testing.
The product integrates with z/OS ecosystem components (CICS, IMS, Db2) and provides control elements and a repository for managing simulations.
IBM documentation references simulation up to the end of year 2099 on supported z/OS levels.

Where competitors may have an advantage

Softdate emphasizes broader operating-system coverage and cross-platform time synchronization, which may suit hybrid architectures.
Modern testing suites (e.g., BMC AMI DevX Total Test) focus on CI/CD integration and broader automated testing capabilities and may be prioritized by teams seeking comprehensive testing platforms.

03Field reports

Reality check on review availability

Community / practitioner references (proxy evidence)

Because direct review pages are scarce, this analysis relies on practitioner references where HourGlass appears as part of real-world mainframe workflows.

Practitioner reference (usage context):

A COBOL career discussion references performing “hours of Hourglass testing,” implying date/time simulation testing is a known activity in legacy/mainframe environments (example: community discussion thread).

Third-party product listings and reseller summaries describe the product with claims consistent with IBM’s documentation: control center, security controls by programmer/job group, the ability to run simultaneous tests with different system dates, and support for CICS/IMS. These listings do not constitute independent user validation but indicate common use cases.

What customers likely choose it for (inferred from vendor docs and practitioner context)

Testing hard date boundaries (month end, year end, time zone differences).
Avoiding dedicated LPARs or frequent IPLs that disrupt shared environments.
Coordinating time simulation across subsystems such as CICS, IMS, and Db2.

Why some customers might avoid it (inferred)

Limited public peer reviews and a niche profile may lead teams to develop internal abstractions for time or choose cross-platform suites for multi-environment needs.
Some organizations may avoid system-level time interception due to governance or operational risk concerns.

Availability of case studies

No public, detailed IBM-published customer case studies for HourGlass with named customers and quantified metrics were located during this research.

What IBM publishes (documentation-based scenarios)

IBM documentation and presentations describe scenarios such as:

Testing time-sensitive code without dedicated LPARs or frequent IPLs.
Supporting major subsystems (Db2, IMS, CICS, COBOL) and sysplex synchronization (described in older release materials).

Critical evaluation: These are vendor-authored materials and do not provide independently verified ROI or quantified defect-reduction metrics.

04Best fit

Company sizes

Typical fit: Large enterprises operating IBM Z in production.
Practical range: Enterprise-scale organizations with substantial headcount and significant revenues, though smaller regulated institutions running IBM Z can also fit.

Industries

Financial services (banking, payments)
Insurance
Government
Healthcare payers and providers with legacy systems
Retail, airlines, and transportation with high-volume transaction processing

Roles and personas

Decision makers: IBM Z platform owners, mainframe engineering leadership, QA and test leadership
Influencers: CICS/IMS/Db2 administrators, z/OS systems programmers, release managers
End users: Test engineers executing batch and online test suites; developers validating date-bound logic

Pain points addressed

Reducing production incidents arising from date/time logic (billing cycles, interest calculations, eligibility windows, batch cutoffs)
Reducing the need for dedicated test partitions or LPARs solely for time testing
Increasing confidence in deployments around critical calendar events

Qualification criteria (good fit)

Significant portfolio of time-sensitive z/OS applications that use system date/time services
Need to test multiple date/time scenarios quickly and repeatedly
Adequate change-control discipline and platform skills to govern time simulation

05The pitch

What the product does (core value proposition)

IBM’s product documentation states:

Simulation of arbitrary date/time values (documentation references support for dates well into the long-term future on supported z/OS levels).
Avoiding operational steps such as re-IPLing or modifying runtime JCL for many scenarios.
A control-center style interface and control elements for managing test scenarios.

Target market and positioning

Primary buyers/users: Mainframe platform teams; QA and testing teams supporting z/OS workloads; operations teams coordinating test windows; CICS/IMS/Db2 middleware administrators.
Typical environment: Enterprises with long-lived z/OS applications (financial services, insurance, government, healthcare, retail, etc.) where time-based logic is high-risk.
Positioning: A specialized z/OS testing utility for date/time simulation testing, intended to support reliability testing of mission-critical applications.

Get a comprehensive analysis of IBM Hourglass including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →