You can download a PDF or an EPUB file of an article or content area for offline use. You can choose what you want to download— a page. your use of the CA software to which the Documentation relates; or (ii) a VB record length Action Option field on the CA Endevor Quick-Edit Option panel. Welcome to the CA Endevor Software Change Manager Version bookshelf. Use the Search field on this bookshelf to search the product documentation.
|Published (Last):||5 August 2005|
|PDF File Size:||8.25 Mb|
|ePub File Size:||11.7 Mb|
|Price:||Free* [*Free Regsitration Required]|
An exit will specify where in the exit tree that the code will be executed and what will be affected. Each approver group has a set quorum for which can be set to 0 to The default system processor executes a standard copy, move or delete action. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package.
Getting Started – Installing and configuring and User Guide. I am new to Endevor. Years, where available, indicate the date of first stable release. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values. Articles needing additional references from August All articles needing additional references. Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast.
This article needs additional citations for verification. Click here for details.
The system uses these values to determine the source and target locations. The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory.
It also competes against another CA source code management tool, Panvalet. As Endevor provides an interface for creating, modifying, moving, deleting and transferring elements via pre-defined lifecycles there is no need for any end user to have alter or update access to libraries controlled by Endevor. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process.
Much of what you really need to actually use Endevor will be dependant on how Endevor is customised at your shop. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. As such, control of source happens internally to Endevor and source control actions are separate from changes to objects in the output libraries which includes load modules and copies of processed code.
A package is a container for Endevor SCL and associated control information for code release.
Unsupported SSL/TLS Version
An exit is generally used to determine when and to whom to send emails to, for example to notify Endevor approvers that a package is waiting to be reviewed or that a package has been reset. These changes are only applicable to the package guuide cast and are not permanent changes to approver group configuration. Retrieved from ” https: Each Endevor environment has a granular breakdown of functions specific to that environment.
ca-ndevor Generally, an approver group will have a quorum of 1, meaning that at least one of the users listed in the approver group needs to approve the package in order for the package to progress to the APPROVED status. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. The move function moves an element registration from the target to the source stage and also, by invoking a move processor, moves the element output objects from the target to source libraries.
Every type has at least one processor defined ac-endevor which lists the name of the processor that performs the action required.
Endevor Package Editor tutorial
Many functions executed in interactive mode are completed in batch mode. As the Endevor product does not have a scheduling component a usfr party tool such as IBM Tivoli Workload Scheduler or CA7 must be used to execute Endevor packages according to release schedule.
At a minimum a package has a name, an execution window defined the time range for when the package can be executed, notes about the package, various flags and at least one value SCL statement. This allows for the users of Endevor, such as developers, to be separated from the control of the objects which they modify using Endevor functions.
The same functionality for source control and release management functions are provided by several other products. As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. Unsourced material may be challenged and removed. Access to Endevor Environments is defined by a single security table per Endevor environment.
Exits are generally used to enforce system policy and enhance Endevor functionality.