CA ENDEAVOR MANUAL PDF
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.
|Published (Last):||7 August 2008|
|PDF File Size:||2.64 Mb|
|ePub File Size:||14.28 Mb|
|Price:||Free* [*Free Regsitration 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.
The default configuration for Endevor approver groups is that manua one specific approver in an approver group is mandatory. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. There are several exit types, each attached to a specific Endevor function.
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. As the Endevor product does not have a scheduling component a third party tool such as IBM Tivoli Workload Scheduler or CA7 manuaal be used to execute Endevor packages according to release schedule.
Each approver group has a set quorum for which can be set to 0 to Languages Deutsch Edit links. 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. Which approver groups are linked to a package is based on the approver group rules.
Unsupported SSL/TLS Version
The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries. Many functions executed in interactive mode are completed in batch mode. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast. Exits are generally used to enforce system policy and enhance Endevor functionality. Va supports release management, as defined by ITIL in the form of package control.
All Endevor element functions are described using a propriety Software Control Endeavo. Each security group specifies a list of users authorised to act for that group with a set quorum per group.
Unsupported SSL/TLS Version
Processors can use both Endevor symbols and Endevor variables. The move function moves an element registration from the target to the source stage and also, by invoking a move processor, moves the element manul objects from the target to source libraries.
Each approver group can have up to 16 userids. This is due to the security model within Endevor for which requires explicit security access. In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas.
In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process. Years, where available, indicate the date of first stable release. This allows ,anual the users of Endevor, such as developers, to be separated from the control of the objects which they modify using Endevor functions.
These tables are where the access for Endevor functions is defined when using native security.
Endevor – Wikipedia
Retrieved 15 May The system uses these values to determine the source and target locations. 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. 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.
Click here for details. 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 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.
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. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. Generally, the result of manyal 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.
Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast. Systems with names in italics are no longer maintained or have planned end-of-life dates.
This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of endeacor changes.
There is no limit to how many approver groups can be linked to a single package. An Endevor exit program has access to most of the information relevant endeavo the action being performed, for example name of the package, package action, package contents, etc.
A key attribute of package control is that security approver groups can be linked to each package. As Endevor provides an interface for creating, modifying, moving, deleting and transferring elements via pre-defined lifecycles there is no need for any end endeavpr to have alter or update access to libraries controlled by Endevor.