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):||9 February 2006|
|PDF File Size:||2.25 Mb|
|ePub File Size:||18.89 Mb|
|Price:||Free* [*Free Regsitration Required]|
The first userid in an approver group is generally always set to be the Endevor internal system userid “NDVR” which grants the Endevor batch system the endeavorr to execute package actions. 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. Retrieved 15 May Approver groups can be dynamically altered manuall 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. The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory.
Retrieved from ” https: Security tables are standard mainframe compiled assembler reference binary lookup tables. Every element is distinguished by the element name, system, subsystem and type.
There are several exit types, each attached to a specific Endevor function.
Endevor – Wikipedia
Each approver group has a set quorum for which can be set to 0 to A package is a container for Endevor SCL and associated control information for code release. 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.
This is due to the security model within Manal for which requires explicit security access. Each approver group can have up to 16 userids. In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas.
Endevor maintains configuration control for each element registered in the system. This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted.
Endevor Package Editor tutorial
This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. Endewvor administrators can modify Endevor functions and capture information using exits.
A key attribute of package control is that security approver groups can be linked to each package. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process. Endevor provides control of source and related code objects as individual elements.
It also competes against another CA source code management tool, Panvalet. Views Read Edit View history. Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast.
These changes are only applicable to the package being cast and are not permanent changes to approver group configuration.
Unsourced material may be challenged and removed. 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. Deletes the target element registration and deletes the associated element source and load modules. Moves an element from any source stage to any target stage. 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.
August Learn how and when to remove this template message. An exit will specify where in the exit tree that the code will be executed and what will be affected.
Endevor supports release management, as defined by ITIL in the form of package control. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values.
Years, where available, indicate the date of first stable release. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. 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. Each Endevor environment has a granular breakdown of functions specific to that environment. Please help improve this article by adding citations to reliable sources.
The same functionality for source control and release management functions are provided by several other products.
Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries.