configuration management Questions

Wondering if anyone has come accross this issue? (It's not a show stopper but has got me scratching my head)

I am trying to "migrate" some Items from an existing Dimensions Product into a new Product.
NB I am in essence cloning "part" the old Product.
I do actually want to create new CI/items rather than variants of the existing CI/Items.
The new CI/Items will all be V1 with no history etc in the new Product.

So pretty simple steps:
1) Get copies of the Items I want
2) Load them into new Product
3) Prove they are identical *see below
4) Get on with my life.......

As I did a direct get from old and load to new I "know" they are identical I am just "documenting" the proof for the end user.

I have set up a few scripts to:
a) Run diff/compares between the fetch from New Dimensions (O/S directory structure) vs fetch from Old Dimensions (O/S directory structure) and saved report (They are identical :-) )
b) Run detailed directory listings showing dates, sizes etc and produced a compariosn report. (They are identical :-) )
and finally:
c) Produced seperate output from Dimensions listing all (relevant) Dimensions metadata and produced a comparison report......... THEY ARE DIFFERENT!!!

For some files (a very small subset) the Dimensions metadata for "CHECKSUM" and "FILES SIZE" don't match!!
(Revised Date (UTC) DOES match).....

I have loaded the offending files a few times and they always produce the same values for this metadata (& the file size value ALWAYS matches the O/S file size).

So basically the "old" values for this metadata is "wrong"!!!

I have no way of reproducing this (as all experiments now produce "correct" values)....

The only thing I can think is that this is in some way connected to the various character translations between UNIX and Windows (as all the files "could" have been via UNIX at some point).

As mentioned it's not a show stopper (as I KNOW the files are OK) but if anyone has any ideas/experience I'd like to know!!


I'm looking for any suggestions anybody might have of real parameters that are mesurable and could be used to improve the quality and robustness of Configuration Management Business Cases to encourage the adoption of CM as early as possible in new programmes and projects

By Bob Mosu - March 25, 20152 Answers



I am new to CA SCM. We are currently running version 12.1.03. I am wondering if, as a regular user, I can run a command/set of commands so I can get an output of the following form:


Please provide a set of instructions on how I can get this info running at command line CA SCM commands.

Thank you,



I like to know the output of a command from Synergy 7.1. Since, we have already moved to the newer version Synergy 7.2, I dont have environment to check this. This output of this command is needed for modification in one of our internal script.

If you still uses Synergy 7.1, may you able to provide me the output of the following command:
ccm properties -f %status% non-existing-object-four-partname

Following output is resulted in Synergy 7.2 ::
ccm properties -f %status% non-existing-object-four-partname
CRCCG1025E The value 'non-existing-object-four-partname' for the object_spec argument is not valid.
CRCCM0302W The object specified by 'non-existing-object-four-partname' does not exist.
Recommendation: Read the Synergy help for information about this command.

Best Regards

Deepak Bawankar

By Paul McElhone - February 16, 20152 Answers

We are about to migrate from ClearCase (Both Base and UCM) to GIT. Are there any papers or scripts out there that can help?

how to configure users to only see their projects they are assigned. When I assign users I want them to only be able to view their assigned projects. I know the users can filter their projects within the workbench, but I want it done in the Administrator.

Ideally, I'd like to take a unix shell programming course that is offered in the classroom but I would consider an online course as well.  I have ten years of release engineering experience but I was laid off five years ago and I want to work in unix/linux release engineering again or in even switch to system administration.TIA,

Linda Dawson, Lexington, MA

There are a lot of COTS products nowadays that can be customised through configuration and scripting which can significantly change the functionality, so are these still COTS or are they MOTS (Modified-of-the-shelf) or are they something else?

My specific question is about ServiceNow where you can modify the CMDB structure, change and add workflows; create scripts and even change the layout of screens etc. All of this is done through ServiceNow itself and you do not need to develop any 'external' code. Remedy is another tool where this happens.

So do these changes mean that it has been "modified"; is it just a configuration of a COTS, or is it something else?



We have a code review tool Atlassian Fisheye+Crucible already implemented, but we are using this with Perforce as our version control tool. Since Perforce has another code review tool "SWARM" we'd like to evaluate this tool. But need to know the benefits of using this tool over Crucible with fisheye.

SOme of the benefits I know is:

- efficient Pre-Commit code reviews
- No extra database to administrator
- Performance - Swarm executes transactions much faster than Crucible because Swarm is so tightly integrated with Perforce
- Ability to commit code from SWARm UI

I need to know from a core technical perspective if there is any other benefits.

I'm have promarily used Subversion in the past, and the structure we used was:

/branches    - Self evident name for branch management

   /int          - Integration branches

      /projectA_effort_q4_2014 - Integration branch for release on q4 of 2014

   /usr         - Individual engineers branches

      /fred    - Fred's set of branches

         /some_bug - Fred's branched from somewhere to fix some bug

      /sally    - Sally's set of branches

         /some_feature - Sally's branched from somewhere to add some feature

/tags          - Self evident name for tagging

   /projectA_v1.0 - Tag of projectA at version 1.0

/trunk         - Trunk for various projects

   /projectA  - ProjectA

   /projectB  - ProjectB

/vendor      - Repo path for storing pristine drops of 3rd party code used in various projects

   /acme     - Vendor name of a 3rd party source of code

      /superLib - Acme provides us the superLib

         /current - Latest drop of superLib

         /v1.0_drop - Tagged drop of superLib

         /v1.1_drop - Tagged drop of superLib


The machanics of this is to allow for segregated development with maximum traceablity. For example any propriatary changes specific to a project needed within superLib would happen within that project, and only the pristine changes from the vendor would be within the /vendor area, then merged into the project to minimise merge errors.  Users brnach off the integration branches to their own staging areas in usr to integrate new functionality of fix issues and merge them back into the integration branches once proven.  The CM, PM, EM, and PVM would be responcible for merging the integration branch to the trunk project and tagging the trunk project versions.


Our current system is TFS based, and is really porrly managed - it was a historical conversion from ClearCase to TFS and there is no clear deliniation as described above.  In fact, it's more like a shot gun of tags and branches, without a really good organzation of where the root of changes should reside, and there's multiple code forks even though 90% of the code is shared.
I was looking to see if it makes sence to refactor the release structure into something like the above, but I'm not sure if it makes sense for TFS and the documentation I can find on TFS doesn't really describe best practices or typical work flows, and the rest of the users here are actually more familier with ClearCase as TFS was a corporate edict of standardization that was pushed onto them.
If you are familier with a better flow or best practice for TFS, please share as our current structure is unmaintainable and unscallable for validation and test purposes.

Thanks much,



CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.