Site Overlay

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.

Author: Shami Yozshujora
Country: Bhutan
Language: English (Spanish)
Genre: Personal Growth
Published (Last): 22 March 2013
Pages: 130
PDF File Size: 1.6 Mb
ePub File Size: 19.42 Mb
ISBN: 291-7-72848-805-3
Downloads: 60840
Price: Free* [*Free Regsitration Required]
Uploader: Zulkisar

Endevor provides multiple methods for installing and accessing distinct separate instances of Endevor for which are installed on the same LPAR. Please help improve this article by adding citations to reliable sources.

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 endeavlr. Endevor supports release management, as defined by ITIL in the form of package control.

An exit is generally used to determine when and mnual 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. A key attribute of package control is that security approver groups can be linked to each package. Processors can use both Endevor symbols and Endevor variables. 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 enceavor remove users from an approver group.

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.

A package is a container for Endevor SCL and associated control information for code release. Each Endevor environment has a granular breakdown of functions specific to that environment. As an example, an exit could fail the generate action where the CCID is invalid. Each approver group can have up to 16 userids. This allows for defined systems development lifecycle stages to have set approvers and controlled releases. Years, where available, indicate the date of first stable release.

  JOSS BASELLI PDF

This means endeagor if the internal Endevor system userid is not linked into one of the approver groups when a package is cast endeavlr the Endevor batch system can not execute commands against that package.

Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package. 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 enveavor target stage load libraries.

August Learn how and when to remove this template message. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process. The ADD function invokes a generate processor which then executes all actions required to register or update the element metadata and process outputs.

Unsupported SSL/TLS Version

The type definition determines how the element is endeabor and how subsequent changes, known as deltas, are handled. Endevor administrators can modify Endevor functions and capture information using exits.

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. As an example, an exit endeacor be written to trigger “before package cast” to link an additional endeavr group to the package being cast. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values. Retrieved 15 May Every element is distinguished by the element name, system, subsystem and type.

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. Views Read Edit View history. 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.

  GO TOOL PPROF PDF

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. An exit will specify where in the exit tree that the code will be executed and what will be affected.

Endevor Package Editor tutorial

Access to Endevor Environments is defined by manul single security table per Endevor environment. These tables are where the access for Endevor functions is defined when using native security. Each approver group has a set quorum for which can be cq to 0 to 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.

Languages Deutsch Edit links. 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. Many functions executed in interactive mode are completed in batch mode. Processor code looks like and executes similar to JCL.

Endevor Package Editor tutorial

Which approver groups are linked to a package is based on the approver group rules. This article needs additional citations for verification. The default system processor executes a standard copy, move or delete action. As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries.

The system uses these values to determine the source and target locations. Every type has at mannual one processor defined for which lists the name of the processor that performs the action required.