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: Mezinris Tuzil
Country: Timor Leste
Language: English (Spanish)
Genre: Personal Growth
Published (Last): 21 March 2007
Pages: 324
PDF File Size: 9.39 Mb
ePub File Size: 9.70 Mb
ISBN: 443-9-97973-524-4
Downloads: 87138
Price: Free* [*Free Regsitration Required]
Uploader: Kikus

A package is a container for Endevor SCL and associated control information for code release. As an example, an exit could fail the generate action where the CCID is invalid.


This allows for defined systems development lifecycle stages to have set approvers and controlled releases. From Wikipedia, the free encyclopedia. The move function moves an element registration from the target to the source stage and also, by invoking a move processor, moves endevir element output objects from the target to source libraries. In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas.

Every type has at least one processor defined for which lists the name of the processor that performs the action required. Click here for details. Every generate, move and delete action is executed by calling a processor. This article needs additional citations for verification.

As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast.

It also competes against another CA source code management tool, Panvalet. Years, where available, indicate the date of first stable release. Exits are generally used to enforce system policy and enhance Endevor functionality. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process.

Endevor Package Editor tutorial

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.


Access to Endevor Environments is defined by a single security table per Endevor environment. 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. The ADD instruction can be used to define a new element to an Endevor stage or add a previously registered element to the first stage in a define lifecycle.

Which approver groups are linked to a package is based on the approver group rules. Retrieved 15 May A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. Each approver group has a set quorum for which can be set to 0 to Generally, the result of issuing an ADD function is that the element will be registered to the target Endevor stage, or the element registration will be updated in the target stage and the appropriate generate processor will be invoked.

Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast. Endevor native security is a built in security option which allows Endevor Administrators to define approver groups per Endevor Environment, approver group relationships per Endevor Environment and security tables per Endevor Environment and for specific Endevor functions.

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. The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries.

A key attribute of package control is that security approver groups can be linked to each package. Endevor provides control of source and related code objects as individual elements. Every element is distinguished by the element name, system, subsystem and type.

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. The default system processor executes a standard copy, move or delete action. By using this site, you agree to the Terms of Use and Privacy Policy.


In this manner Endevor can be configured to handle most mainframe files. All Endevor element functions are described using a propriety Software Control Language. Systems with names in italics are no longer maintained or have planned end-of-life dates. Each approver in an approver group can be defined as being a mandatory or optional approver by specifying a flag in the approver maindrame definition. These tables are where the access for Endevor functions is defined when using native security.

Languages Deutsch Edit links. As Endevor provides an interface manuzl creating, modifying, moving, deleting and transferring ensevor via pre-defined lifecycles there is no need for any end user to have alter or update access to libraries controlled by Endevor. Approver groups can be dynamically altered by Endevor exits at cast time, for example, to change the quorum, link an additional approver group, or to add or remove users from an approver group.

This security table defines the access control lists defined by groups for which users are assigned to and lists the stages for which users mamual interact with. Retrieved from ” https: The type definition determines how the element is stored and how subsequent maiinframe, known as deltas, are handled. 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.

The first userid in an approver group is generally always set to be the Endevor internal system userid ebdevor which grants the Endevor batch system the authority to execute package actions. The system uses these values to determine the source and target locations.

Endevor systems are defined by a specific symbol table which is essentially a list of name pair values. Moves endecor element from any source stage to any target stage.