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.
|Published (Last):||21 August 2011|
|PDF File Size:||11.44 Mb|
|ePub File Size:||4.43 Mb|
|Price:||Free* [*Free Regsitration Required]|
Please help improve this article by adding citations to reliable sources. 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.
It also competes against another CA source code management tool, Panvalet. A package is a container for Endevor SCL and associated control ebdevor for code emdevor. Endevor provides control of source and related code objects as individual elements. Every element is distinguished by the element name, system, subsystem and type. A key attribute of package control is that security approver groups can be linked to each package.
Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. This means that if the internal Endevor system maual is not linked into one of the approver groups when a package is cast then the Endevor batch system can not execute commands against that package.
The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values.
Each security group specifies a list of users authorised to act for that group with a set quorum per group. Processor code looks like and executes similar to JCL. Each Endevor environment has a granular breakdown of functions specific to that environment.
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 mainfrxme package but are not explicitly required to approve. Many functions executed in interactive mode are completed in batch mode.
Endevor – Wikipedia
Endevor administrators can modify Endevor functions and capture information using exits. There are several exit types, each attached to a specific Endevor function.
Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package. Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments. 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 are copied to the target stage load libraries.
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. Retrieved 15 May As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries.
Exits are generally used to enforce system policy and enhance Endevor functionality. In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas. Generally, an approver group will have a quorum of 1, meaning that at least one manuao the users listed in the approver group needs to approve the package in order for the package to progress to the APPROVED status.
Endevor Package Editor tutorial
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. 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 Ehdevor Environment and for specific Endevor functions.
Every generate, move and delete action is executed by calling a processor. This security table defines the access control lists defined by groups for which users are assigned to rndevor lists the stages for which users can interact with.
The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries.
MAINFRAME MATERIALS – ENDEVOR
These changes are only applicable to the package being cast and are not permanent changes to approver group configuration. 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 mankal to libraries controlled by Endevor.
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. This article needs additional citations for verification.