In a Parallel Sysplex, the Sysplex Timer (now replaced by Server Time Protocol – STP) ensures that all systems in the complex share a single, tightly synchronized time source, so distributed operations remain logically consistent and correctly ordered.

This is essential because in a multi-system environment, even tiny time differences can break:

• transaction ordering
• lock timeout behavior
• log sequencing
• recovery consistency

1. Core idea: a single “authoritative time”

Sysplex time synchronization ensures:

All z/OS systems behave as if they share the same clock, even though they run on separate physical processors.

This is achieved using:

• Sysplex Timer (legacy)
• STP – Server Time Protocol (modern IBM Z)

2. Why consistency depends on time

Many sysplex functions depend on time ordering:

• Database commit timestamps (DB2)
• Log sequence ordering (RRS, IMS, CICS)
• Lock timeout expiration
• Audit trails and security logs
• Recovery point-in-time consistency

👉 If clocks differ across nodes:

• “future” and “past” events could appear out of order
• recovery logs become inconsistent
• distributed transactions break

3. How synchronization works (STP model)

Modern IBM Z uses STP (Server Time Protocol) instead of the old external Sysplex Timer box.

A. Time hierarchy

STP creates a hierarchy:

• Time Source (stratum 1): GPS or atomic clock reference
• Primary time server (Stratum 2)
• Backup time server
• Client systems (LPARs)

B. Continuous clock adjustment

Each system:

• measures offset from master clock
• applies small adjustments continuously
• avoids sudden jumps in time

👉 This preserves application stability.

4. Mechanism of synchronization

Step 1: Time exchange

Systems periodically exchange:

• current time
• delay/latency estimates

Step 2: Offset calculation

STP computes:

• difference between local clock and master clock
• network delay compensation

Step 3: Gradual correction (slewing)

Instead of jumping time:

• clock speed is slightly adjusted
• time is slowly corrected

👉 prevents:

• transaction rollback confusion
• log sequence disruption

Step 4: Convergence

All systems converge to same time within microsecond accuracy.

5. Role in consistency mechanisms

A. Transaction ordering

Distributed transactions rely on timestamps:

• commit timestamps must be globally ordered
• ensures correct serialization across DB2/CICS/IMS

B. Lock timeout correctness

If clocks differ:

• one system might think lock expired earlier/later incorrectly

With STP:

• all systems agree on timeout boundaries

C. Log sequence integrity

Logs across sysplex must be consistent:

• recovery depends on correct ordering
• STP ensures timestamps are monotonic across systems

D. Recovery and restart consistency

During failure recovery:

• timestamps determine last committed state
• ensures correct roll-forward/rollback decisions

6. Key consistency guarantee: monotonic time

STP ensures:

Time never moves backward across sysplex systems.

This is critical because:

• backward time breaks log ordering
• causes duplicate or missing transaction interpretation

7. Interaction with Coupling Facility (CF)

Although CF handles:

• locks
• cache coherency
• shared structures

STP ensures:

• timestamps used in CF operations are consistent
• ordering of CF events is globally meaningful

👉 CF = shared state
👉 STP = shared time reference

8. Failure handling

If primary time source fails:

• backup STP time server takes over
• systems continue synchronized operation
• no discontinuity in time progression

9. Precision levels

Modern IBM Z STP achieves:

• sub-microsecond synchronization between systems
• extremely low drift rates
• continuous correction without disruption

10. Simple mental model

Think of sysplex time synchronization as:

A distributed clock system where all machines constantly “fine-tune” their clocks to match a single master, ensuring a globally consistent notion of time across the entire cluster.

Key takeaway

Sysplex time synchronization ensures consistency by:

• Maintaining a single authoritative time source (STP)
• Continuously adjusting system clocks to eliminate drift
• Guaranteeing monotonic, globally consistent timestamps
• Enabling correct ordering of transactions, logs, and locks across all sysplex nodes