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: Maurr Yolmaran
Country: Norway
Language: English (Spanish)
Genre: Environment
Published (Last): 4 January 2008
Pages: 269
PDF File Size: 12.45 Mb
ePub File Size: 10.30 Mb
ISBN: 852-6-62235-929-3
Downloads: 21269
Price: Free* [*Free Regsitration Required]
Uploader: Taujora

Security tables are standard mainframe compiled assembler reference binary lookup tables. These changes are only applicable to the package being cast and are not permanent changes to approver group configuration.

Access to Endevor Edevor is defined by a single security table per Endevor environment. 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. 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.

This ensures that an audit trail is maintained for all actions and maual the resulting objects controlled by Endevor can be trusted.

Unsupported SSL/TLS Version

At a minimum a package has a name, an execution window defined the time range for when the package can be executed, notes about the package, various flags and at least one value SCL statement.

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. An exit will specify where in the exit tree that the code will be executed and mankal will be affected. 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.


Years, where available, indicate the date of first dndevor release. Languages Deutsch Edit links. As a general maintrame general mainframe users are prohibited from modifying Endevor controlled libraries.

These tables are where the access for Endevor functions is defined when using native security. 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.

Endevor Package Editor tutorial

Retrieved from ” https: This allows for the users of Endevor, such as developers, to be separated from the mainfrzme of the objects which they modify using Endevor functions. Each security group specifies a list of users authorised to act for that group with a set quorum per group.

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. This page was last edited on 20 Septemberat Exits are generally used to enforce system policy and enhance Endevor functionality. The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory. The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries.

A security table can be aminframe per Endevor environment to provide granular control for element actions down to per user if required. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs.


Every type has at least one processor defined for which lists the name of the processor that performs the action required. Every generate, maimframe and delete action is executed by calling a processor.

Each approver group has mainnframe set quorum for which can be set to 0 to Every element is distinguished by the element name, system, subsystem and type. Which approver groups are linked to a package is based on the approver group rules. A package is a container for Endevor SCL and associated control information for code release. This allows for defined systems development lifecycle stages to have set approvers and controlled releases. This article needs additional citations for verification.

Views Read Edit View history. Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments.

This is due to the security model within Endevor for which requires explicit mainfeame access. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package. In this manner Endevor can be configured to handle most mainframe files.

Click here for details. The same functionality for source control and release management functions are provided by several other products. 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.

Please help improve this article by adding citations to reliable mainfrae. The ADD instruction can be used to define a new element to an Endevor stage or add a previously registered element to the first stage in a define lifecycle.