Glossary

Access Security table

The Access Security Table is the CA Endevor SCM table that defines the environments to which users have access. Each site has one Access Security Table.

action

An action is a command to manage elements.

Add action

The Add action places members from an external data set or USS directory under control of CA Endevor SCM.

alternate ID

An alternate ID is a facility that protects the data sets controlled by CA Endevor SCM (such as the Master Control Files, package data sets, and base and delta libraries) from access by users, while still allowing CA Endevor SCM to have access. The alternate ID is defined by the RACFUID parameter in the CA Endevor SCM Defaults Table.

append SCL

To append SCL is to add new SCL statements to the end of an existing data set, rather than overwriting the existing SCL. This option is available on the Batch Options Menu when building element action SCL in foreground for execution in batch, and it is also available on the Create/Modify Package panel when creating or modifing a package.

approval

An approval is an electronic signoff mechanism for packages. An approval may be required for a package before execution.

Approved

Approved is the status of a package after the required approvers have reviewed, signed off, and approved the package.

approver

An approver is a person authorized to sign off on a package, before execution. Signing off on a package involves reviewing the information in the package and approving or denying the package.

approver group

An approver group is a collection of one or more approvers. An approver group is defined within each environment and can be associated with inventory areas.

approver group relationship

An approver group relationship is established between an approver group and one or more inventory areas, authorizing members of the approver group to review (and then approve or deny) packages related to the inventory areas.

approver type

An approver type is the specification of the kinds of packages that an approver group can review. When the approver type is Standard, the approver group can review only standard packages related to its authorized inventory areas. When the approver type is Emergency, the approver group can review only emergency packages related to its authorized inventory areas.

Archive action

The Archive action writes an element and all related CA Endevor SCM information to a sequential data set.

Autogen action option

The Autogen action option, when specified for an element, automatically generates the elements that use this component element. For example, specifying Autogen for an element of type COPYBOOK would automatically generate the COBOL PROGRAM elements that use the macro, which would in turn generate the appropriate LNK elements. An element that uses a component element is known as a using element. The using elements generated on behalf of Autogen are generated with the NOSOURCE option or the COPYBACK option, depending on the ENCOPTBL setting. Autogen is available in batch only for the Add, Update, and Generate actions and cannot be used in packages.

Automated Configuration Manager (ACM)

The Automated Configuration Manager (ACM) is an optional facility that allows you to monitor selected libraries and data sets and maintain a component list for each element in the monitored areas. The component list provides an audit trail of program-component information at the time of each compilation.

backin

The backin command restores the executable members of a package to the state they were in before the package was backed out. A backin reverses the backout process.

backout

The backout command returns the executable members of a package to the state they were in before package execution.

base level

The base level is the lowest level of an element within a particular stage when storing elements with forward deltas. This level represents the source for the element in that stage. If an element exists in both stages, there is a base level in each stage. When storing elements with reverse deltas, the base level is the current level.

base library

The base library is a partitioned data set (PDS), a CA Panvalet, a CA Librarian, or ELIB file, or a USS directory that stores the base members for elements defined to CA Endevor SCM. A base library is defined for each element type, but it can be shared across types.

base regression

The base regression is the percent by which the statements stored in a new level of an element change the statements stored in the base level.

batch

A batch is an IBM term referring to an environment in which noninteractive programs are executed. In CA Endevor SCM, batch refers to the execution of actions and reports in a noninteractive region, as opposed to execution in the foreground.

browse

The ISPF browse mode lets you view the content of a data set, but does not let you change the content. In CA Endevor SCM, the foreground Display function lets you browse CA Endevor SCM elements. The Print element option browse lets you print the element source in batch.

Bulk Data Transfer (BDT)

The Bulk Data Transfer (BDT) is an IBM transmission utility supported by the CA Endevor SCM package shipment utility. BDT is abbreviated as BDT2 for BDT version 2 and BDTN for BDT with NJE/NJI.

C1DEFLTS table

The C1DEFLTS Table is the CA Endevor SCM Defaults Table.

CA Endevor Parallel Development option

The CA Endevor Parallel Development Option lets users compare and integrate three versions of source code, resolving conflicts resulting from concurrent development or from applying vendor updates to applications that have been customized in-house.

CA Endevor SCM listing libraries

CA Endevor SCM listing libraries are libraries used to store compressed compiler listings produced by processors.

CA Endevor SCM location

The CA Endevor SCM location refers to the stage and environment where an element resides.

Cast

The Cast command freezes the actions included in the package. After a package is cast, it cannot be edited and only approvers can work with it.

CCID definition data set

The CCID definition data set identifies the CCIDs to be used within CA Endevor SCM. The definition file must be a card-image data set (80-byte, fixed-format records).

CCID validation

The CCID validation checks a CCID specified on an action against the CCIDs defined in the CCID definition data set.

Change Control ID (CCID)

A Change Control ID (CCID) is a logical grouping mechanism by which user-specified portions of the CA Endevor SCM inventory can be tagged, and then viewed, tracked, and manipulated. CCIDs are optional but may be required on a system-by-system basis. The same is true of comments.

change regression

The change regression is the percent by which the statements stored in a new level change the revisions made by the previous level.

checksum

The checksum is an internally calculated value within a package. CA Endevor SCM uses the checksum to determine if a package has been changed.

classification

Classification is the System, Subsystem, and Type associated with an element and is used in conjunction with the element's location (Environment and Stage).

comment

A comment is a user-defined remark (up to 40 characters) associated with an action or package. A comment is used with CCIDs, and generally describes the reason for the action or purpose of the package.

Commit

The Commit command records all events related to a package, and removes all backin and backout information. After a package is committed, the package can no longer be backed out or backed in.

Committed

Committed is the status of a package after the successful completion of the Commit command.

complementary data sets

Complementary data sets can be shipped along with package shipments. The complementary data sets for a shipment contain a backout of the shipment.

component

A component (primarily for the CA Endevor Automated Configuration option) is the output produced or the input read in by a generate or move processor. The components of a generated element include the input components that were included to produce an output of the generate processor, the element itself, all outputs created by the generate or move processor, and user-defined data. Components are referenced by element or member names.

component list

A component list is a list of all components created or read by a generate or move processor. The component list can be viewed using the Print Elements action, or the Display Element/Component panel (CA Endevor Automated Configuration option). The component list provides an audit trail of program-component information at the time of each compilation.

component monitoring

Component monitoring is a feature of the CA Endevor Automated Configuration option that allows you to check selected data sets for component relationships.

component validation

Component validation occurs when a package is cast. CA Endevor SCM then validates that all dependent components are in the package and that those components have not changed since they were last used.

Concurrent Action Processing

The Concurrent Action Processing facility causes certain element action requests to be executed concurrently, which reduces the elapsed time it takes to process multiple actions and, therefore, speeds processing of batch jobs and packages. This option must be enabled by the CA Endevor SCM administrator.

Concurrent Number

The Concurrent Number parameter, on the Submit Package panel, lets you specify the number of started tasks to be initiated, when you submit a package for processing using the Concurrent Action Processing facility. This parameter overrides the default set by the SPAWNCNT value in C1DEFLTS.

configuration management

Configuration management is the capture and storage of program-component relationships and the tracking of these relationships over time.

CONNECT:Direct

CONNECT:Direct is a network transmission utility provided by Sterling Commerce and supported by the CA Endevor SCM package shipment utility. It is abbreviated as NWD when establishing destinations. CONNECT:Direct was formerly known as Network DataMover.

consolidation

A consolidation is a CA Endevor SCM facility that allows you to specify a number of delta levels to retain when a member reaches the consolidation level specified for its type.

Copy action

The Copy action copies an element from an archive data set to a data set external to CA Endevor SCM.

copyback

When copyback (also known as fetch) is specified, CA Endevor SCM searches for an element along the map (beginning at a designated stage), finds the element, and then copies it back to the initial stage. Copyback is available as an explicit option with the Generate Elements action. Copyback is also used when adding, transferring, and moving elements.

create a package

The Create/Modify function in foreground lets you create a package, specifying package-related information such as a package ID, an execution window, and so on.

current level

The current level is the most recent source for an element. When using forward deltas, the current level of an element comprises the base level plus all subsequent change levels. When using reverse deltas, the current level of an element is the current source.

data set validation

Data set validation is an optional feature to verify that retrieved elements are added or updated from the data set to which they were last retrieved. This ensures that the same copy of the element (revised as appropriate) is placed back in CA Endevor SCM. Data set validation can be specified separately by system. If this facility is in effect for a system, you can override it to add the element back from a different data set if you have proper authority.

Defaults table

The Defaults Table (also known as C1DEFLTS) is a table of site-specific information necessary for CA Endevor SCM operation. The Defaults Table includes environment and stage definitions, installed options, and site-specific hardware settings. There is only one Defaults Table for each site.

Delete action

The Delete action erases base and delta forms of an element and removes element information from a Master Control File (MCF) or a component list.

delete processor

A delete processor is a processor that is run when an element is deleted from a stage. Typically, the delete processor deletes the output created by the corresponding generate processor.

delta level

A delta level is a record of a change to the base level of an element. Each change to an element creates a delta level. CA Endevor SCM compares the current level to the new source and builds a delta level containing the changes to the source.

delta library

A delta library is a partitioned data set (PDS), a CA Panvalet, a CA Librarian, or an ELIB file that stores the delta members for elements defined to CA Endevor SCM.

Denied

A Denied status of a package is when the package has been reviewed, but denied, by an approver.

Deny

The Deny command is an option for a package approver. If one approver denies a package, it cannot be executed.

destination

A destination is where package outputs are shipped. A destination record contains the information needed by CA Endevor SCM to ship package outputs to the destination.

Display action

The Display action is used to view environment definitions, element information, and footprint-related data.

DSN mapping rule

A DSN mapping rule is a user-defined correspondence between host and remote data set names. DSN mapping rules are used when shipping package outputs.

element

An element is a partitioned data set (PDS) member, a CA Panvalet, CA Librarian, sequential data set, or USS file that has been placed under control of CA Endevor SCM.

element change

Element changes can be reviewed in the view Display changes current level. This view of element information shows the current level of an element, annotated to indicate the level at which each line was added to the source. This view is accessible in batch using the Print element,option changes SCL.

element component

The element component is the part of a component list referred to as element information. This information includes the footprint of the CA Endevor SCM source.

element history

Element history can be reviewed in the view Display history current level. This view of element information shows all lines that have been present in a piece of source code, annotated to show the level at which the line was added, deleted, or both from source.

element master

Display element master info is a view of Master Control File (MCF) information about an element. This view is accessible in batch using the Print Element option.

element name

The element name is the name assigned to an element, used to identify the element within CA Endevor SCM.

element summary of levels

Display summary of levels is a summary view of activity against an element at all levels. Information provided includes the number of statements at each level, the number of lines added, and the number of lines deleted. This view is accessible in batch using the Print Element option summary SCL.

ELIB

An ELIB (Endevor LIB) is a high-performance alternative to OS-partitioned data sets under CA Endevor SCM. ELIB data sets can reorganize member space automatically as members are rewritten or deleted, exploit 31-bit storage for VSAM-organized data sets, expand directories and data sets automatically, provide improved directory processing, and maintain additional statistical information about member size.

emergency approval

An emergency approval is used to approve an emergency package. An approver group must be assigned the authority to approve emergency packages.

emergency package

An emergency package is one of two types of packages (either standard or emergency when created). Emergency packages require approval from emergency approver groups.

enable backout

The enable backout option appears when creating a package. You can decide whether or not to allow the package to be backed out.

Environment

An environment is the top level of the logical structure used to classify elements in CA Endevor SCM. Environments usually correspond to functional levels in an organization (for example, development, quality assurance, and production). Each environment has two stages. There is no limit to the number of environments you can use.

Environment name

The environment name is a name to identify each environment within CA Endevor SCM. The name can be up to eight characters, and include any of the following: A-Z, 0-9, @, #, and $.

Environment title

The environment title is a descriptive title assigned to each environment that is used in various displays and reports (up to 40 characters).

ESI (External Security Interface)

The External Security Interface (ESI) is an optional interface used to implement external security at your site. When installed, this interface replaces the native security facility supplied with installation files (and implemented through the security tables), with calls to RACF, CA ACF2, or CA-Top Secret.

execute a package

The execute command runs a package. Packages that execute successfully can be backed out or committed.

Execution Report

The Execution Report is output when you run CA Endevor SCM actions. The Execution Report documents the actions requested and the processing that occurred. The report can be viewed online by browsing data sets userid.C1TEMPR1.MSGS or userid.C1TEMPR2.MSGS. CA Endevor SCM prints the report on DDNAME C1MSGS1 on the batch SYSOUT.

execution window

The execution window is a timeframe (start and end date) within which a package must be executed.

exit

An exit is part of the CA Endevor SCM exit interface designed for use with exits written in either assembler or in high-level languages such as COBOL.

export a package

The export command copies package SCL into an external data set.

External Security Interface (ESI)

The External Security Interface (ESI) is an optional interface used to implement external security at your site. When installed, this interface replaces the native security facility supplied with the installation files (and implemented through the security tables), with calls to RACF, CA ACF2, or CA Top Secret.

footprint

A footprint is encrypted data added by processors to individual source, object, or load modules, to identify the CA Endevor SCM element associated with the module. CA Endevor SCM uses the data to display and process information for the element. A footprint includes the site ID, environment name, stage number, system name, subsystem name, element name, element type, element version or level, and the date and time the footprint was assigned, all in encrypted format.

foreground

The foreground is an IBM term referring to an environment in which interactive programs are executed. In CA Endevor SCM, you run actions in the foreground by requesting those actions through the CA Endevor SCM Foreground Options Menu.

forward delta

Forward delta is a method for recording changes that stores a base version of code, and then builds current versions by applying changes made to the base.

forward recovery

Forward recovery is the process of taking an old level of an element and making it the current one (new level). As a result, any changes made by the levels between are backed out. To perform forward recovery, you first retrieve the older (to-be-recovered) level, and then add or update the element using the retrieved source to create the new level.

Generate Action

The Generate action translates source into executables, and then populates output libraries with the executables by executing the generate processor for an element.

generate processor

A generate processor translates source into executables, and then populates output libraries with these executables.

group name

A group name is a name associated with a security configuration that applies for multiple users, found within the definition of the Access and User Security Tables. The name is then associated with any number of specific user IDs, to associate the IDs with the group-level security. This is a convenient way to assign security to several users having identical levels of access to the CA Endevor SCM environment.

identify record (IDR)

An identify record (IDR) is an IBM term for a record in a load module that contains user-defined data. An IDR is created by the linkage editor when it encounters an IDENTIFY statement in the object deck. Within CA Endevor SCM, IDRs are used to store the footprints associated with load modules.

IDR (identify record)

import a package

The import command is used to create a package by copying SCL from an external data set.

Include library

An Include library is a CA Panvalet library, CA Librarian library, or partitioned data set (PDS) that contains INCLUDE members referenced within CA Endevor SCM elements. This library is optional and it can be defined for each element type. The Include library is used by Retrieve actions if you specify that you want to expand Include members at the time the element is retrieved. It is also used by the CONWRITE utility, if you specify that you want to expand Include members during CONWRITE processing.

input component

An input component is an included component to produce an output when executing the generate or move processor when using the CA Endevor Automated Configuration option. For example, a copybook is the input component when compiling a COBOL program.

inventory

An inventory contains the software components that make up your application software systems.

Inventory Analyzer

The Inventory Analyzer is a CA product that allows you to analyze your software inventory, classifying it according to CA Endevor SCM types. This product can be used when implementing CA Endevor SCM.

inventory area

The inventory area is a subset of a software inventory, defined by its CA Endevor SCM location (environment and stage) and classification (system, subsystem, and type).

jump

A jump occurs when moving an element from stage 2 in one environment to a stage in another environment on a map route, when a version of the element exists at an intermediate stage that is not part of the map route.

last action

The last action is the most recent action executed for an element. Once executed, each action is recorded as the last action except Archive, Delete, Display, List, and Print.

last action CCID

The last action CCID is the CCID specified for the last action executed against an element.

level

A level is the source for an element at a particular time. When an element is first added to a stage, there is one level (known as the base level). Each time CA Endevor SCM actions change the source thereafter, a new delta level is created.

level number

The level number is an identifier for a specific level of an element. CA Endevor SCM assigns each set of changes a level number that is one higher than the number assigned to the preceding level.

library management

Library management is the classification, control, and storage of the physical components of a software inventory.

List action

The List action lists elements from a Master Control File (MCF) or archive data set in the form of action requests or members from a library. This action can also be used for text scanning. If the Automated Configuration Manager facility is installed, this action can also search a component list based on specified criteria.

load utility

The load utility is a CA Endevor SCM utility that is used to load members from an external data set into any stage in an environment.

map

A map is the promotion routes established for software inventory at a site. Environments and stages are mapped to each other in the CA Endevor SCM Defaults Table. Systems, subsystems, types, and processor groups are mapped to each other on their respective definition panels.

Master Control File (MCF)

The Master Control File (MCF) is a CA Endevor SCM file that contains the definitions of stages, systems, subsystems, element types, and elements. This file is accessed and updated by CA Endevor SCM to manage the element definitions, to execute processors, and for other miscellaneous functions. There are two Master Control Files (MCFs) for each environment—one per stage.

MAXRC

The MAXRC is a processor keyword that defines the highest acceptable return code for a processor step. If a step exceeds this return code, the CA Endevor SCM return code (NDVR RC) is set to 12. When this happens, the Element Master display shows *FAILED* in the NDVR RC field.

MCF (Master Control File)

model transmission control statements

Model transmission control statements control the functioning of data transmission programs used by the package shipment utility.

Move action

The Move action moves elements between stages, within or across environments.

move processor

Move processors copy outputs, element information, and component lists from the source location to the target location of a Move or, optionally, a Transfer action.

name masking

Name masking lets you substitute a wildcard asterisk (*) character or a placeholder percent sign (%) character for one or more characters in a search string. Name masking is valid on many, but not all search requests.

Native Security

Native Security provides functional security by controlling environment access, primary and foreground menu options, and action authorization. When security control points are reached, CA Endevor SCM checks access privileges defined in the Native Security tables. This is one of two methods of providing functional security; the administrator must choose to implement functional security using either the Native Security feature or the CA Endevor SCM External Security Interface (ESI) option.

NDVR RC (return code)

The return code (NDVR RC) results from action processing. Values can be 00, 04, 08, 12, and 16.

NoSource action option

NoSource is an option for the Generate action that eliminates the need to fetch an element's source back to the target location when the element does not already exist at the target. This option can be specified on foreground or batch Generate actions.

notification facility

The notification facility is a CA Endevor SCM facility that allows you to notify users of events that require a response from them.

output component

An output component is created as a result of executing the generate or move processor when using the CA Endevor Automated Configuration option. For example, an object deck is an output component when compiling a COBOL program.

output library

An output library is any of several libraries used during output management, including the CA Endevor SCM processor listing library, processor load library, and source output library as well as user copy libraries, load libraries, listing libraries, macro libraries, JCL libraries, databases, and so forth.

output management

Output management is an aspect of CA Endevor SCM that handles the creation and maintenance of various outputs that relate to an element. The exact nature of these outputs varies depending on the corresponding element type, and is defined by the output management for that type.

package

A package is a group of CA Endevor SCM actions that requires approval before it can be executed. Creating packages allows you to group specific actions so they can be maintained and tracked as a single unit, establish formal approval procedures to ensure data integrity through modifications, and centralize specific action groups so you can see them across environments and reuse them.

package data set

A package data set is where packages are stored. There is one package data set for a site.

package events

The package events are an audit trail recording the events that have occurred involving a package, logged by user ID, date, and time. Package events relate to the various steps of the package processing procedure, and include Created, Last Updated, Cast, Approved, Executed, Backed Out, Backed In, and Committed.

package exits

A package exit is called before, after (or both) package functions and subfunctions.

package shipment

A package shipment is the transmission of package outputs, and optionally their backouts, from host sites to remote sites.

package status

A package status indicates the status of a package at any specific time. Status levels for packages include In-edit, In-approval, Denied, Approved, In-execution, Executed, Exec-failed, and Committed.

Print action

The Print action is a batch command that prints element or member information.

PROC RC (processor return code)

The processor return code (PROC RC) is the highest return code from the execution of a processor. This returns code is set to *FAILED* if the return code for any step in a processor exceeds the MAXRC for the processor. This return code is set to *PROC'D?* if the element has not been generated after being restored or transferred from an archive data set or added or updated.

PROC statement

A PROC statement is a job control statement used in catalogued or in-stream procedures. PROC statements can be used to assign default values to symbolic parameters contained in a procedure. A PROC statement is also used to mark the beginning of in-stream procedures.

processor component

A processor component is the part of a component list that includes processor information when using the CA Endevor Automated Configuration option. This information includes the footprint of the processor.

processor group

A processor group identifies a set of processors for a specific element type, as well as the default symbolic overrides for the processors' JCL. A group can include up to three processors (one generate, one delete, and one move processor, or any combination). Processor groups are useful when elements of one type require slightly different processing. When you define a type to CA Endevor SCM, you can also identify a default processor group for that type. Using symbolics when writing the processors for the default processor group can allow you to use the same processors, by changing symbolic definitions, for other processor groups associated with this type.

processor group symbolics

Processor group symbolics are defined in PROC statements in one or more processors in a processor group. The symbolics and their default values appear on the Processor Group Symbolics panel. By modifying the default values, you can use one processor in more than one processor group.

processor listing library

The processor listing library is an optional library that stores the listings output from the CA-supplied processor named GPPROCSS.

processor load library

The processor load library is a CA Endevor SCM library that contains the load-module form of each processor. The modules from this library are executed when processors are invoked.

processor output library

The processor output library is a library (referred to in a processor) to which the processor writes output. Processor output libraries can be source libraries, executable libraries, or listing libraries.

processor return code (PROC RC)

processors

A processor is a standard OS JCL job stream that manipulates elements and their outputs. There are generate, delete, and move processors. CA Endevor SCM supports both CA Endevor SCM symbolics and user-defined symbolics in processors. This capability allows you to write one processor that you can use in multiple processor groups by changing the values assigned to one or more symbolics. CA Endevor SCM also provides a set of utilities for use when writing processors, and supports the use of in-stream data in processors.

production data set

The production data set is used to store production code. This term is used in the package shipment utility to refer to host and remote production data sets.

program pathing

Program pathing is a security option under RACF, CA ACF2, and CA Top Secret, that allows you to restrict the data sets available to particular users, as well as the programs and load libraries from which those data sets can be accessed. This is not a CA Endevor SCM option, but is specific to RACF, CA ACF2, and CA Top Secret.

promote

Promote is another term for moving an element from one inventory area to another inventory area.

promotion management

Promotion management is the task of coordinating and validating successive changes to the various inventory areas in a software development setting.

promotion package

A promotion package is a type of package that contains move actions only and the from environment and stage location for all move actions must be the same. A promotion package can be reused until the contents have been promoted to the end of the map, without having to reset the package, manually edit the SCL to modify the inventory source location, or re-cast the package. However, a promotion package needs to be approved between executions, if required.

quorum

A quorum is the minimum number of approvers for which approval is required to execute a package. When a quorum size is specified, at least that many approvers must review and approve a package.

regression

Regression refers to the condition where one set of changes to element source is overwritten by a subsequent set of changes. CA Endevor SCM flags regression when the changes stored for a specific level of an element overwrite more than a predefined percentage of the element statements.

regression percent

The regression percent is the percent of acceptable change to element source, defined for each element type. When this percent is exceeded, the result is a user-specifiable CA Endevor SCM return code (0, 4, 8, or 12). Each time a new level is created for an element, CA Endevor SCM checks the changes stored in that level against this percent, changes to both the statements stored for the base level (known as base regression) and changes to the statements stored for the previous level (known as change regression). If the amount of change in either case exceeds the defined percent, CA Endevor SCM issues a message of user-defined severity.

Reload utility

The Reload Utility allows you to recover a CA Endevor SCM VSAM control file (Master Control File, package data set) or a base or delta data set that was lost because of a physical device failure or site disaster. The RELOAD action restores data from data sets created by the unload process.

remote footprint synchronization

Remote footprint synchronization is a procedure in which footprinted executables are shipped from a remote site to a host site, where footprint reports are run to compare the executables' footprints with host Master Control File (MCF) information.

remote nodename

A remote nodename is part of a package shipment destination that identifies the site to which package outputs are to be shipped. The name must be valid for the selected data transmission program.

request data set

A request data set contains action requests to be submitted for batch processing. You create request data sets in foreground using the SCL Generation facility.

request for data

The request for data is a package exit capability allowing package exit programs to make multiple, successive requests for CA Endevor SCM information on a single invocation of the exit.

reset a package

The reset a package action erases all package event records, returning the package to In-edit status.

Resource Security Table

The Resource Security Table defines the element names that are restricted to a particular system and subsystem, within a specific environment. The Resource Security Table is defined by the CA Endevor SCM administrator using the CONSDEF macro. Each CA Endevor SCM environment can contain, at most, one Resource Security Table.

Restore action

The Restore action restores an element to CA Endevor SCM from an archive data set.

Retrieve action

The Retrieve action copies any level of an element to an external data set.

Return Code (NDVR RC)

The return code (NDVR RC) results from action processing. Values can be 00, 04, 08, 12, and 16.

reverse delta

The reverse delta is a method for recording changes that stores the most recent version of the code, rebuilding prior versions by backing out individual changes from the current version.

review a package

A review a package is performed to review the contents of the package. After reviewing a package, an approver approves it or denies it.

route

A route is a series of environment and stage locations that make up the stages in a software life cycle. Working together, all the routes at a site constitute the map for that site.

SCL (Software Control Language)

Software Control Language (SCL) is the CA Endevor SCM language that is used in batch processing to maintain or act against elements within CA Endevor SCM.

security

Security is a CA Endevor SCM feature that allows you to restrict action requests and access to elements. The security system supplied with CA Endevor SCM (known as native security) is implemented using three tables.

sharable

A sharable package can be edited by users who did not create the package.

ship utility

The ship utility is a CA Endevor SCM utility that allows you to ship package outputs to remote sites.

shipment confirmation

Shipment confirmation occurs in a package shipment after executing the data transmission utility and after executing the remote copy or delete job step.

shipment staging

Shipment staging is the creation and population of host staging data sets with package outputs or backout members.

Signin action

The Signin action removes the current signout for an element. Signin can be implicit or explicit.

signout

A signout is the assignment of a user ID to an element, establishing ownership of the element. Signout is automatic when adding or updating elements in, or when retrieving elements from, CA Endevor SCM.

site

The site is the location at which CA Endevor SCM is installed. The site is defined in the CA Endevor SCM Defaults Table, where it is assigned a site ID.

Software Control Language (SCL)

Software Control Language (SCL) is the CA Endevor SCM language that is used in batch processing to maintain or act against elements within CA Endevor SCM.

software lifecycle

The software lifecycle defines the stages through which software passes at a site during development and maintenance. A software lifecycle may consist of development, testing, quality assurance, and production.

software management

Software management is the process of tracking changes to software components and their interrelationships over time. This process includes configuration management, library management, software distribution, and version control.

source

The source is the non-executable form of an element.

source management

Source management is the aspect of CA Endevor SCM that deals with the creation and maintenance of element source. Element source is maintained in base and delta libraries in an internal format or in standard IBM format (if reverse deltas and non-encryption are selected).

source output library

A source output library is a CA Endevor SCM library that contains the latest full source version of each element. This library is designed for use with copybooks, macros, procedures, and so forth that are copied to other places. This is an optional library. However, if used, it is specified in the definition of the corresponding element type.

sourceless element

A sourceless element is created when the Generate NoSource action does not find the element source at the target location and then uses the first element source found up the map from the target to generate the element at the target. Because the element source is not fetched back to the target location, the MCF record for the element generated at the target identifies it as a sourceless element. The MCF element contains the last level timestamp of the upstream element. Base and deltas do not exist for the sourceless elements, so these fields are blank in the MCF. When actions are performed against sourceless elements, the source from the next sourced element upstream from it is used, providing that the last level timestamps are equal.

stage

A stage is a step in the software lifecycle. There are two stages defined for each CA Endevor SCM environment.

stage ID

The stage ID is an identifier for the stage that is used when processing an element action to select (identify) the stage you want to process.

stage name

The stage name is assigned to each stage during CA Endevor SCM installation. A stage name can include any of the following characters: A-Z, 0-9, @, #, and $.

stage number

The stage number (either 1 or 2) is the relative number for the stage within the environment.

stage title

The stage title (up to 20 characters) is assigned to each stage and is used in displays and reports to describe the stage.

standard approval

A standard approval is one of two types of package approval. Standard packages can be approved only by standard approver groups.

standard package

A standard package is one of two types of packages (standard or emergency). Standard packages require approval from standard approver groups.

STOPRC

The STOPRC value provides a control for processing during batch execution by setting your highest acceptable return code for the action that is currently processing. Batch processing will terminate if the return code for the executed action exceeds the STOPRC value. The STOPRC value is set by the statement SET STOPRC nn specified as input to the SCL run. Also, the STOPRC value can be set from the Batch Options Menu when building SCL in foreground for execution in batch, and it can be set on the Create/Modify Package panel when creating or modifing a package. Valid values are 4 to 16. The default is 16.

subsystem

A subsystem is a part of the CA Endevor SCM classification of an element. Subsystems are used for specific applications within a system. For example, you may have a purchase order and accounts payable subsystem within the financial system.

symbolic

A symbolic is used by CA Endevor SCM processors to represent a value specific to an individual run of a processor. CA Endevor SCM supports two kinds of symbolics (CA Endevor SCM symbolics and user symbolics). CA Endevor SCM symbolics (preceded by &C1) are used in CA Endevor SCM processors to represent a value specific to an individual run of the processor. Values are assigned to CA Endevor SCM symbolics when the processor is executed. User symbolics are defined by users in JCL PROC statements in processors. You can use one processor in multiple processor groups.

synchronize

A synchronize conflict is detected when transferring or moving an element with history, if the current level of the target does not match any level of the source. CA Endevor SCM searches for the level of the target to match a level of the source, and this level becomes the synchronization level. When there is a synchronization conflict, CA Endevor SCM does not allow the element to be transferred or moved unless the synchronization flag (SYNC option) is set to Y.

system

A system is a way to classify elements in CA Endevor SCM (defined to each environment where it will be used). A system typically represents the applications at a site. For example, you may have financial and manufacturing applications.

System Management Facilities (SMF) interface

The System Management Facilities (SMF) interface is an optional interface to IBM's System Management Facilities (SMF) that allows you to record historical information through SMF records. In CA Endevor SCM, they are called Action Records or Security Records. This information is used to generate historical reports. The implementation of the SMF interface is optional at each site, and the recording of historical information is optional within each environment.

Transfer action

The Transfer action transports elements from a source location to a target location. Each location can be a CA Endevor SCM location or an archive data set.

transmission method

The transmission method is a part of package shipment destinations to identify the transmission utility to be used to ship packages to the destination.

transportable footprint

A transportable footprint is a CA Endevor SCM footprint that can be imbedded in DOS/VSE- and VM/CMS-bound object modules using a z/OS compiler, a VSE compiler, or a VM compiler.

type

A type is a category of source code that is used as part of the classification of a CA Endevor SCM element. For example, there are types for COBOL (COBOL code), COPYBOOK (copybooks), JCL (JCL streams), and so forth.

type processing sequence

A type processing sequence is a relative sequence of processing for the element types defined to each system. By defining a processing sequence, for example, you can make sure that copybooks (type COPYBOOK) are updated before any COBOL programs (type COB) that may use the copybooks.

Unload utility

The Unload Utility unloads and validates the contents of the VSAM Master Control Files (base and delta files associated with the environments and systems specified on the job request). The file created by the Unload function contains a backup of all internal MCF definitions (system, subsystem, type, type sequence, data set, element master record) and base or delta data (element base, element delta, component base, component delta). Packages contained within a package data set can also be unloaded. The utility can be run for an entire environment or for selected systems within an environment. Unload may also be directed to back up an entire package data set or individual packages.

Update action

The Update action adds a member to CA Endevor SCM when an element with the same name is located in the target entry stage.

User Exit table

The User Exit Table identifies exit programs to be called at each CA Endevor SCM exit point.

user ID

The user ID is used in TSO for actions that run in foreground for the session. For those actions run in batch, the user ID is the job name or the ID specified through the USER= parameter on the job card, depending on how your CA Endevor SCM Defaults Table is set up.

user menu facility

The user menu facility allows your CA Endevor SCM administrator to attach user-defined functions to the CA Endevor SCM TSO/ISPF front end.

User Security table

The User Security Table defines the systems and subsystems to which users have access, and for each system and subsystem, the type of processing (authorization level) allowed. Each environment has one User Security Table.

using elements

A using element is an element that uses a component element. For example, programs that use copybook COPYA are known as the using elements for COPYA. For more information, see the Autogen action option.

validate

The validate function allows you to ensure the integrity of one or more existing CA Endevor SCM environments and systems, and their related elements and components. These are the same checks performed as part of Unload processing, allowing this function to operate in a stand-alone mode.

Validate action

The Validate action performs element master, synchronization, and component validation checks against the element you specify. These inventory validation checks can be performed at any time, enabling developers to ensure the integrity of elements before including them in a package. This is a batch only action and is not supported in a package.

version

The version is a two-digit identifier associated with an element. You cannot have two versions of an element in the same environment.

version control

Version control is the maintenance, tracking, and auditing of modifications to an application over time, allowing prior development versions to be restored.

version number

The version number identifies the version assigned to an element.