UmeySan
Active Member
Joined: 22 Aug 2006
Posts: 771
Location: Germany
|
|
|
|
Hi !
ENDEVOR
ENDEVOR PDM Parallel Development Manager
ENDEVOR/PDM (compare facility)
Problems at Synchronization of Source Code
When creating an ENDEVOR/PACKAGE the Synchronization default value is "N". The "N" specifies ENDEVOR will not SYNC up the code when it is moved to the next stage. This is ENDEVOR working as designed. It saves only the member changes in the DELTA file when saving a next version of an NDVR dataset member. When SYNC=Y, ENDEVOR saves a full version delta and should only be used when a Synchronization error is detected. If SYNC=Y is used as default it would cause a problem. The DELTA file would become larger than the actual NDVR dataset.
Synchronization errors are detected during the CASTING of the package. They are usually caused by a discrepancy in the version numbers or could be a high percentage of differences in the code from old version and the new version. Before SYNC=Y should be used the reason for the error should be determined and resolved.
This is done by using the ENDEVOR/PDM compare facility (O.O.L;2).
The ENDEVOR/PDM compare facility will display differences in the code and let you merge any changes needed. The newly merged version can then be put into a separate package with SYNC=Y and then reCAST, APPROVED and MOVED to Production.
please have a look at:
dirm.state.nc.us/team51/endevor/change01.html
Regards, UmeySan |
|
.jpg)
