Skip to content

Team-Oriented Projects

You can create a team-oriented project in the same way you create an individual project. Set the Team Project option to YES. You can update, load, delete, and purge a teamoriented project if you are its owner. Otherwise, you can only select it to load the reconciliation task assigned to you by the team leader—that is, the owner of that project.

The Complexity Limit setting is important when a big M+R project will be divided between team members by the Degree of Complexity determined by M+R for each version set. The Complexity Limit is used to separate Middle and High Complexity version sets that will be assigned to programmers with corresponding qualifications. In short, the Complexity Limit allows you to determine how many conflicting changes in the versions will render a high degree of reconciliation complexity.

Low complexity (1 to 3) indicates no conflicts. The changes in the derivatives do not overlap or, if overlap, all the changes are the same.

To distinguish between Middle (4 to 6) and High (7 to 10) complexity, a threshold must be set. It is the ratio of the number of conflicts to the total number of changed lines of the base version. The default is 50 percent. If that ratio is below the threshold, the complexity is Middle; otherwise, it is High.

However, if there are conflicts involving more than two versions, the complexity is considered High, even when the ratio is below the threshold.

When you create a project, an entry is made in a shared M+R project data set: a sequential fixed length record data set which is allocated as a part of the M+R installation procedure. If this data set is not available, you will be presented with the following panel that explains how to remedy the situation.

...

SEROJECT-------------- M+R PROJECTS REPOSITORY ------------------------------  
Command ===> _________________________________________________________________

This panel displays only because the Merge+Reconcile installation has not been completed successfully.  
Press ENTER and ask your System Programmer to edit this SEROJECT panel. 
You won't be able to use the project management facility - Option 5 PROJECT 
and Option W Walk through M+R of the Primary Menu.    

A SEQuential data set needs to be allocated with Record format FB, Record 
length 80, Block size 6000, 1st extent 20 blocks, Secondary blocks 400.    

All M+R users should have read/write access to this data set that will 
contain information about the profiles of all team-oriented M+R Projects. 
The fully qualified name of this data set needs to be set in the )INIT section 
of this panel, as well as the fully qualified name of the M+R Samples data set.  
    M+R Projects DSNAME ===>   
    M+R Samples DSNAME  ===>

...

Each M+R project needs two profile data sets: one as an intermediate storage 
("Work In Suspense" or WIS ) and one for writing different M+R reports. The
preferred Unit Name and High Level Qualifiers for their allocation need to be 
set in the )INIT section. Defaults are SYSDA and User logon ID, respectively.
    WIS / Print Unit Name ===>   
    High Level Qualifiers ===>

Project Task Assignment

The purpose of creating team-oriented projects is the ability to assign blocks of version members to other user's user IDs. A big reconciliation can be divided on the following selectors:

  • Member name patterns.

  • Member name ranges.

  • Member name masks.

  • Degree of Complexity.

  • Source code language.

  • Specified members.

When a team member selects a project, all the profile options and working data sets are automatically set and the Consolidation Workplace panel lists only the relevant to him or her members.

When the team leader (project owner) selects a project, their Consolidation Workplace lists all the members and their status, including their current Degree of Complexity, which indicates the progress of the reconciliation work for each member.