Working with Endevor

1. INTRODUCTION

a) Tool Description

ENDEVOR is an integrated set of management tools used to automate, control, and monitor
applications development process. ENDEVOR runs under MVS, within the TSO/ISPF
environment, and in batch.

The application development process in our case consists of five stages

* DEVELOPMENT - Programs are developed / changed.

* TEST - Programs are unit tested. This is the stage where we put our
programs after making changes to them.
* ACCEPTANCE - Applications are system tested. This is generally done at
customer site.
* SHIPMENT - Fixes are applied to production code in emergency.
* PRODUCTION - Production applications reside.

All the TEST, ACCEPTANCE, SHIPMENT and PRODUCTION stages are under the control of
ENDEVOR.

b) Procedures followed while using ENDEVOR in projects:

* Normal procedure

* Emergency procedure

NORMAL PROCEDURE:

Normal change procedures include:

* Retrieving from Production to a development region.

* Making changes.

* Adding/updating into the Test stage.

* Moving to Acceptance.

* Moving back into Production.

EMERGENCY PROCEDURE :

Emergency change procedures include:

* Retrieving from production to a development region.

* Making changes.

* Adding/updating into the shipment stage.

* Moving to Production.

2. PROCEDURE FOR ADDING FILES TO ENDEVOR

ENDEVOR (Development Region) Project Test Directory

Add to ENDEVOR (Ex. N0XXXX.AETDMBB1.ELEMENT.TEST)

Retrieve the element to project base directory Copy the element to project test
directory

Project Base Directory Copy to your working folder Individual Working Directory
(Ex. N0XXXX.AETDMBB1.ELEMENT.BASE) (N015966.SOURCE.ELEMENT FOR USER N015966.
MAKE CHANGES IN THIS PDS)

So any element being retrieved from ENDEVOR will be retrieved to Project Base directory of
that element. From the base directory a copy will be made to the working directory of the
developer and changes are made here and later copied to the Project Test directory. From the test
directory the element is added to the ENDEVOR.

This step is only applicable for elements in the ENDEVOR which are undergoing some
changes.
In case of new elements, the elements are moved to the Project Test directory from the
working directories and then added to ENDEVOR.

Benefits from following this approach

1. Project Test directory will always has the same version as in ENDEVOR
 2. For a Reviewer, he can see the difference between the files in the Project Base directory
and the Project Test directory to certify the changes made.
3. Systematic procedure which avoids confusion.

3. KEYWORDS FREQUENTLY USED IN THE DOCUMENT

The following Keywords will be used in the frequently used, so lets know what they are.
1. Link Card
2. Bind Card
3. Generate
4. SCL(Software Control Language)

1) Link Card: If you have a static cobol call from one program to another. These two
programs need to be linked after compilation, to create a load module which is final
executable during execution. Link Card is used for this purpose. It links the object
modules which are available from compilation and prepares a load module.

When we compile a program in ENDEVOR (Adding the program with Generate option),
the object module is stored in the name as that of module. At this point if you write a link
card like

ENTRY PROGRAMID
INCLUDE OBJLIB(PARNTPGM)
INCLUDE OBJLIB(CHILDPGM)
NAME LOADNAME(R)

Here PROGRAMID is the PROGRAM-ID in the PARNTPGM. The object libraries of

both the Parent Program(PARNTPGM ) and the called program Child Program
(CHILDPGM ) are included. LOADNAME is the name in which executable load
module will be created.

2) Bind Card: This Card is needed for a DB2-COBOL program.

 DSN SYSTEM (DSN)
BIND PLAN (CCSV 100) -
QUALIFIER (GCSV 00B) -
OWNER (GCSV 00B) -
MEMBER (CHILDPGM) -
ENABLE (BATCH, CICS) -
FLAG (W) -
ISOLATION (CS) -
RELEASE (DEALLOCATE) -
CURRENTDATA(NO) -
VALIDATE (BIND) -
ACTION (REPLACE) -
EXPLAIN (YES)
END

To give a foreground information, when a cobol program is added to the

ENDEVOR with the generate option, it pre-compiles, compiles producing the
object module and the DBRM. Both the Object module and the DBRM are stored
in the name of the program. Now when the bind card is added to the ENDEVOR
with the generate option, the ENDEVOR picks up the DBRM specified in the
bind card and generates the PLAN for the program. The bind card has parameters
like Isolation (Cursor Stability), Release, Validate, Action, Explain which are
needed during Binding. The member name is also given as a parameter specifying
the ENDEVOR which DBRM to pick.

3) Generate: Generate option (4th option in SCL Generation panel) generates

Object libraries/Load Libraries according to the input elements given to it. This
option is also present in the Add Panel with the default value as Y. So when you
add, say a cobol program to the ENDEVOR. The ENDEVOR calls the Generate
Processor which is mentioned in the same panel, which automatically does the
pre-compilation, compilation step and outputs the object module for the element.
If the input element is an Link card the generate processor processes the link card
and accordingly outputs the load module.

4)SCL : ENDEVORS inventory is manipulated by executing commands called

actions. Some actions are available in both foreground and in batch, while others
are available only in batch.
Software Control Language(SCL) is used to code batch action requests. Using
SCL, a JCL can be created, edited and submitted for any job that is to be
executed.
When you enter your development region enter the batch option(3). Now you get
the batch options menu which looks like
1. Building an SCL: Give the member name in the Request Data Set block. This
creates an SCL in the mentioned PDS. The job statement information is given
below which can as well be modified. The Job Name is sequentially
generated. So the build screen look like
Specify what you want in to do while submitting the SCL in the next screen which
comes like
Say you selected option 2 (ADD/UPDATE), and press enter the next screen looks
like this after entering the necessary values and pressing enter
Now SCL is Generated. See the message in top left corner. Press F3 button two
times which takes you to the first screen. Batch Options Menu. Press 2 here.
You get the information of what all you have done
Check if its proper, you can also edit here and change if something is typed
incorrectly. Now do an F3 and come to the previous screen. Type 3 and submit the
SCL.
 The SCL is submitted and the action is performed, if no errors occur.

4. STEPS FOR ADDING A DB2-COBOL PROGRAM TO ENDEVOR

Stepwise procedure for adding all the elements for a DB2-COBOL program into Test
Environment of ENDEVOR for Data Migrator Project:

1. First add the Copybooks and DCLGENS used in the program with the corresponding
Element Types. Make sure that you add it to Correct Environment (MTEST2),
System(DATAMIGR) and SubSystem(SOURCE). Check with the Test Environment
document in Project\Docs\FromOnsite folder for the details.

2. Add the Cobol Program with the Generate Element Option as Y (which comes by
Default).
This step will generate the object module in the name as that of the cobol module name.

3. Add the Link Card to ENDEVOR with the Generate Option Y.

This step generates the Load module for the COBOL program according to the entries
made in the link card.

4. Add the Bind Card with the Generate option Y

This step generates Plan/Package as per the bind card specifications.

These four steps needs to be done when a DB2-COBOL program is added to ENDEVOR
afresh.
Other cases:
a) In case a copybook already added to endevor gets changed

1) Add the new copybook to endevor with an update option, and the other options
are same as above.
2) Check the programs that are getting affected by this copybook. Do an Impact
Analysis. List down all these programs.
3) Since these programs are not changed, so there is no need to add them again, but
you definitely need to Generate them to include the changes in the copybook.
4) Go to the 4th option in the SCL Generation panel of the ENDEVOR.
5) Generate all the programs. This will give us the object modules of all the cobol
programs which include the changed copybooks.
6) Generate the link cards also for these programs which outputs the Load modules
for these programs.

b) In case if an SQL is changed

Just generating the Bind card will not work since this picks up already existing DBRM
and produces the Plan. So the DBRM is the old one and not the new one. So therefore
you need to do all the three steps.

1) Add the changed Cobol program to ENDEVOR, with the Generate option. This
generates the object module and the DBRM.
2) Generate the Link card which was already added. This generates the load
module.
3) Thirdly, Generate the Bind card which gives us the Plan.

References:
1) Couple of Boks in knowledge shop.
2) Help provided by IBM Mainframe.

************************************************************************

Contact person : Hanumanthu Sekhar Employee No : 9920