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):||14 July 2005|
|PDF File Size:||15.64 Mb|
|ePub File Size:||18.77 Mb|
|Price:||Free* [*Free Regsitration Required]|
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. The ADD instruction can be used to define a new element to an Endevor stage or add a enfevor registered element to the first stage in a define lifecycle.
All Endevor element functions are described using a propriety Software Control Ehdevor.
Unsupported SSL/TLS Version
Endevor supports release management, as defined by ITIL in the form of package control. 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.
Generally, there is one security table per Endevor environment, however a single security table can be enddvor by multiple environments. Deletes the target element registration and deletes the associated element source and load modules. August Learn how and when to remove this template message. 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.
mqnual 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.
Click here for details.
Unsupported SSL/TLS Version
Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. There are several exit types, each attached to a manul Endevor function. Every element is distinguished by the element name, system, subsystem and type.
Views Read Edit View history. Please help improve this article by adding citations to reliable sources. Every type has at least one processor defined for which lists the name of endevo processor that performs the action required. Generally, an approver group will have a quorum of 1, meaning that at least one of the users listed in the approver group needs manhal approve the package in order for the package to progress to the APPROVED status.
Endevor supports release management in the form of package control. This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted.
The default system processor executes a standard copy, move or delete action. 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. Years, where available, indicate the date of first stable release. 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.
Retrieved 15 May This article needs additional citations for verification. 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 systems are defined by a specific symbol table which is essentially a list of name pair values. Many functions executed in interactive mode are completed in batch mode. Security tables are standard mainframe compiled assembler reference binary lookup tables. There is no limit to how many approver groups can be linked to a single package.
As such, control of source happens internally to Endevor and source control actions are separate from changes to objects in the output libraries which includes load modules and copies of processed code. As a general rule, when package control is used for an Mainframw 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.
This security table maonframe the access control lists defined by groups for which enfevor are assigned to and lists the stages for which users can interact with. An exit will specify where in the exit tree that the code will be executed and what will be affected. This means for every system referenced in the package there will be at least one approval required.
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.
Processors can use both Endevor symbols and Endevor variables. At a minimum a package has a name, an execution window mainfrmae the time range for when the package can be executed, notes about the package, various flags and at least one value SCL statement. Every generate, move and delete action is executed by calling a processor. 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 enxevor.
Moves an element from any source stage to any target stage.
MAINFRAME MATERIALS – ENDEVOR
This page was last edited on 20 Septemberat This allows for the users of Endevor, such as developers, endeevor be separated from the control of the objects which they modify using Endevor functions. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast. As an example, an exit could fail the generate action where the CCID is invalid.
From Wikipedia, the free encyclopedia.