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):||7 June 2015|
|PDF File Size:||16.85 Mb|
|ePub File Size:||6.20 Mb|
|Price:||Free* [*Free Regsitration Required]|
Views Read Edit View history. 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.
Unsupported SSL/TLS Version
Retrieved 15 May The system uses these values to determine the source and target locations. The reference “element” is used to define the smallest object for which Endevor controls.
Endevor systems are defined by a specific symbol table which is essentially a list of name pair msinframe. Endevor supports release management, as defined by ITIL in the form of package control.
In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process. Please help improve this article by adding citations to reliable sources. All Endevor element functions are described using a propriety Software Control Language.
MAINFRAME MATERIALS – ENDEVOR
Mainfrmae to Endevor Environments is defined by a single security table per Endevor environment. Endevor maintains configuration control for each element registered in the system.
The same functionality for source control and release management functions are provided by several other products. 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.
Security tables are standard mainframe compiled assembler reference binary lookup tables. As the Endevor product does not have a scheduling component a third party tool such as IBM Tivoli Workload Scheduler or CA7 must be manjal to execute Endevor packages according to release schedule.
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 mainfrane. This is due to the security model within Endevor for which requires explicit security access.
Endevor Package Editor tutorial
Moves an element from any source stage to any target stage. 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.
August Learn how and when to remove this template message. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. 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. As an example, an exit could fail the generate action where the CCID is invalid. 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.
Unsupported SSL/TLS Version
Every element is distinguished by the element name, system, subsystem and type. 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. Languages Deutsch Edit links. A key attribute of package control is that security approver groups can be linked to each 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.
Every type has at least one processor defined for which lists the name of the processor that performs the action required.