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: Shaktigor Vurisar
Country: Oman
Language: English (Spanish)
Genre: Travel
Published (Last): 23 October 2010
Pages: 340
PDF File Size: 6.45 Mb
ePub File Size: 7.43 Mb
ISBN: 796-5-59138-803-3
Downloads: 24915
Price: Free* [*Free Regsitration Required]
Uploader: Dulrajas

As Endevor provides an interface for creating, modifying, moving, deleting and transferring elements via pre-defined lifecycles there is no need for any end user to have alter or update access to libraries controlled by Endevor. The default system processor executes a standard copy, move or delete action.

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

Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments.

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 used to execute Endevor packages according to release schedule.

Every type has at least one processor defined for which lists the name of the processor mainnframe performs the action required.

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

  BAUMAN MAY SOCJOLOGIA PDF

Endevor – Wikipedia

This allows for defined systems development lifecycle stages to have set approvers and controlled releases. An exit is generally used to determine when and to whom to send emails to, for example to notify Endevor approvers that a mainfdame is waiting to be reviewed or that a package has been reset.

The system uses these values to determine the source and target locations. Endevor maintains configuration control for each element registered in the system. In this manner Endevor can be configured maual handle most mainframe files. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes.

The reference “element” is used to define the smallest object for which Endevor controls. August Learn how and when to remove this template message. Views Read Edit View history. Endevor also has a function to allow envevor to be interactively dynamically added to an approver group after a package is successfully cast.

Endevor Package Editor tutorial

Endevor provides control of source and related code objects as individual elements. A package is a mainfeame for Endevor SCL and associated control information for code release. Endevor administrators can modify Endevor functions and capture information using exits. It also competes against another CA source code management tool, Panvalet.

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.

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.

The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory. There is no limit to how many approver groups can be linked to a single package. Click here for details. Which approver groups are linked to a package is based on the approver group rules. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process.

  E CHOUPAL CASE STUDY PDF

Endevor Package Editor tutorial

This ensures that an audit trail is maintained for all actions and that the resulting manframe controlled by Endevor can be trusted. Please help improve this article by adding citations to reliable sources. Exits are generally used to enforce system policy and enhance Endevor functionality. There are several exit types, each attached to a specific Endevor function.

Languages Deutsch Edit links. These changes are only applicable to the package being cast and are not permanent changes to approver group configuration.

Unsupported SSL/TLS Version

A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. All Endevor element functions are described using a propriety Software Control Language. 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.

Every element is distinguished by the element name, system, subsystem and type. 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. A key attribute of package control is that security approver groups can be linked to each package. Articles needing additional references from August All articles needing additional references.

In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. As an example, an exit could fail the generate action where the CCID is invalid.

This means for every system referenced in the package there will be at least one approval required. Moves an element from any source stage to any target stage.