Mainframe to Cloud

Specialty · SR01

SR01: Mainframe Systems Programmer → Cloud Solutions Architect

The Highest-ROI IT Pivot in 2026

Target audience: Mainframe sysprogs (z/OS, COBOL, JCL) seeking cloud architecture roles
Timeline: 18–30 months (12–18 months core, 6–12 months on-the-job refinement)
ROI: Base salary +$50–85K; premium market demand; 5–10 year runway before retirement

1. Why This Pivot Now

The Demographic Cliff

The mainframe workforce is at a critical inflection point. While historically projected as an aging, retiring profession, recent data shows more nuance: the average mainframe systems programmer age is 47, but this masks significant generational dynamics.

According to BMC Software's 2025 survey, 66 percent of respondents identify as Gen Z or Millennial — an increase of 37 percent from 2018, with Generation Z mainframers comprising 15 percent (up from just 1 percent in 2018). Concurrently, Forrester's 2025 State of Mainframe report notes that while skills gaps have persisted for two decades, "mainframe budgets are increasing; modernization takes many forms; and the staffing crisis is not as bad as it was projected."

The paradox: COBOL developers command $150K+ annually with booking lead times exceeding 12 months, yet few new entrants are arriving. The sysprogs who do exist have deep, irreplaceable knowledge—but their career ceiling on mainframes is fixed. Cloud architecture, by contrast, offers:

  • Salary delta: $95–135K (mainframe sysprog) → $155–210K (cloud architect) — $60–75K jump
  • Breadth: From z/OS (narrow, deep) to cloud (broad, deep, multi-vendor)
  • Runway: Until age 70+; mainframe roles compress at 55–60
  • Market velocity: Mainframe skills decay; cloud skills compound

The Modernization Wave

AWS Mainframe Modernization and AWS Transform for mainframe (agentic AI for automated refactoring) launched in 2024–2025 and are now general availability. Micro Focus Enterprise Server (now OpenText) enables "lift-and-shift" COBOL to EC2/RDS without rewriting. IBM watsonx Code Assistant for Z, released 2.8 in 2026, offers end-to-end agentic automation.

Every large enterprise with a mainframe is now in a 3–5 year modernization window. Sysprogs who understand both z/OS architecture and cloud architecture become force multipliers: they translate legacy constraint models into cloud patterns, validate refactored COBOL on AWS, design data migration strategies, and oversee cost/performance tuning.

Market size: The global mainframe modernization market reached USD 9.01 billion in 2026, with projects costing $450K–$2.3M (median) and generating $23.3M annualized cost savings per initiative.

Companies Hiring This Profile (2026)

  • Banks & Financial: JPMorgan Chase, Bank of America, Wells Fargo (COBOL-heavy treasury, ATM networks)
  • Insurance: State Farm, Allstate, Cigna (policy engines, claims processing)
  • Government: DoD, Social Security Administration, IRS (CICS batch and online)
  • Retail & Airlines: Walmart, Delta, United (legacy point-of-sale, reservation systems)

Job boards: Glassdoor Mainframe Modernization, ZipRecruiter Mainframe Modernization ($47–$81/hr roles). Entry-level transition roles pay $105–132K; Senior Cloud Architect on Mainframe Modernization projects: $150–210K.

2. Your Starting Point: Mainframe Sysprog (z/OS)

What You Already Know

A mainframe systems programmer has spent 5–20 years mastering:

  • OS fundamentals: z/OS architecture, memory management (24-bit, 31-bit, 64-bit addressing), interrupts, MVS/ESA/z/OS lineage
  • Batch processing: JCL (Job Control Language), JES2/JES3 job entry systems, GDGs (Generation Data Groups), dataset allocation/deallocation
  • Transactional systems: CICS (Customer Information Control System) — transaction routing, recovery, link/xctl, pseudo-conversational programming
  • Database: IMS (Integrated Management System — hierarchical), DB2 (SQL on z/OS, cursors, RUNSTATS tuning)
  • Security & access: RACF (Role-Based Access Control), z/OS user profiles, data class/storage class definitions
  • Systems tuning: RMF (Resource Management Facility), SMF (System Management Facility) capacity planning, DASD (disk) layout, tape management
  • Modernization tools exposure (optional, but increasingly common): Micro Focus, Rocket Software, IBM migration assessment tools

Salary baseline: $95–135K median per Glassdoor; $90,763–$145,482 (25th–75th percentile).

What You're Not Fluent In Yet

  • Linux/Unix filesystem, process management, systemd, shell scripting
  • Modern cloud networking (VPC, subnets, NAT, peering, Transit Gateways)
  • Infrastructure as Code (Terraform, CloudFormation, Ansible)
  • Containerization and orchestration (Docker, Kubernetes — even if not needed immediately)
  • CI/CD pipelines, version control (Git), automated testing
  • Observability at cloud scale (CloudWatch, Datadog, Prometheus; vs. RMF/SMF dashboards)
  • Cost modeling and cloud FinOps (RI, Spot, Reserved Capacity Plans on AWS)
  • Serverless and event-driven architecture (Lambda, SNS, SQS — no direct mainframe parallel)

3. The Bridge: 18–24 Months of Deliberate Upskilling

Phase 1: Foundations (Months 1–4)

Goal: Comfort with Linux, cloud infrastructure, and the conceptual model of distributed systems.

Linux fundamentals (30–40 hours)

  1. Free resource: Linux Journey — self-paced, interactive
  2. Paid course: Coursera Linux for Cloud and DevOps Engineers or Udemy "Complete Linux Bash Course" (~$12–15)
  3. Hands-on: Set up a VM (VirtualBox on your PC), run a web server (Nginx), manipulate files, write a bash script
  4. What you're learning:
    • Filesystem hierarchy (/etc, /var, /home, /usr)
    • Process management (ps, top, kill, systemd)
    • Permissions (chmod, chown, umask)
    • Package management (apt, yum)
    • Text processing (grep, awk, sed) — familiar to shell scripting on z/OS, but faster/more powerful

Mainframe parallel: Think of /etc as the z/OS parmlib; systemd as WLM (Workload Manager); cron as internal reader batch scheduling.

AWS EC2 + VPC essentials (20–25 hours)

  1. Free: AWS Skill Builder (included with AWS account). "Getting Started with Amazon EC2" learning path.
  2. Paid: Udemy Ultimate AWS Certified Solutions Architect Associate 2026 (~$15–17). Focus on EC2 + VPC modules only.
  3. Hands-on: Launch an EC2 instance, attach a security group, modify VPC routing
  4. What you're learning:
    • EC2 instance types, AMIs, EBS volumes
    • VPC design (public/private subnets, NAT Gateways, Route Tables)
    • Security Groups ≈ z/OS firewall rules; NACLs ≈ dataset access rules

Mainframe parallel: EC2 "instances" are like LPAR (Logical Partitions); EBS "volumes" are like DASD (disk); Route Tables are like z/OS TCP/IP routing tables.

AWS RDS + data persistence (15–20 hours)

  1. Free: AWS Skill Builder "Amazon RDS Core" module
  2. Hands-on: Spin up RDS Postgres, connect via SQL client, restore a backup
  3. What you're learning:
    • RDS (managed relational database), Aurora (cloud-native)
    • Backup/restore, Multi-AZ (≈ z/OS GDPS), read replicas
    • Cost implications (IOPS, reserved capacity plans)

Mainframe parallel: RDS Aurora ≈ DB2 on z/OS; Multi-AZ ≈ Enterprise Disaster Recovery (EDR) Parallel Sysplex.

Month 1–4 effort: ~80–100 hours self-study + lab work. Cost: $50–80 (subscriptions); free up front.

Phase 2: Core Cloud Architecture (Months 5–12)

Goal: Earn AWS Solutions Architect Associate (SAA-C03) and begin Terraform; understand cloud governance and cost.

AWS SAA-C03 certification (120 hours / 10–12 weeks)

Official route:

Study resources:

  1. Udemy: Ultimate AWS Certified Solutions Architect Associate 2026 by Stephane Maarek (~4.5 hours video, $15)
  2. Paid practice exams: Tutorials Dojo AWS SAA-C03 Practice Exams (~$25)
  3. Free hands-on labs: AWS Skill Builder free tier, A Cloud Guru SAA-C03 path (requires subscription ~$35/mo; A Cloud Guru is now part of Pluralsight)
  4. Interactive study: Cantrill AWS SAA-C03 (structured, $30, excellent reviews)

Mainframe angle: Study the exam's emphasis on cost optimization (RI, Spot), disaster recovery (RTO/RPO), and multi-region failover. These map directly to your z/OS disaster recovery experience.

Passing the exam: Most sysprogs with 10+ years IT experience pass on first attempt (68% pass rate industry-wide).

Terraform Associate 004 (60 hours / 4–6 weeks)

Official path:

Study resources:

  1. Free: HashiCorp Learn Terraform Associate 004 Learning Path
  2. Paid: Udemy Terraform Associate 004 courses ($15); A Cloud Guru Terraform path ($35/mo)
  3. Practice labs: KodeKloud Terraform Labs (~$20/mo for all labs); free tier limited

Hands-on (essential):

  • Clone a Terraform repo; modify .tf files to define VPC, subnets, EC2
  • Use Terraform state management; plan before apply; understand backends
  • Write a simple module for reusability
  • Destroy resources safely

Mainframe angle: Terraform ≈ JCL for cloud infrastructure. State management ≈ dataset cataloging; terraform plan ≈ dryrun; terraform apply ≈ SUBMIT job.

AWS cost mastery (20 hours)

  1. Free: AWS Skill Builder "AWS Cost Explorer" and "AWS Trusted Advisor" modules
  2. Reference: AWS FinOps Foundation — free ebook
  3. Hands-on: Use Cost Explorer on your AWS account to spot waste; reserved instances; savings plans

Why it matters: Sysprogs understand hardware costs (DASD, MIPS licensing). Cloud cost is behavioral — a misconfigured NAT Gateway bleeds $30K/month. This becomes your selling point.

Phase 2 effort: ~120–150 hours, $100–120 (exams + subscriptions). Outcome: 2 certs, Terraform hands-on, cost intuition.

Phase 3: Modernization & Linux Depth (Months 13–18)

Goal: Understand mainframe-to-cloud migration patterns; earn LFCS (Linux Foundation Certified System Administrator).

Linux Foundation LFCS (60 hours / 8–10 weeks)

Official:

Resources:

  1. Free: Linux Foundation Learning Path - LFCS
  2. Paid (~$30–50): Udemy LFCS prep courses
  3. Hands-on (critical): KodeKloud LFCS Labs (~$20/mo)
  4. Community: r/linuxadministration (reddit); Linux Academy forums

Mainframe angle: LFCS is to Linux what z/OS Systems Programming is to mainframes — broad, practical, performance-tuning focused. The test is hands-on, not multiple-choice: you SSH into a system and fix problems. Sysprogs excel here.

Why it matters: After SAA-C03, employers expect proof of Linux depth beyond "I can launch an EC2." LFCS signals you can troubleshoot, tune, and architect Linux-based infrastructure.

Mainframe modernization deep-dive (40 hours)

  1. IBM resources (free):
  2. AWS resources (free):
  3. Vendor docs:
  4. Hands-on (if accessible): Set up a Micro Focus Enterprise Server sandbox on EC2; refactor a COBOL copybook; understand CICS-to-microservices mapping

Topics to master:

  • Lift & shift (rehost): COBOL as-is on EC2 with Rocket/Micro Focus
  • Automated refactoring (reimagine): AWS Transform for mainframe, IBM watsonx Code Assistant for Z
  • Replatforming (modernize): Decompose CICS transactions into REST/gRPC services; IMS → DynamoDB; Db2 → Aurora
  • Data migration: EBCDIC ↔ ASCII; VSAM ↔ S3; tape ↔ EBS snapshots
  • Cost models: MIPS licensing → EC2 per-second billing; fixed CapEx → OpEx

Phase 3 effort: ~100–120 hours, $50–100. Outcome: LFCS cert, modernization fluency, confidence in your niche.

Phase 4: Capstone & On-the-Job (Months 19–30)

Goal: Land a cloud architect role in a mainframe modernization project; learn by doing.

Job search positioning

  1. Resume highlights:

    • "20 years z/OS Systems Programming" (proof of depth)
    • "AWS Solutions Architect Associate (SAA-C03), HashiCorp Terraform Associate 004, Linux Foundation LFCS"
    • "Mainframe modernization tooling: Micro Focus Enterprise Server, AWS Transform, IBM watsonx Code Assistant"
    • Any projects you architected: "Designed Micro Focus Enterprise Server migration of 2M+ LOC COBOL codebase to AWS EC2 + Aurora, reducing MIPS costs by 45%"

  2. Target companies:

    • JPMorgan Chase — massive mainframe footprint, active AWS modernization
    • [AWS consulting partners** specializing in mainframe: Accenture, IBM Consulting, Deloitte, EY, Capgemini, KPMG
    • Independent consulting: If you're senior (15+ years), startups like EPAM, Thoughtworks, Bessemer Venture Partners hire fractional cloud architects for modernization advisory

  3. Job titles to pursue:

    • Cloud Architect – Mainframe Modernization
    • Solutions Architect – Mainframe Migration
    • AWS Solutions Architect (specialization in mainframe/AWS Transform)
    • Senior Cloud Engineer – Modernization

  4. Salary negotiation:

    • Entry-level cloud architect (3–5 years cloud): $130–160K
    • Cloud architect with mainframe legacy (your profile): $155–200K (mainframe expertise commands 20–30% premium)
    • Cloud architect + AWS Solutions Architect Exam; $200K+ (Google/Microsoft/big tech)
    • Consulting/advisory roles: $180–250K + bonus

First 90 days in role (critical success factors)

  1. Pick a cloud provider and own it: AWS (70% of mainframe migration market); Azure (second); GCP (rare for mainframe). Commit hard.
  2. Get certified in month 1: Schedule your AWS SAA-C03 or AZ-104 retake to prove you're serious. (If you haven't passed yet, this is non-negotiable.)
  3. Join a real modernization project: Don't accept an offer in a static "cloud operations" team. You want active migration/refactoring. Ask: "Is this a greenfield project or a legacy-to-cloud initiative?"
  4. Find a mentor: A cloud architect at your company who hasn't worked on mainframes. Trade your z/OS knowledge for their AWS/multi-region/serverless chops.
  5. Learn the cost model obsessively: In month 2, build a cost model for your first project. Track Reserved Instances, Spot usage, data transfer. Sysprogs understand DASD costs; you'll dominate FinOps.
  6. Document your architecture decisions: The best cloud architects write; write decision trees, trade-off matrices, capacity plans. Your mainframe RMF/SMF reports skills transfer here.

4. Recommended Certifications & Books

Certifications (in order)

CertIssuerCostEffortMonthsPriority
AWS SAA-C03Amazon$150 (50% w/ discount)120 hrs5–12 wksMust-have
HashiCorp Terraform 004HashiCorp$70–10060 hrs4–6 wksMust-have
Linux Foundation LFCSLinux Foundation$445 ($289 w/ EARTH26)60 hrs8–10 wksRecommended
MS Azure AZ-104Microsoft$165100 hrs8–10 wksAlternative to AWS
Google Cloud Associate Cloud EngineerGoogle$200100 hrs8–10 wksAlternative / 2nd cloud
IBM Z Certified Solutions ArchitectIBMVaries40 hrs4–6 wksOptional (if IBM focus)

Your path:

  1. AWS SAA-C03 (mandatory, highest ROI)
  2. Terraform 004 (mandatory, IaC proof)
  3. LFCS (recommended, 6 months later once employed)
  4. AZ-104 or GCP ACE (optional, year 2 if employer pushes multi-cloud)

Books (cited & annotated)

Foundation — Cloud Architecture

  1. Architecting the Cloud: Design Decisions for Cloud Computing Service Models (SaaS, PaaS, and IaaS) by Michael J. Kavis

    • Publisher: Wiley, 2014. ISBN 9781118617618
    • Why: The only book that bridges legacy systems thinking to cloud architecture. Kavis worked on Oracle enterprise systems; he understands the "we have to maintain state & transactions" constraint. Not fluffy; dense with trade-offs.
    • Chapters for you: #2 (Design Principles), #4 (Storage & Databases), #5 (Security).
    • Cost: $30–50 paperback; $20 Kindle (typical)

  2. Cloud Architecture Patterns by Bill Wilder

    • Publisher: O'Reilly, 2012. ISBN 978-1449357733
    • Why: Hands-on patterns (distributed caching, queue-based load leveling, retry logic) you'll architect daily.
    • Cost: $35–45 paperback; $30 Kindle

Mainframe-to-Cloud Specific

  1. Free: Open Mainframe Project Master the Mainframe (online, no ISBN)

    • Open-source COBOL tutorials + Linux intro + IBM Z Xplore credits. Free forever.

  2. Free: IBM Z Xplore Learning Platform

    • IBM's official hands-on lab environment. Mainframe fundamentals + modernization paths. No cost; digital badge upon completion.

Infrastructure as Code

  1. Terraform: Up & Running, 2nd ed. by Yevgeniy Brikman
    • Publisher: O'Reilly, 2019. ISBN 978-1492046899
    • Why: Canonical guide to Terraform; focus on state, modules, testing. Clear and practical.
    • Cost: $35–45 paperback; $30 Kindle

Linux Systems Administration

  1. UNIX and Linux System Administration Handbook, 5th ed. by Nemeth et al.
    • Publisher: Pearson, 2017. ISBN 978-0134277554
    • Why: 1200 pages, the definitive reference. Every sysadmin (mainframe or Linux) should own this.
    • Cost: $60–80 hardcover; $50 Kindle (expensive, but worth it)

Cost & Governance

  1. Free: AWS FinOps Foundation — Ebook
    • Cloud cost optimization first principles. Sysprogs will love the rigor.

Free Resources (high-signal)

5. Salary Progression & ROI

Baseline (Mainframe Sysprog, 2026)

  • Median: $114,414
  • Range: $90,763 (25th percentile) – $145,482 (75th percentile)
  • Regional variation: US West (SF, Seattle, Austin) +15%; Midwest (Chicago, St. Louis) -5%

Transition Role (Mainframe Modernization Specialist, 18–24 months in)

  • Median: $115–150K
  • Differentiator: You know both z/OS and AWS. Rare. Employers pay for rarity.

Target Role (Cloud Solutions Architect, 30+ months in)

  • Median: $200,534 (Glassdoor)
  • Range: $157,450 (25th percentile) – $258,939 (75th percentile)
  • Big tech (Levels.fyi):
    • Amazon: $166–471K (L4–L7)
    • Google: $192K–$1.47M (L3–L8)
    • Microsoft: $129–467K
  • Consulting (McKinsey, Accenture, EY): $180–280K + bonus

Total ROI Over 10 Years

YearRoleSalaryCumulative
0–2Mainframe Sysprog$114K/yr$228K
2–5Transition + Cloud Architect$140K/yr (avg)$420K + $1,050K = $1,470K
5–10Cloud Solutions Architect$210K/yr (avg)$1,050K
Total$2,748K

Comparison: Stay on mainframe (no pivot)

  • $114K × 10 = $1,140K
  • Career ends at 60–62

Pivot gain: +$1.6M over 10 years; runway extends to 70+.

6. Common Failure Modes & How to Avoid Them

1. Underselling your mainframe experience as "legacy"

Trap: You interview for a junior cloud architect role and say, "I've been doing mainframe work, but I'm new to cloud, so I'm flexible on level."

Reality: Your 15 years of disaster recovery, tuning, capacity planning, and regulatory compliance are directly applicable. A Cloud Architect at Google or AWS who has never tuned a system under constrained resources is weaker than you.

Fix: Frame mainframe as depth & constraint-driven. "I've architected z/OS systems handling 50M transactions/day with sub-50ms latency and 99.99% uptime. Now I'm applying the same rigor to cloud architecture — cost optimization, multi-region failover, observability at scale."

2. Trying to learn 3 clouds at once

Trap: You pursue AWS SAA-C03, Azure AZ-104, and GCP ACE simultaneously.

Reality: Cloud depth (one provider) beats breadth (three weak). Employers hire for one cloud expert who can do the job; they'll cross-train to a second if needed.

Fix: AWS first (70% of enterprise, 90% of mainframe migration market). Azure second (if you take a Microsoft job). GCP third (optional, 3+ years in).

3. Not joining a real migration project

Trap: You land a "Cloud Architect" role at a company, but it's actually "maintain existing EC2 instances and RDS databases" — no new architecture, no migrations, no learning.

Reality: Your growth stalls. You'll be bored in 2 years and job-hunting again.

Fix: During interviews, ask: "What active migration or modernization projects will I contribute to in my first 18 months?" If they say "mostly operations," pass.

4. Neglecting cost optimization

Trap: You build a beautiful, high-availability system. It costs $500K/month.

Reality: Your architecture is rejected. Cloud is OpEx; CFOs audit it quarterly. Mainframe sysprogs understand cost deeply (MIPS licensing, DASD allocation). Leverage it.

Fix: Every architecture decision, estimate cost. Use AWS Cost Explorer. Build FinOps intuition early.

5. Skipping the Linux LFCS

Trap: "I know EC2 and Terraform; Linux certification is overkill."

Reality: Employers want proof you can SSH into a broken system at 2 AM and fix it. LFCS is that proof.

Fix: Get LFCS 6–12 months into your first cloud role. By then, you've hit real production issues (permissions, package conflicts, systemd timeouts) and the exam will feel immediately relevant.

7. First 90 Days in a Cloud Role

Week 1: Onboarding & Environment

  • Meet your team and manager. Ask: "What are the 3 biggest architectural challenges in our next 12 months?"
  • Get AWS console access. Explore the company's architecture in AWS Systems Manager / CloudFormation.
  • Read the company's cloud governance policy (cost guardrails, region strategy, tagging standards).
  • Pair with a peer for 2–3 days. Watch how they navigate incident response, code review, architecture decisions.

Week 2–4: Deep knowledge transfer

  • If modernizing a mainframe: Get access to the legacy system. Understand the current architecture, dependencies, performance baselines.
  • If greenfield: Study the business domain. Banking? Insurance? E-commerce? Understand the constraints.
  • Review prior architecture decisions (RFCs, ADRs, design docs). Understand trade-offs.
  • Shadow your first on-call shift. Understand monitoring, alerting, runbooks.

Month 2: Active contribution

  • Pick a small story / task: "Optimize RDS costs" or "Build a Terraform module for VPC creation."
  • Deliver it. Get code reviewed. Learn the team's standards.
  • Build cost model for a key system. Present it to stakeholders. This will impress (sysprogs care about cost).

Month 3: Capstone project

  • Lead a design decision: "Should we use Lambda or Fargate for this workload?" or "Rehost or replatform this legacy component?"
  • Write a 1–2 page RFC (Request for Comments). Circulate it. Incorporate feedback.
  • You've now architected something on your new platform. Confidence +100%.

8. Staying Current: 2026 & Beyond

Conferences & Communities

  • IBM Z Day — Free annual 1-day summit (virtual); focus on mainframe modernization, watsonx, hybrid cloud. Hosted by IBM Customer Council.
  • SHARE — The mainframe community conference. Hundreds of sysprogs, workshops on modernization.
  • AWS re:Invent — Nov 30–Dec 4, 2026, Las Vegas. Expect strong mainframe modernization content; AWS Transform for mainframe will be a major theme.
  • Linux Foundation Open Source Summit — If you care about cloud-native infrastructure, kubernetes, etc.

Tools & Releases to Watch (2026)

Continuous Learning

  • Year 2: AWS Solutions Architect Pro (advanced exam; $300). Deep into multi-account, multi-region, cost optimization.
  • Year 3+: Specialize — Serverless, container orchestration, FinOps certification, or pivot to enterprise architecture.

9. International Salary Data (where available)

United States (2026)

  • Mainframe Sysprog: $95–135K
  • Cloud Architect (entry): $130–160K
  • Cloud Solutions Architect: $155–210K

United Kingdom (2026)

  • Mainframe Sysprog: GBP 65–95K (~USD $82–120K @ 1.27 exchange)
  • Cloud Architect: GBP 90–140K (~USD $114–177K)

South Africa (ZAR, 2026)

  • Mainframe Sysprog: ZAR 1.2M–1.8M/yr (~USD $65–97K @ 18.5 ZAR/USD)
  • Cloud Architect: ZAR 1.6M–2.4M/yr (~USD $86–130K) — Significantly lower than US; emigration/relocation common for SA IT talent

Note: Mainframe roles in ZA are rare but highly paid (legacy systems, banking sector). Cloud architect salaries globally are compressing; US > UK > ZA. Remote-first roles (especially from AWS/Google) command global salaries; consider this in career planning.

10. Vendor Resources & Official Documentation

IBM

AWS

Microsoft Azure

Open Mainframe Project

Sources

Last updated: April 30, 2026
Status: Ready for production
Author: IT Career Roadmap Deep Dive Research

Rate this article
…
Was this helpful?
Comments (—)
0/2000