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):||18 March 2010|
|PDF File Size:||18.23 Mb|
|ePub File Size:||13.3 Mb|
|Price:||Free* [*Free Regsitration Required]|
Every type has at least one processor defined for which lists the name of the processor that performs the action required. Unsourced material may be challenged and removed. This means for every system referenced in the package there will be at least one approval required. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs.
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.
Generally, there is one security table per Endevor environment, however a single security table can be referenced endeavlr multiple environments. Moves an endfavor from any source stage to any target stage. 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.
Systems with names in italics are no longer maintained or have planned end-of-life dates. Endevor administrators can modify Endevor functions and capture information using exits.
Languages Deutsch Edit links. 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.
Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed.
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. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast.
The system uses these values to determine the source and target locations. This page was last edited on 20 Septemberat Each approver in an approver group can be defined as being a mandatory or optional approver by specifying a flag in the approver endesvor definition.
As a general rule, when package control is used for an Endevor stage then every Endevor system will have at least endfavor approver group for that stage and the approver group would have a quorum of zero. Endevor maintains configuration control for each element registered in the system.
Each approver group can have up to 16 userids. The same functionality for source control and release management functions are provided by several other products. 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 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.
Access to Endevor Environments is defined by a single security table per Endevor environment. Years, where available, indicate the date of first stable release. Processors can use both Endevor symbols and Endevor variables. Click here for details. Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR.
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 such, control of source happens internally to Endevor and source enddeavor actions are separate from changes to objects in the output libraries which includes load modules and copies of processed code.
Many functions executed in interactive mode are completed in batch mode. Every generate, move and delete action is executed by calling a processor.
Endevor provides control of source and related code objects as individual elements. From Wikipedia, the free encyclopedia.
This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. This allows for defined systems development lifecycle stages to have set approvers and controlled releases. These changes are only applicable to the package being cast and are not permanent changes to approver group configuration. Please help improve this article by adding citations to reliable sources.
Each approver group has a set quorum for which can be set to 0 to