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):||11 July 2018|
|PDF File Size:||9.42 Mb|
|ePub File Size:||11.26 Mb|
|Price:||Free* [*Free Regsitration Required]|
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.
Access to Endevor Environments is defined by a single security table per Endevor environment.
Endevor Package Editor tutorial
The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. From Wikipedia, the free encyclopedia. The quorum of zero is normally used for a scenario where a specific approver group requires the ability to deny a package in a situation where approval is automatic. Each Endevor environment has a granular breakdown of functions specific to that environment. This means for every system referenced in the package there will be at least one approval required.
In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas.
Unsupported SSL/TLS Version
The same functionality for source control and release management functions are provided by several other products. This is due to the security model within Endevor for which requires explicit security access.
All Endevor element functions are described using a propriety Software Control Language. 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. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the endevpr development life cycle process.
Endevor – Wikipedia
The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries. The default system processor executes a standard copy, move or delete action. 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 access to libraries controlled by Endevor.
There are several exit types, each attached to a specific Endevor function. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. 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.
Systems with names in italics are no longer maintained or have planned end-of-life dates. Security tables are standard mainframe compiled assembler reference binary lookup tables.
Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package. 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.
Deletes the target element registration and deletes the associated element source and load modules. Each security group specifies a list of users authorised to act for that group with a set quorum per group.
August Learn how and when to remove this template message. The nedevor 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.
Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments. Every type has at least one processor defined for which lists the name of the processor that performs the action required. An exit will specify where in the exit tree that the code will be executed and what will be affected. Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR.