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):||16 March 2014|
|PDF File Size:||2.38 Mb|
|ePub File Size:||18.19 Mb|
|Price:||Free* [*Free Regsitration Required]|
Articles needing additional references from August All articles needing additional references. Endevor maintains configuration control for each element registered in the system. This article needs additional citations for verification.
Security tables are standard mainframe compiled assembler reference binary lookup tables. Generally, the result of issuing an ADD function is that the element will be 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. This allows endeavvor defined systems development lifecycle stages to have set approvers and controlled releases. Which approver groups are linked to endeavorr package is based on the approver group rules.
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. Languages Deutsch Edit links. This is due to the security model within Endevor for which requires explicit security access.
From Wikipedia, the free encyclopedia. The Endevor application executes system actions using two dedicated system accounts manula which have the access to write to Endevor controlled libraries.
Each Endevor environment has a granular breakdown of functions specific to that environment. Please help improve this article by adding citations to reliable sources. There is no limit to how many approver groups can be linked cq a single package. 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.
Endevor Package Editor tutorial
All Endevor element functions are described using a propriety Software Control Language. An exit will specify where in the exit tree that the code will be executed and what will be affected.
Unsourced material may be challenged and removed. Retrieved 15 May 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.
Endevor – Wikipedia
Every generate, move and delete action is executed by calling a processor. Access to Endevor Environments is defined by a single security table per Endevor environment. Deletes the target element registration and deletes the associated element source and load modules. 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. Every type has at least one processor defined for which lists the name of the processor that performs the action required.
The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. Years, where available, indicate the date of first stable release. 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.
Endevor supports release management, as defined by ITIL in the form of package control.
Many functions executed in interactive mode are completed in batch mode. Endevor provides control of source and related code objects as individual elements.
A package is a container for Endevor SCL and associated control information for code release. In this manner Endevor can be configured to handle most mainframe files. Every element is distinguished by the element name, system, subsystem and type. The default system processor executes a standard copy, move or delete action. In particular, exits are used to manuaal end users from executing actions which would subvert the integrity of the system development life cycle process. The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled.
These changes are only applicable to the package being cast and are endeaor permanent changes to approver group configuration. Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments. As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries.
Systems with names in italics are no longer maintained or have planned end-of-life dates. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package.
Each security group specifies a list of users authorised to act for that group with a set quorum per group. This page was last edited on 20 Septemberat 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. The system uses these values to determine the source and target locations. 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.
Views Read Edit View history. Moves an element from any source stage to any target stage. 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.
Processors can use both Endevor symbols and Endevor variables. 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. 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.