Endeavor Workflow

CA-ENDEVOR SE WORKFLOWS
(VERSION 1.0)
TABLE OF CONTENTS
1 INTRODUCTION.......................................................................................................1
2 OVERVIEW................................................................................................................3
2.1 ENVIRONMENTS AND STAGES...........................................................................................................3
3 ROLES AND RESPONSIBILITIES.........................................................................4
4 COMMONLY USED COMMANDS/ACTIONS......................................................5

4.1 FOREGROUND AND BATCH PROCESSING..............................................................................5
4.1.1 Foreground...............................................................................................................................5
4.1.2 Batch........................................................................................................................................5
4.2 SOFTWARE CONTROL LANGAGE.............................................................................................6
4.2.1 SCL Generation........................................................................................................................6
4.2.2 EDIT SCL.................................................................................................................................7
4.2.3 VALIDATING SCL...................................................................................................................7
4.2.4 ADDITIONAL JCL...................................................................................................................7
4.2.5 SUBMITTING THE JOB..........................................................................................................8
4.3 PACKAGES.....................................................................................................................................9
4.3.1 Creation....................................................................................................................................9
4.3.2 Casting...................................................................................................................................10
4.3.3 REVIEW/APPROVAL/DENIAL..............................................................................................11
4.3.4 EXECUTE/SUBMIT...............................................................................................................12
4.3.5 Commit...................................................................................................................................13
4.4 RETRIEVE.....................................................................................................................................15
4.5 DISPLAY ELEMENTS..................................................................................................................17
4.6 ADD /UPDATE..............................................................................................................................18
4.7 MOVE..............................................................................................................................................20
4.8 GENERATE...................................................................................................................................22
4.9 DELETE.........................................................................................................................................24
4.10 SIGN IN/OUT/OVERRIDE...........................................................................................................26
4.11 MASTER CONTROL FILE...........................................................................................................30
5 PROCEDURES TO FOLLOW...............................................................................31
5.1 STANDARD CHANGE OVERVIEW.....................................................................................................31
5.2 STANDARD CHANGE PROCEDURE........................................................................................31
5.3 EMERGENCY CHANGE OVERVIEW..................................................................................................37
5.4 EMERGENCY CHANGE PROCEDURE.....................................................................................37
6 CA-ENDEVOR QUICK-EDIT................................................................................42
6.1 MOVE............................................................................................................................................43
6.2 GENERATE...................................................................................................................................44
6.3 DELETE.........................................................................................................................................44
7 PARALLEL DEVELOPMENT MANAGER.........................................................46
7.1 BUILDING A WIP FILE.....................................................................................................................46
7.1.1 Structure of a WIP file............................................................................................................46
7.2 EDITING A WIP FILE.......................................................................................................................47
7.3 MERGING A WIP FILE.....................................................................................................................47
8 AUTOMATED CONFIGURATION MANAGEMENT........................................49
8.1 DATA COLLECTION..........................................................................................................................49
8.2 DATA STORAGE...............................................................................................................................49
8.3 SOFTWARE CONFIGURATION ANALYSIS AND MANAGEMENT..........................................................49
8.4 THE COMPONENT MONITOR...........................................................................................................50
8.5 MONITORING INPUT COMPONENTS.................................................................................................51
8.6 MONITORING OUTPUT COMPONENTS.............................................................................................51
8.7 MONITORING COMPONENTS IN A GENERATE PROCESSOR..............................................................51
8.8 MONITORING COMPONENTS IN A MOVE PROCESSOR.....................................................................52
8.9 COMPONENT LIST...........................................................................................................................52
9 COMMON ERRORS AND THEIR SOLUTIONS................................................54
10 FREQUENTLY ASKED QUESTIONS...................................................................62
11 APPENDIX................................................................................................................63
11.1 DEFINITIONS....................................................................................................................................63
11.2 NAMING CONVENTIONS..................................................................................................................63
11.3 SOME FACTS RELATED TO BARS APPLICATIONS...........................................................................64
SE Workflow Document Introduction
1 Introduction
CA-Endevor is an integrated set of management tools that is used to automate, control,

and monitor your software development life cycle. CA-Endevor is implemented and run
under MVS, within the TSO ISPF environment, and in batch.
Using CA-Endevor, you can:
 Keep source synchronized with execution by comparing the date and time that
element was last generated with the date and time information in footprint
 Automatically compare and track your changes against production, creating an online
change history. This speeds up the debugging process and enables you to always
know what was changed, by whom, why and when
 Prevent conflicting changes to the same elements
 Browse and manipulate all components relating to an application from a single
screen, saving your time and ensuring that changes are complete
 Create executables automatically
 Ensure that the source, executable, and any other form (for example, listings) of an
element correspond
 Apply the same procedures (including automating compiles, analyzing impacts, and
standards checking functions) to any component type, dramatically simplifying the
standardization process
 Put change packages and approvals online, eliminating change-related paperwork
 View or retrieve prior levels of any element
 Report on element definition, content, and change history
 Enforce change control procedures
Endevor has a wonderful facility called Parallel Development Manager (PDM) that is
used to control the concurrent development activities necessitated by the complexity of
today's applications and the pace at which these applications are developed. Some
general aspects of parallel development include:
 Allowing several programmers working on the same application and often the same
programs. Identifying and resolving conflicts in programs that have been
independently updated by more than one programmer.
SE Workflow Document Introduction
 The time-consuming, resource-intensive, and error-prone process of manually

integrating independent changes to a program.
 Reconciling differences between customized vendor software packages and vendor
release updates.
 Assessing project complexity, duration, and the resource requirements.
CA-Endevor also provides the feature called MVS ACM (Automated Configuration
Manager) that works in conjunction with CA-Endevor to enable you to manage, through
advanced automated technology, the interrelationships between software components.
SE Workflow Document Overview
2 Overview
CA – Endevor helps to manage the software life cycle by providing a consistent and
flexible logical structure for classifying software inventory. There are six components in
the inventory structure: environments, stages, systems, subsystems, types and elements.
Environments, stages, systems, subsystems and types are setup by the CA-Endevor
administrator. SEs act on elements.
2.1 Environments and Stages
CA-Endevor allows you to automate and control the movement of software through SLC.
Software Life Cycles are site/application specific. A representative cycle might consist of
two environment (CCCC TEST and CCCC PROD) and four stages (PROD, FIX, TEST
and HOLD) shown below.
The following diagram illustrates the Environments & Stages:
CCCC TEST CCCC PROD
TEST HOLD FIX PROD
PROD: Elements Retrieved and Moved back from Hold and FIX.
TEST: Programs/Elements are tested after changes(added/updated )
HOLD: QA takes place.
FIX: Emergency Fixes are made and tested
Note:
Refer section # 5 “Definition/Acronyms/Naming Conventions” for more details about
Environment, Stage, System, Subsystem and Types.
SE Workflow Document Roles and Responsibilities
3 Roles and Responsibilities

SE may need to do the following tasks:
Display Members
 Retrieve elements
 Add/Update elements
 Move elements
 Generate elements
 Create, Cast, Review, Execute/Submit and Commit Packages
SE Workflow Document Commonly used Commands/Actions
4 Commonly used Commands/Actions
4.1 FOREGROUND AND BATCH PROCESSING

4.1.1 Foreground
 In foreground processing, actions are performed in foreground mode
 Select 2, FOREGROUND in the CA-Endevor Primary Option Menu and hit ENTER,
it will takes you to FOREGROUND OPTIONS MENU
Note: Due to the security options in effect at your installation, not all actions may be
available to you in foreground. Foreground option Menu is as shown in the picture below
-------------------------- FOREGROUND OPTIONS MENU --------------------------

OPTION ===>
1 DISPLAY - Display an element
2 ADD/UPDATE - Add or update an element into stage 1
3 RETRIEVE - Retrieve or copy an element
4 GENERATE - Execute the Generate Processor for this element
5 MOVE - Move an element to the next inventory location
6 DELETE - Delete an element
7 PRINT - Print elements, changes and detail change history
8 SIGNIN - Explicitly sign-in an element
-------------------------------------------------------------------------------------------------------
4.1.2 Batch
 Select 3, BATCH in the CA-Endevor Primary Option Menu and hit ENTER, it takes
you to the BATCH OPTIONS MENU
BATCH ----------------------- BATCH OPTIONS MENU -----------------------------

OPTION ===>
1 BUILD SCL - Build batch SCL actions
2 EDIT - Edit request data set
3 SUBMIT - Submit job for batch processing
4 VALIDATE - Check request data set for syntax errors
5 BUILD JCL - Enter additional JCL to be included with the job
REQUEST DATA SET:
PROJECT ===> user-id APPEND ===> N (Y/N)
GROUP ===> group-name INCLUDE JCL ===> N (Y/N)
TYPE ===> type
MEMBER ===> member-name
OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DSNAME ===> dataset(member)
JOB STATEMENT INFORMATION:
===> jobcard information
------------------------------------------------------------------------------------------------------------------------------------------------------------------
In this panel, select the action you want to perform by entering the action number.
SE Workflow Document Software Control Language
4.2 SOFTWARE CONTROL LANGAGE

 When you request action in Batch you have to build SCL
 To create CA-Endevor requests (such as ADD or UPDATE) for BATCH processing
you must allocate partitioned or sequential dataset. After that go to the BATCH
OPTION MENU
 Select 1, BUILD SCL, specify must specify the dataset name in the field REQUEST
DATA SET or OTHER PARTITIONED OR SEQUENTIQAL DATA SET to which
you want to write the action requests
 If you enter OTHER PARTITIONED OR SEQUENTIQAL DATA SET field to define
the dataset by entering the appropriate dataset name and member in the following
format: ‘dataset(member)’
 Enter APPEND = ‘Y’ to add new request to the end of an existing data set. To
overwrite any data currently in the dataset then enter APPEND = ‘N’
 To include JCL in addition to the standard execution of JCL, enter ‘Y’ in the
INCLUDE JCL field. Default is ‘N’
 The field JOB STATEMENT INFORMATION field allows you to provide jobcard
settings for submitting batch jobs. Provide all jobcard parameters, including job
name, time, message parameters and any other parameters you want
4.2.1 SCL Generation

 Select 1, BUILD SCL and hit ENTER. It takes you to SCL GENERATION panel.
This panel allows you to select the type of action request you want to perform
 To move elements from a map location to a location not in the map, select 9,
TRANSFER
 To print or browse footprinted members from a library, select 10, PRINT MEMBER
 To list elements from Master Control File(MCF), select 11, LIST ELEMENTS
 To list or browse members from a library, select 12, LIST MEMBER
 To write the current version of the elements to a sequential file, select 13, ARCHIVE
-------------------------------------- SCL GENERATION ----------------------------------------

OPTION ===>
1 DISPLAY - Display an element
2 ADD/UPDATE - Add or update an element into stage 1
3 RETRIEVE - Retrieve or copy an element
4 GENERATE - Execute the Generate Processor for this element
5 MOVE - Move an element to the next inventory location
6 DELETE - Delete an element
7 PRINT ELEMENT - Print elements, changes and detail change history
8 SIGNIN - Explicitly sign-in an element
9 TRANSFER - Transfer elements between two CA-Endevor locations
10 PRINT MEMBER - Print a compressed listing or member
11 LIST ELEMENT - Create List actions for CA-Endevor elements
12 LIST MEMBER - Create List actions for external members
13 ARCHIVE - Archive elements
REQUEST DATA SET: BST.SUPPORT.SRCLIB(SCL)
APPEND: Y
4.2.2 EDIT SCL
 To edit the SCL, select 2, EDIT in the BATCH OPTION MENU. You must specify
the dataset you want to edit using the REQUEST DATA SET or OTHER
PARTITIONED OR SEQUENTIAL DATASET field
4.2.3 VALIDATING SCL
 To validate the SCL, select 4, VALIDATE in the BATCH OPTION MENU

 When you select VALIDATE, you must specify the dataset you want to edit using the
REQUEST DATA SET or OTHER PARTITIONED OR SEQUENTIAL DATASET
field
 When you validate the SCL, CA-Endevor checks the syntax of the action request just
as if it were going to run the job, and returns an appropriate message(s) if there are
errors. The ISPF/PDF Browse facility shows syntax error, if any
 Always validate the SCL
4.2.4 ADDITIONAL JCL

 To include additional JCL, select 5, BUILD JCL, from the BATCH OPTION MENU.
CA-Endevor display JCL TO BE INCLUDED WITH BATCH JOB panel. Fill in the
JCL you want to include with the job, press PF3 to return to the BATCH OPTION
MENU
4.2.5 SUBMITTING THE JOB

 Select 3, SUBMIT, from the BATCH OPTION MENU to submit a job that executes
action request in batch
 You must specify the dataset you want to edit using the REQUEST DATA SET or
OTHER PARTITIONED OR SEQUENTIAL DATASET field
SE Workflow Document Packages
4.3 PACKAGES
Description:
A Package is a set of CA-Endevor actions that may require approval before being
executed
4.3.1 Creation
 Select 5 in the CA-Endevor Primary Option Menu, It takes you to ‘Package

Foreground Option Menu’ panel
 Give a Package-ID as per the naming convention suggested. Select 2 to
Create/Modify a Package. It takes you to CREATE/MODIFY PACKAGE panel.
 Select B to build Package Action
 In this panel you must fill the description field. Decide the Package is either
STANDARD or EMERGENCY (Default is Standard). The status is in IN-EDIT.
Decide the package is shareable or not. Enter Y or N in the SHARABLE PACKAGE
field (Default is ‘Y’). Make packages always sharable. Hit ENTER
 It takes you to SCL Generation panel. Select the action (Example MOVE or
DELETE) that you want to perform
 It takes you to the related Action panel from there you can continue the Actions
described in the related action section
 When you create the Package successfully then you will get a message ‘Package
Constructed’
---------------------- Package Foreground Options Menu ---------------------

Option ===>
1 DISPLAY - Display Package Information
2 CREATE/MODIFY - Create or Modify Package
3 CAST - Prepare Package for Review
4 REVIEW - Approve or Deny Package
5 EXECUTE - Submit or Execute Package
6 SHIP - Ship Packages
7 BACKOUT - Perform Backout or Backin Processing
8 COMMIT - Clear Backout Information
9 UTILITIES - Reset, Delete, or Export Package
L DistribuLink - Perform Product Collection Request
Package ID ===> package-id
Limit selection list by Package Status. These are used by the DISPLAY
and UTILITIES options:
In-Edit…......... Y In-Execution.... Y
In-Approval..... Y Executed..….... Y
Denied..…...... Y Committed..…... Y
Approved……..Y
-------------------------------------------------------------------------------
----------------------------------- CREATE/MODIFY PACKAGE -------------------------------------

OPTION ===>
B - Build Package Actions I - Import SCL
E - Edit Package C - Copy Package
N - Add Notes to Package
PACKAGE ID: package-id STATUS: IN-EDIT
DESCRIPTION ===> description about the package
PACKAGE TYPE ===> STANDARD
SHARABLE PACKAGE ===> N (Y/N) APPEND TO PACKAGE ===> N (Y/N)
ENABLE BACKOUT ===> Y (Y/N)
EXECUTION WINDOW FROM ===> date time TO ===> date time
INPUT PACKAGE ID ===>
NOTES EXIST FOR PACKAGE
FROM ISPF LIBRARY:
PROJECT ===> user-id
GROUP ===> pds
TYPE ===> lib
MEMBER ===>
OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>
------------------------------------------------------------------------------------------------------------
4.3.2 Casting
When you cast the package, CA-Endevor
 Determines approvers
 Validate Package Components (optional)
 Check action security
 Check Component integrity
Description:
 After casting, if the Package requires approval CA-Endevor change the Package to
IN-APPROVAL, If the Package does not require an approval, it’s status change to
APPROVED
 After a Package has been cast, it can be approved and then executed.
Procedure:
 You must cast a Package after creating it
 Select 3 to CAST the Package in the Package Foreground Option Menu, it takes you
to ‘CAST PACKAGE’ Panel. Select C to cast the package.
 VALIDATE COMPONENTS = ‘Y’ means validate components and do not allow the
cast if validation fails, ‘N’ does not validate components. ‘W’ does the validation but
does not fail the cast if validation fails. Hit ENTER
 Check any cast warning/errors carefully. If the casting is successful you will get a
message CAST SUCCESSFUL
CAST---------------------------------------- CAST PACKAGE -------------------------------------------------

OPTION ===>
C – Cast Package S – Display SCL
N – Add Notes to Package
PACKAGE ID: package-id
DESCRIPTION: description about the package
PACKAGE TYPE: type of the package
SHARABLE PACKAGE: Y (Y/N)
VALIDATE COMPONENTS ===> (Y,N or W)
ENABLE BACKOUT ===> (Y/N)
NOTES EXIT FOR PACKAGE
EXECUTION WINDOW FROM ===> 02FEB97 00:00 TO ===> 31DEC97 00:00
USER ID DATE TIME
CREATED: user-id date time
LAST UPDATED:
--------------------------------------------------------------------------------------------------------------------------
4.3.3 REVIEW/APPROVAL/DENIAL
Description:
 If one or more approver groups are associated with the inventory area(s) included in
the packages, then Package must be reviewed and approved before it is executed. To
be approved, it must be accepted by all the approvers or at least by the necessary
approver(s)
 The Approver(s) can approve or deny the Package
 After getting the required approver(s) approval the Package may be executed by the
approver
4.3.4 EXECUTE/SUBMIT
Description:
 This is the exact step that does the CA-Endevor action what you want to do
To Execute:
 To execute a Package, you must have the authority to execute the Package and also
have the authority to perform the action contained in the Package
 The Package must be in status APPROVED
Available Modes:
 Packages can be executed in Foreground or Background
How to Execute?
 Select 5 in the CA-Endevor Primary Option Menu. Type the Package-id to go directly
to the
EXECUTE/SUBMIT PACKAGE panel
Foreground Execution:
 To execute a package online, select ‘E’ in the EXECUTE/SUBMIT PACKAGE panel
 A message appears in the upper right corner of the panel indicating whether the
Package executed successfully or not
 The status of the package is changed to Executed, if execution was successful. If there
is an execution error, the status is changed to Exec Failed
 After execution, hit ENTER to display the first page of the CA-Endevor Package
Execution Report. Press END to return to the CA-Endevor Primary Option Menu
Batch Execution:
 To execute a Package in Batch, select ‘S’ in the EXECUTE/SUBMIT PACKAGE
panel and hit ENTER
 It takes you to SUBMIT PACKAGE panel, select ‘S’ to submit the Package or select
‘E’ to include additional JCL with the Job and hit ENTER
 To include JCL in the JOB STATEMENT INFORMATION field you can include
 The status of the package is changed to Executed, if execution was successful. If there
is an execution error, the status is changed to Exec Failed
 Depends on the system you works you may receive a message indicating that your job
has been submitted
EXECUTE ---------------- EXECUTE/SUBMIT PACKAGE -----------------------------

OPTION ===>
E - Execute Package S - Submit Package
PACKAGE ID: package-id STATUS: APPROVED
PACKAGE TYPE: STANDARD
SHARABLE PACKAGE: Y
EXECUTION WINDOW FROM ===> date time ===> date time
USER ID DATE TIME
LAST UPDATED: user-id date time
CAST: user-id date time
APPROVED: date time
EXECUTED: ENDEVOR RC:
------------------------------------------------------------------------------------------------------------
SUBMIT-----------------------------SUBMIT PACKAGE----------------------------------------------
OPTION ===>
S – Submit job for batch processing
E – Enter additional JCL to be include with the job
PACKAGE ID: package-id
PACKAGE TYPE: type of the package
INCLUDE JCL ===> N (Y/N)
JOB STATEMENT INFORMATION:
===> // jobcard information
===> //
===> //
===> //
----------------------------------------------------------------------------------------------------------------
4.3.5 Commit
Description:
 Commit is the last stage in Package life cycle
 When package outputs are acceptable in their current stage, you can commit the
Package
 To COMMIT the Package, it must be in ‘EXECUTED’ status
What it does?
 It removes all backout/backin data for the Package
 After commit you can no longer be backed out, shipped or collected
 Once a Package is Committed, its dependent Packages (If any) can no longer be
backed out or backed in
How to commit?
 Enter the Package name in the PACKAGE-ID field of the Package Foreground
Option Menu and select 8, hit ENTER it takes you to COMMIT PACKAGE panel
 To see the Package selection list leave the Package–id field blank and hit ENTER
 It will list the Packages available for your userid. Select the package you want to
commit then hit ENTER
 To commit the package, select C in the COMMIT PACKAGE panel and hit ENTER
 The Package is committed and the status of the Package is set to ‘COMMITED’
COMMIT ------------------------- COMMIT PACKAGE ----------------------------------

OPTION ===>
C - Commit Package
PACKAGE ID: package-id STATUS: EXECUTED
PACKAGE TYPE: STANDARD
SHARABLE PACKAGE: N
EXECUTION WINDOW FROM: date time TO: date time
USER ID DATE TIME
LAST UPDATED: user-id date time
CAST: user-id date time
APPROVED: date time
EXECUTED: user-id date time ENDEVOR RC: 0000
BACKED OUT: user-id date time
BACKED IN: user-id date time
-------------------------------------------------------------------------------------------------------
SE Workflow Document Retrieve
4.4 RETRIEVE
Description:
 RETRIEVE gets a copy of the source from Production library in to a dataset
How to retrieve?
 RETRIEVE can be performed in Foreground or Batch
Foreground:
 Select 2, FOREGROUND in the CA-Endevor Primary Option Menu, It takes you to
Foreground Options Menu
 select 3, to RETRIEVE, It takes you to RETRIEVE ELEMENTS panel
 Enter ‘R’ to retrieve
 Enter the environment, system, subsystem, type, stage-id and element name of the
element to be retrieved
 Other than ENVIRONMENT field, all the other fields can be left blank to get a list
 If you get a list enter ‘R’ before the element name to be retrieved
 Enter a valid CCID and a meaningful comment in the respective field
 Signout is important. Enter signout as Yes (Default). If you don’t signout, you can’t
ADD
 Enter your dataset name where the retrieved member is going to be placed in the field
TO ISPF LIBRARY
 You will get a message ‘Retrieved’, if retrieval is successful
Batch:
 Select 3, BATCH in the CA-Endevor Primary Option Menu
 It takes you to BATCH OPTION MENU
 Build SCL (As explained in sec.x.x) and submit it from this panel for Action Retrieve
------------------------------------------ RETRIEVE ELEMENTS ----------------------------------------------

OPTION ===>
SE Workflow Document Retrieve
ELEMENT DISPLAY OPTIONS:

blank - Element list S - Summary B - Browse H - History
R - Retrieve element M - Master C - Changes
FROM CA-Endevor: ACTION OPTIONS:
ENVIRONMENT ===> CCCCprod CCID ===> CCIDname
SYSTEM ===> EXPAND INCLUDES ===> N (Y/N)
SUBSYSTEM ===> SIGNOUT ELEMENT ===> Y (Y/N)
ELEMENT ===> OVERRIDE SIGNOUT ===> N (Y/N)
TYPE ===> REPLACE MEMBER ===> N (Y/N)
STAGE ===> F-QF P - PROD
COMMENT ===>
TO ISPF LIBRARY: LIST OPTIONS:
PROJECT ===> DISPLAY LIST ===> N (Y/N)
LIBRARY ===> WHERE CCID EQ ===>
TYPE ===> WHERE PROC GRP EQ ===>
MEMBER ===> BUILD USING MAP ===> N (Y/N)
TO OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>
------------------------------------------------------------------------------------------------------
SE Workflow Document Display Elements
4.5 DISPLAY ELEMENTS

Description:
 This facility display the elements or an element related information in CA-Endevor
How to display elements?

Element information can be displayed in two ways.
i. From the CA-Endevor Primary Option Menu.

From this menu select 1 it will takes you to another panel DISPLAY
OPTION MENU. Select 1 in that panel it takes you to Display Elements
/Component Lists panel
ii. From the CA-Endevor Foreground Option Menu select 1 (By selecting 2
in the CA-Endevor Primary Option Menu you got this Foreground Option
Menu) it takes you to Display Elements /Component Lists panel
In the Display Elements /Component Lists panel, specify the details related to the
element like Environment, System, Subsystem, Type and Stage-id. You can leave any
fields other than ENVIRONMENT. It will list all the details about the elements like
version, level and other details.
---------------------------------- Display Elements/Component Lists --------------------------------------

OPTION ===>
blank - Display selection list B - Browse element current level
S - Display summary of levels C - Display changes current level
M - Display element master info H - Display history current level
Enter SX, BX, CX or HX to display component list information
FROM CA-Endevor: LIST OPTIONS:
ENVIRONMENT ===> CCCCPROD DISPLAY LIST ===> Y (Y/N)
SYSTEM ===> WHERE CCID EQ ===>
SUBSYSTEM ===> WHERE PROC GRP EQ ===>
ELEMENT ===> DISPLAY SYS/SBS LIST ===> Y (Y/N)
TYPE ===> BUILD USING MAP ===> N (Y/N)
STAGE ===> F-QF P-PROD
---------------------------------------------------------------------------------------------------
SE Workflow Document Add/Update
4.6 ADD /UPDATE

Description:
ADD /UPDATE action puts a member under CA-Endevor control from your PDS.
Availability:
ADD /UPDATE can be performed in foreground or batch.
Foreground:
 From PRIMARY OPTIONS MENU, select 2, FOREGROUND.CA-Endevor displays
the FOREGROUND OPTIONS MENU.
 From FOREGROUND OPTIONS MENU, select 2, to go to ADD /UPDATE
ELEMENTS panel to ADD /UPDATE an element into stage1.
 Choose OPTION ===> A to Add an element or OPTION ===> U to Update an
element.
 Specify the ENVIRONMENT, SYSTEM, SUBSYSTEM, ELEMENT and TYPE.
 The TYPE, COMMENT, and NEW VERSION fields initially display the information
from the ADD /UPDATE ELEMENTS panel.
 Make sure that following ACTION OPTIONS are completed.
 CCID is as per the naming conventions.
 To generate the element enter GENERATE ELEMENT = Y (Default).
 DELETE INPUT SOURCE = Y to delete the input member in your edit
PDS.
 Leave NEW VERSION option always blank.
 OVERRIDE SIGNOUT = N
 UPDATE IF PRESENT = Y to Add the element, even if an element with
the same name exists. UPDATE IF PRESENT = N (Default) is for not to
add the element if an element with the same name exists.
 The Add/Update elements panel is shown below:
SE Workflow Document Add/Update
---------------------------------------- ADD /UPDATE ELEMENTS ----------------------------------------

OPTION ===>
blank - Member list A - Add an element U - Update an element
TO CA-Endevor: ACTION OPTIONS:
ENVIRONMENT ===> ccccTEST CCID ===>
SYSTEM ===> GENERATE ELEMENT ===> Y (Y/N)
SUBSYSTEM ===> DELETE INPUT SOURCE ===> N
(Y/N)
ELEMENT ===> NEW VERSION ===>
TYPE ===> OVERRIDE SIGNOUT ===> N (Y/N)
STAGE: T PROCESSOR GROUP ===>
UPDATE IF PRESENT ===> N (Y/N)
COMMENT ===>
FROM ISPF LIBRARY: LIST OPTIONS:
PROJECT ===> USERID DISPLAY LIST ===> Y
LIBRARY ===> PDS
TYPE ===> LIB
MEMBER ===> THRU MEMBER ===>
FROM OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>
----------------------------------------------------------------------------------------------------------------------
Batch:
 From the CA-Endevor Primary Option Menu select 3 for BATCH OPTIONS MENU
 In the BATCH OPTION MENU select Build SCL (as in sec.xx) and submit for the
action ADD /UPDATE.
 Refer sec # xx for further steps to continue in BATCH OPTIONS MENU.
SE Workflow Document Move
4.7 Move
Description:
MOVE action moves elements from one inventory area to the next inventory area on a
map route.
Availability:
Move action can be performed in foreground, batch or packages. A package move is a
must when the element is moved to production.
Foreground:
 From Primary Options Menu, select 2, FOREGROUND, CA-Endevor displays the
Foreground Options Menu.
 From Foreground Options Menu select 5, MOVE.
 Specify the ENVIRONMENT, SYSTEM, SUBSYSTEM, ELEMENT, TYPE and
STAGE ID of the source stage to define the element to move.
 Make sure that the following ACTION OPTIONS are completed:
 CCID is as per the naming conventions.
 SYNC = N (Default)
Note: SYNC = Y, when the base level of the element at the source location
is different from the current level of the element at the target.
 WITH HISTORY = N
 RETAIN SIGNOUT = N (Default. This option does not retain the source
location Signout at the target location.)
 SIGNOUT TO = N (Default)
Note: If RETAIN SIGNOUT = Y, you cannot use this option.
 ACKNOWLEDGE ELM JUMP = N
 DELETE FROM ELEMENT = Y
Caution: If DELETE FROM ELEMENT = N then you must specify SYNC
= Y for any subsequent moves of this element.
 The MOVE ELEMENTS panel is shown below:
SE Workflow Document Move
------------------------------------------------------- MOVE ELEMENTS ---------------------------------------------------

OPTION ===>
O - Move element M - Master C - Changes
ENVIRONMENT ===> ccccTEST CCID ===>
SYSTEM ===> SYNC ===> N (Y/N)
SUBSYSTEM ===> WITH HISTORY ===> N (Y/N)
ELEMENT ===> RETAIN SIGNOUT ===> N (Y/N)
TYPE ===> SIGNOUT TO ===>
STAGE ===> ACKNOWLEDGE ELM JUMP ===> N (Y/N)
T - TEST H - HOLD DELETE FROM ELEMENT ===> Y (Y/N
COMMENT ===>
LIST OPTIONS:
DISPLAY LIST ===> Y (Y/N)
WHERE CCID EQ ===>
WHERE PROC GRP EQ ===>
BUILD USING MAP ===> N (Y/N)
---------------------------------------------------------------------------------------------------------------------------------------------
Batch:
 From Primary Options Menu, select 3, BATCH.
 From Batch Options Menu, select 1, BUILD SCL.
 From SCL Generation panel, select 5, MOVE. CA-Endevor displays the Move
Elements panel.
 Refer sec # xx for further steps in BATCH OPTIONS MENU.
 Package:
 To MOVE elements through package refer sec. xx for further steps to continue.
SE Workflow Document Generate
4.8 GENERATE
Description:
Creates an executable form of an element.
Availability:
Generate can be performed in Foreground or Batch.
Foreground:
 From Primary Options Menu, select 2, FOREGROUND.
 From Foreground Options Menu, select 4, GENERATE ELEMENTS panel to execute
the Generate Processor for the element.
 Fill the ENVIRONMENT, STAGE fields where the element is to be generated.
 COPY BACK = N (Default) it does not copy back the element.
 Note: COPY BACK = Y (This option copies the element back from Stage 2, or the
first time it is found up the map, to the FROM stage and generate it at that stage).
 OVERRIDE SIGNOUT = N, (Default). This option does not generate the element if it
is not signed out to you. OVERRIDE SIGNOUT = Y, this is to generate the element,
even if it is not signed out to you.
 PROCESSOR GROUP = *
Note: If you do not provide a processor group name, CA-Endevor selects the
existing group associated with the element if the element exists in Stage 2 or
further up the map, or the default group for the element type.
 OPTION ===> G to generate the element.
----------------- ----------------------------- GENERATE ELEMENTS -----------------------------------------------------------

OPTION ===>
G - Generate element M - Master C - Changes
ENVIRONMENT ===> CCID ===>
SYSTEM ===> COPYBACK ===> N (Y/N)
SUBSYSTEM ===> * OVERRIDE SIGNOUT ===> N (Y/N)
ELEMENT ===> PROCESSOR GROUP ===>
TYPE ===> *
STAGE ===> T – TEST H – HOLD
COMMENT ===>
LIST OPTIONS:
WHERE CCID EQ ===>
---------------------------------------------------------------------------------------------------------------------------------------------
SE Workflow Document Generate
Batch:
 From SCL GENERATION panel, select 4, GENERATE. CA-Endevor displays the
Generate Elements Panel.
SE Workflow Document Delete
4.9 DELETE
Description:
Erases base/delta forms of an element and removes related information from Master
Control File or component list
Availability:
DELETE action can be performed in Foreground or Batch.
Foreground:
 From Primary Options Menu, select 2, FOREGROUND.
 From Foreground Options Menu, select 6, DELETE. CA-Endevor displays the Delete
Elements panel.
 Choose OPTION ===> # to Delete an element
 Specify the ENVIRONMENT, SYSTEM, SUBSYSTEM, ELEMENT and TYPE.
 Make sure that following ACTION OPTIONS are completed.
 CCID is given as per the naming conventions associated with the action.
 OVERRIDE SIGNOUT= N (Default). This option does not delete the
element if it is not signed out to you.
 ONLY COMPONENT = N (Default). This option deletes the element as
well as the element component list.
----------------------------------------------------- DELETE ELEMENTS -----------------------------------------------------------

OPTION ===>
# - Delete element M - Master C - Changes
ENVIRONMENT ===> CCID ===>
SYSTEM ===> OVERRIDE SIGNOUT ===> N (Y/N)
SUBSYSTEM ===> ONLY COMPONENT ===> N (Y/N)
ELEMENT ===>
TYPE ===>
STAGE ===> T - TEST P - PROD
COMMENT ===>
LIST OPTIONS:
WHERE CCID EQ ===>
----------------------------------------------------------------------------------------------------------------------------------------------------
Batch:
 From Batch Options Menu, select 1, BUILD SCL. From the SCL Generation panel,
select 6, DELETE. CA-Endevor displays the Delete Elements panel.
SE Workflow Document Delete
 Refer sec # xx for further steps to continue in BATCH OPTIONS MENU

SE Workflow Document SIGNIN/OUT/OVERRIDE
4.10 SIGN IN/OUT/OVERRIDE

Description:
Signin: Releases the user signout associated with an element. Signin also takes place
automatically when an element is moved back to Production.
Signout: Performed on an element for locking.
Signout Override: Performed on an element, which is already signed out. Persons have
higher Authority can override the sign out.
Availability:
SIGN IN/OUT/OVERRIDE can be performed in Foreground or Batch.
Foreground:
Signin (Following are the steps performed by SEs on an element, which is already signed
out.)
 From Primary Options Menu, select 2, FOREGROUND. From Foreground
Options Menu, select 8, SIGNIN. CA-Endevor displays the Signin Elements
panel.
 Enter ENVIRONMENT, STAGE-ID.
 Choose OPTION ===> SI to sign-in the element
 OVERRIDE SIGNOUT= N (Default). This option does not allow the Signin
action unless the element is already signed out to you.
 OVERRIDE SIGNOUT = Y. This option will sign in the element even if it is not
currently signed out to you. Proper authority is required to specify Y.
 SIGNOUT TO= Y, only when you want to sign out the element. Type the TSO
user ID of the person to whom you want to sign out the element in this field.
SIGNOUT TO = N, when you do not want to sign out the element.
Note: If RETAIN SIGNOUT = Y, you cannot use this option.
The Signin Elements panel is shown next.
---------------------- ------------------------------ SIGNIN ELEMENTS ------------------------------------------------------------

OPTION ===>
SI - Sign-in element M - Master C - Changes
ENVIRONMENT ===> OVERRIDE SIGNOUT ===> N (Y/N)
SYSTEM ===> SIGNOUT TO ===>
SUBSYSTEM ===>
ELEMENT ===>
TYPE ===>
STAGE ===> T - TEST P - PROD
LIST OPTIONS:
WHERE CCID EQ ===>
WHERE USER EQ ===>
----------------------------------------------------------------------------------------------------------------------------------------------
Following are the signout, signout override action options incorporated in various
actions.
Add/Update:
 OVERRIDE SIGNOUT =N (Default).This option does not add/update the element if
it is not signed out to you.
Retrieve:
 SIGNOUT ELEMENT = Y(Default).This option retrieves the element but does not
sign it out to your userID.
 OVERRIDE SIGNOUT= N(Default).This option retrieves the element, even if it is
not signed out to you.
Generate:
 OVERRIDE SIGNOUT= N(Default).This option does not generate the element if it is
not signed out to you. If OVERRIDE SIGNOUT= Y, it generates the element, even if
it is not signed out to you.
Move:
 RETAIN SIGNOUT = N(Default).This option does not retain the current signout.
CA-Endevor signs in the element at the target location. RETAIN SIGNOUT=Y, retain
the signout. CA-Endevor does not sign in the element at the target location.
 SIGNOUT TO= N(Default). If RETAIN SIGNOUT = Y, you cannot use this option.
SIGN IN/OUT/OVERRIDE
Delete:
 OVERRIDE SIGNOUT = N(Default).This option does not delete the element if it is
not signed out to you. If OVERRIDE SIGNOUT =Y, it deletes the element, even if it
is not signed out to you.
Batch:
Sign in:
 From the Primary Options Menu, select 3, BATCH.
 From SCL Generation panel, select 8, SIGNIN. CA-Endevor displays the Signin
Elements panel.
Add/Update:
 From the Primary Options Menu, select 3, BATCH.
 From the Batch Options Menu, select 1, BUILD SCL.
 From the SCL Generation panel, select 2, ADD/UPDATE.
Retrieve:
 From the SCL Generation panel, select 3, RETRIEVE.
Generate:
 From SCL Generation panel, select 4, GENERATE.
Move:
 From SCL Generation panel, select 5, MOVE.
Delete:
 From SCL Generation panel, select 6,DELETE.

Both CCIDs and comments may be required for an action. In batch processing, if
you fail to provide a required CCID or comment, the action fails when submitted.
SE Workflow Document Master Control File
4.11 MASTER CONTROL FILE

Description:
 Master Control file is a VSAM dataset
 MCF contain Management Information
 MCF is defined in C1DEFLTS table
 Every Stage in the Environment has a MCF
 MCF can’t be shared between STAGES and ENVIRONMNETS
How to see MCF details:
 Select 1, DISPLAY in the CA-Endevor Primary Options Menu
 It takes you to DISPLAY OPTIONS MENU. Select 1, ELEMENT. It takes you to
 Display Element/Component list Information
 Enter M to see the MCF Information for an ELEMENET
 Enter Environment, System, Subsystem, Element, Stage, Type to see the Master
Information. If you want to get a list leave the field (except Environment) blank
 It takes you to ELEMENT SELECTION LIST. Enter M before the Element name and
hit ENTER
 It takes you to Element Master panel, where you can see all the information like Last
element modification, CURRENT SOURCE, GENERATE and so. Hit ENTER to see
the Next Panel
 This panel shows information RETRIVE, BASE and from which ENDEVOR
location, Press PF3 to return
SE Workflow Document Standard Change Overview
5 Procedures To Follow
5.1 Standard Change Overview
Following are the steps to be followed when SEs does the actions in Standard
Development.
 Retrieving elements from production to a development library (PDS).
 Making changes to elements in PDS.
 Adding/Updating elements into the test stage.
 Moving elements to hold stage.
 Moving elements from hold stage back to production.
The following diagram shows normal change procedures in the SLC.
TEST PROD
T H F P
PDS
Figure 1
5.2 STANDARD CHANGE PROCEDURE
1. The SE receives the change request.

2. The SE performs the impact analysis to determine the elements to be changed and
which of those elements should be retrieved. For information concerning CA-
Endevor’s capabilities related to impact analysis, see the section titled ‘ Automated
Configuration Manager’ or see the Endevor/MVS ACM manual.
3. The SE RETRIEVEs the appropriate elements to their individual work in progress
PDS. Use the appropriate CCID number and comments. For assistance with CCID
numbers, see the section titled ‘Naming Conventions. If any of the elements are
already signed-out to another SE, see the procedure named ‘Concurrent

Development’.
4. The SE edits the elements in their work in progress PDS or within Pacbase.
Note: If using Pacbase, be sure to update the Endevor pseudo source that you retrieved
earlier. It contains the Pacbase element name, the Pacbase library and the Pacbase
frozen session number.
5. The SE in batch or foreground, ADDs/UPDATEs the elements into the GC01PTST
Environment/TEST Stage using the appropriate CCID number and comments. If
using Pacbase, Endevor will extract the element from Pacbase.
If using Pacbase, the SE should choose not to delete the source element from their
work in progress PDS since an update to this Endevor pseudo source will be
necessary after testing is complete. The update will be to place the Pacbase frozen
session number within these control statements.
If the element you are adding will be compiled, you must add the element using the
Endevor batch options.
For a processor group selection list (to use XPEDITER), enter an asterisk (*) in the
processor group field on the ADD/UPDATE panel. If no processor group is entered
on this panel (for this particular element), the previously used processor group will be
used for existing elements, the default processor group will be used for new elements.
Source programs will be compiled or assembled automatically.
Review the compile or assemble listing in SAM. If batch processing was used to
ADD/UPDATE, the listing(s) will be located in the batch job output. If foreground
processing was used, the listing(s) will be located in the SAM output area, under your
TSO ID. For information on how to see detailed information on program inputs and
outputs, see the section titled: ‘Automated Configuration Manager’ or see the
Endevor/MVS ACM manual.
6. The SE performs Unit Testing. If an error is found and you chose ‘Delete Input
Source’ in step 5, Retrieve the element from the GC01PTST environment, TEST
stage and modify the element in your work in progress PDS or in Pacbase. If you did
NOT choose ‘Delete Input Source’ in step 5, simply modify the element in your work
in progress PDS or Pacbase. In either case, you will need to repeat Steps 5 and 6 as
many times as necessary.
7. Perform this step if using XPEDITER
When testing is complete, an UPDATE will be necessary to Environment GC01PTST,
stage TEST if the element was last ADDed using the XPEDITER processor group.
When performing the UPDATE to compile without XPEDITER, you must choose the
non-XPEDITER processor group since Endevor remembers and reuses the previous
processor group.
8. Perform this step if using Pacbase.
When testing is complete, an UPDATE will be necessary to Environment GC01PTST,
stage TEST if the element is a Pacbase element. This UPDATE will be performed in
order to have Endevor pull the source from the appropriate Pacbase frozen session.
The frozen session number is placed in the Endevor pseudo source located within the
SE’s work in progress PDS.
Additional testing may be necessary in order to validate this new compile/link.
9. The SE BUILDs a Change Package using the appropriate Change Package ID. For
assistance with change package IDs, see the section titled ‘Naming Conventions’.
The Change Package will move the elements from the GC01PTST Environment,
TEST Stage to the GC01PTST Environment, MOFC Stage. You can choose the
elements to include within the Change Package by selecting all elements associated
with one or more CCIDs or you can individually select elements without using the
‘Where CCID EQ’ list command.
Create your packages with a package type of ‘Standard’
Make your packages ‘shareable’ and enable ‘backout’
Fill in an appropriate execution window
Choose the appropriate ENDEVOR actions and elements
10. The SE CASTs the Change Package. If cast errors occur, the SE views the cast report
through the package display option and corrects any problems.
11. After successfully casting the package, the package creator notifies the System
Assurance (SA) group that the change package is ready for approval. The person
creating the Change Package provides the approvers with the change package ID and
related documentation. Valid approvers and the package status can be viewed from
the package display option.
12. The SA group, prior to approving the change package, reviews the actions which will
be performed in the package by using the ‘display action summary option’. If the
approver agrees the appropriate testing has been performed, the correct Endevor
actions are being performed and the date and time when the actions will be performed
is correct, the SA group approves the change package.
Caution: A scheduled batch job may be in place which will execute all approved
packages. Do not approve this package until it is time for it to be executed.
13. The scheduled package execution job or the SA group approver submits the change
package through the Endevor Foreground Package Options panel in order to perform
the actions within the package (MOVE elements from the GC01PTST environment,
TEST stage to the GC01PTST environment, MOFC stage). If the approver executes
the package, the approver chooses option ‘5’ Execute Package option. The approver
then chooses the ‘submit package’ option. Next, choose option ‘E’ (Enter additional
JCL to be included with the job). The JCL to be included is the LLA refresh JCL.
The JCL to be entered should look like this (just one line):
//JS010 EXEC PGM=LLA001,PARM='LLA001I DA'
After entering the JCL press enter and then PF3. Select ‘Include JCL - Y’ and then
option ‘S’ (Submit job for Batch Processing). This will submit a job which will cause
the package to be executed.
14. The Change Package submitter is responsible to review the package execution log to
ensure all processing completed successfully.
15. The Change Package submitter is also responsible to COMMIT the package when
package backout is no longer required for this package. This will clean up the
encrypted backout members in the source and load output libraries. After a COMMIT
is performed, a backout of this package will not be possible.
16. The SA group directs the joint acceptance or Model Office testing. If an error is
found, the SE will RETRIEVE the element from the GC01PTST environment,
MOFC stage and modify the element in their work in progress PDS. The SE will
ADD the element into stage TEST (a compile will be performed). The SE will
perform some level of testing and then request the SA group MOVE the element back
to the MOFC stage. The move of the corrected element(s) (by the SA group) to the
MOFC stage is performed through a package as described in steps 9 through 15.
These steps can be repeated as many times as necessary.
17. When the SA group has proven the production support changes to be problem free,
the SA group BUILDs a Change Package using the appropriate Change Package ID.
For assistance with change package IDs, see the section titled ‘Naming Conventions’.
The Change Package will move the elements from the GC01PTST Environment,
MOFC Stage to the GC01PROD Environment, PROD Stage. You can choose the
 Create your packages with a package type of ‘Standard’
 Make your packages ‘shareable’ and enable ‘backout’
 Fill in an appropriate execution window
 Choose the appropriate ENDEVOR actions and elements
18. The SA group CASTs the Change Package. If cast errors occur, the SA group views
the cast report through the package display option and corrects any problems.
19. After successfully casting the package, the SA group notifies the Production Support
(PS) group that the change package is ready for approval. The SA group provides the
PS group with the change package ID and related documentation. Valid approvers
and the package status can be viewed from the package display option.
20. The PS group, prior to approving the change package, reviews the actions which will
is correct, the PS group approves the change package.
Caution: A scheduled batch job may be in place which will execute all approved
packages. Do not approve this package until it is time for it to be executed.
21. The scheduled package execution job or the PS approver submits the change package
through the Endevor Foreground Package Options panel in order to perform the
actions within the package (MOVE elements from the GC01PTST environment,
MOFC stage to the GC01PROD environment, PROD stage). If the approver executes
the package, the approver chooses option ‘5’ Execute Package option. The approver
then chooses the ‘submit package’ option. Next, choose option ‘E’ (Enter additional
JCL to be included with the job). The JCL to be included is the LLA refresh JCL.
The JCL to be entered should look like this (just one line):
//JS010 EXEC PGM=LLA001,PARM='LLA001I GA'
24. After the change package is moved to production and the production support changes
are shown to be working properly, the SE works with other SEs performing release
development to bring their copies of the changed modules up to date. This is done in
order to prevent regression.
SE Workflow Document Emergency Change Overview
5.3 Emergency Change Overview

Following are the steps to be followed when SEs do the actions in Emergency Fix.
 Retrieving elements from production.

 Making changes to elements
 Adding/Updating elements and moved into the fix stage.
 Moving elements back to production.
The following diagram shows emergency change procedures in the SLC
TEST PROD
T H F P
PDS
5.4 EMERGENCY CHANGE PROCEDURE

1. The SE is contacted with the emergency abend or problem.
2. The SE performs the impact analysis to determine the elements to be changed and
which of those elements should be retrieved. For information concerning Endevor’s
capabilities related to impact analysis, see the section titled ‘ Automated
Configuration Manager’ or see the Endevor/MVS ACM manual.
3. The SE RETRIEVEs the appropriate elements to their individual work in progress
PDS. Use the appropriate CCID number and comments. For assistance with CCID
numbers, see the section titled ‘Naming Conventions. If any of the elements are
already signed-out to another SE, ask the on-site Production Support personnel to use
the Endevor SIGNIN option to SIGNIN the production element. It will then be
available for RETRIEVE by the SE performing the emergency fix. Production
Support must then send an email to both the SE who did have the element signed out
and the emergency fix SE reminding them to speak with each other concerning what
fixes need to be made to the code being developed.
4. The SE edits the elements in their work in progress PDS or within Pacbase.
Note: If using Pacbase, be sure to update the Endevor pseudo source that you
retrieved earlier. It contains the Pacbase element name, the Pacbase library and the
Pacbase frozen session number.
5. The SE in batch or foreground, ADDs/UPDATEs the elements into the GC01PROD
Environment/FIX Stage using the appropriate CCID number and comments. If using
Pacbase, Endevor will extract the element from Pacbase.
If using Pacbase, the SE should choose not to delete the source element from their
work in progress PDS if they would like to take a frozen session number later during
this emergency fix. This is because an update to this Endevor pseudo source will be
necessary after testing is complete. The update will be to place the Pacbase frozen
session number within these control statements.
If the element you are adding will be compiled, you must add the element using the
Endevor batch options.
For a processor group selection list (to use XPEDITER), enter an asterisk (*) in the
processor group field on the ADD/UPDATE panel. If no processor group is entered
on this panel (for this particular element), the previously used processor group will be
used for existing elements, the default processor group will be used for new elements.
Source programs will be compiled or assembled automatically.
Review the compile or assemble listing in SAM. If batch processing was used to
ADD/UPDATE, the listing(s) will be located in the batch job output. If foreground
processing was used, the listing(s) will be located in the SAM output area, under your
TSO ID. For information on how to see detailed information on program inputs and
outputs, see the section titled: ‘Automated Configuration Manager’ or see the
Endevor/MVS ACM manual.
6. The SE performs Unit Testing. If an error is found and you chose ‘Delete Input
Source’ in step 5, Retrieve the element from the GC01PROD environment, FIX stage
and modify the element in your work in progress PDS or in Pacbase. If you did NOT
choose ‘Delete Input Source’ in step 5, simply modify the element in your work in
progress PDS or Pacbase. In either case, you will need to repeat Steps 5 and 6 as
many times as necessary.
7. Perform this step if using XPEDITER
When testing is complete, an UPDATE will be necessary to Environment
GC01PROD, stage FIX if the element was last ADDed using the XPEDITER
processor group. When performing the UPDATE to compile without XPEDITER,
you must choose the non-XPEDITER processor group since Endevor remembers and
reuses the previous processor group.
8. Perform this step if using Pacbase.
When testing is complete, an UPDATE will be necessary to Environment
GC01PROD, stage FIX if the element is a Pacbase element and you wish to take a
Pacbase frozen session. This UPDATE will be performed in order to have Endevor
pull the source from the appropriate Pacbase frozen session. The frozen session
number is placed in the Endevor pseudo source located within the SE’s work in
progress PDS.
Additional testing may be necessary in order to validate this new compile/link.
Note: Emergency fixes should be executed from the PROD stage (and production
libraries) if either of the following conditions are met:
 If the type being fixed is DB2 related
 If the correction is to an on-line module
All other fixes may be executed from the FIX stage (and fix libraries).
If you are moving these elements to the PROD stage, continue with step 9.
9. The SE BUILDs a Change Package using the appropriate Change Package ID. For
assistance with change package IDs, see the section titled ‘Naming Conventions’.
The Change Package will move the elements from the GC01PROD Environment,
FIX Stage to the GC01PROD Environment, PROD Stage. You can choose the
 Create your packages with a package type of ‘Standard’
 Make your packages ‘shareable’ and enable ‘backout’
 Fill in an appropriate execution window

 Choose the appropriate ENDEVOR actions and elements
10. The SE CASTs the Change Package. If cast errors occur, the SE views the cast report
through the package display option and corrects any problems.
11. After successfully casting the package, the SE notifies the Production Support (PS)
group that the change package is ready for approval. The SE provides the PS group
with the change package ID and related documentation. Valid approvers and the
package status can be viewed from the package display option.
12. The PS group, prior to approving the change package, reviews the actions which will
is correct, the PS group approves the change package.
13. The scheduled package execution job or the PS approver submits the change package
through the Endevor Foreground Package Options panel in order to perform the
actions within the package (MOVE elements from the GC01PROD environment, FIX
stage to the GC01PROD environment, PROD stage). If the approver executes the
package, the approver chooses option ‘5’ Execute Package option. The approver then
chooses the ‘submit package’ option. Next, choose option ‘E’ (Enter additional JCL
to be included with the job). The JCL to be included is the LLA refresh JCL. The
JCL to be entered should look like this (just one line):
//JS010 EXEC PGM=LLA001,PARM='LLA001I GA'
16. After the change package is moved to production, the SE directs the abend resolution
with batch scheduling or other operations area.
17. After resolving the abend, the SE works with other SEs performing release
development or standard production support changes to bring their copies of the
changed modules up to date. This is done in order to prevent regression.
SE Workflow Document CA-Endevor Quick-Edit
6 CA-ENDEVOR QUICK-EDIT
What Is CA-Endevor Quick-Edit?

CA-Endevor for MVS Quick-Edit is an ISPF dialog that allows you to create, update,
generate, or display an CA-Endevor for MVS element. CA-Endevor Quick-Edit
simplifies the steps required to change an CA-Endevor element by consolidating several
CA-Endevor functions into a single interaction.
There are two differences between standard CA-Endevor processing and CA-Endevor
Quick-Edit processing:
 The environment name can be wildcard.
 You can edit, generate, or display an element from the same Element
When you select the CA-Endevor Quick-Edit option for an element, CA-Endevor Quick-
Edit does the following:
 Writes a copy of that element to an external data set
 Invokes the ISPF/PDF editor so you can change the element
 Adds or updates the element to CA-Endevor when you finish your changes
CA-Endevor Quick-Edit Panel:
The CA-Endevor Quick-Edit panel appears when you invoke CA-Endevor Quick-Edit
from ISPF. There are two types of commands you can enter from this panel:
 Dialog Commands. These commands affect the dialog environment.
 Element Options. These commands manipulate an CA-Endevor element.
The CA-Endevor Quick-Edit panel
------------------------------------------- -------------------------- CA-Endevor Quick-Edit -------------------------------------------------------------
Command ===> ________________________________________________________
Dialog Commands:
D Dialog Defaults AO Action Options
Element Options:
blank Element list CR Create Element # Delete S Summary B Browse
E Edit Element G Generate Element O Move M Masters C Changes
LL List Listing LO List Outputs H History
CA-Endevor Location: List Options:
Environment.. Where CCID is............... ____________
System....... Where Processor Group is.... ________
Subsystem.... Build Using Map............. N (Y/N)
Element...... __________ Return First Found.......... Y (Y/N)
Type......... Display System/Subsys List.. N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
Override Signout............. N (Y/N)
The Action Options panel displays when you select option AO, Action Options from the
CA-Endevor Quick-Edit panel. You use this panel to further define the following action
requests:
 Move
 Generate
 Delete
6.1 MOVE
Use the MOVE option to move an element from one CA-Endevor inventory location to
the next location along the map route. The MOVE option is available from the CA-
Endevor Quick-Edit panel and the Element Selection List panel.
To move an element, type O in:
 The Command field on the CA-Endevor Quick-Edit panel.
 The Selection field next to the desired element on the Element Selection List panel.
Press ENTER.
When MOVE action is used for the first time, make note of the following information:
The Move action moves elements from one inventory location (environment, stage) to the
next location on a map route.
 You can move elements either with history or without history by specifying the With
History option on the Actions Options panel (see the section entitled "Action Options
Panel").
 You can only move elements from one environment to another if the elements start in
Stage 2 of the source environment. So, for example, to move an element from Stage 1
of the Development environment into Stage 1 of the QA environment, you have to
move the element to Stage 2 in Development and then move it into Stage 1 in QA.
 You can move elements in foreground, or in batch by specifying which Move action
mode on the Actions Options panel.
 Use the Action Options panel to further define the type of move processing you want
to perform. See the section entitled "Action Options Panel" for information on
available Move action options.
6.2 GENERATE
To generate an element, type G in the appropriate place:
 On the COMMAND line of the CA-Endevor Quick-Edit panel
 In the SELECTION field next to the element(s) desired, on the Element Selection List
Press ENTER.
When performing GENERATE ELEMENT option make note of the following

information:
 If you generate an element that is not at the entry stage and the BUILD USING MAP
field is set to Y, CA-Endevor Quick-Edit copies the element back to the entry stage
before invoking the generate processor. You cannot bypass the copyback operation.
Note: If you generate an element from a stage up the map and that element exists at
the entry stage, CA-Endevor Quick-Edit generates the element found at the entry
stage--not the element originally selected.
 Signout processing validation for the CA-Endevor Quick-Edit GENERATE
ELEMENT option is the same as for the standard CA-Endevor GENERATE action.
That is, you must have proper signout authority. If you do not have the authority to
sign the element out or to override a signout, you will not be able to continue.
 The Last Action CCID and Last Action Comment are updated, as appropriate, when
the generate processor is executed.
6.3 DELETE
Use the Delete option to delete elements and/or an element component list from CA-
Endevor. The Delete option is available from the CA-Endevor Quick-Edit panel and
Element Selection List panel.
To delete an element, type #, in:
 The Command field on the CA-Endevor Quick-Edit panel.
 The Selection field next to the desired element on the Element Selection List panel.
Press ENTER.
When performing DELETE action makes note of the following information:
 Use the Delete action to delete all levels of an element, any associated processor
outputs from either stage or, if you are using the CA-Endevor Automated
Configuration Manager (ACM), the component list for the element. If you are using
ACM, you can also elect to delete only the component list for an element.
 You can delete elements in foreground, or in batch by specifying the Delete action
mode on the Actions Options panel.
 Use the Action Options panel to further define the type of delete processing you want
to perform.
SE Workflow Document Parallel Development Manager
7 Parallel Development Manager

The Parallel Development Manager is a powerful tool to address the problems inherent in
the three steps of parallel development projects. This can help in analyzing the
complexity of parallel development projects, consolidate changes and identity conflicts
more quickly and above all automate the integration process. Some reports can also be
generated based on one or more work in process files.
CA-PDM process involves three steps

1. Building a WIP file
2. Editing a WIP file
3. Merging a WIP file
7.1 Building a WIP file
 The first step in using the Parallel Development Manager is to build the Work-in-
Process (WIP) file and analyze the results. The WIP file is produced by comparing
the Root (or base) file against one or two Derivation (modified) files. The WIP file
combines the Root file and every insertion and deletion that has been made to the
Derivation file(s), noting conflicting changes i.e. when building the WIP file, CA-
PDM uses the Derivation 1 and Derivation 2 files to determine which lines to include
in the WIP file.
 The build WIP process analyzes the input files, identifies differences and conflicts,
and creates statistics and reports. Once the WIP is edited to resolve conflicts, CA-
PDM can create an integrated output file by inserting and deleting lines based on the
annotations in the WIP file, and write the integrated output file to a user specified
location.
7.1.1 Structure of a WIP file
A WIP file contains
 Header
 Annocations
 Rest of WIP file
7.2 Editing a WIP file

Once the WIP File has been built, you can edit it using the CA-PDM Edit WIP function.
The (edited) WIP File will be used as input to the Merge process, the result of which is an
output file that can be added back into CA-Endevor, stored in a source repository, or
serve as input to a compiler.
To edit a WIP file, do the following:
1. Type 2 (EDIT WIP) in the OPTION field on the CA-Parallel Development Manager -
Primary Option Menu
2. Press ENTER to display the Edit - Entry Panel. Specify the WIP library and the
member you want to edit on this panel, using standard ISPF conventions.
3. When you have specified the member you want to edit, press ENTER to display an
ISPF/PDF edit panel.
4. CA-PDM invokes the standard ISPF/PDF editor. All ISPF/PDF edit commands are
available. Resolve the conflicts in the WIP File, using these ISPF/PDF editing tools.
When you have finished editing the WIP File, press PF3; the Edit – Entry Panel
reappears. The message Member Saved appears in the upper right-hand corner of the
screen. This message indicates that the edited WIP member has been saved. Press PF3 to
return to the CA-Parallel Development Manager - Primary Option Menu.
7.3 Merging a WIP file

The next step is merging the edited WIP File into an output source file, which can then be
added back into CA-Endevor, stored in the appropriate source repository, or compiled.
CA-PDM creates a merge output file Automatically, during the build WIP process, when
you specify AUTOMATICALLY MERGE=Y on the WIP Specification Panel and there
are no conflicts in the WIP file.
Upon request, by invoking option 3 on the CA-Parallel Development Manager - Primary
Options Menu. To merge a WIP File, do the following:
1. Type 3 in the Command field on the CA-Parallel Development Manager Primary
Option Menu, and specify the appropriate processing mode in the PROCESSING
MODE: FOREGROUND OR BATCH field--F or B. Press ENTER to display the

Merge Work In Process File screen.
2. Define the WIP file that you want to merge, using standard ISPF conventions.
When specifying a WIP member on this panel, you can:
 Enter an explicit member name, to merge only that member.
 Enter an asterisk (*) to merge all members in the library.
 Leave the MEMBER field blank or enter a name mask to select a member(s) from the
Merge Output Member Selection List.
3. When you press ENTER after typing in the appropriate information, the Merge
Output Specification Panel is returned.
4. Specify the library and member to which you want CA-PDM to write the merge
output file, using standard ISPF conventions. Press ENTER when you have typed in
all pertinent data.
5. When specifying the target member name, you can:
6. Enter an explicit member name, to create a merged member in the output data set.
7. Leave the field blank to select member names from the Merge Output Selection List.
8. Provide an overlay mask to be applied to all member names.
9. If you specify an explicit member name or entered an asterisk for all members, the
Merge process is immediately invoked. When processing is complete, the Merge
Work In Process File screen is returned with the message MERGE COMPLETE in
the upper right corner.
10. This message indicates that the WIP File(s) specified on the screen was successfully
merged into the output source file specified on the Merge Output Specification Panel.
11. If the MEMBER field is left blank or provided a name mask, then select one or more
members from the Merge Output Member Selection List, You complete the merge
process from this selection list.
SE Workflow Document Automated Configuration Management
8 Automated Configuration Management

A typical software inventory is comprised of numerous application programs and the
components - the common code (such as COBOL copybooks, Assembler macros, and
CALLed subroutines) - which make up those programs. The discipline of managing the
interrelationships between programs and their associated components is called automated
configuration management.
CA-Endevor ACM can be divided into three distinct areas:
1. data collection,
2. data storage, and
3. software configuration analysis and management.
8.1 Data Collection

Data Collection begins when you invoke CA-Endevor ACM through the
MONITOR=COMPONENTS parameter in an CA-Endevor processor. With this
parameter, you specify the libraries and data sets that are to be monitored automatically
by CA-Endevor ACM. Then, the Component Monitor tracks all change activity and
program-component relationships for the data sets you earmarked for monitoring.
8.2 Data Storage

CA-Endevor ACM produces a component list during program translation (compilation),
thus beginning the data storage process. The component list is an internal data structure
which assembles all program-component information, along with an audit stamp or
"footprint" for each component, at the time of each compile. component list "levels"
(differences in component lists from one translation to the next) are stored in CA-
Endevor base/delta format. The component list provides a "snapshot" of a program at
compilation - identifying an element's components, where they originated, their version
and level, and the output created as the result of the translation.
8.3 Software Configuration Analysis and Management

Through the component list, it is possible to initiate CA-Endevor actions and make online
inquiries. When viewed over time, component lists provide a historical audit trail of
component changes which serves as the
foundation for all software configuration analysis and management activities, including:
 Analyzing system behavior
 Propagating a component change to all affected programs
 Validating a system for consistent use of components
 Recreating past program versions
 Moving related source components during promotion to production
CA-Endevor ACM functions can be separated into the following three categories:
 Monitoring and Collecting Data--performed automatically by the CA-Endevor ACM
Component Monitor
 Storing and Viewing Configuration Information--capabilities provided by CA-
Endevor ACM through Component Lists and base/delta technology
 Analyzing and Managing Configuration Information--performed by users, with
configuration information automatically monitored and stored by CA-Endevor ACM.
8.4 The Component Monitor

The CA-Endevor ACM Component Monitor is invoked by adding a special
MONITOR=COMPONENTS" keyword to DD statements in a CA-Endevor processor.
CA-Endevor ACM has been built to be compatible with source translators (COBOL
compilers, assemblers, PL/1 compilers, and linkage editors) without modification. These
translators resolve element-to-component relationships by reading in components--called
"input components"—from specific libraries. Utilities such as the linkage editor,
CONLIST, create and write members--called "output components"--to various libraries.
The CA-Endevor ACM Component Monitor automatically and transparently captures
relationships by monitoring selected library data sets. You select the libraries you want
monitored by CA-Endevor ACM through a processor.
The information captured by the Component Monitor includes the step name, DD
statement, volume, data set name, PDS or PDS/E directory and footprint information (if it
exists).
8.5 Monitoring Input Components

Typical input components would be INCLUDE object modules, load modules, program
objects, copybooks, and CALLed modules. COBOL compilers, for example, read in
copybooks from a SYSLIB DD statement. Thus, for each data set in the SYSLIB
concatenation, you would code MONITOR=COMPONENTS, as shown in the following
example:
//SYSLIB DD
DSN=BST.C1DEMO.COPYLIB1,DISP=SHR,MONITOR=COMPONENTS
// DD DSN=BST.C1DEMO.COPYLIB2,DISP=SHR,MONITOR=COMPONENTS
8.6 Monitoring Output Components

Typical outputs would be load modules, program objects, object decks, and listings. The
linkage editor, for example, writes load modules to a SYSLMOD DD statement. For
each output data set you want to monitor, code MONITOR=COMPONENTS, as shown
in the following example:
//SYSLMOD DD
DSN=BST.C1DEMO.LOADLIB1,DISP=SHR,MONITOR=COMPONENTS
8.7 Monitoring Components in a Generate Processor

Any data set defined to a program within a processor can be monitored by the
Component Monitor. The following programs are typically used in a generate processor.
This sampling represents DD statements containing data sets that would normally warrant
monitoring.
 CONWRITE
 IKFCBL00
 IEWL
 CONLIST
8.8 Monitoring Components in a Move Processor

Typically, the move processor is coded to perform two generic functions:
1. to perform a translation (compile and link-edit), and
2. to move a load module and any other Stage 1 members created by the Stage 1
generate processor.
 If you code a move processor to perform a translation (for example, compile, link-
edit), code MONITOR=COMPONENTS.
 If you code a move processor in order to move load modules, listings, etc. from
Stage 1 to Stage 2, you might also want to move the current (version/level) of the
Component List. This can be done using a special processor utility BC1PMVCL,
which is provided with CA-Endevor ACM. To execute this program, code a step in
the CA-Endevor move processor that specifies the EXEC statement with a
MAXRC=0, as illustrated below:
//MOVE EXEC PGM=BC1PMVCL,MAXRC=0

Now when the element in Stage 1 is moved to Stage 2, its corresponding Component List
(containing all the element-to-component relationships) will also be moved to Stage 2.
8.9 Component List

The CA-Endevor ACM component list comprises six internal component categories:
element information, processor information, symbol information, input components,
output components and related data. Each of these component categories provides an
essential piece of the in-depth information needed to analyze and manage software
configurations.
 Element Information--the CA-Endevor source for which an CA-Endevor processor
is being executed. It tells you what the originating CA-Endevor element source was
when the component list was created.
 Processor Information--the CA-Endevor processor that is being executed for this
particular element. It contains the MONITOR=COMPONENTS keyword for specific
data sets, and tells you the specific CA-Endevor processor used when the component
list was created.
 Symbol Information--the symbolics that have been defined by the user for this
processor. It tells you the symbolic, the value that will be substituted for it when the
processor is run, and where that value has been defined -- either directly in the PROC
statement of the processor or as overridden through the Processor Group Symbolics
panel.
 Input Components--the members in the monitored data sets which are read by
programs (such as the compiler or linkage editor) in the CA-Endevor processor when
it collects components to build composite modules. It tells you the related "pieces" of
the element and where they came from.
 Output Components--the monitored data sets which are written to by programs
(such as the linkage editors or CA-Endevor utilities) when composite modules are
created. It tells you the members created during processor execution.
SE Workflow Document Common Errors and their Solutions
9 Common Errors and their Solutions

DURING RETRIEVAL PROCESS
EM 01. C1G0167E
ERROR MESSAGE :
FINARP01 IS NOT AVAILABLE. IT HAS BEEN PREVIOUSLY SIGNED OUT BY TETRN04
WHY THIS MESSAGE IS ISSUED AND HOW DO YOU FIX IT :
Sol.
THIS MESSAGE IS ISSUED BECAUSE USER TETRN04 HAS RETRIEVED
FINARP01 WITH SIGNOUT OPTION ‘Y’.
PROBABLE SOLUTIONS :
1) Call user tetrn04 and ask him to sign in finarp01
2) If unable to reach him use override signout option in case it is emergency.
DURING RETRIEVAL PROCESS
EM02. C1G0126E
ERROR MESSAGE :
NO REPLACE SPECIFIED AND FINARP01 WAS FOUND IN
TETRN01.PDS.WIP
WHY THIS MESSAGE IS ISSUED AND HOW DO YOU FIX IT:
Sol.
Cause: A Retrieve request for element FINARP01 found a member with that name
already present in the data set TETRN01.PDS.WIP.
To fix: Re-execute the request, using a different data set as the destination, or allow
the present element FINARP01 to be replaced.
DURING ADD/UPDATE PROCESS
EM03. C1G0168E
ERROR MESSAGE :
FINAPP02 CANNOT BE ADDED BECAUSE IT IS NOT IN "SIGNED-OUT"
STATUS
Sol.
Cause: An Add was attempted for element FINAPP02, but was rejected because the
element FINAPP02 exists elsewhere on the map, but has not been signed out.
To Fix: Retrieve the element, then resubmit the Add request.
DURING ADD/UPDATE PROCESS
EM04. C1G0024E
ERROR MESSAGE :
ELEMENT FINARP01 ALREADY PRESENT AT UT:
Sol.
Cause: An Add request specified for the element FINARP01 is already present in
UT stage.
To Fix: Review the action request. Verify that the element specified for an Add
request is the correct one, and modify the request if appropriate. If a different action
was intended, correct the request and resubmit.
DURING MOVE PROCESS
EM05. ERROR MESSAGE : C1G0148E

THE LAST GENERATE PROCESSOR EXECUTION AT UT FAILED.
MOVE CANNOT OCCUR
Sol.
Cause: During Move the processor return code of the most recent generate
processor was greater than the maximum acceptable return code specified in the
processor definition. The "processor failed" flag was
set.
To Fix: Submit a Generate request for the element. Ensure that it has successfully
completed before moving or transferring the element.
DURING MOVE
EM06.
ERROR MESSAGE :
THE MOVE ACTION CANNOT BE PERFORMED - PROC GRP
EXPEDITOR NOT DEFI NED FOR TYPE COBOL AT STG Q
Sol.
Cause : Processor group EXPEDITOR defined by the user for TYPE COBOL is not
available.
To Fix: Check the available Processor group for TYPE COBOL and give the exact
available processor.
DURING MOVE
EM07. FPVL003E
ERROR MESSAGE:
NO FOOTPRINT MATCH AVAILABLE ANYWHERE
WHY THIS MESSAGE IS ISSUED AND HOW DO YOU FIX IT?
Sol.
Cause: No Master Control File records for the element matches the location and
event information in the footprint. If of the other related components of the elements
are not foot printed, that may cause this problem.
To Fix: Compile all the related components to get footprint and redo the process.
Check the Environment, Site ID, Stage-ID, System, Sub system, Type what you
specified.
DURING ADD
EM08. C1U0900E
ERROR MESSAGE:
EXIT 2 -ACTION DENIED - INVENTORY AREA FINANCE -ACCTREC
-COBOL 2 PACKAGE UPDATE ONLY
Sol.
Cause: The specified inventory area for which an action is being requested has an
approver group relationship so action denied.
To Fix: Delete the relationship between the inventory area and the approver group, or
use package processing to update the inventory area.
DURING MOVE
EM09. CIX0104E
ERROR MESSAGE :
JUMP OPTION IS REQUIRED FOR SYSTEM GMBRRIN TO BYPASS THE
ELEMENT IN THE PHYSICAL PATH
WHY THIS MESSAGE IS ISSUED AND HOW DO YOU FIX IT ?
Sol:
Cause: The system named in the message requires that move actions be specified
with JUMP=Y when CA- Endevor has encountered a version of the element(s) to be
moved in a mapped environment but not on the map itself.
To Fix: Resubmit the move request with JUMP=Y.
DURING CASTING OF PACKAGE
EM10. PKMR403E
ERROR MESSAGE:
TARGET ON MOVE ACTION DOES NOT EXIST FROM ENV:DEMO PROD
SYS FINANCE STG P
Sol:
Cause: No target location exists for the environment, system, subsystem, type, and
stage specification in the message.
To Fix: Make sure the from location is specified correctly, then resubmit the move
request.
DURING EXECUTION OF PACKAGE
EM11. PKMR516E
ERROR MESSAGE:
INTEGRITY ERROR:
FINARP01 HAS BEEN MODIFIED SINCE THE PACKAGE WAS CAST -
TETRN01.PDS.WIP
Sol:
Cause: The data set in the message has been modified since the package was cast.
To Fix: Reset, recast, and reprove the package.
DURING CASTING
EM12: PKMR509E
ERROR MESSAGE :
STMT#2 ELM HEADER01 NOT FOUND AT
DEMOTEST/FINANCE/ACCTREC/COPYBOOK/QA
STMT#3 ELM PAGEHDR NOT FOUND AT
DEMOTEST/FINANCE/ACCTREC/COPYBOOK/QA
STMT#1 ELM FINARPJK NOT FOUND AT
DEMOTEST/FINANCE/ACCTREC/COBOL/QA
Sol:
Cause: The element specified in the statement identified in the message was not
found at the specified CA-Endevor location.
To Fix: Ensure that the element and/or CA-Endevor location is specified correctly.
DURING RETRIEVAL/GENERATE
EM13. C1G0030E
ERROR MESSAGE:
C1G0030E UNABLE TO VERIFY FOOTPRINT FOR ELEMENT FINARP12
IN THE ELEMENT BASE L
C1G0030I AT LOCATION: ENV: DEMOPROD, STG: P, SYS: FINANCE,

SBS: ACCTREC, TY
C1G0014E UDSAA.WAYCM.D37C.PROD.BASE(ELSV8SCT) NOT FOUND
C1G0030E UNABLE TO VERIFY FOOTPRINT FOR ELEMENT FINARP12
IN THE ELEMENT DELTA
C1G0030I AT LOCATION: ENV: DEMOPROD, STG: P, SYS: FINANCE,
SBS: ACCTREC, TY
C1G0014E UDSAA.WAYCM.D37C.PROD.DELTA(ELSV8SEO) NOT FOUND
C1G0277E RETRIEVE PROCESSING TERMINATED BECAUSE OF THE
PREVIOUS ERROR
Sol:
Cause: One of the following members was not found while attempting to obtain the
footprint from the library: element base; element delta; component base; component
delta; processor output.
To Fix: If the error is associated with a processor output, regenerate the element.
If the error is associated with an element, delete the element and restore it from a
prior unload tape or archive file.
If the error is associated with a component list, use the Delete action with ONLY
COMPONENT option to delete the component list base and delta, then regenerate
the element to recreate the component list.
Cause: The member name in a user data set ELSV8SCT could not be found.
To Fix: Verify the request, ensuring that the element name was correctly specified. If
an Add or Update was requested and the TO/FROM option used, check that the
TO/FROM member name was specified correctly. Resubmit the request.
Cause: An unrecoverable error occurred while performing the action identified.
CA-Endevor stopped processing the action.
To Fix: See C1MSGS1 output for any other E or S level messages and take the
actions necessary to correct that error.
PROCESSOR RELATED ERRORS MESSAGES
DURING ADD/UPDATE/GENERATE PROCESS
EM14. C1G0129E
ERROR MESSAGE:
STEP COMPILE RC (0012) EXCEEDS THE MAX RC (0004) FOR THE
PROCESSOR STEP
PROCESSOR C2XXXXGW EXECUTION COMPLETED, HIGHEST
PROCESSOR STEP RC WAS 0012
Sol:
Cause: The named step in a processor resulted in a return code (RC 0012) that is
greater than the maximum acceptable return code (RC 0004) for that step in the
processor definition. CA-Endevor set a "processor failed flag."
To Fix: Examine the processor output and messages to determine the cause of the
error. Correct the error conditions and resubmit the request.
DURING ADD/UPDATE/GENERATE PROCESS
EM15. C1G0129E
ERROR MESSAGE :
CPXUPTSM MODULE NOT FOUND IN STEP COMPILE
Sol:
Cause: The module CPXUPTSM was not found, because of that the step in a
processor resulted in a return code that is greater than the maximum acceptable
return code for that step in the processor definition. CA-Endevor set a "processor
failed flag."
error. Correct the error condition and resubmit the request.
DURING GENERATE PROCESS
EM16: C1G0129E
ERROR MESSAGE :
STEP LINK RC (0008) EXCEEDS THE MAX RC (0004) FOR THE
PROCESSOR STEP
Sol:
Cause: The Link step in a processor resulted in a return code (RC 0008) is greater
than the maximum acceptable return code ( RC 0004) in the processor definition.
CA-Endevor set a "processor failed flag."
error. Correct the error conditions and resubmit the request.
DURING EXECUTION OF PACKAGE
EM17. SMGR006E
ERROR MESSAGE :
ERROR READING DELTA MEMBER - EXPECTED DELTA CONTROL
RECORD – BADCNTL
Sol:
Cause: Internal error.
To Fix: Contact CA-Endevor Technical Support.
SE Workflow Document Frequently Asked Questions
10 Frequently Asked Questions
Q1. WHEN DO COMPILE OCCUR?

Sol:
 When ADDing into any stage-1 a Compile or Generate will be performed
 When ADD to stage-T (Unit testing area)
 When we ADD to stage-F (Fixing area)
 In addition, when a MOVE is performed (in the processor group definition is set to G
then) will takes place.
Q2. WHERE IS MY COMPILE LISTING?
Sol:
 If executing actions in foreground, listings are written to SAM and are shown under
your TSO id output
 If executing actions in batch, listings are written to your job output, also available in
SAM
Q3. Are the level number assigned to component list are the same as of the level number
of elements?
Sol. The level numbers assigned to a component list (component levels) are independent
of the level numbers assigned to an element (element levels). Since an element may be
recompiled many times due to copy or macro changes, there may be more component
levels than element levels. In addition, monitoring may be initiated at any time and at
any element level.
SE Workflow Document Appendix
11 Appendix
11.1 Definitions
Root:
The base program with which programmers are working. Derivation 1 and Derivation 2
files are derived from this program. y
Derivation 1:
A modified copy of the Root
Derivation 2:
Another modified copy of the Root.
Work-In-Process (WIP):
The file built when CA-PDM compares the Root and one or two Derivations. The WIP
File is an annotated intermediate file that identifies the insertions and deletions made
individually by the Derivations, as well as the insertions and deletions common to both.
Potential insert conflicts are also identified.
Merge output file:
An output file created by CA-PDM using the WIP File as input. When the Merge Output
File is created, the annotations from the WIP File are removed, and all insertions and
deletions are performed.
11.2 Naming Conventions

Change Control Identifier (CCID)
The CCID number should identify the change request number in some way. Not all sites
have the same format for the CR number. For example, the change requests are in the
format of XXX9999999 where XXX denotes the sub-system and 9999999 identifies the
request number (ex. VSX0000722).
The naming conventions for change packages should also be broad enough to apply to all
sites. This can be a combination of the following items in the name: the sub-system,
earliest date to be executed, and a user defined change identifier. The change identifier
would be any combinations of characters the developer feels describes the package. Most
of our change packages include multiple change requests bundled for a particular release.
An example of this name might be VSX990108-BP984. VSX denotes the sub-system,
990108 means that the package cannot be executed until January 8, 1999, and the
remaining characters describe the package.
11.3 Some Facts Related to BARS Applications

BARS APPLICATION has the system GMBR and the following subsystems and their
respective types:
SUBSYSTEM : RAR
TYPE : JCL
SUBSYSTEM : RCM
TYPES : REXX, CZPB, FCNB, SYSIN, PROC, JCL
SUBSYSTEM : RIN
TYPES : SYSIN, JCL
SUBSYSTEM : RIT
TYPES : SYSIN, PROC
SUBSYSTEM : RNV
TYPES : SYSIN, JCL
The following actions are performed both in standard and emergency mode in BARS
APPLICATION.
 RERIEVE ( In standard mode)
Description : Retrieve an element from PROD
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
Libraries to verify: WZWDW8.PDS.LIB
 EDIT
Description : Make changes as required
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
 ADD TO TEST
Description : Add an element to TEST
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
Libraries to verify: PGMBR.ALLCM.TEST.PROC
WZWDW8.PDS.LIB
 MOVE TO HOLD
Description : Move element from TEST to HOLD
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
Libraries to verify: PGMBR.ALLCM.HOLD.PROC
PGMBR.ALLCM.TEST.PROC
 MOVE TO PROD
Description : Move element from HOLD to PROD
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
Libraries to verify: PGMBR.ALLCM.PROD.PROC
PGMBR.ALLCM.HOLD.PROC
 RERIEVE ( In emergency mode)
Description : Retrieve an element from PROD
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
 EDIT ( In emergency mode)
Description : Make changes as required
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
 ADD TO FIX ( In emergency mode)
Description : Add element to FIX
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
Libraries to verify: PGMBR.ALLCM.FIX.PROC
WZWDW8.PDS.LIB
 MOVE TO PROD ( In emergency mode)
Description : MOVE element from FIX to PROD
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
Libraries to verify: PGMBR.ALLCM.PROD.PROC
PGMBR.ALLCM.FIX.PROC
 DELETE
Description : DELETE element from PROD
System : GMBR
Subsystem : RCM
Type : PROC
Element : RCMAELIT
Libraries to verify: PGMBR.ALLCM.DELE.PROC
PGMBR.ALLCM.PROD.PROC

Endeavor Workflow

Uploaded by

Copyright:

Available Formats

Endeavor Workflow

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Endeavor Workflow

Uploaded by

Copyright:

Available Formats

CA-ENDEVOR SE WORKFLOWS

4 COMMONLY USED COMMANDS/ACTIONS......................................................5

10 FREQUENTLY ASKED QUESTIONS...................................................................62

CA-Endevor is an integrated set of management tools that is used to automate, control,

 The time-consuming, resource-intensive, and error-prone process of manually

2.1 Environments and Stages

TEST HOLD FIX PROD

3 Roles and Responsibilities

4 Commonly used Commands/Actions

4.1 FOREGROUND AND BATCH PROCESSING

-------------------------- FOREGROUND OPTIONS MENU --------------------------

BATCH ----------------------- BATCH OPTIONS MENU -----------------------------

4.2 SOFTWARE CONTROL LANGAGE

4.2.1 SCL Generation

-------------------------------------- SCL GENERATION ----------------------------------------

4.2.2 EDIT SCL

4.2.3 VALIDATING SCL

 To validate the SCL, select 4, VALIDATE in the BATCH OPTION MENU

4.2.4 ADDITIONAL JCL

4.2.5 SUBMITTING THE JOB

 Select 5 in the CA-Endevor Primary Option Menu, It takes you to ‘Package

---------------------- Package Foreground Options Menu ---------------------

----------------------------------- CREATE/MODIFY PACKAGE -------------------------------------

CAST---------------------------------------- CAST PACKAGE -------------------------------------------------

EXECUTE ---------------- EXECUTE/SUBMIT PACKAGE -----------------------------

 To COMMIT the Package, it must be in ‘EXECUTED’ status

COMMIT ------------------------- COMMIT PACKAGE ----------------------------------

------------------------------------------ RETRIEVE ELEMENTS ----------------------------------------------

ELEMENT DISPLAY OPTIONS:

4.5 DISPLAY ELEMENTS

How to display elements?

i. From the CA-Endevor Primary Option Menu.

---------------------------------- Display Elements/Component Lists --------------------------------------

4.6 ADD /UPDATE

---------------------------------------- ADD /UPDATE ELEMENTS ----------------------------------------

------------------------------------------------------- MOVE ELEMENTS ---------------------------------------------------

----------------- ----------------------------- GENERATE ELEMENTS -----------------------------------------------------------

----------------------------------------------------- DELETE ELEMENTS -----------------------------------------------------------

 Refer sec # xx for further steps to continue in BATCH OPTIONS MENU

4.10 SIGN IN/OUT/OVERRIDE

---------------------- ------------------------------ SIGNIN ELEMENTS ------------------------------------------------------------

 Refer sec # xx for further steps to continue in BATCH OPTIONS MENU.

4.11 MASTER CONTROL FILE

The following diagram shows normal change procedures in the SLC.

5.2 STANDARD CHANGE PROCEDURE

1. The SE receives the change request.

already signed-out to another SE, see the procedure named ‘Concurrent

5.3 Emergency Change Overview

 Retrieving elements from production.

5.4 EMERGENCY CHANGE PROCEDURE

 Fill in an appropriate execution window

What Is CA-Endevor Quick-Edit?

When performing GENERATE ELEMENT option make note of the following

7 Parallel Development Manager

CA-PDM process involves three steps

7.1 Building a WIP file

7.2 Editing a WIP file

7.3 Merging a WIP file

MODE: FOREGROUND OR BATCH field--F or B. Press ENTER to display the