CA ENDEVOR 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. 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.
|Published (Last):||16 January 2014|
|PDF File Size:||11.33 Mb|
|ePub File Size:||13.38 Mb|
|Price:||Free* [*Free Regsitration Required]|
Endevor supports release management in the form of package control. As an example, an exit could fail the generate action where the CCID is invalid. An exit will specify where in the exit tree that the code will be executed and what will be affected.
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. 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.
A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. As an example, an exit could be written to trigger “before package cast” to link an additional approver group to the package being cast. Unsourced material may be challenged and removed.
August Learn how and when to remove this template message. 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 provides control of source and related code objects as individual elements. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values.
The system uses these values to determine the source and target locations. 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.
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. Please help improve this article by adding citations to reliable sources. 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. This allows for defined systems development lifecycle stages to have set approvers and controlled releases.
Systems with names in italics are no longer maintained or have planned end-of-life dates.
Endevor – Wikipedia
The default configuration for Endevor approver groups is that no one specific approver in manuall approver group is mandatory. Many functions executed in interactive mode are completed in batch mode.
There are several exit types, each attached to a specific Endevor function. Endevor maintains configuration control for each element registered in the system. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process. 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.
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. Deletes the target element registration and deletes the associated element source and load modules. Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. An Endevor exit program has access to most of the information relevant to the action being performed, for example name of the package, package action, package contents, etc.
Generally, result of emdevor a generate processor is that the source ejdevor 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. Which approver groups are linked to a package is based on the approver group rules.
Any Manaul stage which is flagged as being packaged controlled requires all actions to be executed using a package. Processor code looks like and executes similar to JCL.
The reference “element” is used to define the smallest object for which Endevor controls. 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.
Unsupported SSL/TLS Version
At a minimum a package has a name, an execution window defined the time range for when the package can majual executed, notes about the package, various flags and at least one value SCL statement. The default system processor executes a standard copy, move or delete action. All Endevor element functions are described using mmanual propriety Software Control Language. This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted.
This article needs additional citations for verification. Click here for details. 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.