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 June 2018|
|PDF File Size:||7.39 Mb|
|ePub File Size:||11.12 Mb|
|Price:||Free* [*Free Regsitration Required]|
Endevor native security is a built in security option which allows Manul 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.
The same functionality for source control and release management functions are provided by several other products. Endevor supports release management, as defined by ITIL in the form of package control.
Processor code looks like and executes similar to JCL. As a general rule, when package control is used for an Endevor 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.
As a general rule general mainframe users are prohibited from modifying Endevoe controlled libraries. These changes are only applicable to the package being cast and are not permanent changes to approver group configuration.
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 nainframe schedule. Unsourced material may be challenged and removed.
The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. August Learn how and when to remove this template message. This is due to the security model within Endevor for which requires explicit security access. Endevor administrators can modify Endevor functions and capture information using exits.
Retrieved from ” https: A key attribute of package control is that security approver groups mainrame be linked to each package.
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. 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 endevo. It also competes against another CA source code management tool, Panvalet. The janual 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.
The reference “element” is used to define the smallest object for which Endevor controls. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes.
Please help improve this article by adding citations to reliable sources. The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory. Access to Endevor Environments is defined by a single security table per Endevor environment. Views Read Edit View history. Many functions executed in interactive mode are completed in batch mode.
These tables are where the access for Endevor functions is defined when using native security. 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. 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.
Articles needing additional references from August All articles needing additional references. Every element is distinguished by the element name, system, subsystem and type.
Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. The default system processor executes a standard copy, move or delete action.
Retrieved 15 May Which approver groups are linked to a package is based on the approver group rules. Endevor provides control of source and related code objects as individual elements.
At a minimum a package has a name, an execution window defined the mainftame range for when the package can be executed, notes about the package, various flags and at least one value SCL statement.
Endevor supports release management in the form of package control. Each approver group can have up to 16 userids.
This security table defines the access control lists defined by groups for which users are assigned to and lists the stages for which users can interact with.
There are several exit types, each attached to a specific Endevor function. Languages Deutsch Edit links.
Click here for details. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package. Endevor maintains configuration control for each element registered in the system. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required.
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.
The first 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.