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: Faushura Nigrel
Country: Sudan
Language: English (Spanish)
Genre: Health and Food
Published (Last): 15 October 2009
Pages: 417
PDF File Size: 12.50 Mb
ePub File Size: 13.42 Mb
ISBN: 949-9-69132-565-8
Downloads: 58228
Price: Free* [*Free Regsitration Required]
Uploader: Mikagal

Access to Endevor Environments is defined by a single security table per Endevor environment.

Unsupported SSL/TLS Version

As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. Retrieved 15 May By using this site, you agree to the Terms of Use and Privacy Policy. Each security group specifies a list of users authorised to act for that group with a maknframe quorum per group. This article needs additional citations for verification.

Retrieved from ” https: A key attribute of package control is that security approver groups can be linked to each package. The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries. Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values.

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. Each Endevor environment has a granular breakdown of functions specific to that environment. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast.


This is due to the security model within Endevor for which requires explicit security access.

As a general rule, maanual 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. Endevor maintains configuration control for mainfame element registered in the system. 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.

Endevor Package Editor tutorial

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. 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.

The system uses these values to determine the source and target locations.

Exits are generally used to enforce system policy and enhance Endevor functionality. These tables are where the access for Endevor functions is defined when using native security. Views Read Edit View history. Every element is distinguished by the element name, system, subsystem and type.

Unsupported SSL/TLS Version

The first userid in an approver group is generally always set to be the Endecor internal system userid “NDVR” which grants the Endevor batch system the authority to execute package actions. Processors can use both Endevor symbols and Endevor variables.

Endevor provides control of source and related code objects as individual elements. In this manner Endevor can be configured to handle most mainframe files. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required.

There are several exit types, each attached to a specific Endevor function. Which approver groups are linked to a package is based on the approver group rules. The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. This means for every system referenced in the package there will be at least one approval required.

  COFEN 358 DE 2009 PDF

Endevor Package Editor tutorial

It also competes against another CA source code management tool, Panvalet. The same functionality for source control and release management functions are provided by several other products.

In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas. All Endevor element functions are described using a propriety Software Control Language.

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.

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.

Every generate, move and delete action is executed by calling a processor. An exit will specify where in the exit tree that the code will be executed and what will be affected. From Wikipedia, the free encyclopedia. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process.

Security tables are standard mainframe compiled assembler reference binary lookup tables. 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.