Software Development Change Control › Admin Guide Overview

Admin Guide Overview

CA Endevor SCM is an integrated set of management tools used to automate, control, and monitor your application development process. You can use this software to perform the following activities:

• Automatically compare and track your changes against production, creating an online change history. This speeds up the debugging process and enables you to always know what was changed, by whom, and why.
• Prevent conflicting changes to the same system component.
• Browse and manipulate all components relating to an application from a single screen, saving you time and ensuring that changes are complete.
• Create executables automatically.
• Ensure that the source, executable, and any other form (for example, listings) of an element correspond.
• Apply the same procedures (including automating compiles, analyzing impacts, and standards checking functions) to any component type, dramatically simplifying the standardization process.
• Put change packages and approvals online, eliminating change-related paperwork.
• View or retrieve prior levels of any element.
• Report on element definition, content, and change history.
• Enforce change control procedures.

CA Endevor SCM is implemented and run under z/OS, within the TSO ISPF environment, and in batch. Your site can also run an API program that interfaces with CA Endevor SCM.

Audience

This guide address the tasks of the CA Endevor SCM administrator. The following tasks are discussed in this guide.

• define the software management lifecycle in CA Endevor SCM
• define and place the inventory of software components under the control of CA Endevor SCM
• define and maintain maps that control how elements progress through the lifecycle
• define and maintain global options

What You Need to Know

To use the product, you need a working knowledge of the mainframe environment, the z/OS mainframe operating system, Time Sharing Option facility (TSO), and the Interactive System Productivity Facility (ISPF). It is also assumed that the product has been properly installed at your site.

This guide describes the tasks that administrators can perform in the ISPF environment. Foreground and many batch tasks can be performed using the ISPF panel driven interface. Batch JCL streams can also be written using the standard ISPF editor and submitted from TSO/ISPF.

For more information about writing batch JCL streams, see the SCL Reference Guide and the Packages Guide.

For information about installing and configuring the product, see the Installation Guide.

For more information about terms used in this guide, see the "Glossary" in the User Guide.

The Software Lifecycle

CA Endevor SCM allows you to automate and control the movement of software through your software lifecycle.

Software lifecycles are site-specific. A representative lifecycle might consist of five stages:

• DEV—Programs are developed.
• TEST—Programs are unit tested.
• QA—Applications are system tested.
• EMER—Fixes are applied to production code.
• PROD—Production applications reside.

Note: This example illustrates one lifecycle. CA Endevor SCM can be implemented to adapt to any software lifecycle requirements.

Basic Operations

Normal change procedures include the following:

• Retrieving elements from production to a development library.
• Making changes to elements.
• Adding/updating elements into the test stage.
• Moving elements to QA.
• Moving elements to production.

The following diagram shows normal change procedures in a software lifecycle:

Emergency Operations

Emergency change procedures include the following:

• Retrieving elements from production.
• Making changes to elements.
• Adding and updating elements into the emergency stage.
• Moving elements to production.

The following diagram illustrates emergency change procedures in a software lifecycle: