Site Loader

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: Faelmaran Vinris
Country: Samoa
Language: English (Spanish)
Genre: Sex
Published (Last): 24 April 2018
Pages: 406
PDF File Size: 18.89 Mb
ePub File Size: 19.51 Mb
ISBN: 364-9-52117-849-7
Downloads: 49495
Price: Free* [*Free Regsitration Required]
Uploader: Kegis

Years, where available, indicate the date of first stable release. This is due to the security model within Endevor for which requires explicit security access.

Endevor systems are defined by a specific symbol table which is essentially a list of manuql pair values. Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. 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.

Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package.

The ADD instruction can be used to define va new element to an Endevor stage or add a previously registered element to the first stage in a define lifecycle. 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.

Endevor supports release management, as defined by ITIL in the form of package control. 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 dndeavor have a quorum dndeavor zero. 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.


Each Endevor environment has a granular breakdown of functions specific to that environment. As an example, an exit endeavro fail the generate action where the CCID is invalid. It also competes against another CA source code management tool, Panvalet. 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

By using this site, you agree to the Terms of Use and Privacy Policy. Endevor maintains configuration control for each element registered in the system. A key attribute of package control is that security approver groups can be linked to each package. The reference “element” is used to define the smallest object for which Endevor controls. The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory.

Generally, 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. 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. There are several exit types, each attached to a specific Endevor function.

Unsupported SSL/TLS Version

Exits are generally used to enforce system policy and enhance Endevor functionality. The default system processor executes a standard copy, move or delete action. Endexvor the target element registration and deletes the associated element source and load modules. Every element is distinguished by the element endeaavor, system, subsystem and type. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process.

The same functionality for source control and release management functions are provided by several other products. This allows for the users enxeavor Endevor, such as developers, to be separated from the control of the objects which they modify using Endevor functions.

Every generate, move and delete action is executed by calling a processor. A package is a container for Endevor SCL and associated control information for code release. Systems with names in italics are no longer maintained or have planned end-of-life dates. This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted. Unsourced material may be challenged and removed.


Which approver groups are linked to a package is based on the approver group rules.

Endevor – Wikipedia

The move function moves an element registration from the target fndeavor the source stage and also, by invoking a move processor, moves the element output objects from the target to source libraries. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. The Endevor application executes system actions using two dedicated system accounts for cw have the access to write to Endevor controlled libraries.

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

The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. There is no limit to how many approver groups can be linked to a single package. Endevor supports release management in the form of package control. In this manner Endevor can be configured to handle most mainframe files.

Each approver group can have up to 16 userids. From Wikipedia, the free encyclopedia. Retrieved from ” https: 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. Each security group specifies a list of users authorised to act for that group with a set quorum per group. In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas.

Articles needing additional references from August All articles needing additional references.