Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML No SYNCH17 reported if multiple source libtypes share same baseline
For example, If you have SRC and SR1 pointing to same source baseline library in an application, then in the package you have TESTSRC.SR1 copying TESTCPY.CPY, stage TESTSRC.SR1, and then TESTCPY.CPY is deleted from the package (both newly staged from development). When you run Audit you do not get a SYNCH17.
PDF ChangeMan ZMF Quick Reference
SYNCH16! Like-copy component in the package, which doesn’t contain the calling like- source, was changed after the baseline version of the like-copy but before the calling like-source in baseline. SYNCH 17 ! Like- copy component in a staging library was deleted after it was used to stage or recompile a like-source in the package. SYNCH18! Called load in a staging library was deleted after it was statically linked into a composite load in the package.
PDF ChangeMan ZMF 6.1.2 Readme
 On page 199, the description of SYNCH17! should include this note: Note: No SYNCH 17 ! is issued if a like- copy component is checked out or staged from development from the baseline library, referenced in a like-source stage or recompile, but is never changed in the package before it is deleted .
PDF ChangeMan ZMF 6.1.2 Readme
 On page 199, the description of SYNCH17! should include this note: Note: No SYNCH 17 ! is issued if a like- copy component is checked out or staged from development from the baseline library, referenced in a like-source stage or recompile, but is never changed in the package before it is deleted . ChangeMan®ZMF6.1.2 - 29 - Copyright ©2011,SerenaSoftware,Inc.
PDF ChangeMan ZMF 7.1.1 Readme
General Features & Fixes Installation Compatibility Known Issues Documentation Updates  On page 192, the description of SYNCH17! should include this note: Note: No SYNCH 17 ! is issued if a like- copy component is checked out or staged from development from the baseline library, referenced in a like-source stage or recompile, but never changed in the package before it is deleted .
PDF ChangeMan ZMF 7.1.1 Readme
 On page 192, the description of SYNCH17! should include this note: Note: No SYNCH 17 ! is issued if a like- copy component is checked out or staged from development from the baseline library, referenced in a like-source stage or recompile, but never changed in the package before it is deleted .
PDF ChangeMan ZMF 6.1.2.02 Patch Release Readme
 On page 199, the description of SYNCH17! should include this note: Note: No SYNCH 17 ! is issued if a like- copy component is checked out or staged from development from the baseline library, referenced in a like-source stage or recompile, but is never changed in the package before it is deleted . ChangeMan®ZMF6.1.2.02 - 37 - Copyright ©2011,SerenaSoftware,Inc.
PDF ChangeMan ZMF 6.1.3 Readme
looks to match the SETSSI in the subroutine loads exactly.  On page 199, the description of SYNCH17! should include this note: Note: No SYNCH 17 ! is issued if a like- copy component is checked out or staged from development from the baseline library, referenced in a like-source stage or recompile, but is never changed in the package before it is deleted .
PDF ChangeMan ZMF User's Guide
Out-of- Sync Condition Description Return Code SYNCH 17 ! A like- copy component in a staging library was deleted after it was referenced in a like-source component that was staged or recompiled. Suggested Resolution: If you inadvertently deleted the like- copy component from the package, restage the component from baseline, make the desired changes to it, and recompile the like-source modules from staging and baseline that reference it.
PDF ChangeMan ZMF 8.1 User’s Guide
Out-of- Sync Condition Description RC SYNCH 17 ! A like- copy component in a staging library was deleted after it was referenced in a like-source component that was staged or recompiled. Suggested Resolution: If you inadvertently deleted the like-copy component from the package, restage the component from baseline, make the desired changes to it, and recompile the like-source modules from staging and baseline that reference it.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Delivering changes from a work area to a stream (demonstration)
This demonstration shows you how to deliver changes from a work area to a stream in Dimensions CM, restrict the deliver to specific folders in the work area, and relate a new item to the correct design part.
Dimensions CM: Updating a work area from a stream (demonstration)
This Dimensions CM demonstration shows you how to update a work area from a stream, restrict the update to specific folders in the stream, and exclude files from the update.
Dimensions CM: Working with Items, Part 2 (demonstration)
This Dimensions CM demonstration shows you how to copy item revisions to a work area using the Get and Update commands, deliver a modified file from a work area to a stream using the Deliver command, and action an item revision
Dimensions CM: Introduction to streams (demonstration)
This demonstration introduces Dimensions CM streams.
Dimensions CM: Using multiple teams and multiple streams to perform parallel development (demonstration)
This demonstration shows you how to use multiple teams and multiple streams to perform parallel development in Dimensions CM.

Additional Assistance

  • Submit a Case Online
  • FAQs