Endevor User Guide – Free download as Word Doc .doc), PDF File .pdf), Text File .txt) or read online RETAIL OPERATIONS MAINFRAME TOOLS SUPPORT. AllFusion® Endevor® Change ManagerAutomated Configuration Option Guide r7 FE This documentation Mainframe Basics For a complete list of Endevor manuals, see the PDF Table of Contents file in the PDF directory, or the . Endevor is a source code management and release management tool for mainframe computers running z/OS. It is part of a family of administration tools by CA.

Author: Kazilabar Voodoozilkree
Country: Cuba
Language: English (Spanish)
Genre: Automotive
Published (Last): 20 August 2008
Pages: 334
PDF File Size: 13.52 Mb
ePub File Size: 2.4 Mb
ISBN: 573-8-91311-583-2
Downloads: 53629
Price: Free* [*Free Regsitration Required]
Uploader: Dozahn

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. Each approver group has a set quorum for which can be set to 0 to Every generate, move and delete action is executed by calling a processor.

Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments. The default system processor executes a standard copy, move or delete action.

Generally, result of invoking a generate processor endecor that the source code is copied to the appropriate source library and, in the case of programs, the source is compiled and linked and the load modules are copied to the target stage load libraries.

A security table can be defined per Endevor environment mainfframe provide granular control for element actions down to per user if required. This is due to the security model within Endevor for which requires explicit security access. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values.

An Endevor exit program has access to most of the information relevant to the action being performed, for example name of the package, package action, package contents, etc.

In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process. 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.


Endevor maintains configuration control for each element registered in the system. This page was last edited on 20 Septemberat Languages Deutsch Edit links. As a general rule, when package control is used for an Endevor stage then every Endevor system will have at least one approver group for that stage and the approver group would have a quorum of zero.

Unsupported SSL/TLS Version

In most cases, an element mainfrmae stored internally by Endevor as the code base with subsequent changes stored as deltas. Please help improve this endevoor by adding citations to reliable sources. As the Endevor product does not have a scheduling component a third party tool such as IBM Tivoli Workload Scheduler or CA7 must be used to execute Endevor packages according to release schedule.

Many functions executed in interactive mode are completed in batch mode.

As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast. Endevor administrators can modify Endevor functions and emdevor information using exits. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. This security table defines the access control lists defined by groups endveor which users are assigned to and lists the stages for which users can interact with.

All Endevor element functions are described using a propriety Software Control Language. Endevor provides control of source and related code objects as individual elements. 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 majnframe the target to source libraries.

Endevor – Wikipedia

The system uses these values to determine the source and target locations. The reference “element” is used to define the smallest object for which Endevor controls.

Every element is distinguished by the element name, system, subsystem and type. Processors can use both Endevor symbols and Endevor variables.

As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. Security tables are standard mainframe compiled assembler reference binary lookup tables. It also competes against another CA source code management tool, Panvalet.


Each approver in an approver group can be defined as being a mandatory or optional approver by specifying a flag in the approver group endevir. Unsourced material may be challenged and removed. Systems with names in italics are no longer maintained or have planned end-of-life dates.

Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package. As an example, an exit could fail the generate action where the CCID is invalid.

Moves an element from any source stage mainfarme any target stage. A key attribute of package control is that security approver groups can be linked to each package. 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.

Views Read Edit View history.

The ADD instruction can be used to define a new element to an Endevor stage or add a mainframme registered element to the first stage in a define lifecycle. By using this site, you agree to the Mainfraem of Use and Privacy Policy. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. This allows for the users mainfrme Endevor, such as developers, to be separated from the control of the objects which they modify using Endevor functions.

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. A package is a container for Endevor SCL and associated control information for code release. Exits are generally used to enforce system policy and enhance Endevor functionality.

Which approver groups are linked to ehdevor package is based on the approver group rules. The same functionality for source control and release management functions are provided by several other products.