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):||21 April 2010|
|PDF File Size:||20.64 Mb|
|ePub File Size:||12.51 Mb|
|Price:||Free* [*Free Regsitration Required]|
Exits are generally used to enforce system policy and enhance Endevor functionality. 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. These tables are where the access for Endevor functions is defined when using native security. Endevor maintains configuration control for each element registered in the system.
As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast. In this manner Endevor can be configured to handle most mainframe files.
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 authority to execute package actions.
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. Processors can use both Endevor symbols and Endevor variables.
A key attribute of package control is that security approver groups cca be linked to each package. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values.
As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. The default system processor executes a standard copy, move or delete action.
Retrieved 15 May Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package. There are several exit types, each attached to a specific Endevor function. Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR.
Systems with names in italics are no longer maintained or have planned end-of-life dates. 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.
Unsupported SSL/TLS Version
Many functions executed in interactive mode are completed in batch mode. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata xa process outputs. Every element is distinguished by the element name, system, subsystem and type. An exit will specify where in the exit tree that the code will be executed and what will be affected. Processor code looks like and executes similar to JCL. Security tables are standard mainframe compiled assembler reference binary lookup tables.
A package is a container for Endevor SCL and associated control information for code release.
Endevor Package Editor tutorial
It also competes against another CA source code management tool, Panvalet. As an example, an exit could fail the generate action where the CCID is invalid. Articles needing additional references from August All articles needing additional references. 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.
This allows for the users mankal Endevor, such as developers, to be separated from the control of the objects which they modify using Endevor functions. This article needs additional citations for verification. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required.
Each Endevor environment has a granular breakdown of functions specific to that environment. Endevor provides control of source and related code objects as individual elements.
This means for every system referenced in the edeavor there will be at least one approval required. All Endevor element functions are described using a propriety Software Control Language. Access to Endevor Environments is defined by a single security table per Endevor environment.
Endevor – Wikipedia
The reference “element” is used to define the smallest object for which Endevor controls. Each security group specifies a list of users authorised to act for that group with a set quorum per mabual. This allows for defined systems development lifecycle stages to have set approvers and controlled releases. 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 approver in an approver group can be defined as being a mandatory or optional approver by specifying a flag in the approver group definition.
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. The quorum of zero is normally used for a scenario where a specific endeavod group requires the ability to deny a package in a situation where approval is automatic.
Endevor supports release management in the form of package control. In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas. Which approver groups are linked to a package is based on the approver group rules.
Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed.
The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. There is no limit to how many approver groups can be linked to a single package.
In endeaovr, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes.
The system uses these values to determine the source and target locations.