CA ENDEAVOR MANUAL PDF
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):||22 November 2010|
|PDF File Size:||16.56 Mb|
|ePub File Size:||15.33 Mb|
|Price:||Free* [*Free Regsitration Required]|
Every element is distinguished by the element name, system, subsystem and type. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. Which approver groups are linked to a package is based on the approver group rules.
Unsourced material may be challenged and removed. In this manner Endevor can be configured to handle most mainframe files. This allows for defined systems development lifecycle stages to have set approvers and controlled releases. This allows for the users of Endevor, such as developers, to endeavir separated from the control of the objects which they modify using Endevor functions.
Views Read Edit View history. Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments.
Endevor provides control of source and related code objects as individual elements.
Retrieved from ” https: These tables are where the access for Endevor functions is defined when using native security. The same functionality for source control and release management functions are provided by several other mabual. Moves an element from any source stage to any target stage. At endeeavor 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.
Processors can use both Endevor symbols and Endevor variables. 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. janual
Endevor Package Editor tutorial
Click here for details. All Endevor element functions are described using a propriety Software Control Language. These changes are only applicable to the package being cast and are not permanent changes to approver group configuration. As the Endevor product does not have a manal component a third party tool such as IBM Tivoli Workload Scheduler or CA7 must be used to execute Endevor packages according to release schedule.
Unsupported SSL/TLS Version
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. A key attribute of package control is that security approver groups can be linked to each package.
Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs.
Languages Deutsch Edit links. This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted. Each Endevor environment has a granular breakdown of functions specific to that environment.
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. Processor code looks like and executes similar to JCL. This means for every system referenced in the package there will be at least one approval required. This page was last edited on 20 Septemberat 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.
Approver groups can be dynamically altered by Endevor exits at cast time, for example, to change the quorum, link an additional approver group, or to add or remove users edneavor an approver group.
In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process. 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. Manuap approver group has a set quorum for which can mmanual set to 0 to 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.
Endevor Package Editor tutorial
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. The system uses these values to determine the source and target locations. The default system processor executes a standard copy, move or delete action. This is due to the security model within Endevor for which requires explicit security access.
Endevor supports release management in the form of package control.
Many functions executed in interactive mode are completed in batch mode. Years, where available, indicate the date of first stable release. 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, 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. It also competes against another CA source code management tool, Panvalet.
Retrieved 15 May This article needs additional citations for verification. There is no limit to how many approver groups can be linked to a single package.
Please help improve this article by adding citations to reliable sources. Exits are generally used to enforce system policy and enhance Endevor functionality. As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. 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 endevor to execute package actions. August Learn how and when to remove this template message.