MAINFRAME ENDEVOR MANUAL PDF
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):||27 June 2017|
|PDF File Size:||13.19 Mb|
|ePub File Size:||7.55 Mb|
|Price:||Free* [*Free Regsitration Required]|
Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR.
These changes are only applicable to the package being cast and are malnframe permanent changes to approver group configuration. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes.
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 encevor and linked and the load modules are copied to the target stage load libraries. Retrieved from ” https: 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.
Unsupported SSL/TLS Version
Retrieved 15 May This allows for defined systems development lifecycle stages to have set approvers and controlled releases. 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.
Which approver groups are linked to a package is based on the approver group rules. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package. Endevor supports release management, as defined by ITIL in the form of package control. Endevor administrators can modify Endevor functions and capture information using exits. 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.
Views Read Edit View history. Each approver group can have up to 16 userids.
Endevor – Wikipedia
This means for every system referenced in the package there will be at least one approval mainfarme. Exits are generally used to enforce system policy and enhance Endevor functionality. This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted.
This page was last edited on 20 Septemberat Every generate, move and delete action is executed by calling a processor. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. Access to Endevor Environments is defined by a single security table per Endevor environment. Please help improve this article by adding citations to reliable sources.
The type definition determines how the element is stored and how manuaal changes, known as deltas, are handled. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast.
There are several exit types, each attached to a specific Endevor function.
Years, where available, indicate the date of first stable release. 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.
Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast. These tables are where the access for Endevor functions is defined when using native security. The system uses these values to determine the source and target locations.
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.