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.

Author: Fele Voodoogar
Country: Reunion
Language: English (Spanish)
Genre: Technology
Published (Last): 8 June 2015
Pages: 341
PDF File Size: 17.42 Mb
ePub File Size: 12.22 Mb
ISBN: 509-8-86402-179-8
Downloads: 72849
Price: Free* [*Free Regsitration Required]
Uploader: Tot

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. Please help improve this article by adding citations to reliable sources. Endevor supports release management in the form of package control. Retrieved from ” https: This is due to the security model within Endevor for which requires explicit security access.

Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast. This means that if the internal Endevor system userid is not linked into one of the approver groups when a package is cast then the Endevor batch system can not execute commands against that package. Endevor provides control of source and related code objects as individual elements.

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.

There are several exit types, each attached to a specific Endevor function.

MAINFRAME MATERIALS – ENDEVOR

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. Articles needing additional references from August All articles needing additional references. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed.

  ALCHEMIA UWODZENIA AGNIESZKA ORNATOWSKA PDF

An exit will specify where in the exit tree that the code will be executed and what will be affected. Each security group specifies a list of users authorised to act for that group with a set quorum per group. By using this site, you agree to the Terms of Use and Privacy Policy. The system uses these values to determine the source and target locations.

This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. 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, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments.

Languages Deutsch Edit links.

Unsupported SSL/TLS Version

The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. 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 the Endevor product does not have a scheduling component a third party tool such as IBM Manua, Workload Scheduler or CA7 must be used to execute Endevor packages according to release schedule.

The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory. Every element is distinguished by the element name, system, subsystem and type.

The reference “element” is used to define the smallest object for which Endevor controls. A package is a container for Endevor SCL and associated control information for code release. 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.

  LIBRO LA PANZA DEL TEPOZTECO PDF

In this manner Endevor can be configured to handle most mainframe files. Endevor administrators can modify Endevor functions and capture information using exits. These changes are only applicable to the package being cast and are not permanent changes to approver group configuration.

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.

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

The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. 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.

Every generate, move and delete action is executed by calling a processor.

Endevor supports release management, maiinframe defined by ITIL in the form of package control. Endevor maintains configuration control for each element registered in the system. From Wikipedia, the free encyclopedia. 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.

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

A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required.