|
View previous topic :: View next topic
|
| Author |
Message |
Jon D Knutson
New User
Joined: 27 Jun 2012
Posts: 4
Location: usa
|
|
|
|
| Do others use Endevor in a source managment way along with source migration? We have some projects that seem to come up every 6 months, we do a little work, and then the funding dissapears. The argument is do we keep that code on Endevor as a source management repository or pull it out because there isn't a plan to migration it to live production. Just looking for what others do. |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello and welcome to the forum,
If you "pull it out" where will you save it for the next iteration?
If your Endevor is set up to have a separate TEST set of source, what harm will it cause to just leave it there?
I'm not an Endevor Admin, but most places i've been do both source management and migration with the product. |
|
| Back to top |
|
|
Jon D Knutson
New User
Joined: 27 Jun 2012
Posts: 4
Location: usa
|
|
|
|
| That is the $20,000 question. Personally I believe we should keep it in endevor. But 'others' would say pull it out and keep in a personal pds library. To me that means you will probably loose it at some point. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Nearly everywhere i've been (many, many places) a personal pds has proved disastrous. People leave and their datasets get deleted. Some data sets get migrated all the way out of the system. Someone makes a mistake and deletes the dataset. And on and on.
I suspect that the cost of rebuilding everything from scratch would be most unattractive. What can it "really" cost to just leave it in Endevor?
Also, many Endevor sites also use Librarian. If the modules were stored in a protected Librarian Master File, that should work.
Just make sure wherever the code is kept, it is routinely backed up and is available quickly for re-activating. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
in addition to unit/sys/qa/prod you can also have an ARCHIVE level.
i have been at sites that setup ARCHIVE so that we could create a package
and migrate directly to ARCHIVE from anywhere.
modification was required to change the archive process from delete all and move, to just delete current version and move.
each package relates to a project.
yeah, you will have jumps in PROD due to modules migrating to ARCHIVE w/o going thru PROD.
remember, PROD is normally the source for any new development.
i am not an endevor support guy, just someone who has used it.
The design specs were also loaded as text,
different element type and migrated with the source to archive. |
|
| Back to top |
|
|
Jon D Knutson
New User
Joined: 27 Jun 2012
Posts: 4
Location: usa
|
|
|
|
| Archive looks like a good option, thanks. |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| Jon D Knutson wrote: |
| That is the $20,000 question. Personally I believe we should keep it in endevor. But 'others' would say pull it out and keep in a personal pds library. To me that means you will probably loose it at some point. |
Not relevant to the use or misuse of Endeavor (it's not installed here), but what's this "personal PDS" stuff? I have ALTER access (naturally) to my own (= TSO ID) HLQ...but also to departmental and division HLQs; if I were assigned to projects (I haven't been in a few years), I'd have at least UPDATE and maybe ALTER to the projects' HLQs, too. Do other shops not have a similar hierarchy of HLQs for use by developers? |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
if you can edit/update a pds, you can delete it.
there is always some clown that insists on using 3.4 to access pds's.
and of course, they turn off the 'do you want to delete it' interruption
and they inevitably strike a "D" instead of an "E" and then enter
and the gd-pds is gone.
sure you can restore it, but at best it is last night's,
some times it is last weekend's.
I carry a rexx script that will take an xpeditor ddio print image of a source
and parse it down to a good source module.
I have had to use it a least once at every shop that i have worked,
that used pds's and not repositories.
at least with a good repository, you always have a last SAVEd,
and you don't have to worry about restoring something. |
|
| Back to top |
|
|
|
|
