Clearcase config spec behaves odd when using setcs command
Asked Answered
S

1

2

I have config spec stored in a text file . Following are the content

element * CHECKEDOUT
element ...\lost+found\... -none
element \My\... MYF_R2.1.0.9.5179
element \My\... My_2.1.0.13.4875
element \My\... MyComponents_8_8_2011.6859
element \My\... My_2.1.0.13.7098
element \My\... My_2.1.0.13.8206
element \My\... My_2.1.0.13.433
element \My\... My_2.1.0.13.423
element \My\... My_2.1.0.13.3763
element \My\... My_2.1.0.13.5983
element \My\... My_2.1.0.13.7095
element \My\... My_2.1.0.13.5986
element \My\... My_2.1.0.13.8209
element \My\... My_2.1.0.13.437
element \My\... My_2.1.0.13.9321
element \My\... My_2.1.0.13.1548
element \My\... My_2.1.0.13.1537
element \My\... MyComponents_11_2_2011.461
element \My\... My_2.1.0.13.2649
element \My\... My_2.1.0.13.1534
element \My\... My_2.1.0.13.3760
element \My\... My_2.1.0.13.4872
element * /main/0

When i use cleartool setcs command upto "element \My... MyComponents_11_2_2011.461" line the config spec is updated and remaining lines were neglected.

While i added them manually , it works fine.

Any idea why setcs command behaves like that? is there any length restriction is there while using setcs command?

Following is my setcs command

cleartool setcs -tag $ViewName $ConfigSpec
Sigfried answered 22/12, 2011 at 13:54 Comment(2)
We have cspecs with 300 lines in them...you've not reached the limit with 20 lines.Kelliekellina
@Jonathan Leffler: I think you should be able to write a good book/posts on practical applications of configuration management and help more people with your knowledgeSigfried
D
2

There is no special limitation, according to cleartool setcs man page.

The only way this file isn't applied completely while applied manually if is there is some kind of encoding issue or newline issue in that file.

A way to debug it is to:

  • apply it manually
  • cleartool catcs -tag aViewTag > aFile: see cleartool catcs man page: redirect the content of a config spec for a given view in a file.
  • compare aFile with your initial config spec file.
Dickdicken answered 22/12, 2011 at 14:0 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.