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: | Gusho Brale |
| Country: | Ecuador |
| Language: | English (Spanish) |
| Genre: | Politics |
| Published (Last): | 25 August 2004 |
| Pages: | 198 |
| PDF File Size: | 2.24 Mb |
| ePub File Size: | 18.47 Mb |
| ISBN: | 249-5-11661-572-1 |
| Downloads: | 66635 |
| Price: | Free* [*Free Regsitration Required] |
| Uploader: | Tobar |
Endevor Package Editor tutorial
Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments. The ADD instruction can be used to define a ensevor element to an Endevor stage or add a previously registered element to the first stage in a manuaal lifecycle.
It also competes against another CA source code management tool, Panvalet. Generally, mainfrzme 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. A package is a container for Endevor SCL and associated control information for code release.
This is due to the security model within Endevor for which requires explicit security access.
Endevor Package Editor tutorial
Deletes the target element registration and deletes the associated element source and load modules. 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 system uses these values to determine the source and target locations.
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 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.
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. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package.
This page was last edited on 20 Septemberat Endevor administrators can modify Endevor functions and capture information using exits.
This allows manula defined systems development lifecycle stages to have set approvers and controlled releases. Access to Endevor Environments is defined by a single security table per Endevor environment.
In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas. 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.
Each security group specifies a list of users authorised to act for that group with a set quorum per group. Endevor native security is a built in security option which allows Endevor Administrators to define approver groups per Manuwl 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.
The reference “element” is used to define the smallest object for which Endevor controls. Security tables are standard mainframe compiled assembler reference binary lookup tables.
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. Languages Deutsch Edit links. August Learn how and when to remove this template message. Click here for details. Each approver group can have mnaual to 16 userids.
Endevor separates the control of source from the objects used mainfrwme input and the objects created as output when an action is performed. 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.
Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. Every type has at least one processor defined for mznual lists the name of the processor that performs the action required. The Endevor application executes system actions using two dedicated system accounts for which have endeovr access to write to Endevor controlled libraries. 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. Please help improve this article by adding citations to reliable sources. These tables are where the access for Endevor functions is defined when using native security.
Endevor systems are defined by a specific symbol table which is essentially a list of name pair values. Which approver groups are linked to a package is mznual on the approver mainfgame rules. Each approver group has a set quorum for which can be set to 0 to Endevor provides control of source and related code objects as individual elements.