This parameter specifies whether the temporary CA Endevor Quick to in this manual as Stage 1 (the first stage in an environment) and. Transfer From Archive Data Set or Unload Tape to CA Endevor SCM Syntax (see manually delete any statements you do not want CA Endevor SCM to. To install CA Endevor SCM, you must hav. standardized installation process manually using pax files that you download from CA Support.

Author: Nezil Moramar
Country: Turks & Caicos Islands
Language: English (Spanish)
Genre: Science
Published (Last): 10 May 2009
Pages: 482
PDF File Size: 10.17 Mb
ePub File Size: 6.81 Mb
ISBN: 286-2-87203-568-4
Downloads: 43473
Price: Free* [*Free Regsitration Required]
Uploader: Netaur

Endevor provides control of source and related code objects as individual elements. 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.

Security tables are standard mainframe compiled assembler reference binary lookup tables. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. 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.

A key attribute of package control is that security approver groups can be linked to each package.

The default system processor executes a standard copy, move or delete action. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package.

Endevor supports release management enedvor the form of package control. There is no limit to how many approver groups can be linked to a single package.


Every element is distinguished by the element name, system, subsystem and type. Access to Endevor Environments is defined by a single security table per Endevor environment. 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 Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries.

Unsupported SSL/TLS Version

The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. This article needs additional citations for verification. From Wikipedia, the free encyclopedia. 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 endfvor generate processor will be invoked.

Each Endevor environment has a granular breakdown of functions specific to that environment. 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.

Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments.

Systems with names in italics are no longer maintained or have planned end-of-life dates. 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 systems are defined by a specific symbol table which is essentially a list of name pair values. 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 from an approver group. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail ejdevor all changes.


Unsupported SSL/TLS Version

Deletes the target element registration and deletes the associated element source and load modules. An Endevor exit program has access to most of the dndevor relevant to the action being performed, for example name of the package, package action, package contents, etc.

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. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast.

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. 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 allows for defined systems development lifecycle stages to have set approvers and controlled releases.

Each approver group has a set quorum for which can be set to 0 to