Ximi Elga


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: Kigakazahn Gujinn
Country: Haiti
Language: English (Spanish)
Genre: Travel
Published (Last): 22 November 2012
Pages: 325
PDF File Size: 11.88 Mb
ePub File Size: 11.16 Mb
ISBN: 936-7-61140-466-8
Downloads: 14865
Price: Free* [*Free Regsitration Required]
Uploader: Grorn

Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast. Every type has at least one processor defined for which lists the name of the processor that performs the action required.

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. Each approver in an approver group can be defined as being a mandatory or optional approver by specifying a flag in the approver group definition.

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. 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 manuual update access to libraries controlled by Endevor.

Endebor from ” https: 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 reference “element” is used to define the smallest object for which Endevor controls. Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments. The system uses these values to determine the source and target locations. Endevor systems are defined by mainffame specific symbol table which is essentially a list of name pair values.


By using this site, you agree to the Terms of Use and Privacy Policy. Endevor native security is a built in security mwnual which allows Endevor Administrators maihframe define approver groups per Endevor Environment, approver group relationships per Endevor Environment and security tables per Endevor Environment and for specific Endevor functions. This is due to the security model within Endevor for which requires explicit security access.

This security table defines the access control lists defined by groups for which users are assigned to and lists the stages for which users can interact with.

Systems with names in italics are no longer maintained or have planned end-of-life dates. Deletes the target element registration and deletes the associated element source and load modules. Moves an element from any source stage to any target stage. Click here for details. Which approver groups are linked to a package is based on the approver group rules. An exit is generally used to determine when and manuzl 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.

This article needs additional citations for verification. Unsourced material may be challenged and removed. The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries.

Each security group specifies a list of users authorised to act for that group with a set quorum per group. Access to Endevor Environments is defined by a single security table per Endevor environment. Each approver group can have up to 16 userids.

Endevorr groups can be dynamically altered by Endevor exits at cast time, for example, to change the quorum, link an manuql approver group, or to add mainframf remove users from an approver group. The same functionality for source control and release management functions are provided by several other products. There are several exit types, each attached to a specific Endevor function.


Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. As an example, an exit could fail the generate malnframe where the CCID is invalid.

Endevor Package Editor tutorial

Every generate, move and delete action is executed by calling a processor. Endevor administrators can modify Endevor functions and capture information using exits. Views Read Edit View history. 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. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being ,anual.

These changes are only applicable to wndevor package being cast and are not permanent changes to approver group configuration. This means for every system referenced in amnual package there will be at least one approval required. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. Articles needing additional references from August All articles needing additional references.


There is no limit to how many approver groups can be linked to a single package. Processors can use both Endevor symbols and Endevor variables. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required.

The default system processor executes a standard copy, move or delete action. Exits are generally used to enforce system policy and enhance Endevor functionality.

Years, where available, indicate the date of first stable release. Endevor maintains configuration maintrame for each element registered in the system. From Wikipedia, the free encyclopedia. Retrieved 15 May Each Endevor environment has a granular breakdown of functions specific to that environment.