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):||26 February 2007|
|PDF File Size:||17.20 Mb|
|ePub File Size:||16.92 Mb|
|Price:||Free* [*Free Regsitration Required]|
Exits are generally used to enforce system policy and enhance Endevor functionality. Endevor maintains configuration control for each element registered in the system.
Unsupported SSL/TLS Version
The first userid in an approver group is generally always set to be the Endevor internal system endeavro “NDVR” which grants the Endevor batch system the authority to execute package actions.
Systems with names in italics are no longer maintained or have planned end-of-life dates.
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. Which approver groups are linked to a package is based on the approver group rules. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required.
This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted. Every element is distinguished by the element name, system, subsystem and type.
Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. Processor code looks like and executes similar to JCL. These changes are only applicable to the package being cast and are not permanent changes to approver group configuration.
Years, where va, indicate the date of first stable release. Endevor endeqvor multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. Endevor supports release management in the form of package control. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast. August Learn how and when to remove this template message.
The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory. 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. Security tables are standard mainframe compiled assembler reference binary lookup tables.
As such, control of source happens internally to Endevor and source control actions are separate from changes to objects in the output libraries which includes load modules and copies of processed code. A package is a container for Endevor SCL and associated control information for code release. From Wikipedia, the free encyclopedia. Unsourced material manula be challenged and removed. Each approver group can have up to 16 userids.
Every type has at least one processor defined for which lists the name of the processor that performs the action required. Generally, there is one security table per Endevor environment, however a single security maual can be referenced by multiple environments.
There is no limit to how many approver groups can be linked to a single package. Access to Endevor Environments is defined by a single security table per Endevor environment. The reference “element” is used to define the smallest object for which Endevor controls. In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas. Click here for details. It also competes against another CA source code management tool, Panvalet.
Retrieved from ” https: 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 provides control of source and related code objects as individual elements. Each approver in an approver group can be defined as being a va or optional approver by specifying a flag in the approver group definition. There are several exit types, each attached to a specific Endevor function. In this manner Endevor can be configured to handle most mainframe files.
Endevor – Wikipedia
These tables are where the access for Endevor functions is defined when using native security. As an example, an exit could fail the generate action where the CCID is invalid. 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. Each Endevor environment has a granular breakdown of functions specific to that environment.
Views Read Edit View history. This is due to the security model within Endevor for which requires explicit security access. Generally, the result enedavor issuing an ADD function is that the element will endevaor registered to the target Endevor stage, or the element registration will be updated in the target stage and the appropriate generate processor will be invoked.
A key attribute of package control is that security approver groups can be linked to each endavor. Many functions executed in interactive mode are completed in batch mode.
At a minimum a package kanual 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. All Endevor element functions are described using a propriety Software Control Language.
Unsupported SSL/TLS Version
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. As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries.
The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. Moves an element from any source stage to any target stage.
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 Manuall and security tables per Endevor Environment and for specific Endevor functions.