Supporting other SCMs with CARMA
Many mainframe user organizations store their source code in proprietary software configuration management systems, also known as software configuration managers (SCMs). The source code is locked in the SCM, in a native format that Developer for z/OS® cannot access in an integrated manner. The Common Access Repository Manager (CARMA) toolkit for Developer for z/OS facilitates customer access to SCMs from within Developer for z/OS by providing a common interface for accessing SCMs.
Overview
The following topics provide information about the Common Access Repository Manager (CARMA). They describe the steps necessary for accessing, using, and extending the CARMA toolkit.
Getting started
The following topics provide instructions for completing some of the basic tasks you need to do to start accessing SCMs using the CARMA toolkit.
Samples and tutorials
The following sample RAMs allow you to access a PDS associated with TSO users or, to access Software Configuration Library Manager (SCLM) assets that are stored in SCLM projects.
Resources for learning available on the web
Many resources for learning and using the CARMA toolkit are available. Use the following links to learn more about how to put CARMA to work:
- IBM® Developer for z/OS Using SCLM DT Technology to Provide CARMA Services without Submitting Batch Jobs
- Accessing SCMs using the WebSphere® Developer for zSeries CARMA plug-in
- Integrating Source Code Management Systems into WebSphere Developer for zSeries CARMA
- IBM Developer for z/OS product Web site
- IBM Developer for z/OS Information Roadmap