It's all about the answers!

Ask a question

Max number of locked source/files on the same components

ryosuke oka (17994648) | asked Aug 26 '13, 2:15 a.m.
edited Oct 10 '17, 2:14 p.m. by David Lafreniere (4.8k7)

Version: Rational Team Concert 4.0.1(Enterprise Extension)                     
Currently RTC can only lock 512 sources/files from our observation.               
If we lock more than that, then it will behave like this          
1. when there are locked files on a same component                      
- unlock of the same component and get a new lock                       
- end code with "0" (checking with scm command)                         
2. when there are no locked files on the same components                
- can not lock                                                          
- end code with "0" (checking with scm command)                         
In both case (it dose not matter whether can can lock or not), end code
is "0".   so we an not find whether it is finished correctly or not.              
Q1. Is there a way to increase lock number over 512?                    
If there is let us know how to do it.                                   
Q2. As we have explained in current situation, we are getting "0" for   
not locking case.                                                       
How we can find whether we had successfully locked or not.              
Q3. We can only show 100 locked sources/files on Eclipse client by right
click on stream > show > locks.                                         
Is there a way to show more than 100 locked sources/files on Eclipse?   
If so, please let us know.                                              
We confirmed that we could see more than 100 locks with scm list locks.
I checked Eclipse setting but I could not see related setting in there. I also checked Advanced properties in Application Administration (ccm).

If anyone can point me out where to look this, then

Accepted answer

permanent link
Geoffrey Clemm (30.1k33035) | answered Sep 16 '13, 9:20 p.m.
edited Sep 16 '13, 11:27 p.m.
I did some exploring on this issue.   Based on my experiments, there is no limit to the number of locks that you can apply in a component, but there are issues in the code that is used to retrieve those locks.  In particular, the Eclipse client appears to only display around 512 of those locks in displays like the Package Explorer.   I've reported that problem in If more than than 512 files are locked in a component, only about 512 locks are shown in the Eclipse package explorer (280745)
David Lafreniere selected this answer as the correct answer

ryosuke oka commented Sep 19 '13, 4:59 a.m.

Thank you for checking on this issue, Geoffrey!

David Lafreniere commented Oct 10 '17, 2:11 p.m.

Note: What Goeffrey explained above was the correct observed behavior. The issue was that the server API did not support paging, and so by default it just returned 512 locks. The defect that he mentioned (Defect 280745) was fixed and delivered for RTC 4.0.6. This introduced an advanced server property called 'Maximum number of locks returned from query' which would allow a larger number to be returned (but there still would be a maximum).

In RTC 6.0.5 however, we added proper paging support, and so now all RTC clients will be able to fetch and display 'ALL' locks as expected.

One other answer

permanent link
Tim Mok (6.6k38) | answered Aug 26 '13, 2:23 p.m.
You may want to open a work item or go through IBM support to open a ticket about the exit code issue with the CLI.

For the Eclipse client, you can go to the menu (Search > Jazz Source Control > Locks) and the default is the 100 limit. You can change this to a larger value.

ryosuke oka commented Aug 26 '13, 9:09 p.m.

Hi Tim,
Thank you for a quick reply for Q3.
I had actually opened work Item for Q1 & Q2.

Do you have any idea for Q1? 512 locks? the number seems to be related with memory of something but I could not find any document or setting for lock number of source on 1 component.

Simon Eickel commented Aug 27 '13, 1:17 a.m.

can you please post those work item links here?


Tim Mok commented Aug 27 '13, 8:50 a.m.

You've already opened a work item for Q1 so I expect it would be investigated there. As Simon points out, posting the work item links would help others follow the issue.

Karl Weinert commented Aug 27 '13, 8:52 a.m.

It is an internal escalation, we will be sure to follow up here with our findings.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.