Context page

The context page is used to specify the TeamConnection family, release, and work area used as the context for the default bridge con®guration.

Family Use this ®eld to input the name of your TeamConnection family server. Select the Test Server pushbutton to return an information window that provides server-speci®c information. If you cannot successfully communicate with the TeamConnection server, you may have speci®ed an invalid family name. Your TeamConnection family administrator may be of some assistance at this point.

Release

The TeamConnection release. By selecting the Query releases pushbutton, you can prime the Release ®eld drop-down menu with valid release choices based on the Family ®eld value.

Work area

The TeamConnection work area in which you will perform TeamConnection actions. By selecting the Query work areas pushbutton, you can prime Work area ®eld drop-down menu with valid work area choices based on theRelease ®eld value.

Note: Any communication with a TeamConnection server takes time. Querying the available releases and work areas typically takes a few seconds, which is the reason that this data is not automatically used to populate the dialog.

Operations page

The Operations page determines how operations are performed in TeamConnection, including whether operations are forced and how parts in the database are locked.

Force The Force and Don't force radio buttons are mutually exclusive.

In TeamConnection terms, force is an indication that changes should be forced into the TeamConnection repository, possibly breaking links with the part in other version contexts. Its intent is to indicate that, although the speci®ed version might not match the current set of versions applicable to the object in the persistent store, the changes in those versions speci®ed in the version string are to be made, breaking the links to those current versions not speci®ed.

The force option is important only if you specify that a part version is to be locked. If you want to retrieve or store a locked part in a particular release or work area that is linked to another release or work area, you might want to specify the force option when you are checking in or checking out the part, even if someone else might have the part checked out in another context. See the discussion of locking below for a description of TeamConnection locking options.

Locking

These mutually-exclusive radio buttons enable you to instruct TeamConnection

256User's Guide

Page 276
Image 276
IBM SC34-4499-03 manual Context, Operations, Locking