IBM SC34-4499-03 Manuel d'utilisateur

Naviguer en ligne ou télécharger Manuel d'utilisateur pour Manuels des logiciels IBM SC34-4499-03. IBM SC34-4499-03 User's Manual Manuel d'utilisatio

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 356
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs

Résumé du contenu

Page 1 - User’s Guide

IBM VisualAge TeamConnection Enterprise ServerUser’s GuideVe r s i o n 3.0SC34-4499-03IBM

Page 2

Setting up your project options ...241Using your TeamConnection Workframe project ...242Project actions ...

Page 3

Accepting a defectWhen you accept a defect or feature, you accept the responsibility of resolving it. Adefect or feature might require changes in more

Page 4

CommandFrom a command line, he issues the following command:teamc defect -accept 456 -answer program_defectResultsDefect 456 moves to working state, a

Page 5 - Contents

CommandFrom a command line, they both issue the following command for the approval recordthat they have:teamc approval -accept -workarea 456 -release

Page 6

CommandFrom a command line, he issues the following command:teamc part -checkout optics.c -release robot_control -workarea 456-relative d:\robot\srcRe

Page 7 - Contents v

Note: Alex follows these steps because he knows the exact name of the part that he ischecking in. If he does not know the name, or if he is checking i

Page 8

arm.c foot.objarm.obj optics.c (Alex's modification 1)hand.c optics.objhand.objFreezing the work areaAlex now wants to save, or freeze, the worki

Page 9 - Contents vii

Note, however, that a freeze action does not make the changes visible to the otherpeople working in the release. This does not occur until the work ar

Page 10

Alex builds the application and tests the results. The modification seems to solve theproblem.Note: For a detailed build example, see “Chapter 15. Buil

Page 11 - Contents ix

Integrating changed parts into a releaseThe changes that Alex has made are now ready to be put into the next set of changesscheduled to be integrated

Page 12

Carol previously created a driver member for driver 0105 that included changes tooptics.c, so Carol is notified that collisions were detected. (Remembe

Page 13

Sample build scripts...305Sample parsers ...306Sample package files ...306Customer support ...

Page 14

Work area 456 is in the fix state. After the fix record is reactivated, Alex will check outoptics.c from this work area to reconcile the differences.Rea

Page 15

From the GUI, he:1. Selects Work areas → Refresh from the Actions pull-down menu on the Taskswindow.2. Types the following in the Refresh Work Areas w

Page 16

2. Types 0105 in the Drivers field and robot_control in the Release field.3. Selects OK.CommandFrom a command line, she issues the following command:tea

Page 17 - Trademarks

CommandFrom a command line, she issues the following command:teamc part -build brain.exe -release robot_control -workarea 0105 -pool normalResultsCaro

Page 18

CommandFrom a command line, she issues the following command:teamc driver -restrict 0105 -release robot_controlResultsThis command restricts driver 01

Page 19 - About this book

From a command line, she issues the following command:teamc driver -commit 0105 -release robot_controlResultsTeamConnection moves the part versions as

Page 20 - Tell us what you think

Testing the built applicationAnnmarie is the tester for the MVS version of the robot application. When she receivesnotification that the test record is

Page 21

Using a configured processThe scenarios in this chapter and the preceding chapter illustrate one release with noprocess management enabled and another

Page 22 - 2 User’s Guide

arm.c foot objarm.obj optics.c (modification 12)hand.c optics.obj (from Alex's build 12)hand.objNext Alex must update the brain.c part to set the

Page 23

workAreaName 1208releaseName robot_controlpredecessor 1208:2hasSuccessor yesreleaseVersion noaddDate 1995/01/14 11:13:25freezeDate 1995/01/15 09:01:35

Page 25 - Interfaces

Note: If the -where clause were not specified, the report would return all of the partsvisible from version 1208:2.The TeamConnection system returns th

Page 26 - Users and host lists

Part 3. Using TeamConnection Notes Integrated DatabasesChapter 7. Introduction to TeamConnection Integrated Notes Databases 103Getting started ...

Page 27 - Components

102 User’s Guide

Page 28 - Work areas

Chapter 7. Introduction to TeamConnection Integrated NotesDatabasesThe VisualAge TeamConnection Integrated Notes Database feature provides adocumentat

Page 29

Prerequisites and dependenciesIn preparation for setting up and administering the Lotus Notes Integration feature,ensure that the machine you are usin

Page 30 - Processes

TheAboutdocument provides graphical previews for the Requirements, Development,and Test database types. These previews provide a graphical depiction o

Page 31

the design. Documents existing in Notes can be associated with existingfeatures and defects in TeamConnection.Test Case Management and TrackingThe Tes

Page 32 - Roles people play

Table 1. Integrated database forms by database type (continued)Form Use for this formResponse to Response Document your response to another’s response

Page 33

specific document title. By using buttons on the action bar, you can choose to view thechildren documents of a parent document or category, all active

Page 34 - 14 User’s Guide

Table 2. Integrated database views (continued)View Documents accessed (purpose)Execution Records To list all of the execution records in the database.

Page 35

Figures1. A sample TeamConnection client/server network ... 52. Sample of a component hierarchy ... 73. Parts, releases, and compon

Page 36

110 User’s Guide

Page 37 - Using the GUI

Chapter 8. Creating and Maintaining Integrated Notes DatabasesThis section and the one that follows (“Chapter 9. Database Design Strategies andAdvance

Page 38 - Starting the GUI

The flow presented in the figure applies to all potential user databases availablethrough the Notes Integrated Database feature.Initializing the origina

Page 39 - Performing tasks with the GUI

3) The Server field should contain the Local value. You can supply the Title ofyour choice.4) Rename the file in the File Name field to match the naming

Page 40 - Using the Settings notebook

NoteSetup is a staging process that may require some planning. See“Chapter 9. Database Design Strategies and Advanced Customization” onpage 121 for de

Page 41 - Online help information

You should also add any users involved in the testing process to the access listfor this database. The default Access of Author is recommended.i. When

Page 42 - 22 User’s Guide

Creating customized production databasesNow that you have initialized the Integrated Notes Database feature and performed apreliminary setup of the da

Page 43

v Open Defects and/or Features.v Examine views.You should also add any users involved in the testing process to the access list forthis database. The

Page 44 - 24 User’s Guide

Performing reconciliationThe Reconciliation facility synchronizes the data in the TeamConnection family and theNotes databases that use it. The reconc

Page 45 - Laying the groundwork

Database maintenance: refreshing design from a templateIn the course of using Notes Integrated databases, you may have occasion to refreshcurrent data

Page 46 - Authority to perform tasks

47. TeamConnection components on separate machines ...13748. Create Builder window ...14849. Modify Part Properties window ...

Page 47 - Finding parts

v Reopen documents.v Select Feature and Defect push buttons.v Open Defects and/or Features.v Examine views.6. When you are satisfied that refreshing th

Page 48 - Using work areas

Chapter 9. Database Design Strategies and Advanced CustomizationThis section include some general strategies for setting up, testing, and tuning yourN

Page 49 - Creating parts

3. Assess and implement any access control/authorization schemes necessary at thislevel of implementation.4. Open the newly initialized database.5. Cr

Page 50 - Preparing to build your parts

The Customization setup facility addresses the following areas of databasemanipulation:v Notes Database Customizationv Modify TeamConnection Accessv R

Page 51 - Working with parts

response documents for the base documents you defined in the Modify whichdocuments your project will use section. This level of customization allowsyou

Page 52 - Working with common parts

Activate ReconcileThe Notes Integrated Database feature provides a reconciliation facility thatsynchronizes the data in the TeamConnection family and

Page 53 - Commands Reference

There are one or more subforms defined for all the Forms that allow user-definedsubforms. This allows you to augment or replace the subform supplied byT

Page 54 - 34 User’s Guide

Part 4. Using TeamConnection to build applicationsChapter 10. Basic build concepts ...129The physical structure of the build function ...

Page 55 - Versioning releases

Putting a parser to work ...178Removing a parser from a part ...179Chapter 15. Building an application: an example ...

Page 56 - Versioning work areas

Chapter 10. Basic build conceptsThis chapter defines terms and briefly describes the TeamConnection pieces that worktogether in building an application.

Page 57 - Versioning drivers

NoticesReferences in this publication to IBM products, programs, or services do not imply thatIBM intends to make these available in all countries in

Page 58 - Versioning parts

Build servers are started by a TeamConnection administrator. For more information, see“Chapter 11. Installing, starting, and stopping build servers” o

Page 59

Build scriptAn object that a builder uses in transforming inputs to outputs; it is essentiallya binding between TeamConnection and a transformation to

Page 60 - 40 User’s Guide

Though parent-child relationships usually imply that the parent part generates the childpart, in a TeamConnection build it is the opposite. Because Te

Page 61

Working with a build treeSoftware developers must provide the information by which TeamConnectiondetermines the build events that make up a build requ

Page 62 - 42 User’s Guide

A build tree is a simplified version of the build object model, showing the dependenciesthat the parts in an application have on one another. If you ch

Page 63

Putting the pieces togetherThe table that follows lists the tasks involved in preparing for building an application andin actually building it. Usuall

Page 64 - 44 User’s Guide

For more information about this task, Go to this page.Starting build servers “Chapter 11. Installing, starting, andstopping build servers” on page 137

Page 65 - The states of work areas

Chapter 11. Installing, starting, and stopping build serversThis chapter explains how to install, start, and stop a build server.Installing the build

Page 66 - 46 User’s Guide

The following are software requirements for the MVS build server:v TCP/IP Version 3.2 for MVSv OS/390 R3 LETo install the build server on MVS, you cre

Page 67 - The states of drivers

Note: The file fhbmsg.mvs is installed in the language subdirectory of the\nls\msg directory path in the TeamConnection installation directory, forexam

Page 69 - Verification and test records

2. From the oe subdirectory where TeamConnection is installed, use ftp to upload thefollowing files to MVS/OE, in binary.v rename teamcbld.oe to teamcb

Page 70 - 50 User’s Guide

v -s sends log file messages to the screen.The build server generates a log file calledteamcbld.log. Build server log messages can be routed to the scre

Page 71 - Working in serial development

– TC_BUILDMINWAIT - Minimum amount of time to wait (in seconds) betweenqueries for new jobs. Default setting is 5, minimum setting is 3.– TC_BUILDMAXW

Page 72

vunit_nameindicates the default unit type for dynamic data set allocations. VIO isthe default.vlogin_passwordis required only when the family server a

Page 73 - Creating a work area

vlogin_passwordis used only when the family server authentication level requires aTeamConnection user password. The user ID used by the build server i

Page 74

You can store the build startup files wherever you like, provided that you give the fullfile path names for them in the -b parameters, or in the TC_BUIL

Page 76 - 56 User’s Guide

Chapter 12. Working with build scripts and buildersA builder is an object that can transform one set of TeamConnection parts into anotherby invoking t

Page 77

To create a builder using the command line:From a command line, type the teamc builder -create command and press Enter.The complete command syntax is

Page 78 - Checking in a part

To use the builder from a previous release, you can link to a part that uses it inthat release. This action copies the builder to the new release. Oth

Page 79

TrademarksThe following terms are trademarks of International Business Machines Corporation inthe United States and/or other countries:AIX® NetView®C/

Page 80 - 60 User’s Guide

starting, and stopping build servers” on page 137 for more information.) It isrecommended that you follow a naming convention for this attribute, usin

Page 81 - Figure 12. Build Parts window

Passing parameters to a build scriptThere are three places where parameters can be specified that affect the outcome of abuild.As attributes of a build

Page 82 - Extracting a part

Note: There is a one-to-one relationship between each object in theTC_OUTPUT list and this list of types (TCPart, for example).TC_WORKAREAThe name of

Page 83 - Figure 14. Check Out Parts

Writing a simple build scriptThis kind of build script is written into the Script attribute of the builder. When youcreate or modify the builder, you

Page 84 - Checking the part back in

debug = VALUE('DEBUG',,environ)if debug = 'YES' thendoparms = parms || '/Ti+'endicc parms '/Fo'||output inpute

Page 85

DEBUG parameters, and then runs the command file against a local copy of hello.c. Ifthe test is successful, the script correctly builds hello.obj in th

Page 86

v From a command line, type the following and press Enter.teamc part -modify name -Builder namewhere the partnameis the name of the output file to be c

Page 87

v From a command line, type the following:teamc part -modify name -builder null -release name -family nameWorking with VisualAge C++ and TemplatesWhen

Page 89 - Closing a defect

Chapter 13. Working with MVS build scripts and buildersA builder is an object that can transform one set of TeamConnection parts into anotherby invoki

Page 90 - 70 User’s Guide

Adobe, the Adobe logo, Acrobat, the Acrobat logo, Acrobat Reader, and PostScript aretrademarks of Adobe Systems Incorporated.Other company, product, a

Page 91

To create a builder using the command line:From an OS/2 command line, type the builder -create command and press Enter.The complete command syntax is

Page 92

To use the builder from a previous release, you can link to a part that uses it inthe previous release. This action copies the builder to the new rele

Page 93 - Reconciling differences

See “Synchronizing the build of unrelated parts” on page 196 for an example.EnvironmentThis is the name of the environment supported by the builder, s

Page 94 - 74 User’s Guide

handling the timing of MVS builds is to start the MVS build server only at nightand ensure that the MVS builders do not have short timeout values.Writ

Page 95

File name conversions for MVSTeamConnection file names are modified by the MVS build server according to thefollowing rules:v The directory path of a fil

Page 96 - 76 User’s Guide

&TCBLDUSROn MVS, can be used in JCL scripts, which will be substituted with the userIDbefore processing the script.&TCINPUTThis variable is us

Page 97 - Accepting the defect 80

– Selecting Part → View → View build message from the Actions pull-down menuon the Tasks windowNote: More than one ddname can specify TCOUT; the resul

Page 98 - 78 User’s Guide

v PARM='information', whereinformationis the parameter string passed to the loadmodule.v COND=(code,operator[,stepname])–codeis the value to

Page 99 - Changing defect ownership

This will always be allocated as a DUMMY DSN.All other keyword parameters are ignored and not used.Example of a build script for a C compileThe follow

Page 100 - Accepting a defect

The first step in converting the JCL fragment is to recognize the intent for each of thedata sets and ddnames. For this C/370 compiler example, the SYS

Page 101 - Approving the fix

About this bookThis book is part of the documentation library supporting the IBM TeamConnectionlicensed programs. It is a guide for client users.For a

Page 102 - Checking out a part

Example of a build script for a COBOL compileTeamConnection provides a sample build script program for compiling MVS COBOLprograms. This sample is cal

Page 103 - Checking in the changes

//*------------------------------------------------------//* PROGRAM: cobolcmp.jcl//* IBM COBOL for MVS//* Compile Only//*//*-------------------------

Page 104 - 84 User’s Guide

This syntax is a subset of the linkage editor INCLUDE card.If the card is an INCLUDE ddname(MEMBER) control statement, the object code iscopied into a

Page 105 - Freezing the work area

The output specified in INCLUDE OBJECT(OUTPUT) contains embedded control statementsspecified from the build script FHBTCLNK. The linkage editor recogniz

Page 107 - Accepting fix records

Chapter 14. Working with parsersThis chapter describes how to create a parser. It assumes that you have read“Chapter 10. Basic build concepts” on page

Page 108 - Adding a driver member

From a command line, type the parser -create command and press Enter. The completecommand syntax looks like the following:teamc parser -create name -c

Page 109 - Reconciling the differences

v A dependency in which the file is stored in the TeamConnection database.For example, hello.c includes hello.h, and both files are stored in theTeamCon

Page 110 - Refreshing the work area

3. Writes out the list of such files into the dependency list fileFor example, for a C source file, the program could report a list of all the files inclu

Page 111 - Refreshing the driver

After you attach a parser to a part, it is ready for action. The next time the part ischecked in, when a part is created, or when the parser is attach

Page 113 - Restricting the driver

vItalicsare used to indicate the first occurrence of a word or phrase that is defined inthe glossary. They are also used for information that you must r

Page 114 - Integrating the parts

v From a command line, type the following:teamc part -modify name -parser null-release name -family nameFigure 56. Modify Part Properties window180 Us

Page 115 - Completing the driver

Chapter 15. Building an application: an exampleThis chapter uses an extended example to describe in more detail how each of thecomponents of the build

Page 116 - Testing the built application

For more examples of build trees, see “More sample build trees” on page 195.In terms of the build object model, the objects that make up this tree loo

Page 117 - Using a configured process

Starting the build serversThe software development team in our example is building large applications using afamily named testfam, so they set TC_FAMI

Page 118 - 98 User’s Guide

mvspoolFor MVS buildspool1 For normal OS/2 buildspool2 For fast, high-priority OS/2 buildsEach pool is formed as Mark starts build servers and assigns

Page 119

builder c_linker, and the parent of hello.obj and bye.obj. Because the file has nocontents initially, he selects No source (or specifies -empty on the c

Page 120 - 100 User’s Guide

2. Creates two place-holder parts for the output of compiling the .c files. These partsare the output of the compile step; c_compiler, the builder that

Page 121

teamc part -create hello.obj bye.obj -builder c_compiler -binary -empty-release 9503 -workarea 223 -component comp1 -parent msgcat.exe -inputteamc par

Page 122 - 102 User’s Guide

Using the command-line interface, he can connect these parts by issuing thefollowing commands:teamc part -connect hello.c -parent hello.obj -input -re

Page 123 - Databases

Starting the build on the clientAfter much hard work on his source code, Greg is ready to start building his application.Using the GUI, he can start t

Page 124 - Sources of user information

Part 1. Introducing TeamConnectionChapter 1. An introduction to TeamConnection... 3TeamConnection definitions ... 4TeamConnect

Page 125 - Database types

Using the command-line interface, he can start the build by issuing the followingcommand:teamc part -build msgcat.exe -release 9503 -workarea 223-pool

Page 126 - Forms and subforms

UnconditionalBuilds only parts that are out-of-date but continues processing even iferrors are returned. Note that outputs are not rebuilt for inputs

Page 127

In our example, each of the build servers receives a compile event to perform. Eachextracts the .c source files it needs from the TeamConnection databa

Page 128 - 108 User’s Guide

Build of 'bye.obj' successfully completed at '15:35:22 1995-08-10'.Completed Jobs: 2Remaining Jobs: 1Build of 'msgcat.exe&apo

Page 129 - Document archiving

Finding out which parts will be builtBefore running a build of a large application, you might want to find out exactly whichparts will be built. If you

Page 130 - 110 User’s Guide

This command will stop all queued and in_progress builds. Any build events alreadyperformed for that build are not undone.For example, if Greg cancels

Page 131

teamc part -build robot.dll -workarea 915 -release 9503The output of this build would be both robot.dll and robot.map. Any parametersspecified in the t

Page 132 - 112 User’s Guide

The -none flag identifies this as a part that will never have any contents.3. Tim connects the other parts to the collector:teamc part -connect robot.dl

Page 133

198 User’s Guide

Page 134 - 114 User’s Guide

Part 5. Using TeamConnection to package productsChapter 16. Using TeamConnection to package a product ...201Setting up your build tree for packag

Page 135

2 User’s Guide

Page 137

Chapter 16. Using TeamConnection to package a productAfter you have built an application to your satisfaction, it is time to distribute it to users.Th

Page 138 - Performing reconciliation

Setting up your build tree for packagingWhen TeamConnection builds an application, the application’s build tree identifies theparts to be built and the

Page 139

existing structure, with parts contained in directories according to their applicationcomponent. A better structure might be to place all of the .dll

Page 140 - 120 User’s Guide

The package file, robot.pkf, specifies the directories into which the robot files aregathered, with e:\robot as the target root directory. When Annmarie

Page 141

Chapter 17. Using the Gather toolThe Gather tool automates the movement of software and data from one directory toanother on the same machine to prepa

Page 142 - 122 User’s Guide

teamcpak [-i] [-o "String"] gather Input_file...Where-i Specifies that only oneInput_fileis specified in the command: an include filecontaining

Page 143 - Notes Database Customization

-f Force deletion from the root: if this is used in combination with -t or -c andTARGETROOT is a root directory (for example, e:\, \, /).-t Ensure tha

Page 144 - Modify TeamConnection Access

Examples of the teamcpak gather commandThe following are examples of the teamcpak gather command.teamcpak gather d:\demoapp demoapp.pkfteamcpak gather

Page 145 - Advanced customization

(DATA(PACKAGEFORMAT gather)(TARGETROOT Filename)(RULE(SOURCE Filename...)(TARGET Path)[(EXITPRIOR String... | EXITREPLACE String... | EXITPOST String.

Page 146 - 126 User’s Guide

Chapter 1. An introduction to TeamConnectionTeamConnection provides an environment and tools to make software development runsmoothly, whether your de

Page 147

TARGET keyword. The files in the SOURCE directory are copied to theTARGET path. The target path is derived by concatenating the value ofTARGETROOT with

Page 148 - 128 User’s Guide

The resulting source path is the concatenation of d:\demoapp with theSOURCE file specifications. Therefore, all of the .exe files in the directoryd:\demo

Page 149

(DATA(TARGETROOT f:\demoapp )..(RULE(SOURCE *.bin *.dll )(TARGET bin\files ))(RULE(SOURCE *.hlp )(TARGET targetroot ))..)EXITPRIOR, EXITPOST, and EXIT

Page 150 - The build object model

v The resolved SOURCE file specificationsv The resolved TARGET specificationThe exit keyword accepts any executable file or command. The exit program must

Page 151

214 User’s Guide

Page 152 - 132 User’s Guide

Chapter 18. Using the Tivoli Software Distribution packaging toolThe Tivoli Software Distribution packaging tool supports automated distribution betwe

Page 153 - Working with a build tree

-o "string"Specifies that the string listed in quotes be passed to the Tivoli SoftwareDistribution tool. For a list of possible flags to be pa

Page 154 - 134 User’s Guide

Example of the teamcpak softdist commandThe following is an example of the teamcpak softdist command.teamcpak -i -o "-a -n -t" softdist Clie

Page 155 - Putting the pieces together

[(LOGNODE ManagedNode)][(LOGFILE directory)]))Keywords for a Tivoli Software Distribution package fileDATA This keyword is required. It must be the firs

Page 156 - 136 User’s Guide

(DATA..(MANAGER Distrib1)..NODESThis keyword specifies the nodes to which the files are to be distributed. Thesemust already have been defined to the pro

Page 157 - Installing the build function

Topic and description PageDeveloping products using TeamConnection:v Getting familiar with the interfacesv The basics of using TeamConnectionv More ab

Page 158 - 138 User’s Guide

(DATA..(DISTRIBUTE CHANGED)..INSTALLPGMUse this keyword to specify an installation script to be run during distributionon each node that receives files

Page 159

Log fileCheck the file name you specified in the LOGFILE keyword for errormessages.Mail Check Tivoli mail messages generated during the distribution.-k o

Page 160 - 140 User’s Guide

v The Client.lst file you create containing the list of files passed to teamcpak. The firstline contains the package file by convention. The example also

Page 161 - Starting an MVS build server

elseprint -u3 /.profile already updatedfi# Set up error logging# - if *.warning is in file (preceeded by spaces and tabs onlygrep "|[]*\*.warning

Page 162 - 142 User’s Guide

else# Clean up installation directory after listing contentsprint -u3 We have successfully copied TeamC installation filesprint -u3 Installation direc

Page 163

Part 6. AppendixesThe following appendixes contain various pieces of information that you can refer to asyou plan for and use TeamConnection.© Copyrig

Page 165 - Stopping an MVS build server

Appendix A. Environment VariablesYou can set environment variables to describe the TeamConnection environment inwhich you are working. You are not req

Page 166 - 146 User’s Guide

Table 3. TeamConnection environment variables (continued)Environment variable Purpose Flag Setting Used byNLSPATH Specifies the search path forlocating

Page 167 - Creating a builder

Table 3. TeamConnection environment variables (continued)Environment variable Purpose Flag Setting Used byTC_BUILDMAXWAIT Maximum amount of time towai

Page 168 - 148 User’s Guide

TeamConnectionfamily serverscontrol all data within the TeamConnection environment.Data stored in a family server’s database includes:v Text objects,

Page 169

Table 3. TeamConnection environment variables (continued)Environment variable Purpose Flag Setting Used byTC_BUILD_RSSBUILDS_FILE Specifies the name of

Page 170 - Writing a build script

Table 3. TeamConnection environment variables (continued)Environment variable Purpose Flag Setting Used byTC_MAKEIMPORTRULES Specifies the name of the

Page 171

Table 3. TeamConnection environment variables (continued)Environment variable Purpose Flag Setting Used byTC_MODPERM Controls whether or not theread-o

Page 172 - 152 User’s Guide

Table 3. TeamConnection environment variables (continued)Environment variable Purpose Flag Setting Used byTC_TRACESIZE Specifies the maximum size ofthe

Page 173 - Writing a simple build script

Table 4. TeamConnection dynamically set build environment variables (continued)Environment variable Purpose Flag Setting Used byTC_LOCATION Directory

Page 174 - Testing a build script

Appendix B. Importing makefile information into TeamConnectionTeamConnection provides a command to help you import makefile information into theTeamConn

Page 175 - Putting a builder to work

found, TeamConnection uses default rules. “Creating a rules file” on page 237explains the rules, the format of this file, and the default rules./x Speci

Page 176 - 156 User’s Guide

used in the commands is mywork. After the commands are issued, the resulting buildtree is shown using the TeamConnection GUI.Creating a rules fileThe i

Page 177

v * indicates to use the name in the makefile, relative to the current workingdirectory.For example, if a makefile specifies a file src\abc.cbl and the ma

Page 178 - 158 User’s Guide

Appendix C. TeamConnection MergeThe TeamConnection VisualMerge provides a way for you to merge two or threeselected files together to make one single fi

Page 179

You can use any interface to do your TeamConnection work, or you can switch amongthem. This book usually gives instructions for using both interfaces.

Page 180 - 160 User’s Guide

The following lists the parameters which may be used with the tcmerge command.Parameter Description<file1|directory1> First file or directory to

Page 181

Appendix D. Enabling an OS/2 Workframe project forTeamConnectionTeamConnection lets you create a Workframe version 3 project that hasTeamConnection op

Page 182 - 162 User’s Guide

Query maskAny valid TeamConnection -where clause for parts. Leave blank to see allparts. (This is used in the project’s Show Parts action.)Show filterC

Page 183 - Writing an MVS build script

View part informationDisplays an unprimed View Part Information window.Edit partDisplays an unprimed Edit Part window.Show partsIf the project attribu

Page 184 - File name conversions for MVS

Using your project: a simple scenarioSuppose you are working on a defect in the family FAMILY1, release REL1_1. Youhave created a TeamConnection work

Page 185

Appendix E. Enabling a Workframe/NT project for TeamConnectionTeamConnection lets you create a Workframe/NT project that has TeamConnectionoptions as

Page 186 - EXEC statement

TC_BECOMEThe current TeamConnection user. Required for all commands.TC_RELEASEThe current TeamConnection release. Required for all commands.TC_COMPONE

Page 187 - DD STATEMENT

Part actionsThe current release and work area are specified with environment variables. See“Setting up your project options:” on page 245.TC Extract Pa

Page 189

Appendix F. Enabling and Using the ENVY/Manager-TeamConnection BridgeOverview of the ENVY/Manager-TeamConnection BridgeENVY provides a repository with

Page 190 - 170 User’s Guide

Check outTo get a copy of a part so that you can make changes to it.Check inTo put the changed part back into TeamConnection.Extract To get a copy of

Page 191

Scope of this documentationThis documentation is intended for users and administrators installing and using thebridge. It is assumed that you familiar

Page 192 - 172 User’s Guide

How the bridge communicates with TeamConnectionThe bridge functions are initiated from within the VisualAge Smalltalk environment.Each operation that

Page 193

These configuration maps should be imported into your development library so that itcan be loaded by all of the users sharing that library. The step-by

Page 194 - 174 User’s Guide

v TC_COMPONENT is used as the default TeamConnection component for partsstored in TeamConnection through the bridge. If TC_COMPONENT is not defined ori

Page 195 - Creating a parser

developers” on page 261, you must also import the configuration map called VAGenENVY/TC Bridge, as described in the previous steps.8. Select the OK pus

Page 196 - 176 User’s Guide

Using the ENVY/Manager-TeamConnection BridgeYou can perform TeamConnection functions on ENVY components, provided that yousupply parameters necessary

Page 197 - Writing a parser command file

Context pageThe context page is used to specify the TeamConnection family, release, and work areaused as the context for the default bridge configurati

Page 198 - Putting a parser to work

cache services (TCCS) on how to manage the locking behavior for parts thatyou are exporting to or importing from the TeamConnection repository.Obtain

Page 199 - Removing a parser from a part

Replace existing filesFiles that currently exist in the target directory are automaticallyoverwritten.Export pageThe Export page provides default setti

Page 200 - 180 User’s Guide

mismatches. If you make a change to an application, it is important to update all theexported configuration maps that contain the application and to ex

Page 201

v The users who have access to the component and the level of access each userhas. This information makes up the component’saccess list.v The users wh

Page 202 - 182 User’s Guide

Note: ENVY components must be versioned in ENVY before being exported toTeamConnection.2. In the Selection Required window, select the desired configur

Page 203 - Starting the build servers

1. Select Configuration Maps, Applications,orFiles from the Import cascademenu.2. If the Show this dialog when exporting and importing option has been

Page 204 - Creating builders and parsers

v A development team using VisualAge Generator wants to perform problem trackingand build generation.v A family is created in TeamConnection with a re

Page 205

BOM file for each application contains an entry (at least the name,edition/timestamp, and TCPart type) for each class and method in eachapplication.Obj

Page 206 - 186 User’s Guide

Refer to the VisualAge GeneratorGenerator’s Guidefor more details on the OVRpart.2. In TeamConnection (build function):a. The build administrator sele

Page 207

f. If there are tables and/or map groups used by the program, the generatordetermines whether there is already a build tree for them. If not, initial

Page 208 - 188 User’s Guide

4. In TeamConnection (change control):v A project administrator completes the fix record(s) for the defect d1 and adds thework area wa2 to a system tes

Page 209

Appendix G. Source Code Control User’s GuideDifferences between other source code control providers and TeamConnectionThe purpose of this document is

Page 210 - 190 User’s Guide

Components are used to organize the data in a family. Components are arranged in ahierarchical tree structure, with a single top component called root

Page 211

Note: If you have not already done so, follow the directions and install theTeamConnection client for your workstation. The following directions assum

Page 212 - 192 User’s Guide

track of all of these changes, even when more than one user updates the same part atthe same time. To make this possible, TeamConnection uses somethin

Page 213

– Port Addressv Componentv Releasev WorkAreaYou also need to know the project name. The project name is used by yourdevelopment tool to relate to the

Page 214 - Canceling a build

Check-inThe steps to check-in a file vary by the development environment. In most casespressing mouse button 2 when the mouse pointer is over a file ico

Page 215 - More sample build trees

designate TeamConnection as the Source Code Control provider. From theTeamConnection GUI you can create new work areas (if you have the correct author

Page 216 - 196 User’s Guide

Starting a new projectStarting a new project in Microsoft Visual Basic, Visual C++, or PowerBuilder isessentially the same regardless of the source co

Page 217 - -release 9503

7. To place the files under source code control, select the Add to Source CodeControl option of the Tools menu.Starting PowerBuilder:To create a new pr

Page 218 - 198 User’s Guide

Appendix H. Supported expandable keywordsTeamConnection supports expandable keywords in text files. When a file containingexpandable keywords is extract

Page 219

keyword to appear in the output, add a minus sign (-) after the dollar sign ($). Forexample, if the statement is prepared as follows:static char _file

Page 220 - 200 User’s Guide

Appendix I. Authority and notification for TeamConnection actionsTeamConnection ships with IBM-supplied authority groups, interest groups, componentpro

Page 221

For this action These users have authority These users are notifiedAccessDeletev Component ownerv Explicitly defined for the component where accessis be

Page 222 - 202 User’s Guide

For this action These users have authority These users are notifiedApproverCreatev Release ownerv Explicitly defined for the component that managesthe a

Page 223

IBM VisualAge TeamConnection Enterprise ServerUser’s GuideVe r s i o n 3.0SC34-4499-03IBM

Page 224 - 204 User’s Guide

Defects and featuresA defect is a record of a problem to be fixed. A feature is a record of a request for afunctional addition or enhancement. Both may

Page 225

For this action These users have authority These users are notifiedCollisionRejectv Component ownerv Explicitly defined for the component that managesth

Page 226 - Command line flags

For this action These users have authority These users are notifiedCoreqDeletev Work area owner of all specified work areasv Explicitly defined for the c

Page 227

For this action These users have authority These users are notifiedDefectModifyv Defect owner can modify:– answer, abstract, environment, driver, prefix

Page 228 - 208 User’s Guide

For this action These users have authority These users are notifiedDefectVerifyv Defect ownerv Explicitly defined for the component associated withthe d

Page 229

For this action These users have authority These users are notifiedDriverExtractv Driver ownerv Explicitly defined for the component associated withthe

Page 230 - 210 User’s Guide

For this action These users have authority These users are notifiedEnvModifyv Release ownerv Explicitly defined for the component associated withthe rel

Page 231

For this action These users have authority These users are notifiedFeatureModifyv Feature owner can modify:– abstract, prefix, reference, and all configu

Page 232 - 212 User’s Guide

For this action These users have authority These users are notifiedFeatureVerifyv Feature ownerv Explicitly defined for the component associated withthe

Page 233

For this action These users have authority These users are notifiedHostCreatev Owner of the user ID for which a host list entry isbeing created or dele

Page 234 - 214 User’s Guide

For this action These users have authority These users are notifiedNotifyDeletev Component ownerv Owner of user IDv Explicitly defined for the component

Page 235

the parts modified for the specified defect or feature in one release andrecords the status of the defect or feature. The work area moves throughsuccess

Page 236

For this action These users have authority These users are notifiedPartCheckOutv Component ownerv Explicitly defined for the component associated withth

Page 237

For this action These users have authority These users are notifiedPartLinkv Component ownerv Explicitly defined for the component associated withthe pa

Page 238 - 218 User’s Guide

For this action These users have authority These users are notifiedPartRecreateForcev Component ownerv Explicitly defined for the component associated w

Page 239

For this action These users have authority These users are notifiedPartUndoForcev Component ownerv Explicitly defined for the component associated witht

Page 240 - 220 User’s Guide

For this action These users have authority These users are notifiedReleaseExtractv Release ownerv Explicitly defined for the component associated withth

Page 241 - Sample package file

For this action These users have authority These users are notifiedShadowCreate Explicitly defined for the component associated withthe releaseNot appli

Page 242 - 222 User’s Guide

For this action These users have authority These users are notifiedSizeRejectv Sizing record ownerv Explicitly defined for the component associated with

Page 243

For this action These users have authority These users are notifiedVerifyAbstainv Verification record ownerv Explicitly defined for the component associa

Page 244 - 224 User’s Guide

For this action These users have authority These users are notifiedWorkAreaCompletv Work area ownerv Explicitly defined for the component associated wit

Page 245 - Part 6. Appendixes

For this action These users have authority These users are notifiedWorkAreaTestv Work area ownerv Explicitly defined for the component associated withth

Page 246 - 226 User’s Guide

v Tracks build times of inputs and outputs so that it builds only those parts that are outof date themselves or that have out of date dependents. You

Page 247

300 User’s Guide

Page 248 - 228 User’s Guide

Appendix J. Sample REXX execs, build scripts, and parsersThis appendix is composed of the IBM-supplied REXX execs, build scripts, and parsers.Your fam

Page 249

Script name Function Inputs EnvironmentvariablesdefClone Creates a new defect based on valuescontained in a specified defect.defectNumber TC_FAMILY[TC_

Page 250 - 230 User’s Guide

Script name Function Inputs EnvironmentvariablesdrvrMem Lists the defect and feature members of aspecified driver for a specified release.driverName[rel

Page 251

Script name Function Inputs EnvironmentvariablesprtWaGt Extracts all the parts associated with aspecific work area and places them in thepath specified

Page 252 - 232 User’s Guide

Sample build scriptsfhbcob2.cmdCalls the COBOL Visual Set for OS/2 compiler.fhbcob2l.cmdCalls the COBOL Visual Set for OS/2 compiler and link editor.f

Page 253

fhbwcomp.cCalls the Microsoft Visual C++ compilerfhbwlink.cCalls the Microsoft linkergather.cmdCalls the Gather tool.Sample parsersfhbcbprs.cmdA parse

Page 254 - Setting environment variables

Customer supportYour options for IBM VisualAge TeamConnection Enterprise Server support, asdescribed in your License Information and Licensed Program

Page 255

DB2 service maintenance and technical libraryTo download the latest service maintenance for DB2, use the DB2 Service and Supporton the World Wide Web

Page 256 - 236 User’s Guide

BibliographyIBM VisualAge TeamConnection Enterprise Server libraryThe following is a list of the TeamConnection publications. For a list of otherpubli

Page 257 - Creating a rules file

v Maintaining one or more familiesv Creating and updating configurable fieldsv Configuring release and component processes for a familyv Creating and upd

Page 258 - 238 User’s Guide

TeamConnection technical reportsThe following is a list of technical reports available for TeamConnection. Refer to theIBM VisualAge TeamConnection En

Page 259

Describes how to monitor DB2 database activity and analyze system performance.v GlossaryA comprehensive glossary of DB2 terms.Related publicationsv Tr

Page 261 - TeamConnection

GlossaryThis glossary includes terms and definitions fromtheIBM Dictionary of Computing, 10th edition(New York: McGraw-Hill, 1993). If you do not findth

Page 262 - Project actions

build associate. A TeamConnection part that isnot an input to or an output from a build. Anexample of such a part is a read.me file.build cache. A dire

Page 263 - Part actions

v The work area or driver’s releasev Another work areaTeamConnection generates a collision recordwhen a user attempts to replace an older versionof a

Page 264 - 244 User’s Guide

defect. A TeamConnection object used toformally report a problem. The user who opens adefect is the defect originator.delete. If you delete a developm

Page 265

development project can be created as aTeamConnection file. Examples include sourcecode, executable programs, documentation, andtest cases.file allocati

Page 266

automatically granted through inheritance or objectownership. Contrast withbase authorityandexplicit authority.import. To bring in data. In TeamConnec

Page 267

originator. The user who opens a defect orfeature and is responsible for verifying theoutcome of the defect or feature on a verificationrecord. This re

Page 269 - TeamConnection Bridge

restricted authority. The limitation on a user’sability to perform certain actions at a specificcomponent. Authority can be restricted by thesuperuser,

Page 270 - Basic functionality

TeamConnection part. A part that is stored bythe TeamConnection server and retrieved by apath name, release, type, and work area. See alsopart,common

Page 271

firmware) used with the product properly exchangeaccurate date data with it.322 User’s Guide

Page 272 - Environment variables

IndexSpecial Characters/Ft(dir) builder parameter 157AAccept Defects window 52Accept Test Records 96Activate Fix Records 90Add Driver Members 88approv

Page 273

builder(continued)for MVScreating 159environment supported 162naming 160passing parameters to a build script 164versions of 160for OS/2creating 147env

Page 274 - 254 User’s Guide

concurrent developmentdefinition of 51example of 34, 70how to work in 31reconciling differences in no-track process 73reconciling differences in tracki

Page 275 - Setting default properties

examples of(continued)starting make import 236teamcpak command for Gather 208teamcpak command for NVBridge 217writing a build script 153expand keyword

Page 276 - Operations page

Hhelpdiagram push button 21how do I 21how to access 21hierarchycomponent example 7displaying component structure 25how do I help 21Iimporting makefile

Page 277 - Import page

parameters(continued)where specified(continued)attributes of part in a build tree 152parameters of part -build command 152parser commandconnecting pars

Page 278 - Export page

releases(continued)using a configured process 97versioning 35report commandlisting work areas in a release 100searching for parts 57to find parts 27used

Page 279

Part 2. Developing a product using TeamConnectionChapter 2. Getting familiar with the TeamConnection client interfaces ...17Using the GUI...

Page 280 - Exporting files

TC_CASESENSE 227TC_COMPONENT 22, 227, 238TC_DBPATH 227TC_FAMILY 22, 51, 151, 183, 227, 234, 235, 236, 245,301TC_INPUT 151, 153, 154, 245TC_INPUTTYPE 1

Page 281 - Scenario assumptions

window examples(continued)Parts Filter 27, 56Reconcile Collision Record 74Refresh Drivers 92Refresh Work Areas 66Restrict Driver 93Tasks 18Verify Defe

Page 283 - Build generation

Readers’ Comments — We’d Like to Hear from YouIBM VisualAge TeamConnection Enterprise ServerUser’s GuideVersion 3.0Publication No. SC34-4499-03Overall

Page 284 - 264 User’s Guide

Readers’ Comments — We’d Like to Hear from YouSC34-4499-03SC34-4499-03IBMRCut or FoldAlong LineCut or FoldAlong LineFold and Tape Please do not staple

Page 286 - 266 User’s Guide

IBMRPrinted in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.SC34-4499-03

Page 287 - Projects vs Families

Verifying and testing part updates ...60Extracting a part ...62Checking out the part one more time ...63Chec

Page 288 - 268 User’s Guide

Chapter 2. Getting familiar with the TeamConnection clientinterfacesTeamConnection provides several interfaces that you can use to access data:v A gra

Page 289 - Before you start

If you are using AIX, HP_UX, or Solaris and are about to use the GUI for the first time,you need to do the following tasks:1. SeeConfigure the environme

Page 290 - Integrated features

Initially, a set of default tasks appears in your Tasks window. As you become morefamiliar with TeamConnection and see what tasks you do most often, y

Page 291

Fourth Edition (March 1998)NoteBefore using this document, read the general information under “Notices” on page xiii.This edition applies to Version 3

Page 292 - Migrating project data bases

Using the Settings notebookThe TeamConnection GUI provides a Settings notebook in which you can set defaultvalues for your working environment. To ope

Page 293 - Starting a new project

On the Extract page:v Destination directoryv Read-onlyv Expand keywordsOn the Pool page:v PoolOnline help informationOnline help information is availa

Page 294 - 274 User’s Guide

TheQuick Commands Referenceis a booklet that lists the syntax of eachTeamConnection command.You can also become familiar with the commands by looking

Page 295

currently available, most other familiar TeamConnection functions are available throughthe Web client. If you want to disable the Web Client interface

Page 296 - 276 User’s Guide

v For the ChangeView action, the following are available with the TeamConnection webclient (but not the TeamConnection GUI):– ChangeView– workAreaStat

Page 297

Chapter 3. The basics of using TeamConnectionAll users of TeamConnection perform a number of basic tasks, such as checking partsout of TeamConnection

Page 298 - 278 User’s Guide

From a command prompt, you can issue the following command to view the componentstructure.teamc report -view -raw bCompView -where "name='ro

Page 299

Note: You can issue queries to generate reports of data from tables and views usingthe -view action flag. If you do not specify selection criteria, suc

Page 300 - 280 User’s Guide

BuildViewUse when you want to search for information related to building yourapplication, such as viewing a build tree, or when you want to do build a

Page 301

version of the work area. For example, you might be adding a major feature to thecode, and you want to be able to return to something that works in ca

Page 302 - 282 User’s Guide

ContentsFigures... xiNotices...xiiiTrademarks ...xvAbout this book...

Page 303

Use the online help facility if you need assistance when creating parts.Naming your partsIf your organization has a naming convention, be sure to foll

Page 304 - 284 User’s Guide

Output The part will be a generated output from the same build that creates itsparent part. In other words, both the parent part and this child part a

Page 305

Before getting parts from TeamConnection, you might want to find out if thedevelopment mode for the release is concurrent or serial. To determine the m

Page 306 - 286 User’s Guide

Getting parts from TeamConnectionChecking out a part implies that you intend to modify it; extracting a part merely givesyou a copy of the part. Norma

Page 307

When you want to make changes to a part, you can do one of the following:v Check out one or more parts and edit the parts on your workstation. When yo

Page 308 - 288 User’s Guide

Finding different versions of TeamConnection objectsTeamConnection version control maintains different versions of the following objects:v Releasesv W

Page 309

Versioning work areasTeamConnection creates new versions of work areas whenever you do the following:v Create a work areaThis is the initial version o

Page 310 - 290 User’s Guide

Versioning driversTeamConnection creates new versions of drivers whenever you do the following:v Create a driverWhen you create a new driver, TeamConn

Page 311

Versioning partsTeamConnection versions parts in association with other TeamConnection objects, suchas work areas. If, for example, you create part1 i

Page 312 - 292 User’s Guide

Reviewing the design and resource estimatesAfter the resolution has been designed and the resources have been identified,the proposal needs to be revie

Page 313

Authority to perform tasks...26Finding objects within TeamConnection ...27Finding parts ...27Using wor

Page 315

Chapter 4. The states of TeamConnection objectsThe actions that you can perform on certain TeamConnection objects are controlled bytwo factors:v The p

Page 316 - 296 User’s Guide

resolution. The component you open a defect or feature against should be onethat manages the parts affected by the enhancement or problem. Use thecomp

Page 317

Review stateDefects or features move to this state after they have been sized. In this state,the design text and sizing records are reviewed to determ

Page 318 - 298 User’s Guide

defect/feature will only go to the verify state when all the workareas for therelease specified move to complete state.Note: If you do not intend to fix

Page 319

The states of work areasA work area is a storage area where you can work on the parts in a release withoutaffecting the ″official″ versions of those p

Page 320 - 300 User’s Guide

How fix records are handled varies according to the subprocesses in effect:Component subprocessesv dsrDefect or dsrFeature - TeamConnection creates fix

Page 321 - Sample REXX execs

Restrict stateWork areas can be moved to the restrict state only when the release includesthe driver subprocess. The work area moves automatically to

Page 322 - 302 User’s Guide

is added to it as a driver member. If all work areas are removed from thedriver, the driver automatically returns to the working state.Work areas can

Page 323

v Abstain if unable to assess the resultsOnce all test records have been accepted or abstained, the states of otherobjects change as follows:v Work ar

Page 324 - 304 User’s Guide

Approving the fix...81Checking out a part ...82Checking in the changes ...83Freezing the work a

Page 325 - Sample build scripts

These records are handled by different people and enable you to monitor yourdevelopment progress in different ways. The sequence of creating and handl

Page 326 - Sample package files

Chapter 5. Working with no component or release processesTo illustrate how to work with objects in a release that does not follow a trackingprocess or

Page 327 - Customer support

to make some modifications to the parts in this release. This fix will require the tasksnoted in the following table:For information about this task, Go

Page 328 - 308 User’s Guide

CommandFrom a command line, he issues the following command:teamc defect -accept 310 -answer program_defectResultThe defect goes to the working state.

Page 329 - Bibliography

Note: 310 is the name of the defect that was opened for the problem, so this ishow Alex wants to identify the work area.CommandFrom a command line, he

Page 330 - 310 User’s Guide

From the GUI, he:1. Selects Parts → Check out from the Actions pull-down menu on the Tasks window.2. Types the following:v optics.c in the Path names

Page 331 - Related publications

He does not select the PartFull choice because he wants to limit his search to aparticular release and work area. He uses PartFull when he wants to se

Page 332 - 312 User’s Guide

6. Double-clicks on the task entry he just created. The Parts window appears.Hereafter, to display the list of parts in his work area, he merely doubl

Page 333 - Glossary

This command returns a list of all the parts that match the query. After Alex determineswhich part he wants to check out, he issues the following comm

Page 334 - 314 User’s Guide

Note: Alex follows these steps because he knows the exact name of the part that he ischecking in. If he does not know the name, or if he is checking i

Page 335 - Glossary 315

The physical structure of the build function ...129The build object model...130Parent-child relationships in a build tree

Page 336 - 316 User’s Guide

Thus, work area 310 contains the following parts:brain.c leg.cbrain.obj leg.objbrain.exe foot.carm.c foot.objarm.obj optics.c (modification 1)hand.c o

Page 337 - Glossary 317

CommandFrom a command line, he issues the following command:teamc part -build brain.exe -release robot_control -workarea 310 -pool normalResultTeamCon

Page 338 - 318 User’s Guide

Note: For a detailed build example, see “Chapter 15. Building an application: anexample” on page 181.Extracting a partNext, Alex tests his modification

Page 339 - Glossary 319

This action places a copy of the part brain.exe in the current directory.Checking out the part one more timeAlex then downloads brain.exe to his robot

Page 340 - 320 User’s Guide

Checking the part back inAlex makes his modification and checks the part in.GUIFrom the GUI, he:1. Does one of the following to display the Check In Pa

Page 341 - Glossary 321

ResultNow the work area contains the following parts:brain.c leg.cbrain.obj leg.objbrain.exe (contains modification 1) foot.carm.c foot.objarm.obj opt

Page 342 - 322 User’s Guide

CommandFrom a command line, he issues the following command:teamc workarea -freeze 310 -release robot_controlResultThe freeze command saves the work a

Page 343 - Special Characters

CommandFrom a command line, he issues the following command:teamc workarea -refresh 310 -release robot_controlResultThis action updates work area 310

Page 344 - 324 User’s Guide

CommandFrom a command line, he issues the following command:teamc part -build brain.exe -release robot_control -workarea 310 -pool normalResultFortuna

Page 345 - (continued)

CommandFrom a command line, he issues the following command:teamc workarea -integrate 310 -release robot_controlResultTeamConnection first determines t

Page 346 - 326 User’s Guide

Creating the build tree for the application...184Starting the build on the client ...189Putting the build scripts to work .

Page 347

From the GUI, he:1. Selects Defects → Verify from the Actions pull-down menu on the Tasks window.The Verify Defects window appears.2. Types 310 in the

Page 348 - 328 User’s Guide

The following tasks are required:For information about this task, Go to thispage.Refreshing the work area from the driver 71Integrating the work area

Page 349

From a command line, she issues the following command:teamc workarea -refresh 415 -release robot_controlResultThis command refreshes her work area wit

Page 350 - 330 User’s Guide

CommandFrom a command line, she issues the following command:teamc workarea -integrate 415 -release robot_controlResultBecause Jenny is up-to-date wit

Page 351

Alex can use either the GUI or the command line to reconcile the differences. Foursteps are required from the command line:1. Check out the latest unc

Page 352 - 332 User’s Guide

CommandFrom a command line, he does the following steps:v Issues a report command to determine which parts are in conflict:teamc report -view collision

Page 353

If Alex decides not to merge the two parts, but instead wants to use his copy ofoptics.c, he uses the collision -reject command. Or, if he wants to us

Page 354 - BUSINESS REPLY MAIL

Chapter 6. Working with component and release processesThe previous chapter described how to work with parts when the release does notfollow a trackin

Page 355

For information about this task, Go to thispage.Approving the fix 81Checking out a part 82Checking in the changes 83Freezing the work area 85Building t

Page 356 - SC34-4499-03

Changing defect ownershipBecause Carol is the component owner, she is currently defined as the owner of defect456. But the problem is in Alex’s code, s

Commentaires sur ces manuels

Pas de commentaire