Page 2: Table Of Contents Lighter than full-size vacuum cleaners, easier to maneuver and less bulky for convenient storage, the Veridian Endeavor cordless handheld stick vacuum makes quick work of everyday messes. With all the power of a high-performance stick vac and the versatility of a hand vac, the Endeavor is a top choice for cleaning multiple floor types plus above floor surfaces. Always switch off the appliance before cleaning, when not in use or attempting any maintenance task. The charger must only be connected to an AC power supply at the voltage shown on the rating label. This cleaner should only be used for its intended purpose as described in this instruction manual.
|Published (Last):||4 December 2019|
|PDF File Size:||20.73 Mb|
|ePub File Size:||9.63 Mb|
|Price:||Free* [*Free Regsitration Required]|
Transfer[ edit ] Moves an element from any source stage to any target stage. Generate[ edit ] Generate outputs. Source Control vs Output Library Control[ edit ] Endevor separates the control of source from the objects used as input and the objects created as output when an action is performed. In most cases, an element is stored internally by Endevor as the code base with subsequent changes stored as deltas.
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. The Endevor application executes system actions using two dedicated system accounts for which have the access to write to Endevor controlled libraries.
As a general rule general mainframe users are prohibited from modifying Endevor controlled libraries. This ensures that the only way to generate and promote code is via Endevor and provides an audit trail of all changes. Output libraries controlled by Endevor are used to store the following types of objects: Element source usually a copy of the most recent version of input source stored to allow direct and easy access using standard mainframe tools Element base normally as an encrypted file name Element deltas normally as an encrypted file name Load modules compiled executables DBRM modules compiled modules containing the SQL statements and variables used by programs Listings verbose summary of actions which occurred during element functions 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.
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 access to libraries controlled by Endevor. This ensures that an audit trail is maintained for all actions and that the resulting objects controlled by Endevor can be trusted. Package Control[ edit ] Endevor supports release management in the form of package control.
A package is a container for Endevor SCL and associated control information for code release. 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.
A key attribute of package control is that security approver groups can be linked to each package. Each security group specifies a list of users authorised to act for that group with a set quorum per group. Any Endevor stage which is flagged as being packaged controlled requires all actions to be executed using a package.
This allows for defined systems development lifecycle stages to have set approvers and controlled releases. 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.
Security[ edit ] Endevor Native Security[ edit ] 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. Each approver group can have up to 16 userids. 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.
This is due to the security model within Endevor for which requires explicit security access. 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. 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.
The default configuration for Endevor approver groups is that no one specific approver in an approver group is mandatory. Each approver group has a set quorum for which can be set to 0 to 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. 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.
There is no limit to how many approver groups can be linked to a single package. Which approver groups are linked to a package is based on the approver group rules. 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.
This means for every system referenced in the package there will be at least one approval 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.
These changes are only applicable to the package being cast and are not permanent changes to approver group configuration. Endevor also has a function to allow approvers to be interactively dynamically added to an approver group after a package is successfully cast.
Endevor Security Tables[ edit ] Security tables are standard mainframe compiled assembler reference binary lookup tables.
Generally, there is one security table per Endevor environment, however a single security table can be referenced by multiple environments.
These tables are where the access for Endevor functions is defined when using native security. 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.
A user can be defined to multiple groups with least restrict access rules being applied. Each Endevor environment has a granular breakdown of functions specific to that environment.
A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. Exits[ edit ] Endevor administrators can modify Endevor functions and capture information using exits. There are several exit types, each attached to a specific Endevor function. An exit will specify where in the exit tree that the code will be executed and what will be affected.
As an example, an exit could be written to trigger "before package cast" to link an additional approver group to the package being cast. As an example, an exit could fail the generate action where the CCID is invalid.
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. Exits are generally used to enforce system policy and enhance Endevor functionality. In particular, exits are used to deny end users from executing actions which would subvert the integrity of the system development life cycle process.
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. Every generate, move and delete action is executed by calling a processor. Every type has at least one processor defined for which lists the name of the processor that performs the action required.
The default system processor executes a standard copy, move or delete action. Processor code looks like and executes similar to JCL. Processors can use both Endevor symbols and Endevor variables. Endevor systems are defined by a specific symbol table which is essentially a list of name pair values. Element Types[ edit ] Endevor maintains configuration control for each element registered in the system.
Every element is distinguished by the element name, system, subsystem and type. The type definition determines how the element is stored and how subsequent changes, known as deltas, are handled. The system uses these values to determine the source and target locations. In this manner Endevor can be configured to handle most mainframe files.
CA ENDEAVOR MANUAL PDF
Shaktilrajas There are several exit types, each attached to a specific Endevor function. A security table can be defined per Endevor environment to provide granular control for element actions down to per user if required. Processors can use both Endevor symbols and Endevor variables. Each Endevor environment has a granular breakdown of functions specific to that environment.
Veridian Endeavor Owner's Manual
Mitsubishi Endeavor Owner's Manual