Repository groups are set up on the IBM i to reflect how non-IBM i repositories are connected to the IBM i repository, so that information can be automatically propagated from the IBM i to these repositories. The propagated information consists of changes to task tracking and partitions on the IBM i, updated information checked in to the IBM i by a member of a work group and user initiated requests from the main "work with" panels on the IBM i.
Note that changes to objects made by a user on the IBM i are not propagated. For example, changes to a function are not propagated.
A change is propagated by automatically sending a check out for read-only transaction to a PC. Note that if an object is checked out for update on the non-IBM i repository, the propagation still overwrites this object. Thus, it is recommended that only one user updates an object at any one time. Refer to Task Tracking for more information. A user on this non-IBM i repository would need to check the object out for update again to be able to modify it.
It should be remembered that checking out is always partition-specific, in other words objects are only checked out to the allowed partitions defined in the PC definition of the member. Please refer to the Visual LANSA online help for more detail on checking objects in and out of an IBM i.