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.
An approver group quorum of zero is used for approver groups where the users either need to be informed of package actions or users require the ability to DENY a package but are not explicitly required to approve.
Retrieved 15 May These changes are only applicable to the package being cast and are not permanent changes to approver group configuration. There are several exit types, each attached to a specific Endevor function.
There is no limit to how many approver groups can be linked to a single package. Which approver groups are linked to a package is based on the approver group rules.
All Endevor element functions are described using a propriety Software Control Language.
Each security group specifies a list of users authorised to act for that group with a set quorum per group. 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.
Endevor provides control of source and related code objects as individual elements.
Endevor Package Editor tutorial
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 type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. As an example, an exit could be written to trigger “before package cast” manuak link an additional approver group to the package being cast.
Generally, result of invoking a generate processor is 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 enrevor copied to the target stage load libraries. Exits are generally used to enforce system policy and enhance Endevor functionality. Systems with names in italics are no longer maintained or have planned end-of-life dates.
As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. The default system processor executes a standard copy, move or delete action. Each approver in an approver group can be defined as being a mandatory or optional approver by specifying a flag in the approver group fndevor. Endevor administrators can modify Endevor functions and capture information using exits.
The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries. Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR.
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. 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.
As Endevor provides an interface for creating, modifying, moving, deleting and transferring elements via pre-defined lifecycles there is no need for any mamual user to have alter or update access to libraries controlled by Endevor. Endevor separates the control of source from manuzl objects used as input and the objects created as output when an action is performed. A key attribute of package control is that security approver groups can be linked to each package.
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 maintains configuration control for each element registered in the system. 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 same functionality for source control and release management functions are nanual by several other products.
The first userid in an approver group is generally always set to be the Endevor internal system userid “NDVR” which grants the Endevor batch system the authority to execute package actions. Years, where available, indicate the date of first stable release.
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. Processor code looks like and executes similar to JCL. The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory. Every generate, move and delete action is executed by calling a processor. Unsourced material may be challenged and removed.
Retrieved from ” https: 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. Access to Endevor Environments is defined by a single security table per Endevor environment. It also competes against another CA source code management tool, Panvalet. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values.
The ADD function invokes a generate processor which then mainfrmae all actions required to register or update the element metadata and process outputs. This means for every system referenced in the package there will be at least one approval required. Many functions executed in interactive mode are completed in batch mode. Any Mznual stage which is flagged as being packaged controlled requires all actions to be executed using a package.