|
View previous topic :: View next topic
|
| Author |
Message |
xenomorph
New User
Joined: 27 Jul 2007
Posts: 9
Location: Europe
|
|
|
|
Hi all,
I've a question regarding CCID in ndvr. We are having "headackes" regarding version handling and promotion.
For instance, soft in production cannot be taken back into dev because the sources and db2 definitions
in dev or acceptance isn't the same. So my question is, can using more than 1 CCID be helpful ?
If you use the emergency repair env how can you test the changes ?
Thank you ! |
|
| Back to top |
|
 |
HappySrinu
Active User
Joined: 22 Jan 2008
Posts: 194
Location: India
|
|
|
|
do you want use CCID for testing and another CCID for production right?
If so you can use it. |
|
| Back to top |
|
|
xenomorph
New User
Joined: 27 Jul 2007
Posts: 9
Location: Europe
|
|
|
|
| Thank you for your comment Srini but I don't think using more than 1 CCID will be enough for my problem. I will try to reformulate my question, maybe my first thread wasn't clear... My question is more like : what is the procedure to test a repair in production env when dev and acceptance env are already updated for a new version of the soft (like table definition in DB2 changes) ? |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
normally endevor has 4 environments: unit, syst, acpt, prod.
a quick prod fix would be accomplished in the acpt environment.
if you have already changed unit/syst/acpt so they don't match prod, you are suffereing from not planning.
by the way, posts are a part of a thread - i.e. a thread is made up of one or more posts. |
|
| Back to top |
|
|
xenomorph
New User
Joined: 27 Jul 2007
Posts: 9
Location: Europe
|
|
|
|
| Quote: |
| suffereing from not planning |
Well, I'm not responsible for that part.
| Quote: |
| by the way, posts are a part of a thread - i.e. a thread is made up of one or more posts. |
I agree, my fault. |
|
| Back to top |
|
|
Mistermind
New User
Joined: 08 Feb 2008
Posts: 46
Location: Dublin
|
|
|
|
CCIDs are designed to "tag" workflow for a project or a team, and provide audit trail and history afterwards. In forcing you to nominate the CCID at every stage Endevor ensures the wrong module was not named thru accidental typos etc.
Different versions of the same element, e.g. one version of a program at stage A undergoing changes for one purpose, but another version of the same program brought down to stage A for a different purpose, these two versions need to sit in different substreams to keep develop separate.
In one installation there is an Emergency or Fix Environment, on par with Production, where compile/linkedit will pick up only Production versions of copybooks, subroutines etc. When proven at this level, it is then re-promoted straight into Production safe from pickup of any impurities. |
|
| Back to top |
|
|
HappySrinu
Active User
Joined: 22 Jan 2008
Posts: 194
Location: India
|
|
|
|
Usualy as it mentioned before every Endevor SDLC have quick fix environment which should be similar to development but just to reduce the path at the time of emergency fix.
If you want to do emergency fix, try Qucik Edit to your bottom environment and Endevor will be taken care automatically.
It completely depends on your Endevor setup, how CCID works. |
|
| Back to top |
|
|
xenomorph
New User
Joined: 27 Jul 2007
Posts: 9
Location: Europe
|
|
|
|
Thank you, I know more about CCIDs now.
Fortunately in 2-3 weeks our DEV and PAT env will look a like. |
|
| Back to top |
|
|
|
|
