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):||19 June 2009|
|PDF File Size:||5.94 Mb|
|ePub File Size:||3.56 Mb|
|Price:||Free* [*Free Regsitration Required]|
These tables are where the access for Endevor functions is defined when using native security. Articles needing additional references from August All articles needing additional references. This is due to the security model within Endevor for which requires explicit security access.
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.
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.
An exit will specify where in the exit tree that the code will be executed and what will be affected. Many functions executed in interactive mode are completed in batch mode.
A package is a container for Endevor SCL and associated control information for code nedevor. 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.
Endevor Package Editor tutorial
Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. Each security group specifies a list of users authorised to act for that group with a set quorum per group. 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.
Unsupported SSL/TLS Version
Click here for details. Endevor supports release management in the form of package control.
Security tables are standard mainframe compiled assembler reference binary lookup tables. This allows for defined systems development lifecycle stages to have set approvers and controlled releases. Every element is distinguished by maijframe element name, system, subsystem and type.
The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory.
This ensures that an audit trail is maintained for all actions and that the mannual objects controlled by Endevor can be trusted. Endevor also has a function to allow approvers to be interactively dynamically added manusl an approver group after a package is successfully cast. The default system processor executes a standard copy, move or delete action. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast.
This page was last edited on 20 Septemberat This means that if the internal Endevor system userid 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. 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.
From Wikipedia, the free encyclopedia. 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.
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. Unsourced material may be challenged and removed. The same functionality for source control and release management functions are provided by several other products.
MAINFRAME MATERIALS – ENDEVOR
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. 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.
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. Retrieved from ” https: It also competes against another CA source code management tool, Panvalet.
Endevor Package Editor tutorial
Retrieved 15 May Every generate, move and delete action is executed by calling a processor. Each Endevor environment has a granular breakdown of functions specific to that environment. The reference “element” is used to define the smallest object for which Endevor controls.