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.

Author: Tojinn Katilar
Country: Italy
Language: English (Spanish)
Genre: Video
Published (Last): 19 January 2012
Pages: 49
PDF File Size: 12.48 Mb
ePub File Size: 14.49 Mb
ISBN: 676-7-99455-288-3
Downloads: 54784
Price: Free* [*Free Regsitration Required]
Uploader: Kilmaran

It also competes against another CA source code management tool, Panvalet. Endevor provides control of source and related code objects as individual elements. The reference “element” is used to define the smallest object for which Endevor controls. Many functions executed in interactive mode are completed in batch mode. All Endevor element functions are described using a propriety Software Control Language.

Unsupported SSL/TLS Version

The ADD instruction can be used endfavor define a new element to an Endevor stage or add a previously registered element to the first stage in a define lifecycle. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs.

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 manula 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 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. Deletes the target element registration and deletes the associated element source and load modules. Moves an element from any source stage to any target stage. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed.

In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas. 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 endeavkr processed code.

The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries. As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail endsavor all changes.

This allows for the users of Endevor, such as developers, to be separated from the control of the objects which they modify using Endevor functions. As Endevor provides an interface for creating, modifying, moving, deleting and transferring elements via pre-defined mwnual there is no need for any end user to have alter or update access to libraries controlled by Endevor. This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted.

Endevor supports release management, as defined by ITIL in the form of package control. Endevor supports release management in the form of package control. A package is a container for Endevor SCL and associated control information for code release. 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. A key attribute of package control is that security approver groups can be linked to each package.


Each security group specifies a list of users endevor to act for that group with a set quorum per group. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package.

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

Each approver group can have up to 16 userids. 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. This is due to the security model within Endevor for which requires explicit security access. 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.

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. The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory. Each approver group has a set quorum for which can be set to 0 to 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 mqnual package to progress to the APPROVED status.

An approver group quorum of zero is used for approver groups where the users either need to be informed of package endevaor or users require the ability to DENY a package but are not explicitly required to approve. The quorum of zero is endeavkr used for a scenario where a specific approver group requires the msnual to deny a package in a situation where approval is automatic.

There is no limit to how many approver groups can be linked to a single package. Which approver groups are linked to a package is based on the approver group rules. 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.

This means for every system referenced in the package there will be at least one approval required. 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.

These changes are only applicable to the package being cast and are not permanent changes to approver group configuration. Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast.

Security tables are standard mainframe compiled assembler reference binary lookup tables. Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments. These tables are where the access for Endevor functions is defined when using native security.


Access to Endevor Environments is defined by a single security table va Endevor environment. 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 endeavpr with. Each Endevor environment has a granular breakdown of functions specific to that environment. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required.

Unsupported SSL/TLS Version

Endevor administrators can modify Endevor functions and capture information using exits. There are several mxnual types, each attached to a specific Endevor function. An exit will specify where in the exit tree that the code will be executed and what will be affected. As an example, an exit could be written cq trigger “before package cast” to link an additional approver group to the package being cast. As an example, an exit could fail the generate action where the CCID is invalid. An Endevor exit program has access to most of the information relevant to the action being performed, for example ejdeavor of the package, package action, package contents, etc.

Exits are generally used to enforce system policy and enhance Endevor functionality. In particular, exits are used to endeavro end users from executing actions which would subvert the integrity of the system development life cycle process.

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. Every generate, move and delete action is executed by calling a processor.

Every type has at least endeqvor processor defined for which lists the name of the processor that performs the action required.

The default system processor executes a standard copy, move or delete action.

Processor code looks like and executes similar to JCL. Processors can use both Endevor symbols and Endevor variables. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values. Endevor maintains configuration control for each element registered in the system. Every element is distinguished by the element name, system, subsystem and type. The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled.

The system uses these values to determine the source and target locations. In this manner Endevor can be configured to handle most mainframe files. Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. The same functionality for source control and release management functions are provided by several other products. Click here for details. From Wikipedia, the free encyclopedia.

This article needs additional citations for verification.

Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.

Endevor Package Editor tutorial

August Learn how and when to remove this template message. Retrieved 15 May Years, where available, indicate the date of first stable release. Systems with names in italics are no longer maintained or have planned end-of-life dates. Retrieved from ” https: Articles ejdeavor additional references from August All articles needing additional references.

Views Read Edit View history. Languages Deutsch Edit links. This page was last edited on 20 Septemberat By endeabor this site, you agree to the Terms of Use and Privacy Policy.