What is Endevor?

Endevor is an integrated set of management tools for automating, controlling, and

monitoring the mainframe software development lifecycle. Endevor is used to
maintain software applications and track their versions.

In Endevor, source code and related code objects are known as Elements. An Element
is a partitioned data set member, a CA Panvalet, CA Librarian, sequential data set,
or USS file that has been placed under the control of CA Endevor. An Element is the
smallest object for which the product provides control.

Endevor Primary Options panel:

Why do we need Endevor?

During the software development lifecycle, the user performs Element actions on
Elements such as Add, Update, Move, Delete, Signout, and so on. These functions
can be performed in foreground or batch mode.

Many functions can be executed in foreground, but submitted for batch processing.
All JCL batch functions are described using the Software Control Language (SCL).
SCL is the Endevor freeform language, with English-like statements, that is used for
the batch execution of Endevor.

What is Endevor Environment?

An Endevor Environment is a phase of the life cycle through which a software change
migrates.

Examples: Test, Production.

Endevor is made up of Environments, Stages, and the following,

• System Name
• Subsystem Name
• Type of Inventory
• Element name

Standard Software Lifecycle:

Endevor automates and controls the movement of software through your software
lifecycle. A standard software lifecycle consists of the following Stages:

1. Development — Applications are developed here.

2. Test — Applications are unit tested here.
3. Quality Assurance — Applications are system tested here.
4. Emergency — Fixes are applied to production code here.
5. Production — Production applications are stored here.

In this lifecycle, new or existing code is developed in the Development library. After
the code has been unit tested by the application developer, the code is added to the
test Stage for unit testing. When the code is ready for system testing, it is moved to
the quality assurance Stage. Finally, when the code is ready to be used by customers,
the code is moved to the production Stage. Any fixes are applied to production code
in the emergency Stage.

Emergency Operations:

When fixes must be applied to production code, Endevor can manage the following
emergency operations:

1. Retrieving elements from production

2. Making changes to elements
3. Adding or updating elements into the emergency Stage
4. Moving elements to production

In this lifecycle, production code is retrieved from the production Stage and is added
back to the emergency Stage. After the fixes are applied to the code in the
emergency Stage, the code is moved back to the production Stage.
Steps involved in Endevor elements update:

1. Retrieving Elements from production to a development library

2. Making changes to Elements
3. Adding or updating Elements into the test stage
4. Moving Elements to QA
5. Moving Elements back into production

What is Endevor Package?

If your site requires approvals to move your software code changes through the
lifecycle, Packages, which are used to group Element actions, must be used to
perform the moves.

Users Access in Endevor:

Application developers, quality control engineers, and managers (development

managers, quality control managers, product and project managers, and production
control managers) benefit from using the product in the following ways:

• Application developers use Element actions to develop, manage, and control

software changes. For example, based on an approved change order, a
developer uses the Retrieve Elements action to retrieve an Element from the
production Stage to a development library. After changing the source code, the
developer uses the Add Elements action to add the Element to the testing
Stage. Finally, the developer can use the Generate Elements action to create
an executable form of an Element.
• Development, quality control, and source control managers use Element
actions to approve and move Elements through the Stages in the software
lifecycle. For example, after all functional testing has been performed on source
code, a quality control manager can create a Package to promote all of the
code comprising a specific piece of software functionality to the production
Stage.
Endevor - Retrieve Element

To retrieve an element from an production to an external (user) data set, you use
the Retrieve Elements action.

Follow the below steps to retrieve an element from an production.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 2 (Foreground) and press Enter.

The Foreground Options menu appears.

3. Enter 3 (Retrieve) and press Enter.

The Retrieve Elements panel appears.

Note: For more information about a field or option on the panel, press PF1.

4. Choose one of the following steps.

o To retrieve an element, enter the information for the action, enter R in
the Option field, and press Enter.
 o To retrieve an element from an Element Selection List (applies when you
set the DISPLAY LIST option to Y), enter the information for the action,
leave the Option field blank, and press Enter.
o To retrieve a prior version of an element, enter the information for the
action, enter S in the Option field, and press Enter.
5. (Optional) If the Element Selection List or Summary of Levels panel appears,
enter an option to the left of each member you want to retrieve and press
Enter. The ISPF Locate command is supported on Element Selection lists.

The element is retrieved to an external (user) data set.

Endevor - Add Element

To control and manage a member from an external data set (PDS or PDS/E member,
CA Panvalet, CA Librarian or sequential data set, or load module), you use the Add
Elements action.

Follow the below steps to add an element into endevor entry stage.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 2 (Foreground) and press Enter.

The Foreground Options menu appears.

3. Enter 2 (Add/Update) and press Enter.

The Add/Update Elements panel appears.

Note: For more information about a field or option on the panel, press PF1.

Note: For more information about adding or updating an element with the
Autogen option, see How Generating Elements with Autogen Works.
 4. Choose one of the following steps.
1. To add a member, enter the information for the action, enter A in the
Option field, and press Enter.

Note: If you want the element name to be different from the member
name, change the name in the ELEMENT option. In addition, if you are
adding an element for the first time, the comment becomes the element
description in the Master Control File.

2. To add multiple members, leave the Option field blank and press Enter.

The Member Selection List appears. This list appears when the source
data set is a library, you leave the Option field blank, the DISPLAY LIST
option is set to Y, and when both the ELEMENT and MEMBER options are
blank or have a name mask. The ISPF Locate command is supported on
Member Selection lists.

5. (Optional) If the Member Selection List appears, enter A to the left of each
member you want to add and press Enter.

The members are added and you return to the Add/Update Elements panel.
You can browse the listing data set for more information about each selected
member.

Endevor - Update Element

To control and manage a member when an element with the same name already
exists in the target entry stage, you use the Update Elements action.

Follow the below steps to update an element into endevor entry stage.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 2 (Foreground) and press Enter.

The Foreground Options menu appears.

3. Enter 2 (Add/Update) and press Enter.

The Add/Update Elements panel appears.

 Note: For more information about a field or option on the panel, press PF1.

Note: For more information about adding or updating an element with the
Autogen option, see How Generating Elements with Autogen Works.

4. Choose one of the following steps.

1. To update a member, enter the information for the action, enter U in the
Option field, and press Enter.
2. To update a member from the source library, enter the information for
the action, leave the Option field blank and press Enter.

The Member Selection List appears. This list appears when the source data set
is a library, you leave the Option field blank, the DISPLAY LIST option is set to
Y, and when both the ELEMENT and MEMBER options are blank or have a name
mask. The ISPF Locate command is supported on Member Selection lists.

5. (Optional) If the Member Selection List appears, enter U to the left of each
member you want to update and press Enter.

The members are updated and you return to the Add/Update Elements panel.
You can browse the listing data set for more information about each selected
member.

Endevor - Move Element

To move an element from one inventory location (environment, stage) to the next
location on a map route, you use the Move Elements action.

Follow the below steps to move an element into different stages.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 2 (Foreground) and press Enter.

The Foreground Options menu appears.

3. Enter 5 (Move) and press Enter.

The Move Elements panel appears.

Note: For more information about a field or option on the panel, press PF1.

4. Specify the element you want to move, and enter a comment to explain the
move.
5. Complete the following fields:

Sync

Enter Y (Yes) or N (No) to indicate whether you want the MOVE action
performed when the base level of the element at the source location is different
from the current level of the element at the target. When you enter Y, the
product creates a "sync" level at the target that reflects the differences
between the base level at the source location and the current level at the
target. The move fails if these levels are different and you have specified SYNC
= N.

With History

Enter Y (Yes) or N (No) to indicate whether you want to move the element with
history. When you move the element without history, the product searches
through the element levels at the source location to find a matching level at
the target location. The product then compares the two, and creates a new
level at the target location that reflects the differences.

Signout To
 Enter the TSO userid of the person at the target location for which you want to
sign out the element. If the RETAIN SIGNOUT option is set to Y, you cannot
use this option.

Delete from Element

Enter Y (Yes) or N (No) to indicate whether you want the product to delete the
elements at the source location after moving them.

6. Press Enter.

The element is moved to the next location on a map route.

Endevor - Delete Element

Follow the below steps to delete the levels for an element.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 2 (Foreground) and press Enter.

The Foreground Options menu appears.

3. Enter 6 (Delete) and press Enter.

The Delete Elements panel appears.

Note: For more information about a field or option on the panel, press PF1.

4. Specify the element you want to delete, enter the additional information for
the action, enter # (pound sign) in the Option field, and press Enter.
 Note: If you enter a CCID, it is logged to IBM's System Management Facilities
(SMF), if enabled, and is available to exits in the product.

5. (Optional) If the System Selection List, Subsystem Selection List, and Element
Selection List appears, enter S to the left of the system, subsystem, and
element you want to delete.

The element levels are deleted, and the Master Control File (MCF) is updated.

Endevor - Generate Element

To create an executable form of an element (that is, outputs: object modules, load
modules, listing, and so forth), use the Generate Elements action (available in
foreground, batch, and in packages).

Follow the below steps for generate elements action.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 2 (Foreground) and press Enter.

The Foreground Options menu appears.

3. Enter 4 (Generate) and press Enter.

The Generate Elements panel appears.

Note: For more information about a field or option on the panel, press PF1.

4. Specify the element for which you want to generate an output, enter the
additional information for the action, enter S in the Option field, and press
Enter.
5. (Optional) If the System Selection List, Subsystem Selection List, and Element
Selection List appears, enter S to the left of the system, subsystem, and
element for which you want to generate an output.

The output is generated for the element.

Endevor - Remove User Signout

If an element is currently signed out to your user ID, you can sign in the element,
which removes the signout ID associated with the element. In addition, after the
element is signed in, you can sign out the element to a different user ID. If your site
administrator has set up authorization for you, you can sign in an element that is not
signed out to you.

Follow the below steps to remove user signout in endevor.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 2 (Foreground) and press Enter.

The Foreground Options menu appears.

3. Enter 8 (Signin) and press Enter.

The Signin Elements panel appears.

Note: For more information about a field or option on the panel, press PF1.

4. Specify the element you want to sign in and enter the additional information
for the action. Enter SI in the Option field, and press Enter.The following
actions are optional:
 Override Signout

Specifies whether element signin is allowed when the element is not currently
signed out to you. Acceptable values are:

Y – Sign in the element even if it is not currently signed out to you.Your site
administrator must set up permission for you to use to specify Y.

N – Default. Do not allow the SIGNIN action unless the element is already
signed out to you.

Signout To

Specifies the user ID that the element will be signed out to after it is signed in.

5. (Optional) If the System Selection List, Subsystem Selection List, and Element
Selection List appears, enter S to the left of the system, subsystem, and
element you want to signin.

The element is signed in. If you entered a user ID in the Signout To field, the
element is signed out to that user ID.

Endevor - Create Package

You create a package by first defining the package, and then including SCL in the
package to specify element actions to be performed. Packages can be executed
online or submitted in batch.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 5 (Package) and press Enter.

The Package Options menu appears.

3. Enter a name for the package, type 2 (Create/Modify) in the Option field and
press Enter.

The Create/Modify Package panel appears.

 Note: For more information about a field or option on the panel, press PF1.

4. Select the package type in the Promotion Package field. Enter Y, if this is a
promotion package, or N if this is not a promotion package.

This option determines whether the package will be processed as a promotion

package.

5. Enter B in the Option field to open the online SCL generator.

6. Enter the package information and press Enter to submit the build request.

The SCL Generation panel appears.

7. Specify the actions in the Option field to build the package and press Enter.

Note: These actions are placed in the request data set displayed at the bottom
of the page.

The appropriate action panel appears.

8. Press END to return to the Create/Modify Package panel.

The package is created, and can now be cast.

Endevor - Cast Package

Some packages must be reviewed and approved before being executed. Casting a
package is the first step in the package review process.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 5 (Package) and press Enter.

The Package Options menu appears.

3. Enter the package name, leave the PACKAGE ID field blank to display a
Package Selection List, or enter a name mask. Enter 3 (Cast) in the OPTION
field and press Enter.

The Cast Package panel appears.

Note: For more information about a field or option on the panel, press PF1.

4. If the Package Selection List appears, select the package you want to cast and
press Enter.

The Cast Package panel appears.

5. (Optional) Enter S in the Option field and press Enter to view the package SCL
before you cast the package.

The Display SCL panel appears.

6. (Optional) Review the SCL and press END.

The Cast Package panel appears.

7. If the Cast Package panel appears, enter C in the Option field to cast the
package.

Note: After you cast a package, you cannot edit it.

Specify the information in the VALIDATE COMPONENTS, ENABLE BACKOUT,

and EXECUTION WINDOW fields.

8. Press Enter to submit the cast request.

9. Press END to return to the Package Options menu.

When you cast a package that requires approval, the package status is changed
to In-approval. When you cast a package that does not require approval, the
 package status is changed to Approved. After a package has been cast, it can
be approved and then executed.

Endevor - Review and Approve Package

If one or more approver groups are associated with the inventory areas included in
a package, then the package must be reviewed and approved before it can be
executed. To be approved, the package must be accepted by all of the required
approvers, be accepted by a quorum of approvers, and not be denied by any
approver.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 5 (Package) and press Enter.

The Package Options menu appears.

3. Enter the package name, leave the PACKAGE ID field blank to display a
Package Selection List, or enter a name mask. Enter 4 (Review) and press
Enter.

The Review Package panel appears or the Package Selection List appears.

Note: For more information about a field or option on the panel, press PF1.

4. If the Package Selection List appears, select the package you want to review
and press Enter.

The Review Package panel appears.

5. On the Review Package panel, choose one of the following steps.

1. To review the SCL for the package, leave the Option field blank and press
Enter.

The Summary SCL panel appears.

2. To approve the package, enter A in the Option field and press Enter.

The Package Options menu appears with a message saying that the
package has been approved.

3. To deny the package, enter D in the Option field and press Enter.
 The Package Options menu appears with a message saying that the
package has been denied.

4. To view the approver groups for the package, enter L in the Option field
and press Enter.

The Approver Groups panel appears. Press END to return to the Package
Review panel.

5. To add or change notes associated with the package, enter N in the

Option field and press Enter.

The Package Note Text panel appears. Press END to return to the
Package Review panel.

6. The package is reviewed and approved, and can be executed.

Endevor - Execute Package

After a package has been approved, you can submit it for execution now or for batch
processing. Before executing the package, the product validates the package to make
sure you have the authority to perform the package's actions, the execution request
is within the execution window, and that no elements have changed since the
package was cast.

1. Start the product using the instructions provided by your site administrator.

The Primary Options panel appears.

2. Enter 5 (Package) and press Enter.

The Package Options menu appears.

3. Enter 5 (Execute) and press Enter.

The Execute Package panel appears.

Note: For more information about a field or option on the panel, press PF1.

4. Enter the package name, leave the PACKAGE ID field blank to display a
Package Selection List, or enter a name mask, and press Enter.

The Execute/Submit Package panel or the Package Selection List appears.

 5. If the Package Selection List appears, select the package you want to execute
and press Enter.

The Execute/Submit Package panel appears.

6. On the Execute/Submit Package panel, enter E in the OPTION field.

The package is executed.

Note: You can submit the job for batch processing from the Execute/Submit
panel, by entering S in the OPTION field.

Note: For more information about batch submission, see Submit a Package for
Batch Processing.

Endevor - Submit Package

You can submit a package to be executed in batch. Batch processing lets you request
concurrent action processing.

1. On the Execute/Submit Package panel, type S in the OPTION field and press
Enter.

The Submit Package panel.

2. Edit the options.

Include JCL

Y--Additional JCL is included when the job is submitted.

N--No additional JCL is included.

Concurrent Action Processing

Use this field to indicate whether or not you want to use concurrent action
processing. Valid values are Y and N. The default value when you enter the
panel is N. If this feature is not enabled for your site, this option is read-only.

Note: The Concurrent Action Processing facility causes certain element action
requests to be executed concurrently, which reduces the elapsed time it takes
to process multiple actions. Before you can use this facility, it must be enabled
by your CA Endevor SCM administrator.

Concurrent Number
 Specify the number of concurrent actions to be processed, if you are using
concurrent action processing. The default is the SPAWNCNT value set in
C1DEFLTS. If you overwrite the default and then decide you want to use the
default, either type in the default value or blank out this field. Valid values are
02 through the Max number shown on the panel. The Max number is the value
of SPAWNMAX specified in the C1DEFLTS.

3. Optional. Type E in the OPTION field and press Enter.

The JCL to Be Included with Batch Job panel opens.

4. Optional. On the JCL to Be Included with Batch Job panel, enter additional JCL
to be included with the job.

This JCL is included when the job is submitted, if the Include JCL option on this
Submit panel is set to yes.

5. Press the End key.

The Submit Package panel reopens.

6. Type S in the OPTION field and then press Enter.

The package is submitted for batch execution.