Connecting IDz to Legacy SCM Repositories (CA Endevor, ChangeMan) using CARMA RAMs
Executive Summary: Connecting IDz to Legacy SCM Repositories (CA Endevor, ChangeMan) using CARMA RAMs
If your organization hasn't yet completed the migration from CA Endevor or Serena ChangeMan to Git, use IBM CARMA (Common Access Repository Manager) inside IDz to check out, edit, and promote elements directly from the modern GUI without 3270 panels.
1 Problem Statement & Architecture Context: Connecting IDz to Legacy SCM Repositories (CA Endevor, ChangeMan) using CARMA RAMs
Developers want to use the modern IDz editor but are still bound to 3270 green-screen panels to lock, check out, compile, and promote elements inside CA Endevor or ChangeMan ZMF.
2 Technical Root Cause & Architecture Mechanics
IBM Developer for z/OS includes CARMA (Common Access Repository Manager):
- CARMA connects to legacy software configuration managers through Repository Access Managers (RAMs).
- The Endevor RAM and ChangeMan RAM map mainframe packages, stages, and elements into tree views inside Eclipse/IDz.
3 Implementation Guide & Modernization Strategy
# 1. Configure the CARMA Server on z/OS
Ensure the CARMA daemon (CRASRV) is running in SYS1.PROCLIB:
//CRASRV EXEC PGM=CRASTART,REGION=0M,
// PARM='PORT=7535,TIMEOUT=300'
# 2. Connect from IDz CARMA Repositories View
1. In IDz, open the CARMA Repositories view.
2. Click Add CARMA Connection.
3. Select CA Endevor SCM RAM or ChangeMan ZMF RAM.
4. Enter your credentials. The entire Endevor inventory structure (Environment → Stage → System → Subsystem) appears as a navigable folder tree!
# 3. Check Out and Edit Elements
Right-click any COBOL element → Extract to Project. Edit in IDz, and right-click → Check In / Generate to trigger Endevor processors automatically!
Technical Specifications Matrix
| Attribute | Specification |
|---|---|
| Target Environment | IBM z/OS • DevOps & Automation |
| Key Technologies | IDz, CARMA, Endevor |
| Delivery SLA | Accelerated Sprint Delivery via StackMF Pods |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Production Readiness & Verification Checklist
- Use CARMA as an interim bridge while planning full Git migration.
- Verify that CARMA RAM security exits enforce the same signout rules as native ISPF.
- Plan your eventual Endevor-to-Git cutover with StackMF's proven migration framework.
? Frequently Asked Questions
What is the root cause of Connecting IDz to Legacy SCM Repositories (CA Endevor, ChangeMan) using CARMA RAMs? ↓
How do you resolve Connecting IDz to Legacy SCM Repositories (CA Endevor, ChangeMan) using CARMA RAMs in production? ↓
How can teams prevent Connecting IDz to Legacy SCM Repositories (CA Endevor, ChangeMan) using CARMA RAMs in enterprise pipelines? ↓
Recommended Technical Runbooks
Migrating from Broadcom Endevor to Git & Modern CI/CD using Zowe CLI and IBM DBB
Broadcom CA-7 / CA-11 Decoupling: Migrating 20,000+ JCL Batch Schedules to Stonebranch or Control-M
Building Enterprise REXX Automation: Scripting TSO/E, ISPF Panels, and SDSF Job Parsing
Authoritative Reference Documentation
Official IBM manuals, Redbooks, and vendor technical advisories:
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 →
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%.