MVSFORUMS.com

[vini]

The following look like the key actions on the Endevor Menu for Change mgmt:

1) Retrieve
2) Add
3) Sign-in
4) Move
5) Package
6) Generate

My questions/concerns :

a) What is the order of these actions incase of a New element vs. Existing element change.

b) How do these steps/actions vary if I were to use ISPF editor instead of Quick-Ed
it.

c) What are the advantages , if any of Quick-Edit over ISPF edit.

d) Are all the actions mandatory/ critical or is it installation dependent.

e) Is the production movement normally controlled by developers or admins or installation dependent.


Thanks.

[Venkata Subbaiah. P]

As everybody know that Endevor is a version control tool. Which facilitates to maintain different version(s) of the same element(s) in different environment(s) for our testing purposes according to our requirements not alone for any development but also for maintenance.

Thus if it is required for us to make some code changes for any existing program, we need to take a copy of any element of latest version either from Production/Pseudo production or Lockdown . This action can be performed by Retrieve.

Once we make the code changes to the program after retrieving from a correct location, we need to add the element to any nominated test environment, for further proceedings such as reviews and unit test cases execution. This action is called Add

The words Sign-IN and SIGN-Out are related to a kind of lock on one particular element for the integrity of its version control. So, when ever one person retries an element for some kind of work on it, the element will be signed out to his/her id. Unless he/she Sign-Ins, no other person can work on the same element. Ultimately, all the versions will be under the well control of Endevor and thus the Configuration Manager can have a clear picture of any retrofit requirements, if required.

Further, depending on the criticality of the project where one is working, for other kinds of tests such as, System testing or System Integration testing, Stress and Volume Testing and User Acceptance Testing , if it is required to test the current version of an element in different environment(s), it would be required to Move, the current version of the element to various environments either by Configuration Manager or the developer. This activity is performed through Move. Some times, if the element is required to me moved from higher level environment to another higher level environment, (Ie., System Integration Test region to Stress and Volume Test region). it is also called as Transfer of element.

In general, in all the Business initiative releases or maintenance releases, there will be many Type and number of components. The activity of Move or Transfer of such huge number of elements, will be handled by creating Packages, casting them and executing them.

In some scenarios, it will be required for us to recompile some of the elements due to some call dependences or due to some copy book changes. This kind of actions can be performed by us by the activity Generate.

It is a best suggestion to you to refer Endevor manuals for better understanding of these activities and also the other features of Endevor as it has lot many other usages and functions.
Hope you clear with some of your doubts.
_________________
Venkata Subbaiah. P
SSE Mphasis, an EDS Company