Measuring Mainframe Developer Velocity: Tracking IDz and Zowe Adoption Metrics

Leadership invests millions in modern mainframe IDEs (IDz, VS Code, Git) to replace ISPF 3270, but 6 months later, nobody knows if developers are actually using the tools or if code velocity has improved:

EXECUTIVE AUDIT QUERY: What is the adoption percentage of IDz vs ISPF?
ANSWER: Unknown. No centralized telemetry or DORA metrics tracked.

Without data, license renewals for legacy tools continue unnecessarily.

Mainframe environments traditionally lack client-side telemetry. Developers switch back to ISPF out of muscle memory, while management lacks visibility into cycle times, build frequencies, or automated test coverage.

# 1. Enable IBM Developer for z/OS Usage Telemetry

Configure IDz client workspace metrics to stream to enterprise dashboards:

In rse.env:

_RSE_TELEMETRY_LOG=/var/log/idz/telemetry.log
_RSE_COLLECT_USAGE_METRICS=TRUE

# 2. Track Zowe CLI Command Frequency

Capture CLI invocations in corporate CI/CD runners:

# In corporate wrapper script or shell profile:
export ZOWE_APP_TELEMETRY=true
export ZOWE_LOG_LEVEL=INFO

Parse logs to measure jobs submitted, datasets edited, and API invocations per developer per week.

# 3. Core DORA Metrics for Mainframe Engineering

Track four essential benchmarks:

1. Deployment Frequency: How often COBOL/PL/I packages are released to production (target: weekly vs quarterly).

2. Lead Time for Changes: Hours elapsed from Git commit to CICS/IMS promotion.

3. Change Failure Rate: Percentage of deployments triggering an immediate rollback or emergency fix.

4. Time to Restore Service (MTTR): Elapsed time to resolve an abend in production.