Skip to content

Member Field

Member List Filters

If the first version—the base—is a library (PDS, PAN, or LIB type), you can leave the Member field blank or enter a pattern or a range, to work on a number of members. If other versions—the derivatives—are also libraries, you can proceed with multiple libraries' consolidation.

All Members

An empty Member field means that all members of the base version library will be included in the Consolidated Workplace for reconciling efforts.

Member Name Pattern

A pattern (like ABC*) entered in Member field will select only members whose name begins with that pattern.

Member Name Range

You can specify a range of members to be selected for reconciliation by entering the first member name (or pattern) in the Member field of the base and the last member name (or pattern) in the Last Member field.

Member Name Masks

Another way to select member versions for reconciliation is through masking the names so that slightly, but uniformly, different names can be aligned together. Using masks is critical for sites that keep all the member versions in one library by applying some naming convention. For example, consequent versions of a member may be ABC1, ABC2, and ABC3.

You can align such versions through suffix masks like *1, *2, and *3, entered in the Member fields of the Base, Drv1, and Drv2 version libraries.

Another example may be version names like AB1C, AB2C, and AB3C. You can specify position masks ??1*, ??2*, and ??3*, to align such members in version sets.

Yet another example may be version names like XABC, YABC, and ZABC; that is, the names of the subsequent version start with a different letter (or string). The prefix masks X*, Y*, and Z* will align such members in version sets.

M+R supports any reasonable combination of these types of masks, including all three of them; combining the above examples, the masks should look like X?1*1, Y?2*2, and Z?3*3, to align members XB1C1, YB2C2, and ZB3C3.

One Member/File

If the base is of SEQ type or you enter a full member name, only the versions of that program can be reconciled. You will have to specify a new set of versions for another reconciliation.

Type Field

The TYPE field refers to the data set organization of the base/derivatives. If it is PDS or SEQ, no entry is required. However, you must enter exactly "PAN" or "LIB" if that is the type for that particular version.

  • PAN refers to a CA Panvalet library (and members).

  • LIB refers to a CA Librarian library (and members).

NICKNAME Field

Nicknames are used for visual references in the Analysis and Reconcile panels. Use, for example, names like BASE, CUSTOM, NEW#RELS, FIX312. If no nickname is entered, M+R generates one with the format "SOURCE#" plus the respective ID. When you edit the merged versions, a new "version" is created. The generated nickname for editing actions is RECONCIL and the ID is the plus (+) sign.

ID Field

You have to assign an ID to each derivative. The ID is used to mark the origin of the changes coming from that derivative. Use letters A to Z for that purpose.