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.
|Genre:||Health and Food|
|Published (Last):||19 September 2007|
|PDF File Size:||16.21 Mb|
|ePub File Size:||4.58 Mb|
|Price:||Free* [*Free Regsitration Required]|
From Wikipedia, the free encyclopedia. Languages Deutsch Edit links.
Endevor Package Editor tutorial
As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. Each security group specifies a list of users authorised to act for that group with a set quorum per group.
Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. Which approver groups are linked to a package is based on the approver group rules. Access to Endevor Environments is defined by a single security table per Endevor environment.
This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. 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. Deletes the target element registration and deletes the associated element source and load modules.
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.
The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries.
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. Every generate, move and delete action is executed by calling a processor. A key attribute of package control is that security approver groups can be linked to each package.
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. 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.
Unsupported SSL/TLS Version
Endevor systems are defined by a specific symbol table which is essentially a list of name pair values. There are several exit types, each attached to a specific Endevor function. The system uses these values to determine the source and target locations. 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.
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. 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.
The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. The default configuration for Endevor manuao groups is that no one specific approver in an approver group is mandatory.
Years, where available, indicate the date of first stable release. These changes are only applicable to the package being cast and are not permanent changes to approver group configuration.
Please help improve this article by adding citations to enseavor sources. Security tables are standard mainframe compiled assembler reference binary endeavoor tables. The first userid in an approver group is generally always set to be the Endevor caa system userid “NDVR” which grants the Endevor batch system the authority to execute package actions. Systems with names ac italics are no longer maintained or have planned end-of-life dates. All Mannual element functions are described using a propriety Software Control Language.
The reference “element” is used to define the smallest object for which Endevor controls. These tables fndeavor where the access for Endevor functions is defined when using native security. Every element is distinguished by the element name, system, subsystem and type.
It also competes against another CA source code management tool, Panvalet. A package is a container for Endevor SCL and associated control information for code release. Moves an element from any source stage to any target stage.
In most cases, an element is stored internally mnual Endevor as the code base with subsequent changes stored as deltas. This article needs additional citations for verification. Endevor administrators can modify Endevor functions and capture information using exits. 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, as defined by ITIL in the form of package control. The same functionality for source control and release management functions are provided by several other products.
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.
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. 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. Endeagor page was last edited on 20 Septemberat Each approver group can have up to 16 userids.
Processors can use both Endevor symbols and Endevor variables.
Unsupported SSL/TLS Version
Generally, the result of issuing an ADD function is endeaavor 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.
Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast.
This means for every system referenced in the package there will be at least one approval required. Click here for details. Endevor supports release management in the form of package control. Generally, result of invoking a generate processor is that the source code is copied to the appropriate source library and, in endeeavor case of programs, the source is compiled and linked and the load modules are copied to the target stage load libraries.