Element Actions

Contents
ce18
 
Contents
 
 
 
You manipulate
Endevor
inventory by executing
Endevor
commands called actions. Some actions are available in foreground and in batch, while others are available only in batch. Batch actions are also available when you build packages. For more information, see the following sections:
  •  The Using section explains how to execute actions in foreground and submit batch action requests.
  •  The SCL Reference section contains the syntax for
    Endevor
    's Software Control Language (SCL). SCL lets you code
    Endevor
    batch action requests.
The following summarizes
Endevor
actions and their availability:
  •  
    Add
    (Foreground and batch). Puts a member under
    Endevor
    control from an external data set.
  •  
    Archive
    (Batch) Writes the current version of an element to a sequential data set.
  •  
    Copy
    (Batch) Copies an element from an archive data set to a data set external to
    Endevor
    .
  •  
    Delete
    (Foreground and batch) Erases base and delta forms of an element and removes related information from a Master Control File.
  •  
    Display
    (Foreground) Displays information about an element.
  •  
    Generate
    (Foreground and batch) Creates an executable form of an element.
  •  
    List
    (Batch) Creates a list of elements that meet specific selection criteria. One effective use of this function is to perform impact analysis.
  •  
    Move
    (Foreground and batch) Moves elements between stages, within or across environments.
  •  
    Print
    (Foreground and batch) Prints element or member information.
  •  
    Restore
    (Batch) Restores elements to
    Endevor
    from an archive data set.
  •  
    Retrieve
    (Foreground and batch) Copies elements from
    Endevor
    to an external data set.
  •  
    Signin
    (Foreground and batch) Removes the user signout associated with an element.
  •  
    Transfer
    (Batch) Moves elements between locations that are not on the same map route.
  •  
    Update
    (Foreground and batch) Updates an element from an external data set
Element Actions by Job Function
A typical site might include the following job functions:
  • Development
  • QA/Test
  • Turnover
  • Audit
  • Management
  • Endevor
    administration
The following table summarizes, for each job function, the actions that someone might perform:
 
Action
 
 
Dev
 
 
QA/Test
 
 
Turnover
 
 
Audit
 
 
Mgmnt
 
 
Admin
 
Add/Update
X
X
X
Archive
X
Copy
X
Delete
X
X
Display
X
X
X
X
X
X
Generate
X
List
X
X
Move
X
X
X
X
Print
X
X
X
X
X
X
Restore
X
Retrieve
X
X
X
Signin
X
X
X
Transfer
X
X
Reporting
Endevor
provides a full set of standard reports.
Source and Output Management
As it executes each action request,
Endevor
categorizes the processing as source management or output management.
  • Source management deals with that aspect of processing that maintains the element source and MCF definitions; that is, updates to the Master Control File and to the base and delta libraries.
  • Output management relates to any processing that creates or maintains data sets related to the element being processed. These data sets include the source output libraries, processor listing and load libraries (applicable for element type PROCESS only), user-defined libraries, and INCLUDE libraries.
 Output management is only available if you have the
Endevor
processor component.
Audit Stamps
Endevor
can place an encrypted audit stamp, called a footprint, in the output source, object, or load modules that are created by processors. The footprint provides an integrity check between the source form of an element and its executable form.
Packages
Endevor
packages allow you to formalize your use of actions by:
  • Creating sets of actions that can be tracked, maintained, and reused as a unit.
  • Establishing approval procedures for packages.
  • Centralizing package location, facilitating their reuse across environments.
  • Shipping packages to remote locations.