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):||2 October 2016|
|PDF File Size:||18.75 Mb|
|ePub File Size:||12.76 Mb|
|Price:||Free* [*Free Regsitration Required]|
An exit will specify where in the eneavor tree that the code will be executed and what will be affected. The default system processor executes a standard copy, move or delete action.
Endevor – Wikipedia
Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. Each approver in endeacor approver group can be defined as being a mandatory or optional approver by specifying a flag in the approver group definition.
An exit is generally used to determine when and to whom to send emails to, for example to notify Endevor approvers that a package is waiting to be reviewed or that a package has been reset. 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.
Endevor provides control of source and related code objects as individual elements. This security table defines the access control endeacor defined by groups for which users are assigned to and lists the stages for which users can interact with. Endevor maintains configuration control for each element registered in the system. 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.
Unsupported SSL/TLS Version
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. 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.
This page was last edited on 20 Septemberat A key attribute of package control is that security approver groups can be linked to each package.
There are several exit types, each attached to a specific Endevor function. A package is a container for Endevor SCL and associated control information for code release. The system uses these values to determine the source and target locations. From Wikipedia, the free encyclopedia.
This article needs additional citations for verification. 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.
Endevor systems are defined by a specific symbol table which is essentially a list of name pair values.
A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. Generally, result of invoking a generate processor is that the source code is copied to the appropriate manuap 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.
Endevor administrators can modify Endevor functions and capture information using exits. Each approver group can have up to 16 userids.
Endevor Package Editor tutorial
Retrieved 15 May As Ebdeavor 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.
These changes are only applicable to the package being cast and are not permanent changes to approver group configuration. Every type has at least one processor defined for which lists the name of the processor that performs the action required.
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. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. Unsourced material may be challenged and removed.
Processor code looks like and executes similar to JCL. The default configuration for Manuak approver groups is that no one specific approver in an approver group is mandatory. In this manner Endevor can be configured to handle most mainframe files.
In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas. Languages Deutsch Edit links.
Unsupported SSL/TLS Version
August Learn how and when to remove this template message. Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast. These tables are where the access for Endevor functions is defined when using native security. It also competes against another CA source code management tool, Panvalet. Each security group specifies a list of users authorised to act for that group with a set quorum per group.
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.
Articles needing additional references from August All articles needing additional references.