Manuals / IBM / Computer Equipment / Personal Computer

IBM SC34-4499-03 manual Refreshing the driver, Refresh Work Areas window

Models: SC34-4499-03

1 356

Download 356 pages 55.74 Kb

Page 111

From the GUI, he:

1.Selects Work areas → Refresh from the Actions pull-down menu on the Tasks window.

2.Types the following in the Refresh Work Areas window and selects OK:

v456 in the Work areas ®eld

vrobot_control in the Releases ®eld

v0105 in the Source ®eld

Figure 35. Refresh Work Areas window

Command

From a command line, he issues the following command:

teamc workarea -refresh 456 -release robot_control -source 0105

Results

TeamConnection noti®es Alex of the collision, so his next step is to reconcile the differences. He follows the same procedure that is described on page 73.

Alex completes the ®x record and then tells Carol that he has reconciled the part differences and that she can now create the driver member. She creates the driver member without any collisions this time.

Refreshing the driver

Carol is ready to integrate the changes in driver 0105 with the release. Because other team leads have integrated changes as well, she wants to build her driver with the most current release part versions. She does one of the following:

GUI

From the GUI, she:

1. Selects Drivers → Refresh from the Actions pull-down menu on the Tasks window.

Chapter 6. Working with component and release processes 91

Image 111

IBM SC34-4499-03 manual Refreshing the driver, Refresh Work Areas window

Contents

IBM Page IBM Fourth Edition March Contents States of TeamConnection objects Working with no component or release processesWorking with component and release processes Creating and Maintaining Integrated Notes Databases Part 3. Using TeamConnection Notes Integrated DatabasesPart 4. Using TeamConnection to build applications Introduction to TeamConnection Integrated Notes DatabasesWorking with parsers Creating a parser Installing, starting, and stopping build serversWorking with build scripts and builders Working with MVS build scripts and buildersPart 5. Using TeamConnection to package products Appendix G. Source Code Control Users Guide Appendix H. Supported expandable keywordsAppendix J. Sample Rexx execs, build scripts, and parsers Readers Comments Ð Wed Like to Hear from You Users Guide Figures Xii Users Guide Xiii Xiv Users Guide Trademarks Xvi Users Guide Xvii About this bookHow this book is organized ConventionsTell us what you think Part 1. Introducing TeamConnection Users Guide An introduction to TeamConnection TeamConnections client/server architecture TeamConnection denitionsInterfaces TeamConnection databaseFamilies Users and host listsParts Components Check outCheck Work areas ReleasesDrivers Processes Defects and featuresApproval BuildRoles people play System administratorFamily administrator PackagingEnd user Build administratorUsers Guide Part 2. Developing a product using TeamConnection Working with component and release processes Getting familiar with the TeamConnection client interfaces Using the GUITasks window Starting the GUIPerforming tasks with the GUI Stopping the GUIOn the GUI Using the Settings notebookOnline help information Using the command line interfaceUsing the TeamConnection web client Getting familiar with the TeamConnection client interfaces Users Guide Laying the groundwork Basics of using TeamConnectionComponents window Authority to perform tasksFinding parts Finding objects within TeamConnectionUsing work areas BuildViewPartFull Creating parts Naming your work areasPreparing to build your parts Naming your partsWorking in serial or concurrent development mode Working with partsDependent Working with common parts Your workstations current working directory Getting parts from TeamConnectionChecking parts in to TeamConnection Versioning releases Finding different versions of TeamConnection objectsVersioning work areas Versioning drivers Versioning parts Working with defects and featuresAnalyzing defects and features Designing the resolutionReviewing the design and resource estimates Testing and verifying part changesResolving defects and implementing features Verifying the resolution of the defect or featureUsers Guide Open state States of TeamConnection objectsComponent subprocesses Release subprocessesSize state Canceled stateReturned state Design stateReview state Working stateVerify state Closed state States of work areas Approve stateFix state Integrate state Test state States of driversRestrict state Commit stateRestrict state Verication and test records Users Guide Working in serial development Working with no component or release processesFor information about this task Go to this Accepting a defectCommand Creating a work areaResult Create Work Areas window Checking out a partCheck Out Parts window Searching for a partPart Filter window Selects Save to Task ListEdit Task List window Checking in a part Teamc part -checkin optics.c -release robotcontrol -workarea Thus, work area 310 contains the following parts Verifying and testing part updatesBuild Parts window Extract Parts window Extracting a partCheck Out Parts Checking out the part one more timeChecking the part back Now the work area contains the following parts Freezing the work areaRefreshing the work area Refresh Work Areas window Building the applicationIntegrating the work area Integrate Work Areas window Closing a defectVerify Defects window Working in concurrent developmentFollowing tasks are required Refreshing the work area from the driverFrom a command line, she issues the following command Reconciling differences GUI Reconcile Collision Record window Result Working with component and release processes Moving through design, size, and review Results Changing defect ownershipAccepting a defect Approving Accept Approval Records window \robot\src in the Destination directory eld\robot\src in the Source directory eld Checking in the changesNow the work area contains the following part versions Teamc workarea -freeze 456 -release robotcontrol Building the application Complete Fix Records window Accepting x recordsAdding a driver member Integrating changed parts into a releaseReturning the work area to the x state Reconciling the differencesActivate Fix Records window Reactivating the x recordRefreshing the driver Refresh Drivers window Building the driverRestricting the driver Restrict Drivers window Integrating the partsComplete Drivers window Completing the driverAccept Test Records window Testing the built applicationRetrieving a past version of a part Using a congured processTeamc workarea -freeze 1208 -release robotcontrol Working with component and release processes TeamConnection system returns the following report 101 Part 3. Using TeamConnection Notes Integrated DatabasesUsers Guide Introduction to TeamConnection Integrated Notes Databases Getting started103 Using TeamConnection with Lotus Notes Prerequisites and dependenciesSources of user information Database types User Dened Forms and subformsTest Case Management and Tracking GenericRequirements ViewsAll documents Document archiving ReviewsUsers Guide Important notice to administrators Creating and Maintaining Integrated Notes Databases111 Initializing the original template and creating a database Select Access Control Users Guide Select File-Save Select Administration-Document ControlCreating customized production databases Select Administration-Document Control Performing reconciliation From the File menu, select Database-Replace Design Database maintenance refreshing design from a templateImportant notice to administrators Rules of thumb and general advice Database Design Strategies and Advanced Customization121 Using the Customization setup facility Modify the document hierarchy Modify Database Optional InformationCommon Database Options Database-specic OptionsReconciliation of Notes and TeamConnection Data Modify TeamConnection AccessActivate Reconcile Defects and Features Advanced customizationLog Document Options Users Guide Working with parsers Part 4. Using TeamConnection to build applications127 Basic build conceptsBuilding an application an example Basic build concepts Physical structure of the build function129 Builder Build object modelTeamConnection part Build eventOutput parts Parent-child relationships in a build treeBuild script Input partsUsers Guide Sample build object model for msgcat.exe Working with a build treeBuild tree for the hello application For more information about this task Go to this Putting the pieces togetherFor more information about this task Go to this 137 Installing, starting, and stopping build serversInstalling the build function Creating a build server on MVSCd JCL data set for load module Cd data set for teamproc jcl Creating a build server on MVS/OEStarting build servers using teamcbld Starting an MVS build server Runpgm Exec PGM=TEAMCBLD Starting the MVS/OE build server Creating build startup les for non-MVS environments Stopping an MVS build server Stopping the build serversUsers Guide Working with build scripts and builders Creating a builder147 Release Fromscriptfilespec -scriptnameEnvironment Parameters TimeoutWriting a build script Comparison operator and RC valueAs attributes of a builder Passing parameters to a build scriptAs attributes of a part in the build tree As parameters of the part -build commandWriting an executable le for a build script Writing a simple build scriptTesting a build script Putting a builder to work Modifying the contents of a build scriptModify Part Properties window Removing a builder from a partWorking with VisualAge C++ and Templates Users Guide Working with MVS build scripts and builders Creating a builder for MVS builds159 Builder Script, File type, and Source le File type none Script fhbcFile type none Script null Comparison operator are as follows ± EQ or == Equals Fhbmpli.jcl Writing an MVS build scriptFhbmasm.jcl Fhbcobm.jclPassing parameters to an MVS build script File name conversions for MVSTcbldusr TeamConnection syntax for MVS build scriptsKeyword parameters Supported JCL syntaxExec statement Positional parametersDD Statement Example of a build script for a C compile WELLSK.TEAMC.ERRORWorking with MVS build scripts and builders UNIT=SYSDA,SPACE=TRK,10,5 Example of a build script for a Cobol compileDCB=RECFM=FB,LRECL=80,BLKSIZE=3200 Example of a build script for a linkSysmod DD TCEXT=LOAD,DISP=NEW,DELETE Working with MVS build scripts and builders Users Guide Working with parsers Creating a parser175 Create Parser window IncludeWriting a parser command le Putting a parser to work Removing a parser from a part From a command line, type the following 181 Building an application an exampleSample build tree Starting the build servers Creating builders and parsers Creating the build tree for the applicationMvspool Create Parts window Create Parts window Modify Part Properties window Connect Parts window Build tree display Starting the build on the clientBuild pool Build modeBuild target Work areaPutting the build scripts to work UnconditionalDetail le name Monitoring the progress of a build Finishing the job and reporting the results to the userBuilding all parts, regardless of build times Running a build in spite of errorsFinding out which parts will be built Canceling a buildDening multiple outputs from a single build event More sample build treesHe creates the collector part Synchronizing the build of unrelated partsBuilding an application an example Users Guide Chapter Part 5. Using TeamConnection to package productsChapter Using TeamConnection to package a product 199Users Guide 201 Using TeamConnection to package a productSetting up a build tree for the gather tool Setting up your build tree for packagingShe also connects a readme le for the application Adding the gather step to the build tree Using the Gather tool Using the teamcpak command for the Gather tool205 Command line ¯ags StringInputles Using the Gather tool Examples of the teamcpak gather command Writing a package le for the Gather toolSyntax rules for a Gather package le Keywords for a Gather package le Packageformat gatherTargetroot targetrootpath Source list of le specications Target Targetpath Using exit keywords in the Data clause Using exit keywords in the Rule clauseEXITPRIOR, EXITPOST, and Exitreplace String Package le looks like this Using exit keywords an exampleUsers Guide 215 Using the Tivoli Software Distribution packaging toolInputFile Example of the teamcpak softdist command Writing a package le for Tivoli Software DistributionSyntax rules for a Tivoli Software Distribution package le Keywords for a Tivoli Software Distribution package le ExamplePackageformat softdist Nodes Installpgm Trace facility Sample package leLog le OptionProfile Using the Tivoli Software Distribution packaging tool Exit # end of file 225 Part 6. AppendixesUsers Guide 227 Appendix A. Environment VariablesNlspath Tcbuildpool Tccasesense Tcmakeimportverbose Tcrelease TeamConnection dynamically set build environment variables Setting environment variables 235 Appendix B. Importing makele information into TeamConnectionModied makele Create leConnect le Connect ContentCreating a rules le Le maskComponent 239 Appendix C. TeamConnection MergeParameter Description Creating a TeamConnection-enabled Workframe project Setting up your project options241 Project actions Using your TeamConnection Workframe projectShow parts Part actionsView part information Edit partUsing your project a simple scenario Tcuser 245Tcbecome TC Build Part TC View Part ContentsTC Extract Part TC View Part InformationUsers Guide 249 Overview of the ENVY/Manager-TeamConnection BridgeScope of this documentation Preparing to use the ENVY/Manager-TeamConnection Bridge How the bridge communicates with TeamConnectionSetting up the bridge environment PrerequisitesEnvironment variables Loading the ENVY/Manager-TeamConnection Bridge Testing the ENVY/Manager-TeamConnection Bridge Using the ENVY/Manager-TeamConnection Bridge Setting default propertiesDefaults Context OperationsLocking Import Storage in TeamConnection ExportExporting Envy components to TeamConnection Replace existing lesExporting conguration maps and applications Importing Envy components from TeamConnection Exporting lesScenario assumptions TeamConnection EnvyVisualAge Generator Developer Build generation Object mapping in TeamConnectionTeamConnection build function TeamConnection change control Making a change to a memberTeamConnection change control Appendix G. Source Code Control Users Guide Projects vs Families267 Installing the TeamConnection source code control DLL Before you start Connecting TeamConnection to an IDEUsing TeamConnection as your source code control provider Removing the TeamConnection Source Code Control DLLOpening a project Integrated featuresUncheck-out Full features of TeamConnectionCheck-in Check-outMigrating project data bases Starting a new project Users Guide 275 Appendix H. Supported expandable keywordsThen the expanded keywords will look like 277 Associated release ApprovalReject Approval record owner Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page Page New test record owner, subscribers Page Page Page Users Guide Appendix J. Sample Rexx execs, build scripts, and parsers Sample Rexx execs301 Script name Function Inputs DrvrMem Lists the defect and feature members of a DriverName Script name Function Inputs Sample build scripts Sample package les Sample parsersInternet Customer support307 IBM TalklinkDB2 service maintenance and technical library Bibliography IBM VisualAge TeamConnection Enterprise Server library309 TeamConnection technical reports Glossary Related publicationsUsers Guide Contrast with Glossary313 Compare toUsers Guide Glossary End user. See user See also build dependentHPFS. See high-performance le system Users Guide Pool. See build pool Users Guide TeamConnection superuser. See superuser Users Guide 323 IndexBuilder Debug GUI Exitpost Parts nding Releases Tcmakeimportrules 227, 235 Work area Automatic creation Users Guide How satised are you that the information in this book is Readers Comments Ð Wed Like to Hear from YouReaders Comments Ð Wed Like to Hear from You IbmrPage Ibmr