May 21, 2001

ENDEVOR FAQ

Version 1.10

COPY IF PRINTED
Infosys Technologies Ltd. Endevor

REVISION HISTORY:

Ver. Date Author Description Verified By Verified Date

Rev.
1.00 May-21-2001 Jayesh G Original Ravi K Bandi Jun-08-2001
1.10 Jun-11-2001 Jayesh G Incorporated suggestions Ravi K Bandi Jun-11-2001

AETSRRC Ver 1.10 Page 2 of 10

Infosys Technologies Ltd. Endevor

Overview:

This document provides information about ENDEVOR concepts and functions in the
form of questions and answers. ENDEVOR is a version control package provided by
Computer Associates. It is an integrated set of management tools used to automate,
control, and monitor your applications development process. ENDEVOR runs under
MVS, within the TSO/ISPF environment, and in batch.

DISPLAY Action:

1. What are the different command line options available in Display

Elements/Component Lists screen (= endevor; 3; 1; 1)?
Command Line Option Description Of Display
S Summary of Levels panel Contains
summary information pertaining to
each source element level.

From this panel you can further display

using options B, C, and H.
SX Summary of Levels panel - Contains
summary information pertaining to the
component list of each source element
level.

From this panel you can further display

using options BX, CX, and HX.
B Element Browse panel - Shows all of
the statements in the current level of the
element and the level at which each
statement was inserted.
BX Element Browse Component list panel -
Shows all the input and output
components (i.e., input = copy records,
includes, etc.), used in the creation of
the output, (output = object module,
load, etc.) for each source element. It
also shows the libraries each input
component came from and the libraries
to which the output component(s) were
written.

**Note: The component list is very

beneficial and should be used
as a primary information
source in problem resolution.
C Element Change panel - Shows all

AETSRRC Ver 1.10 Page 3 of 10

Infosys Technologies Ltd. Endevor

source lines inserted into and deleted

from the current level of the element.
CX Element Change Component list panel -
Shows all source lines inserted into and
deleted from the component list of the
current level of the element.
H Element History panel - Shows all of
the source lines inserted into and
deleted from the element from base
level (00) to the current level and the
level at which each insert/delete was
made.
HX Element History panel - shows all of
the source lines inserted into and
deleted from the element component
list from base level (00) to the current
component list level and the level at
which each insert/delete was made.
M Element Master panel - Shows master
(who, what, when) information for the
element.
Blank List of elements matching the criteria
entered on the screen.

Once the element list is displayed, other

applicable prefix commands may be
used.
Once the command is selected, and the Enter key is hit, the
information about the element / component is displayed.

2. How do I know which id has signed out an element?

In the display screen described in the above question, give M as the command line
option. On hitting Enter key, Element Master screen is displayed. This option provides
the SIGNOUT STATUS information. If the element is not signed out, there will only be
spaces after SIGNOUT ID in the screen. If any element is in signed-out status, the ID
which has signed out the element will be displayed against SIGNOUT ID.

In addition to SIGNOUT status, this option also provides the Last Modification Data.

AETSRRC Ver 1.10 Page 4 of 10

Infosys Technologies Ltd. Endevor

RETRIEVE Action:

1. How do I retrieve a prior level of an element?

Navigate to the Retrieve Elements Screen (= endevor;3;2;2). In the screen, type the
information asked for and leave the command line blank. Hitting Enter will bring up the
Element Selection List Screen. Type an S next to the element to display all levels.
Press Enter. This will bring up the Summary Of Levels Screen. Type an R next to the
level you want to retrieve. On pressing Enter, the corresponding level of the element will
be retrieved to the PDS.

ADD Action:
1. Sometimes when I am adding an element, the Endevor Return Code is 4 even
when the Processor Return Code is zero. Is it ok?
Yes, it is. Processor Return Code is the status of the Processor actions such as Compiling
or Linking. Endevor Return Code is the status of the Endevor action ADD. An Endevor
Return Code of 4 is valid and it is set when Endevor does not detect any source changes.
2. What are the checks that should be performed before adding a program?
Ensure that you are adding the program from the ID that was used for signing out the
element. If it is a new program, adding will automatically sign-out the program in your
ID. Check for the existence of a Link-card. If it is a DB2 program, a Bind-card should
also be present in the Endevor region. A program can be added to TEST region if a link-
card is present in PROD region but a separate Bind-card is required for Test region even
if one exists in PROD region.
3. What are the checks that should be performed before adding a proc?
Ensure that you are adding the program from the ID that was used for signing out the
element. If it is a new proc, adding will automatically sign-out the program in your ID.
Use TSO29( system-specific) while adding the proc. In the Add/Update Elements
Screen( while building SCL); make sure that in the COMMENT line, the name of the
JCL which executes the proc is given. This is necessary since a JSCAN is automatically
run on the proc while it is being added to Endevor.
4. I want to add a new JCL and the corresponding new proc to Endevor. When I am
trying to add the new JCL, it says proc not found and when I try to add the proc
it says JCL not found! The action fails. How will I add them?
This problem arises when we are adding for the first time and when the JCL and the proc
are in different PDSs. Put both JCL and proc in the same PDS and trying adding one of
them. It will work because Endevor will automatically search in the same PDS for the
corresponding JCL or proc as the case may be.

AETSRRC Ver 1.10 Page 5 of 10

Infosys Technologies Ltd. Endevor

System-specific:

1. What is the DSN for JCLCNTL type members in UTEST1? (similar to

R8M2WB.UPROD.JCLCNTL2 in UPROD2)
There is no corresponding PDS for UTEST1 for JCLCNTL. While testing using a
modified JCLCNTL type member, it should be kept in a PDS and necessary overrides
have to be specified in the JCL.

2. What is the DSN for COPYRCD members in UTEST1? (similar to

R8M2WB.UPROD.COPY2 in UPROD2)
It is R1ZLWB.UTEST.SRR.SOURCE.COPY1. These PDSs can be used while
manipulating files using STARTOOL.

MOVE action:
(Thanks to Fariyaz)
1. While doing endevor migration of code, Move failed. The reason was that the
Xpediter symbolic dataset was full. What is the solution to this situation?
The solution to this is simple: Expand this dataset. Endevor has a built-in screen to
expand the libraries. The screen prints on how to go about is given below:

AETSRRC Ver 1.10 Page 6 of 10

Infosys Technologies Ltd. Endevor

AETSRRC Ver 1.10 Page 7 of 10

Infosys Technologies Ltd. Endevor

AETSRRC Ver 1.10 Page 8 of 10

Infosys Technologies Ltd. Endevor

AETSRRC Ver 1.10 Page 9 of 10

Infosys Technologies Ltd. Endevor

Reference:
Endevor Training document

For further details contact:

Jayesh G,
AETSRRC
T: 91-80-8520261 x: 53764
e-mail: [email protected]

. End-of-Document

AETSRRC Ver 1.10 Page 10 of 10