TechnologyLeave a Comment on CA ENDEAVOR MANUAL PDF


This parameter specifies whether the temporary CA Endevor Quick to in this manual as Stage 1 (the first stage in an environment) and. This Guide is part of the Standards and Procedures Manual. The Manual consists of . creating the new CARDLIB member and placing it in the Endevor Staging library, simply submit an .. CI=: ______. FREE SPACE % CA. 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: Tygomi Makinos
Country: Burundi
Language: English (Spanish)
Genre: Spiritual
Published (Last): 25 March 2009
Pages: 351
PDF File Size: 2.92 Mb
ePub File Size: 17.22 Mb
ISBN: 775-4-51463-976-7
Downloads: 37275
Price: Free* [*Free Regsitration Required]
Uploader: Tygolabar

Years, where available, indicate the date of first stable release. In this manner Endevor can be configured to handle most mainframe files.

As an example, an exit could fail the generate action where the CCID is invalid. A package is a container for Endevor SCL and associated control information for code release. Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments.

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.

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

Endevor Package Editor tutorial

Endevor supports fa management, as defined by ITIL in the form of package control. 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.


Retrieved 15 May Many functions executed in interactive mode are completed in batch mode. As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries.

Each Endevor environment has a granular breakdown of functions specific to that environment. The same functionality for source control and release management functions are provided by several other products. 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.

Please help improve this article by adding citations to reliable sources.

The ADD instruction can be used to define a new element to an Endevor stage or add a previously registered element majual the first stage in a define lifecycle. The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries.

Endevor Package Editor tutorial

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.

An exit will specify where in the exit tree that the code will be executed and what will be affected. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes.

Views Read Edit View history. Endeavot element is distinguished by the element name, system, subsystem and type. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package.

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. Security tables are standard mainframe compiled assembler reference binary lookup tables. Every generate, move and delete action is executed by calling a processor. This allows for the users of Endevor, such as developers, to be separated from the control of the objects which they modify using Endevor functions.


An exit is generally used to determine when and to whom to send emails endeavot, for example to notify Endevor approvers that a package is waiting to eneeavor reviewed or that a package has been reset.

This means for every system referenced in the package va will be at least one approval required. Articles needing additional references from August All articles needing additional references.

Endevor – Wikipedia

All Endevor element functions are described using a propriety Software Control Language. Endevor maintains configuration control for each element registered in the system. Retrieved from ” https: Unsourced material may be challenged and removed. This is due to the security model within Endevor for which requires explicit security access.

The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory. The default system processor executes a standard copy, move or delete action.

Click here for details.

In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas.