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 March 2009|
|PDF File Size:||17.14 Mb|
|ePub File Size:||5.27 Mb|
|Price:||Free* [*Free Regsitration Required]|
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. Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR.
The same functionality for source control and release management functions are provided by several other products. The first userid endeavof an approver group is generally always set to be the Endevor internal system userid “NDVR” which grants the Endevor batch system the authority to execute package actions. Security tables are standard mainframe compiled assembler reference binary lookup tables.
The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. In most cases, an element is endeavorr internally by Endevor as the code base with subsequent changes stored as deltas. Processor code looks like and executes similar to JCL. As an example, an exit could fail the generate action where the CCID is invalid. Retrieved from ” https: This page was last edited on 20 Septemberat Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package.
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. Which approver groups are linked to a package is based on the approver group rules. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values. From Wikipedia, the free encyclopedia.
An approver group quorum of zero is used for approver groups where the users either need to be manusl of package actions or users require the ability to DENY a package but are not explicitly required to approve. A package is a container for Endevor SCL and associated control endeacor for code release. This security table defines the access control lists defined by groups for which users are assigned to and lists the stages for which users can interact with.
Endevor – Wikipedia
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 manul for the users of Endevor, such as developers, to be separated from the control of the objects which they modify manua, Endevor functions.
Every element is distinguished by the element name, system, subsystem nedeavor type. An exit is generally used to determine when and to whom to send emails to, for mwnual to notify Endevor approvers that a package is waiting to msnual reviewed or that a package has been reset.
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. All Endevor element functions are described using a propriety Software Control Language. 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.
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. Each Endevor environment has a granular breakdown of functions specific to that environment.
Endevor maintains configuration control for each element registered in the system. There is no limit to how many approver groups can be linked to a single package. It also competes against another CA source code management tool, Panvalet.
This ensures that an audit trail is maintained for all edneavor and that the resulting objects controlled by Endevor can be trusted. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast. Views Read Edit View history. 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.
Deletes the target element registration and deletes the associated element source and load modules.
Unsupported SSL/TLS Version
The manuql system processor executes a standard copy, move or delete action. Every generate, move and delete action is executed by calling a processor.
The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. 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.
This allows for defined systems development lifecycle stages to have set approvers and controlled releases. Click here for details. Endevor supports release management in the form of package control. Endevor provides control of source and related code objects as individual elements.
Endevor administrators can modify Endevor functions and capture information using exits. The ADD instruction can be used to define a new element to an Endevor stage or add a previously registered element to the first stage in a define lifecycle.
The reference “element” is used to define the smallest object for which Endevor controls. This means for every system referenced in the package there will be at least one approval required.
Each approver in an approver group can be defined as being a mandatory or optional approver by specifying a flag in the approver group definition. August Learn how and when to remove this template message.
Every type has at least one processor defined for which lists the name of the processor that performs the action required. Retrieved 15 May