Nodes | IBM SC34-4499-03 guide

(DATA

.

.

(MANAGER Distrib1)

.

.

NODES

This keyword speci®es the nodes to which the ®les are to be distributed. These must already have been de®ned to the pro®le manager as subscriber ManagedNodes or PCManagedNodes. To distribute ®les to non-subscribers, you need to use Tivoli Software Distribution options set in an import ®le package de®nition.

Example:

(DATA

.

.

(NODES "tcaix01 tcaix02")

.

.

IMPORT

Use this keyword to select Tivoli Software Distribution options not supported in the -o parameter of the teamcpak softdist command. The ®lenameparameter is the name of a Tivoli Software Distribution import ®le package de®nition. You can generate an import ®le using the Tivoli Software Distribution user interface. If you use the IMPORT keyword, then instead of calling the standard Tivoli Software Distribution packaging command the Tivoli Software Distribution tool will call wimprtfp to get all of the Tivoli Software Distribution con®guration options. Using the IMPORT keyword disables other options and causes errors if they are speci®ed.

If you specify the IMPORT keyword, do not specify the DISTRIBUTE, INSTALLPGM, LOGNODE, or LOGFILE keywords.

If you use the INCLUDE option in an import ®le, it is overridden by the list of ®les provided to the teamcpak command.

Example:

(DATA

.

.

(IMPORT importFile)

.

.

DISTRIBUTE

Specify FULL to distribute all ®les or CHANGED to distribute only those changed since the last distribution. The default is FULL.

Example:

Chapter 18. Using the Tivoli Software Distribution packaging tool 219

Image 239

IBM SC34-4499-03 manual Nodes

Contents

IBM Page IBM Fourth Edition March Contents Working with component and release processes States of TeamConnection objectsWorking with no component or 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 Databases Working with parsers Creating a parser Installing, starting, and stopping build serversWorking with build scripts and builders Working with MVS build scripts and builders Part 5. Using TeamConnection to package products Appendix J. Sample Rexx execs, build scripts, and parsers Appendix G. Source Code Control Users GuideAppendix H. Supported expandable keywords 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 Conventions Tell us what you think Part 1. Introducing TeamConnection Users Guide An introduction to TeamConnection TeamConnections client/server architecture TeamConnection denitions Interfaces TeamConnection database Parts FamiliesUsers and host lists Check ComponentsCheck out Work areas Releases Drivers Processes Defects and features Approval Build Roles people play System administratorFamily administrator Packaging End user Build administrator Users Guide Part 2. Developing a product using TeamConnection Working with component and release processes Getting familiar with the TeamConnection client interfaces Using the GUI Tasks window Starting the GUI Performing tasks with the GUI Stopping the GUI On the GUI Using the Settings notebook Online help information Using the command line interface Using the TeamConnection web client Getting familiar with the TeamConnection client interfaces Users Guide Laying the groundwork Basics of using TeamConnection Components window Authority to perform tasks Finding parts Finding objects within TeamConnection PartFull Using work areasBuildView Creating parts Naming your work areas Preparing to build your parts Naming your parts Dependent Working in serial or concurrent development modeWorking with parts Working with common parts Your workstations current working directory Getting parts from TeamConnection Checking parts in to TeamConnection Versioning releases Finding different versions of TeamConnection objects Versioning work areas Versioning drivers Versioning parts Working with defects and featuresAnalyzing defects and features Designing the resolution Reviewing the design and resource estimates Testing and verifying part changesResolving defects and implementing features Verifying the resolution of the defect or feature Users Guide Open state States of TeamConnection objectsComponent subprocesses Release subprocesses Size state Canceled stateReturned state Design state Verify state Review stateWorking state Closed state Fix state States of work areasApprove state Integrate state Test state States of driversRestrict state Commit state Restrict state Verication and test records Users Guide Working in serial development Working with no component or release processes For information about this task Go to this Accepting a defect Result CommandCreating a work area Create Work Areas window Checking out a part Check Out Parts window Searching for a part Part Filter window Selects Save to Task List Edit 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 updates Build Parts window Extract Parts window Extracting a part Check Out Parts Checking out the part one more time Checking the part back Now the work area contains the following parts Freezing the work area Refreshing the work area Refresh Work Areas window Building the application Integrating the work area Integrate Work Areas window Closing a defect Verify Defects window Working in concurrent development Following tasks are required Refreshing the work area from the driver From 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 ownership Accepting a defect Approving Accept Approval Records window \robot\src in the Destination directory eld \robot\src in the Source directory eld Checking in the changes Now the work area contains the following part versions Teamc workarea -freeze 456 -release robotcontrol Building the application Complete Fix Records window Accepting x records Adding a driver member Integrating changed parts into a release Returning the work area to the x state Reconciling the differences Activate Fix Records window Reactivating the x record Refreshing the driver Refresh Drivers window Building the driver Restricting the driver Restrict Drivers window Integrating the parts Complete Drivers window Completing the driver Accept Test Records window Testing the built application Retrieving a past version of a part Using a congured process Teamc workarea -freeze 1208 -release robotcontrol Working with component and release processes TeamConnection system returns the following report 101 Part 3. Using TeamConnection Notes Integrated Databases Users Guide 103 Introduction to TeamConnection Integrated Notes DatabasesGetting started Sources of user information Using TeamConnection with Lotus NotesPrerequisites and dependencies Database types User Dened Forms and subformsTest Case Management and Tracking Generic Requirements Views All documents Document archiving Reviews Users Guide 111 Important notice to administratorsCreating and Maintaining Integrated Notes Databases Initializing the original template and creating a database Select Access Control Users Guide Select File-Save Select Administration-Document Control Creating customized production databases Select Administration-Document Control Performing reconciliation From the File menu, select Database-Replace Design Database maintenance refreshing design from a template Important notice to administrators 121 Rules of thumb and general adviceDatabase Design Strategies and Advanced Customization Using the Customization setup facility Modify the document hierarchy Modify Database Optional InformationCommon Database Options Database-specic Options Reconciliation of Notes and TeamConnection Data Modify TeamConnection Access Log Document Options Activate Reconcile Defects and FeaturesAdvanced customization Users Guide Working with parsers Part 4. Using TeamConnection to build applications127 Basic build concepts Building an application an example 129 Basic build conceptsPhysical structure of the build function Builder Build object modelTeamConnection part Build event Output parts Parent-child relationships in a build treeBuild script Input parts Users Guide Sample build object model for msgcat.exe Working with a build tree Build tree for the hello application For more information about this task Go to this Putting the pieces together For more information about this task Go to this 137 Installing, starting, and stopping build serversInstalling the build function Creating a build server on MVS Cd JCL data set for load module Cd data set for teamproc jcl Creating a build server on MVS/OE Starting 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 servers Users Guide 147 Working with build scripts and buildersCreating a builder Release Fromscriptfilespec -scriptname Environment Parameters TimeoutWriting a build script Comparison operator and RC value As attributes of a builder Passing parameters to a build script As attributes of a part in the build tree As parameters of the part -build command Writing an executable le for a build script Writing a simple build script Testing a build script Putting a builder to work Modifying the contents of a build script Modify Part Properties window Removing a builder from a part Working with VisualAge C++ and Templates Users Guide 159 Working with MVS build scripts and buildersCreating a builder for MVS builds Builder File type none Script null Script, File type, and Source leFile type none Script fhbc Comparison operator are as follows ± EQ or == Equals Fhbmpli.jcl Writing an MVS build scriptFhbmasm.jcl Fhbcobm.jcl Passing parameters to an MVS build script File name conversions for MVS Tcbldusr TeamConnection syntax for MVS build scripts Keyword parameters Supported JCL syntaxExec statement Positional parameters DD Statement Example of a build script for a C compile WELLSK.TEAMC.ERROR Working with MVS build scripts and builders UNIT=SYSDA,SPACE=TRK,10,5 Example of a build script for a Cobol compile DCB=RECFM=FB,LRECL=80,BLKSIZE=3200 Example of a build script for a link Sysmod DD TCEXT=LOAD,DISP=NEW,DELETE Working with MVS build scripts and builders Users Guide 175 Working with parsersCreating a parser Create Parser window Include Writing 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 example Sample build tree Starting the build servers Mvspool Creating builders and parsersCreating the build tree for the application Create Parts window Create Parts window Modify Part Properties window Connect Parts window Build tree display Starting the build on the client Build pool Build modeBuild target Work area Detail le name Putting the build scripts to workUnconditional Monitoring the progress of a build Finishing the job and reporting the results to the user Building all parts, regardless of build times Running a build in spite of errors Finding out which parts will be built Canceling a build Dening multiple outputs from a single build event More sample build trees He creates the collector part Synchronizing the build of unrelated parts Building an application an example Users Guide Chapter Part 5. Using TeamConnection to package productsChapter Using TeamConnection to package a product 199 Users Guide 201 Using TeamConnection to package a product Setting up a build tree for the gather tool Setting up your build tree for packaging She also connects a readme le for the application Adding the gather step to the build tree 205 Using the Gather toolUsing the teamcpak command for the Gather tool Inputles Command line ¯agsString Using the Gather tool Syntax rules for a Gather package le Examples of the teamcpak gather commandWriting a package le for the Gather tool Targetroot targetrootpath Keywords for a Gather package lePackageformat gather Source list of le specications Target Targetpath EXITPRIOR, EXITPOST, and Exitreplace String Using exit keywords in the Data clauseUsing exit keywords in the Rule clause Package le looks like this Using exit keywords an example Users Guide 215 Using the Tivoli Software Distribution packaging tool InputFile Syntax rules for a Tivoli Software Distribution package le Example of the teamcpak softdist commandWriting a package le for Tivoli Software Distribution Packageformat softdist Keywords for a Tivoli Software Distribution package leExample Nodes Installpgm Trace facility Sample package leLog le Option Profile Using the Tivoli Software Distribution packaging tool Exit # end of file 225 Part 6. Appendixes Users Guide 227 Appendix A. Environment Variables Nlspath Tcbuildpool Tccasesense Tcmakeimportverbose Tcrelease TeamConnection dynamically set build environment variables Setting environment variables 235 Appendix B. Importing makele information into TeamConnection Connect le Modied makeleCreate le Connect ContentCreating a rules le Le mask Component 239 Appendix C. TeamConnection Merge Parameter Description 241 Creating a TeamConnection-enabled Workframe projectSetting up your project options Project actions Using your TeamConnection Workframe project Show parts Part actionsView part information Edit part Using your project a simple scenario Tcuser 245 Tcbecome TC Build Part TC View Part ContentsTC Extract Part TC View Part Information Users Guide 249 Overview of the ENVY/Manager-TeamConnection Bridge Scope of this documentation Preparing to use the ENVY/Manager-TeamConnection Bridge How the bridge communicates with TeamConnection Environment variables Setting up the bridge environmentPrerequisites Loading the ENVY/Manager-TeamConnection Bridge Testing the ENVY/Manager-TeamConnection Bridge Defaults Using the ENVY/Manager-TeamConnection BridgeSetting default properties Locking ContextOperations Import Storage in TeamConnection ExportExporting Envy components to TeamConnection Replace existing les Exporting conguration maps and applications Importing Envy components from TeamConnection Exporting les Scenario assumptions VisualAge Generator Developer TeamConnectionEnvy Build generation Object mapping in TeamConnection TeamConnection build function TeamConnection change control Making a change to a member TeamConnection change control 267 Appendix G. Source Code Control Users GuideProjects vs Families 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 DLL Opening a project Integrated features Uncheck-out Full features of TeamConnectionCheck-in Check-out Migrating project data bases Starting a new project Users Guide 275 Appendix H. Supported expandable keywords Then 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 301 Appendix J. Sample Rexx execs, build scripts, and parsersSample Rexx execs 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 parsers Internet Customer support307 IBM Talklink DB2 service maintenance and technical library 309 BibliographyIBM VisualAge TeamConnection Enterprise Server library TeamConnection technical reports Glossary Related publications Users Guide Contrast with Glossary313 Compare to Users Guide Glossary End user. See user See also build dependent HPFS. See high-performance le system Users Guide Pool. See build pool Users Guide TeamConnection superuser. See superuser Users Guide 323 Index Builder 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 You Readers Comments Ð Wed Like to Hear from You IbmrPage Ibmr