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.
|Published (Last):||25 November 2008|
|PDF File Size:||5.66 Mb|
|ePub File Size:||5.7 Mb|
|Price:||Free* [*Free Regsitration Required]|
As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. The same functionality for source control and release management functions are provided by several other products. 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.
As an example, an exit could fail the generate action where the CCID is invalid. An exit will specify where in the exit tree that the code will be executed and what will be affected.
All Endevor element functions are described using a propriety Software Control Language. Many functions executed in interactive mode are completed in batch endeagor. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed.
Unsupported SSL/TLS Version
Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. Systems with names in italics are no longer maintained or have planned end-of-life dates. Retrieved 15 May Each Endevor environment has a granular breakdown of functions endeavr to that environment. Each approver group has a set quorum for which can be set to 0 to Each approver group can have up to 16 userids.
These tables are where the access for Endevor functions is defined when using native security. A key endeaor of package control is that security approver groups can be linked to each package.
This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted. Endevor administrators can modify Endevor functions and capture information using exits. From Wikipedia, the free encyclopedia. Languages Deutsch Edit maunal. 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. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values.
Endevor supports release management, as defined by ITIL in the form of package control. As such, control of source happens internally to Endevor and source control actions endeavot separate from changes to objects in the output libraries which includes load modules and copies of processed code. These nedeavor are only applicable to mnaual package being cast and are not permanent changes to approver group configuration.
Every element is distinguished by the element name, system, subsystem and type. Moves an element from any source stage to any target stage. Click here for details.
Endevor Package Editor tutorial
Endevor provides control of source and related code objects as individual elements. This page was last edited on 20 Septemberat 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. The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled.
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 va required to approve. There are several exit types, each attached to a specific Endevor function. Years, where available, indicate the date of first stable release.
Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments. 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. 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.