actions
An action is a command to manage elements.
Add Elements Action
The Add Elements Action places members from an external data set under control of CA Endevor SCM.
alternate ID
An alternate ID is a facility that protects the CA Endevor SCM-controlled data sets (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. Information for the alternate ID is provided by three parameters in the CA Endevor SCM Defaults Table: RACFGRP, RACFPWD, and RACFUID.
approval
An approval is the electronic signoff mechanism for packages. An approval may be required for a package before execution.
approved
The approved status is assigned after the required approvers have reviewed, signed off, and approved a package.
approver
An approver is a person authorized to sign off on a package, prior to 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 only review standard packages related to its authorized inventory areas. When the approver type is Emergency, the approver group can only review emergency packages related to its authorized inventory areas.
Archive Elements Action
The Archive Elements Action writes an element and all related CA Endevor SCM information to a sequential data set.
authorization
An authorization is the ability to perform certain privileged functions within the IBM z/OS environment.
Automated Configuration Manager (ACM)
The Automated Configuration Manager (ACM) is an optional facility that enables 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 compile.
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 will also reverse the backout process.
backout
The backout command returns the executable members of a package to the state they were in prior to 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 that stores the base members for elements defined to CA Endevor SCM. A base library is defined for each element type, but can be shared across types.
base member
The base member is a located in a base library. Each base member corresponds to an element, and contains the source for the base level of the element. Base member names are generated internally by CA Endevor SCM, and do not correspond to the element name unless you use reverse delta with non-encryption.
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 non-interactive programs are executed. In CA Endevor SCM, batch refers to the execution of actions and reports in a non-interactive region, as opposed to execution in foreground.
browse
The browse command lets you view the content of a data set, without being able to change the contents.
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.
cast a package
The cast a package 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.
command field
The command field appears on the second line of panels in which you can specify a TSO command. You can enter any appropriate TSO command in the command field.
comment
A comment is a user-defined remark (up to 40 characters) associated with an action or package. A comment is used in conjunction with CCIDs, and generally describes the reason for the action or purpose of the package.
commit a package
The commit a package 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
The committed status appears after a package has been committed.
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 CA Endevor SCM ACM) 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 SCM ACM). The component list provides an audit trail of program-component information at the time of each compile.
component monitoring
Component monitoring is a feature of CA Endevor SCM ACM that lets you 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.
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 lets you specify a number of delta levels to retain when a member reaches the consolidation level specified for its type. If you do not specify the number of levels to retain, CA Endevor SCM consolidates all levels.
control section (CSECT)
The control section (CSECT) is an IBM term for the part of a program that is a relocatable unit and for which all components are loaded into adjoining main storage locations.
Copy Elements Action
The Copy Elements Action copies an element from an archive data set to a data set external to CA Endevor SCM.
copyback
A copyback (also known as fetch) 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
Create a package is performed to build the SCL for a package, and then associate the SCL with other package-related information such as a package ID, an execution window, and so forth.
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 name (DSN)
The data set name (DSN) is the data set name for the SCL.
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, provided you have proper authority.
default
A default value is the value that CA Endevor SCM assumes to be in a field or statement if you do not provide an alternative value. On foreground panels, fields usually display default values.
defaults table
The defaults table is a reference to C1DEFLTS, also known as the CA Endevor SCM Defaults Table.
Delete Elements Action
The Delete Elements 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 a ELIB file that stores the delta members for elements defined to CA Endevor SCM. A delta library is defined for each element type.
delta member
A delta member is a member in a delta library. Each delta member corresponds to an element, and contains all the levels for that element subsequent to the base level. Delta member names are generated internally by CA Endevor SCM and do not correspond to the element name, unless reverse deltas are used.
denied
A denied status of a package appears when the package has been reviewed, but denied, by an approver.
deny a package
The deny a package 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 Elements Action
The Display Elements 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, or sequential data set that has been placed under control of CA Endevor SCM. The default element name is the member name.
element change
The element change is a view of element information that shows the current level of an element, annotated to indicate the level at which each line was added to the source.
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
The element history is a view of element information that 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
The element master is a view of Master Control File (MCF) information about an element.
element name
The element name is the name assigned to an element, used to identify the element within CA Endevor SCM. It is recommended that any outputs created by output management be assigned the name of the corresponding element. Element names must be unique within each system, subsystem, and type combination.
element summary of levels
The element 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.
emergency approval
Emergency approval is assigned to emergency packages. 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.
Endevor classification
Endevor classification is the system, subsystem, and type associated with an element.
Endevor Defaults Table
The Endevor Defaults Table (also known as C1DEFLTS) is a table of site-specific information necessary for CA Endevor SCM operation. The Endevor Defaults Table includes environment and stage definitions, installed options, and site-specific hardware settings. There is only one Endevor Defaults Table for each site.
Endevor LIB
An Endevor LIB (ELIB) is a high performance alternative to OS partitioned data sets under CA Endevor SCM. These 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.
Endevor Link
Endevor Link is a CA product that enables communication between CA Endevor SCM Workstation and CA Endevor SCM. This is also known as CA Endevor SCM Change Manager Link Option.
Endevor listing libraries
Endevor listing libraries are libraries used to store compressed compiler listings produced by processors.
Endevor location
The Endevor location refers to the stage and environment where an element resides.
Endevor Parallel Development Manager (PDM)
Endevor Parallel Development Manager (PDM) is a CA product that automatically compares and integrates three versions of source code, allowing you to resolve conflicts resulting from concurrent development or from applying vendor updates to applications that have been customized in-house. Also known as the CA Endevor SCM Change Manager Parallel Development Option.
ENDEVOR return code (NDVR RC)
The ENDEVOR return code (NDVR RC) results from action processing. Values can be 00, 04, 08, 12, and 16.
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).
execute a package
The execute a package 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 as member 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 a package 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, eTrust CA-ACF2 Security, or eTrust CA-Top Secret Security. It is also known as the Endevor Change Manager Interface for External Security.
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/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 foreground by requesting those actions through the 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 (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 Elements Action
The Generate Elements Action translates source into executables, and then populate 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.
Global Type Sequencing
Global Type Sequencing is an optional method of defining the order in which element actions are processed. When global type sequencing is enabled, element actions are processed by type sequence regardless of the inventory location of each action. API element actions (if wildcarded) and SCL element actions are executed in the type sequence order defined at the site level in the Type Sequence member created by the CA Endevor SCM administrator.
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.
image
An image is the current level of an element, when the element is stored in reverse delta format, using non-encryption.
image library
An image library is a library that contains elements stored in reverse delta format, using non-encryption.
import a package
The import a package 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 can be defined for each element type. The INCLUDE library is used by Retrieve Elements actions if you specify that you want to expand INCLUDEs at the time the element is retrieved. It is also used by the CONWRITE utility, if you specify that you want to expand INCLUDEs 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 CA Endevor SCM ACM. 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 lets you analyze your software inventory, classifying it according to CA Endevor SCM types. This product is 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 moves 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 Elements Action
The List Elements 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.
List Panel
The List Panel is used by CA Endevor SCM to display lists of systems, subsystems, types, elements, or members, and also displays selection options for users. List panels are prepared and processed by the ISPF Table Display Facility.
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.
model transmission control statements
Model transmission control statements control the functioning of data transmission programs used by the package shipment utility.
Move Elements Action
The Move Elements 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 mask
A name mask enables you to use the asterisk (*) wildcard character and percent sign (%) placeholder characters when performing actions. Use the wildcard character to specify all names or all names beginning with a particular search string. Use the placeholder character to define a specific position within the search string. For example, the search string UPD% would return four character names beginning with UPD.
native security
The native security is an option supplied with the CA Endevor SCM installation files.
notification facility
The notification facility is a CA Endevor SCM facility that lets you 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 CA Endevor SCM ACM. 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 which 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 lets you 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 an environment.
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, 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.
partitioned data set (PDS)
A partitioned data set (PDS) is a data set in direct access storage that is divided into partitions, called members. Each member can contain a program, part of a program, or data.
Print Elements Action
The Print Elements Action prints element or member information.
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 CA Endevor SCM ACM. 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)
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/updated.
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 lets you 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, eTrust CA-ACF2 Security, and eTrust CA-Top Secret Security, that lets you 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, eTrust CA-ACF2 Security, and eTrust CA-Top Secret Security.
promote
The promote action is used to move 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.
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 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, both in terms of change to the statements stored for the base level (known as base regression) and change 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 lets you recover a CA Endevor SCM VSAM control file (Master Control File, package data set) or a base/delta data set that was lost as a result 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 Elements Action
The Restore Elements Action restores an element to CA Endevor SCM from an archive data set.
Retrieve Elements Action
The Retrieve Elements Action copies any level of an element to an external data set.
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 either approves or denies the package.
route
A route is a series of environment and stage locations that make up the stages in a software lifecycle. Working together, all the routes at a site constitute the map for that site. See also map.
security
Security is a CA Endevor SCM feature that lets you 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 lets you 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/delete job step.
shipment staging
Shipment staging is the creation and population of host staging data sets with package outputs or backout members.
Signin Elements Action
The Signin Elements 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 distribution
Software distribution is the automated distribution and synchronization of software changes and the tracking of the implementation of the changes.
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 library
A source library is any of several libraries used during source management, including CA Endevor SCM base libraries, delta libraries, and INCLUDE libraries.
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 either 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.
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 only be approved 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.
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.
symbolics
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 synchronize 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)
System Management Facilities (SMF) is IBM's SMF.
System Management Facilities (SMF) interface
The System Management Facilities (SMF) interface is an optional interface to IBM's System Management Facilities (SMF) that lets you 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.
System Management Facilities (SMF) records
System Management Facilities (SMF) records are written out if SMF recording is in effect, to document various CA Endevor SCM processing. An Action Record is written out at the end of (any) action processing, while a Security Record is written out for each security violation (or each error returned from the security exit, 01).
Transfer Elements Actions
The Transfer Elements Action transports elements from a source location to a target location. Each location can be either 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 footprints
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/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 backup an entire package data set or individual packages.
Update Elements Action
The Update Elements 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.
validate
The validate function lets you 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 standalone mode.
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.
vvll
The vvll identifier refers to a particular version (vv) and level (ll) of element source.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|