S/MF
StackMF Knowledge Base • z/OS
DevOps & Automation 12 min read 2026-09-27

Migrating from Broadcom Endevor to Git & Modern CI/CD using Zowe CLI and IBM DBB

A
Reviewed by Anshu
Chief Technology Architect & Mainframe Systems SME
Enterprise Modernization Advisory
Google AI Overview & Featured Snippet Quick Answer

Executive Summary: Migrating from Broadcom Endevor to Git & Modern CI/CD using Zowe CLI and IBM DBB

Eliminate escalating Broadcom Endevor licensing fees by migrating your mainframe source code inventory, components, and processors to Git repositories orchestrated with Zowe CLI, GitHub Actions, and IBM Dependency Based Build (DBB).

1 Problem Statement & Architecture Context: Migrating from Broadcom Endevor to Git & Modern CI/CD using Zowe CLI and IBM DBB

Enterprises face 150% to 300% price increases during Broadcom Endevor contract renewals. Modern developers find Endevor's green-screen ISPF package promotion workflow archaic and siloed, while enterprise CI/CD teams cannot integrate mainframe deployments into standard GitHub Enterprise or GitLab pipelines.

2 Technical Root Cause & Architecture Mechanics

Broadcom Endevor manages mainframe source code in a proprietary stage-and-element lifecycle (Dev -> Test -> QA -> Prod) bound to PDS datasets.

Modern Git-native mainframe engineering replaces this closed model:

  • Git becomes the single source of truth for all COBOL, Copybook, BMS, and JCL assets.
  • IBM Dependency Based Build (DBB) provides intelligent dependency scanning (identifying exactly which programs must be recompiled when a copybook changes).
  • Zowe CLI & GitHub Actions automate building, compiling, and deploying load modules to z/OS through REST APIs, completely deprecating Endevor.

3 Implementation Guide & Modernization Strategy

# 1. Extract Elements and History from Endevor

Use Endevor's batch utility (BC1PNMTR / CONWRITE) to export source elements, copybooks, and historical levels to z/OS UNIX files:

jcl
//EXPORT   EXEC PGM=NDVRC1,PARM='CONWRITE'
//SYSPRINT DD SYSOUT=*
//OUTPUT   DD PATH='/u/migration/repo/cobol/MOD01.cbl',
//            PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
//            PATHMODE=(SIRWXU,SIRWXG)
//SYSIN    DD *
  WRITE ELEMENT MOD01
        FROM ENVIRONMENT PROD SYSTEM BILLING SUBSYSTEM CORE
        TYPE COBOL STAGE P
        TO DDNAME OUTPUT.
/*

# 2. Organize Git Repository Structure

Structure your enterprise Git repository:

text
├── cobol/
│   ├── ACCNTREC.cbl
│   └── INVP01.cbl
├── copybook/
│   ├── INVOICE.cpy
│   └── COMMREG.cpy
├── jcl/
│   └── RUNINVOICE.jcl
├── build/
│   └── build.groovy (IBM DBB Build Script)
└── .github/workflows/
    └── zos-build.yml

# 3. Automate Deployments with GitHub Actions & Zowe CLI

In .github/workflows/zos-build.yml:

yaml
name: z/OS Mainframe CI/CD Pipeline
on: [push, pull_request]

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v4

      - name: Setup Node & Zowe CLI
        uses: actions/setup-node@v4
        with:
          node-version: '20'

      - name: Install Zowe CLI
        run: npm install -g @zowe/cli

      - name: Submit DBB Impact Build on z/OS
        env:
          ZOWE_OPT_HOST: ${{ secrets.ZOS_HOST }}
          ZOWE_OPT_USER: ${{ secrets.ZOS_USER }}
          ZOWE_OPT_PASSWORD: ${{ secrets.ZOS_PASS }}
        run: |
          zowe zos-uss issue ssh-command "groovyz /u/dbb/build.groovy -r /u/repos/stackmf"

Developers gain instantaneous branch-based development, automated pull requests, and automated testing—all while zeroing out Broadcom software fees!

Technical Specifications Matrix

Attribute Specification
Target Environment IBM z/OS • DevOps & Automation
Key Technologies Endevor, DevOps, Broadcom Replacement
Delivery SLA Accelerated Sprint Delivery via StackMF Pods
Technical Reviewer Anshu, Chief Technology Architect • StackMF Architecture Pod

Production Readiness & Verification Checklist

? Frequently Asked Questions

What is the root cause of Migrating from Broadcom Endevor to Git & Modern CI/CD using Zowe CLI and IBM DBB? ↓
Broadcom Endevor manages mainframe source code in a proprietary stage-and-element lifecycle (Dev -> Test -> QA -> Prod) bound to PDS datasets.
How do you resolve Migrating from Broadcom Endevor to Git & Modern CI/CD using Zowe CLI and IBM DBB in production? ↓
Eliminate escalating Broadcom Endevor licensing fees by migrating your mainframe source code inventory, components, and processors to Git repositories orchestrated with Zowe CLI, GitHub Actions, and IBM Dependency Based Build (DBB).
How can teams prevent Migrating from Broadcom Endevor to Git & Modern CI/CD using Zowe CLI and IBM DBB in enterprise pipelines? ↓
Maintain strict branch protection rules on `main` to replicate Endevor's production approval controls.

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: EndevorDevOpsBroadcom ReplacementGitZowe CLIIBM DBB
Diagnostic Runbook Notice & Nominative Fair Use Disclaimer

This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.

IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. § 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →

Enterprise Advisory

Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?

StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.