You can download a PDF or an EPUB file of an article or content area for offline use. You can choose what you want to download— a page. your use of the CA software to which the Documentation relates; or (ii) a VB record length Action Option field on the CA Endevor Quick-Edit Option panel. Welcome to the CA Endevor Software Change Manager Version bookshelf. Use the Search field on this bookshelf to search the product documentation.
|Genre:||Health and Food|
|Published (Last):||22 June 2015|
|PDF File Size:||14.86 Mb|
|ePub File Size:||3.27 Mb|
|Price:||Free* [*Free Regsitration Required]|
The documentation is extensive and takes some patience to caendevor. Endevor provides control of source and related code objects as individual elements. CA Endevor is a large and complex product to master. Saisha 7 15 Underverse 15 The system uses these values to determine the source and target locations.
Much of what you really need to actually use Endevor will be dependant on how Endevor is customised at your shop. 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.
All Endevor element functions are described using a propriety Software Control Language. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process.
From Wikipedia, the free encyclopedia.
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.
Generally, an approver group will have a quorum of 1, meaning that at least one of the users listed in the approver group needs to approve the package in order for the package to progress to the APPROVED status.
Guive default system processor executes a standard copy, move or delete action.
Unsupported SSL/TLS Version
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. The reference “element” is used to define the smallest object for which Endevor controls. 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.
Deletes the target element registration and deletes the associated element source and load modules. Access to Endevor Environments is defined by a single security table per Endevor environment.
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 ca-wndevor the element metadata and process outputs.
Systems with names in italics are no longer maintained or have planned end-of-life use. Every generate, move and delete action is executed by calling a processor. I found the following documents “floating” around but they provide a very limited view of the product: 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.
Post as a guest Name.
Sign up or log in Sign up using Google. Sorry, I cannot be any more helpful than this! Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package. 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.
These changes are only applicable to the package being cast and are not permanent changes to approver group configuration.
Unsupported SSL/TLS Version
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. I want to learn the Code Manmagement using it. Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast.
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.