Synergy conflilcts: "parallel, not included"

Conflicts report a lot of files, all belong to a single task, the task
is for release that is not in process rules (reconfigure properties).

Here is how to find:

1. List all the objects of the offending task (35742):
> ccm task -show objects  35742  -u -f %objectname >  35742 .obj

2. Query for all the immediate successors of the task objects:
> for obj in `cat  35742 .obj`;do ccm query "has_predecessor('$obj')" -f
"%objectname %task_release" >> successors;done

3. Grep the list for objects of your current release:
> grep 27.0.3.20 successors

2) trroute.c#KUKU_27.0.3.20.1:csrc:3 KUKU_27.0.3.20

End of story.

ccm ps -host gives you the command currently running on a specific database!

> ccm ps –host myhost

rfc address (myhost:36996:131.120.211.116)

        process (engine)

        callback (engine_startup:cb_init)

        platform (unix)

        pid (15767)

        user (mybuild)

        host (myhost)

        host_addr ()

        ui_address (client.corp.company.com:53851:10.213.1.130)

        database (/data/synergydb/mydb/db)

        reconfigure (1/project/KU110/Appl_1.11.08DL_B,1/project/KU110/Appl_1.11.08DL_B)

Set up Synergy Linux client to use non-default merge tool (work tip Synergy merge compare)

To customize merge and compare utilities for Synergy Java client running on Linux:

1. Exit java client.

2. Assuming you use BeyondCompare as a merge and compare tool, and it is installed as /usr/bin/bcompare

 Add into ~/.ccm.user.properties file the following lines:

  unix.tool.merge.ascii=/usr/bin/bcompare %file1 %file2 -mergeoutput\=%outfile

  unix.tool.compare.ascii=/usr/bin/bcompare %file1 %file2

Changes will have an effect when Synergy starts next time.

Synergy error 'Cannot lock project' upon reconfigure (update)

Somehow this page disappeared from IBM site so replicating it here. Historical number below hints that it was created during Telelogic days.

Message 'Cannot lock project' while doing a reconfigure or reconcile

Technote (FAQ)

Question

I am getting the message 'Cannot lock project' while doing a reconfigure or reconcile. How can I resolve this?

Answer

When you initiate an operation which modifies the project members, such as reconfigure, the projectis locked. If the operation terminates abnormally, the lock may not be cleaned up and subsequent actions may fail and result in a 'Cannot lock project' message. For example, if a user terminated their client during a large reconfigure, rather than waiting for the operation to finish.

If all actions took place using the same client, restart the client and this will usually resolve the issue. This is normally the case for a working project.

If however multiple clients are accessing the project it may be more difficult to resolve the issue. This may be the case for prep and shared projects.

The solution for this should be to run:

ccm monitor -showlocks

ccm monitor -removelock XXX

...where XXX is the full line returned from showlocks.

If this still does not resolve the situation, then you will need to shutdown the entire database with the 'ccmdb shutdown' command, to ensure all connections are terminated.

Should the problem persist even after a 'ccmdb shutdown' then you should run:

onstat -k > locks.txt

and contact IBM Rational Client Support for further assistance and specific steps for your environment.

Once the onstat command has been performed then you can also restart Informix, as this should release the locks effecting the operation.

Historical Number

KB7898

Synergy groups: setting up read-only access to sources of specific project that come from specific releases only

Assume a role of group_mgr:

$ ccm set role group_mgr

Note: if you do not have a group_mgr role assume the role of ccm_admin and add yourself the group_mgr role. End the session and start over.

Verify:

$ ccm set role

group_mgr

Create group:

$ ccm groups -c mygroup

This will open the vi (or any other text editor you have set as a default) session where you should write all the names of the users to be members of the group, in a single line, space-delimited.

Once you are done adding the users save the file and close editor session. The group will be created.

Do not bother sorting the names, next time you look at it via ccm groups -show mygroup you will see all the names sorted alphabetically. And they will be cut in several lines anyway.

List groups:

$ ccm query -i group

1) group/admin/mygroup/1 admin myuser admin <void> group <void>

List group attribute: (so we know what can be viewed or changed):

$ ccm attr -l @1

create_time (time) (local)

cvtype (string) (local)

is_asm (boolean) (local)

is_model (boolean) (local)

membership (text) (local)

modify_time (time) (local)

name (string) (local)

owner (string) (local)

status (string) (local)

subsystem (string) (local)

version (string) (local)

View group owner:

$ ccm attr -s owner @1

myuser

View group members:

$ ccm attr -s membership @1

OR

$ ccm groups -show mygroup

Change group membership:

$ ccm groups -e <group name>

e.g. ccm groups –e mygroup

Query for all the objects to assign to the group (all objects in the ABC_v721_00 project that belong to the ABC* releases):

$ ccm query "is_member_of('ABCAPP#V721_00') and is_associated_object_of(cvtype='task' and release match 'ABC*') and type !='dir'"

Assign ABCAPP#V721_00 721-only objects to the dp security group with read-deny access to others:

$ ccm groups -a -v mygroup:readsource @

Synergy issue with object access restriction

Background

Synergy provides for setting both read and write restrictions on all kinds of objects (projects, files, directories).

When the restrictions are applied only the members of the specific predefined security group are able to read or read and modify objects as appropriate.

If you get the "write restrictions" error during check out, you are probably not a member of the security group that owns an object.

Security restrictions are applied hierarchically top down, from the project level down to the individual files.

Access mode to the object can only be changed while the object is in the modifiable state (e.g. "working").

When the security restrictions are lifted from the project, non-modifiable members of it (files and directories) are still left with the original restrictions applied. Even when the objects subsequently become members of other projects, restrictions on objects are retained.

More on the subject is in the original vendor docs.

What to do?

Find out what group the object belongs to (GUI, Object Properties -> Security).

Find out the group owner (CLI, first user that appears in the list of group members).

Call the group owner to see if you should be added to this group to gain an access to the object.

If you create a new project version and wish to lift all the inherited access restrictions that may exist on your project objects, call CM admin to do the job.
(The ugly solution is to have the original group member or admin Check Out all the project members and change the security settings on the checked out versions without making any other modification to the objects. Then Check In all the objects back.)

Synergy Classic client GUI troubles

Trouble: classic client running on Linux RH 5 machine behaves oddly:

- right-click does not work,
- no way to select more than one item at at time (several files in the tree view, or two versions on history view),
- mouse single click responding as a double-click should,
- backspace character typing garbage,
- strange fonts ...

What helps:

1. Make sure NumLock key is disabled. Vendor also suggest checking the CapsLock key.

2. Synergy Classic client GUI is governed by the number of setup files, that define fonts, colors and other application GUI qualities.

Original "CM Synergy - X Resource File" file Ccm is located in $CCM_HOME/etc contains the most of the setting. Upon machine setup this file has to be copied to the local X directory:

root# cp $CCM_HOME/etc/Ccm /usr/lib/X11/app-defaults

If you do not have root over the Linux machine try to copy the Ccm file into your home directory:
user# cp $CCM_HOME/etc/Ccm ~/

Also,

(found on vendor site)

If during ccm start, messages about undefined X attributes are displayed ...

If errors indicating undefined X attribtues are seen duing a Synergy session startp, it is possible the Ccm X app-defaults file isn't being found or was incorrectly installed, or there may be an incompatibility with the user's environment settings (i.e., XAPPLRESDIR, XFILESEARCHPATH or XUSERFILESEARCHPATH may be set).

This issue also can typically be resolved by copying the Ccm file from $CCM_HOME/etc to the user's $HOME directory. If the user is using XAPPLRESDIR, XFILESEARCHPATH or XUSERFILESEARCHPATH, add the location of the Ccm file to one of those paths. Stop and restart the CCM session to validate the solution.