Académique Documents
Professionnel Documents
Culture Documents
Endevor is a change control tool. It is used by many organization to manage the changes
and development in programs and other components. It is a management tool that helps us to
attain the following goals more effectively -
Using Endevor we can retrieve the program from production region, then once we have
tested our changes we can move it back to application region and then to higher regions
subsequently.
To reach upto the Endevor main screen please do the following steps :
- Logon and select TSO session TE3Select option 7
This will take us to the startup Endevor screen where we need to select the Environment type.
Screen is shown below.
--------
----------------------------------------
1 AI1
2 VI1
3 ZF1
ZRICH FS UNIT/APPL
4 ZFP
ZRICH FS LIFE/PROD
5 ZN1
UNIT/APPL
6 ZNP
LIFE/PROD
7 ZDELETE
In the Option place we can select either 5 or 6 or 7. We mainly use these three
systems only.
Option 5 (ZN1) : This system is used to see the programs at Unit and application
level. When we need to change or develop a new program we need to select this
option.
Option 6 (ZNP) : This system is used to see the program in production and life test
level.
Option 7 (Zdelete) : We need to select this system if we want to have a look at
archived programs.
1. Option 1 (Display) : This option is used to see details about a program, macro,
copybook etc in Endevor.
This option takes us to another screen called Display Option Menu. In this menu
again we can select some options and view different things. Just choose the options
and have a look. We can see element details, we can see compilation details,
systems & subsystems in a stage, types of programs environment details. All these
things are possible in this option.
Element
write
Type
Stage
: To display the list. If you are putting N here then no list will be
displayed and the system thinks that you the exact name of the
element
you want to be displayed.
Build Using Map : This option helps to search the element if it is not there in the
stage you have selected. If it is set to Y system will keep looking for
the element in higher levels and will show you the list in whichever
stage it has found the element. But if we are putting N here then it
will search the element only in the stage we mentioned.
Environment : ZN1 , we wont add in ZNP environment as we are not allowed to do so.
System
Subsytem
Element
: Name of the program you are adding. Not required if you want to copy
the member with same name.
Type
: This is type of the program that defines what kind of program it is Cobol,
DB2, IMS , PL1, Batch , Online etc.
CCID
: Automatically generated
Generate Element
Delete Input Source : If we want the source to be deleted from private library after
adding it to Endevor specify Y else N
Override Signout
: If someone else is also adding the same element same time then
Processor Group
Update if present
If you say Y, if you say N then it will not update the Endevor version.
Also specify the library name from where we are copying the member as shown above.
Retrieve : This option allows us to retrieve a code from Endevors any reason to a private
dataset. any higher level to lower level. Like if we want to take some code from
production to do some changes then we need to retrieve the code from
production and put it to our private dataset. This option helps us do so.
Subsytem
Element
Type
: This is type of the program that defines what kind of program it is Cobol,
DB2, IMS , PL1, Batch , Online etc.
Stage
CCID
: Automatically generated
Generate Element
Delete Input Source : If we want the source to be deleted from private library after
adding it to Endevor specify Y else N
Expand Includes
Override Signout
: If someone has already retrieved the code Endevor will not allow
: This is a flag which tells all the users that someone has already
if you say Y, if you say N then it will not update the PDS version.
We can see that lot of details we can find in this list. Element Name, Type,
Environment , Stage, System, Subsystem, Version No, Program added date and
Compilation Date etc.
Please note we have different stages here. We have Unit stage we have
Production stage.We have ZNP as well as ZN1 environment even though we
selected only ZN1 environment.
This is because we have given the Build Using Map option as Y.
We can browse a program by putting the line command B in front of the member
we want to browse. As shown in above screen.
This will show you the program code. Same way we can also use the other
commands as shown in the screen previously
Note: Inorder to Add, Update, Retrieve, Delete etc. an Element we need to Build
an SCL (Structure Control Language).
Now in this we need to give R in Options and then From Location and To ISPF
Library information
From Location: From which Environment, System, Subsystem, Element, Type,
and Stage we are having the Element. To know this navigate from
CA Endevor SCM Primary Options Panel as
1 1 Element. Then we get as
To ISPF Library: The Destination Dataset into which the Element must be
retrieved.
Now come back to Batch Options Menu and Validate the SCL generated.
Once we validate we can see whether there are any Syntax Errors.
Once the Retrieval is done successfully we can see the SCL is generated in
CHZ4394.HUD.SCL with member name ASDA (you can give any member name)
Note: While adding the Element its good to make a LIST of Element TYPE.
How to do Listing:
In SPOOL area check the Listing Dataset. Here it is ZHC1.UNPU.LISTINGB
Once the errors are fixed Recompile the Element & thus the Element will be
successfully compiled.
What is a Package :
Cast the package to ensure it is correctly given with all the details and error free.
JUST LIKE VALIDATING YOUR SCL
Once done. It will throw a message as CAST Successful.
We raise an ask request to execute this Package or send it through SCM
document, if it is planned to move in the desired BUS.
Additional Information:
Adding element from our
Library
Transfer
UNIT (U)
APPL (A)
PROD (P)
LIVE (L)
Prod Package
Steps:
1) Adding an Element from our Library to UNIT region.
2) Transferring the Element from Unit to APPL region through Endevor.
3) Then sending request to ASK team to create package in LIVE region.
4) After the successful performance of UAT by the Client then we need to
request the ASK team to create package in PROD region.