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: Dibar Kagami
Country: Somalia
Language: English (Spanish)
Genre: History
Published (Last): 1 February 2011
Pages: 397
PDF File Size: 16.36 Mb
ePub File Size: 14.93 Mb
ISBN: 779-1-48893-916-5
Downloads: 24752
Price: Free* [*Free Regsitration Required]
Uploader: Kajikora

Every type has at least one processor defined for which lists the name of the processor that performs the action required. Endevor supports release management in the form of package control. The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor mahual libraries. 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 manuak to libraries controlled by Endevor.

Please help improve this article by adding citations to reliable sources. Security tables are standard mainframe compiled assembler reference binary lookup tables.

The reference “element” is used to define the smallest object for which Endevor controls. Each approver group has a set quorum for which can be set to 0 to Articles needing additional references from August All articles needing additional references. There is no limit to how many approver groups can be linked to a single package. 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. 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.


This article needs additional citations for verification.

Unsupported SSL/TLS Version

Deletes the target element registration and deletes the associated element source and load modules. Exits are generally used to enforce system policy and endeavro Endevor functionality. The ADD instruction can be cz to define a new element to an Endevor stage or add a previously registered element to the first stage in a define lifecycle.

In most cases, an element is stored internally by Endevor as endaevor code base with subsequent changes stored as deltas. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs. As the Endevor product does not have a scheduling component a third party tool such as IBM Tivoli Workload Scheduler or Manuxl must be used to execute Endevor packages according to release schedule.

A package is a container for Endevor SCL and associated control information for code release. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. All Endevor element functions are described using a propriety Software Control Language.

As an example, endevor exit could be written to trigger “before package cast” to link an additional approver group to the package being cast. 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. Endevor supports release management, as defined by ITIL in the form of package control.

Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. Each security group specifies a list of users authorised to act for that group with a set quorum per group.

As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. Unsourced material may be challenged and removed. As a general rule, when package control is used for an Endevor stage then endeavorr Endevor system will have at least one approver group for that stage and the approver group would have a quorum of zero.


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. 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.

These tables are where the access for Endevor functions is defined when using native security. 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.

Endevor Package Editor tutorial

Retrieved 15 May Languages Deutsch Edit links. This means that if the internal Endevor system userid is not linked into one of the approver groups when a package is enceavor then the Endevor batch system can not execute commands against that package.

Endevor systems are defined by a specific symbol table which is essentially a list of name pair values. Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast. Moves an element from any source stage to any target stage.

The quorum of zero is normally used for a endeavog where a specific approver group requires the ability to deny a package in a situation where approval is automatic.

Many functions executed in interactive mode are completed in batch mode.