IBM SC34-4499-03 Working with parts, Working in serial or concurrent development mode, Dependent

Output The part will be a generated output from the same build that creates its parent part. In other words, both the parent part and this child part are outputs when the parent part is built.

Dependent

The part will be needed for the build operation of its parent to complete, but it will not be passed directly to the builder. An example of this is an include ®le.

If you do not provide this information when you create the part, you can provide it later using the connect function.

You can also specify the builder or parser that a part will use, as well as any build parameters.

ªPart 4. Using TeamConnection to build applicationsº on page 127 explains the build function in more detail.

Working with parts

After the parts are created in TeamConnection, you will be working with these parts Ð getting them to your workstation so you can change them and then getting them back in to TeamConnection. This section gives a brief overview of these tasks. ªChapter 5. Working with no component or release processesº on page 51 and ªChapter 6. Working with component and release processesº on page 77 go into more detail about these and other TeamConnection tasks.

Working in serial or concurrent development mode

A release is set up for either serial development or concurrent development mode. Once the development mode is set you can change from serial mode to concurrent mode, but not from concurrent mode to serial mode. In serial development, a part is locked when a user checks it out, and no one else can update the part as long as it is checked out. In concurrent development, more than one user can simultaneously have the same part checked out.

In concurrent development, more than one user can check out and change the same part. Prior to integrating their changes, each user should refresh their work area from the driver in which they plan to put it. The ®rst user will be able to integrate their work area, complete ®x records for tracking releases, with their release. When the next user refreshes their work area, TeamConnection recognizes that the parts differ and noti®es them. It is up to this user to resolve the differences, using the TeamConnection merge program, VisualAge TeamConnection VisualMerge Facility, or some other merge program. If the user fails to refresh their work area from the driver, TeamConnection will not notify them that the parts differ until they try to add the work area to the driver. They will then have to put the ®x records back in the ®x state, reactivate the work area, refresh the work area, reconcile the differences, refresh their work area again, and reintegrate their work area before they can add their changes to the driver.

Chapter 3. The basics of using TeamConnection 31