Page 3 - IBM VisualAge TeamConnection Enterprise Server; User’s Guide; IBM
IBM VisualAge TeamConnection Enterprise Server User’s Guide Version 3.0 SC34-4499-03 IBM
Page 5 - Contents; Part 1. Introducing TeamConnection; Chapter 1. An introduction to TeamConnection .; iii
Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . xi Notices . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . xv About this book. . . . . . . . . . . . . . . . . . . . . . . xvii How this book is organized . . . . ...
Page 6 - iv
Authority to perform tasks . . . . . . . . . . . . . . . . . . . 26 Finding objects within TeamConnection . . . . . . . . . . . . . . . 27 Finding parts . . . . . . . . . . . . . . . . . . . . . . . 27 Using work areas . . . . . . . . . . . . . . . . . . . . . . 28 Naming your work areas . . . . . ....
Page 7 - Part 3. Using TeamConnection Notes Integrated Databases; Chapter 8. Creating and Maintaining Integrated Notes Databases .
Approving the fix . . . . . . . . . . . . . . . . . . . . . . . 81 Checking out a part . . . . . . . . . . . . . . . . . . . . . . 82 Checking in the changes . . . . . . . . . . . . . . . . . . . . 83 Freezing the work area. . . . . . . . . . . . . . . . . . . . 85 Building the application . . . . ....
Page 9 - vii
Creating the build tree for the application . . . . . . . . . . . . . . . 184 Starting the build on the client . . . . . . . . . . . . . . . . . . 189 Putting the build scripts to work . . . . . . . . . . . . . . . . . . 191 Finishing the job and reporting the results to the user . . . . . . . . . ....
Page 10 - viii
Setting up your project options . . . . . . . . . . . . . . . . . . 241 Using your TeamConnection Workframe project . . . . . . . . . . . . 242 Project actions . . . . . . . . . . . . . . . . . . . . . . 242 Part actions . . . . . . . . . . . . . . . . . . . . . . . 243 Using your project: a simple ...
Page 11 - Index; ix
Sample build scripts. . . . . . . . . . . . . . . . . . . . . . 305 Sample parsers . . . . . . . . . . . . . . . . . . . . . . . 306 Sample package files . . . . . . . . . . . . . . . . . . . . . 306 Customer support . . . . . . . . . . . . . . . . . . . . . . 307 Bibliography . . . . . . . . . . . ...
Page 13 - Figures; xi
Figures 1. A sample TeamConnection client/server network . . . . . . . . . . 5 2. Sample of a component hierarchy . . . . . . . . . . . . . . . 7 3. Parts, releases, and components . . . . . . . . . . . . . . . . 8 4. Tasks window . . . . . . . . . . . . . . . . . . . . . . 18 5. Components window ....
Page 14 - xii
47. TeamConnection components on separate machines . . . . . . . . . 137 48. Create Builder window . . . . . . . . . . . . . . . . . . . 148 49. Modify Part Properties window . . . . . . . . . . . . . . . . 156 50. Modify Part Properties window . . . . . . . . . . . . . . . . 157 51. Create Builder ...
Page 15 - Notices; xiii
Notices References in this publication to IBM products, programs, or services do not imply thatIBM intends to make these available in all countries in which IBM operates. Anyreference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or serv...
Page 16 - xiv
Page 17 - Trademarks; The following terms are trademarks of other companies:; xv
Trademarks The following terms are trademarks of International Business Machines Corporation inthe United States and/or other countries: AIX® NetView® C/370™ OpenEdition® C Set ++® Operating System/2® DB2® OS/2® DB2 Universal Database® SOM® IBM® SOMobjects@tm; MVS™ TeamConnection™ MVS/ESA™ VisualAge...
Page 18 - xvi
Adobe, the Adobe logo, Acrobat, the Acrobat logo, Acrobat Reader, and PostScript aretrademarks of Adobe Systems Incorporated. Other company, product, and service names may be trademarks or service marks ofothers. xvi User’s Guide
Page 19 - About this book; Commands Reference; when entering commands or online help when using the; Getting Started with the TeamConnection Clients; contains basic information for the; How this book is organized; Administrator’s Guide; Conventions; This book uses the following highlighting conventions:; xvii
About this book This book is part of the documentation library supporting the IBM TeamConnectionlicensed programs. It is a guide for client users. For additional information when performing TeamConnection tasks, refer to the Commands Reference when entering commands or online help when using the gra...
Page 20 - Monospace; Tell us what you think; xviii
v Italics are used to indicate the first occurrence of a word or phrase that is defined in the glossary. They are also used for information that you must replace. v Bold is used to indicate items on the GUI. v Monospace font is used to indicate exactly how you type the information. v File names foll...
Page 23 - Chapter 1. An introduction to TeamConnection; What does TeamConnection do for you? It takes care of the following:
Chapter 1. An introduction to TeamConnection TeamConnection provides an environment and tools to make software development runsmoothly, whether your development team is small or large. Using TeamConnection,you can communicate with and share data among team members to keep up with themany tasks in th...
Page 24 - TeamConnection definitions
Topic and description Page Developing products using TeamConnection: v Getting familiar with the interfaces v The basics of using TeamConnection v More about defects and features v Following TeamConnection processes 16 Using TeamConnection to build applications: v Build concepts v Installing build a...
Page 25 - TeamConnection database
TeamConnection family servers control all data within the TeamConnection environment. Data stored in a family server’s database includes: v Text objects, such as source code and product documentation v Binary objects, such as compiled code v Modeled objects that are stored in the information model b...
Page 27 - Components
Check out To get a copy of a part so that you can make changes to it. Check in To put the changed part back into TeamConnection. Extract To get a copy of the part without making changes to the current version in TeamConnection. Edit To change a part from within TeamConnection using a specified edito...
Page 28 - The; process; by which the component handles defects and features.; Releases; releases; Work areas; A release contains the latest
v The users who have access to the component and the level of access each userhas. This information makes up the component’s access list . v The users who are to be notified about changes to the component. This set of usersis called the notification list . v The process by which the component handle...
Page 29 - Drivers
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 something called a work area . A work area is a logical temporary work space that enables you to isolate your work onthe parts in a release from the official ...
Page 30 - processes
Defects and features A 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 be associated with a work area, and bothfollow the processes defined for the component and release that are associated withthe work area. TeamConne...
Page 31 - Build
the parts modified for the specified defect or feature in one release andrecords the status of the defect or feature. The work area moves throughsuccessive states during its life cycle. The TeamConnection actions that youcan perform against a work area depend on its current state. You must use the t...
Page 32 - Packaging; Roles people play; System administrator
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 can also force a buildregardless of the build times. v Enables you to spread the build over multiple machines running at the same time orinto multiple...
Page 35 - Part 2. Developing a product using TeamConnection; Chapter 3. The basics of using TeamConnection .
Part 2. Developing a product using TeamConnection Chapter 2. Getting familiar with the TeamConnection client interfaces . . . 17 Using the GUI. . . . . . . . . . . . . . . . . . . . . . . . 17 Starting the GUI . . . . . . . . . . . . . . . . . . . . . . 18 Stopping the GUI . . . . . . . . . . . . . ...
Page 36 - Chapter 6. Working with component and release processes .
Verifying and testing part updates . . . . . . . . . . . . . . . . 60 Extracting a part . . . . . . . . . . . . . . . . . . . . . 62 Checking out the part one more time . . . . . . . . . . . . . . 63 Checking the part back in . . . . . . . . . . . . . . . . . . 64 Freezing the work area. . . . . . ....
Page 37 - Using the GUI
Chapter 2. Getting familiar with the TeamConnection clientinterfaces TeamConnection provides several interfaces that you can use to access data: v A graphical user interface based on industry standards. v A command line interface that lets you type TeamConnection commands from aprompt or from within...
Page 38 - Starting the GUI; teamcgui
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. See Configure the environment variables in the .profile in the Getting Started with the TeamConnection Clients manual. 2. See Ensure that the TeamConnection client command i...
Page 39 - Stopping the GUI; To stop the TeamConnection client GUI, do one of the following:; Select Close from the System menu in the Tasks window.; Performing tasks with the GUI; Select a task from the Tasks window.
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, you can change,delete from, and add new tasks to this list. To learn how to do this, select How do Ifrom the Help pull-down menu, and then select Updat...
Page 40 - Using the Settings notebook
Using the Settings notebook The TeamConnection GUI provides a Settings notebook in which you can set defaultvalues for your working environment. To open the Settings notebook, select Settingsfrom the Windows pull-down menu. You can set the following values; for moreinformation about them, refer to t...
Page 41 - Online help information; teamc commandName; commandName
On the Extract page: v Destination directory v Read-only v Expand keywords On the Pool page: v Pool Online help information Online help information is available from anywhere in the TeamConnection GUI. Usethe online help when you need more information about a topic or task. TeamConnection offers two...
Page 42 - Quick Commands Reference; is a booklet that lists the syntax of each; Using the TeamConnection web client
The Quick Commands Reference is a booklet that lists the syntax of each TeamConnection command. You can also become familiar with the commands by looking at the contents of the logfile where TeamConnection stores the commands that are issued as you use the GUI.This file is specified in the Log file ...
Page 45 - Chapter 3. The basics of using TeamConnection; Laying the groundwork; Components from the Objects pull-down menu on the Tasks; window. The Component Filter window appears.
Chapter 3. The basics of using TeamConnection All users of TeamConnection perform a number of basic tasks, such as checking partsout of TeamConnection and then back in, and testing and verifying part changes. Beforeyou start doing these tasks, you need to understand the basic concepts behind them;th...
Page 46 - Authority to perform tasks; Open defects and features; Search; for information within TeamConnection to create reports
From a command prompt, you can issue the following command to view the componentstructure. teamc report -view -raw bCompView -where "name='root'" Authority to perform tasks As a TeamConnection user, you are automatically given the authority to perform somebasic tasks. You can: v Open defects...
Page 47 - Finding objects within TeamConnection; Command usage is explained in the; Use a Filter window in the GUI.; Finding parts; Parts
Note: You can issue queries to generate reports of data from tables and views using the -view action flag. If you do not specify selection criteria, such as the fieldsand the search conditions you want to use, the report query selects all entries forthe table or view indicated that the user has auth...
Page 48 - You cannot use this filter to search for build information.; Using work areas; freezing; your
BuildView Use when you want to search for information related to building yourapplication, such as viewing a build tree, or when you want to do build actions. PartFull Use when you want to search for parts across releases, components, or workareas. For example, you want a list of all the optics.c pa...
Page 49 - path name
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 case the applicationno longer builds. When you integrate a work area or commit a driver, the work area isfrozen automatically. Naming your work areas Wh...
Page 50 - Naming your parts; and; Preparing to build your parts; The parent part that you want to associate the part with.; Input
Use the online help facility if you need assistance when creating parts. Naming your parts If your organization has a naming convention, be sure to follow it when naming yourparts. When the naming convention is not followed, everybody in your organization canhave trouble locating parts. Part names c...
Page 51 - Working with parts
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 areoutputs when the parent part is built. Dependent The part will be needed for the build operation of its parent to complete, butit will not be passe...
Page 52 - Working with common parts; common; You commit the driver when the driver subprocess is followed.; disconnect; parts. When a part is common to more than two releases, you
Before getting parts from TeamConnection, you might want to find out if thedevelopment mode for the release is concurrent or serial. To determine the mode, viewthe information about the specific release. To do this, select View from the Selectedpull-down menu on the Releases window. Working with com...
Page 53 - Getting parts from TeamConnection; PartExtract; authority to extract a part from; PartCheckOut; authority to check a part out. See; current working directory; Whether the TC_TOP environment variable is set
Getting parts from TeamConnection Checking out a part implies that you intend to modify it; extracting a part merely givesyou a copy of the part. Normally, when you extract a part, you do not plan to changethe current version in TeamConnection. You must have the necessary authority to a component be...
Page 54 - Checking parts in to TeamConnection; collision record
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 you finishmaking changes to the parts, you check them back in. v Edit a part from within the TeamConnection GUI using a specified editor. When youexit ...
Page 56 - Versioning work areas
Versioning work areas TeamConnection creates new versions of work areas whenever you do the following: v Create a work area This is the initial version of a work area. When you create myWorkArea, for example,its version name is myWorkArea:1. v Refresh a work area Refreshing a work area updates it wi...
Page 57 - Versioning drivers
Versioning drivers TeamConnection creates new versions of drivers whenever you do the following: v Create a driver When you create a new driver, TeamConnection makes two versions of it:myDriver:1, for example and myDriver:2. v Add a work area (driver member) to a driver If you add myWorkArea:1 to my...
Page 58 - Analyzing defects and features
Versioning parts TeamConnection versions parts in association with other TeamConnection objects, suchas work areas. If, for example, you create part1 in myWorkArea:1, the current version ofpart1 is myWorkArea:1. If part1 is in release myRelease:2 and work areamyWorkArea:2, then you can view the vers...
Page 59 - Testing and verifying part changes
Reviewing the design and resource estimates After the resolution has been designed and the resources have been identified,the proposal needs to be reviewed. If the review indicates that work shouldcontinue on the defect or feature, it is accepted. Resolving defects and implementing features Resolvin...
Page 61 - Chapter 4. The states of TeamConnection objects; The process followed by the component and by the release; Defects and features
Chapter 4. The states of TeamConnection objects The actions that you can perform on certain TeamConnection objects are controlled bytwo factors: v The process followed by the component and by the release v The current state of the object Certain TeamConnection objects follow certain states through t...
Page 62 - In this state, users can create a; sizing record; for each release that contains
resolution. The component you open a defect or feature against should be onethat manages the parts affected by the enhancement or problem. Use thecomponent descriptions and the structure of your family’s hierarchy to find themost appropriate component. If you open a defect or feature in aninappropri...
Page 65 - The states of work areas; Approve state
The states of work areas A work area is a storage area where you can work on the parts in a release withoutaffecting the ″ official ″ versions of those parts. A work area can be associated with a specific defect or feature, but it does not have to be. These attributes can affect thestate of a workar...
Page 67 - The states of drivers
Restrict state Work areas can be moved to the restrict state only when the release includesthe driver subprocess. The work area moves automatically to the restrict statewhen the driver to which it belongs is restricted. If a work area in this state isremoved from the driver, it returns to the integr...
Page 68 - official; Complete state; Accept the record if the test was satisfactory
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 be added to drivers as driver members when the driver is inthe working, integrate, or restrict state and the work area is in the fix state.Adding dri...
Page 69 - – verify - Verification records go to the ready state.; Verification and test records
v Abstain if unable to assess the results Once all test records have been accepted or abstained, the states of otherobjects change as follows: v Work areas - Go to complete state. v Defects and features - Go to verify state if the component includes theverifyDefect or verifyFeature subprocess; other...
Page 70 - integrated into the release.
These records are handled by different people and enable you to monitor yourdevelopment progress in different ways. The sequence of creating and handlingverification and test records is as follows: 1. Verification records are created in the notReady state when a defect or feature is accepted. This i...
Page 71 - Chapter 5. Working with no component or release processes; serial development; means that after you check out; concurrent development; , in which more than one person can; Working in serial development
Chapter 5. Working with no component or release processes To illustrate how to work with objects in a release that does not follow a trackingprocess or component processes, this chapter follows an example of a programmingteam that is developing the control systems for a robot. They are working in a ...
Page 72 - Accepting a defect; GUI; The Accept Defects window appears.
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 to this page. Accepting the defect 52 Creating a work area 53 Checking out a part 54 Searching for a part 55 Checking in a part 58 Verifying and t...
Page 73 - Command; From a command line, he issues the following command:; Result; The defect goes to the working state.; Creating a work area
Command From a command line, he issues the following command: teamc defect -accept 310 -answer program_defect Result The defect goes to the working state. Creating a work area Because the component is not following a design, size, and review process, Alex needsto manually create a work area in which...
Page 74 - how Alex wants to identify the work area.; Checking out a part
Note: 310 is the name of the defect that was opened for the problem, so this is how Alex wants to identify the work area. Command From a command line, he issues the following command: teamc workarea -create -name 310 -release robot_control Result TeamConnection creates a work area named 310 associat...
Page 75 - Searching for a part
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 field v robot_control in the Release field v 310 in the Work area field 3. Selects OK. Command From a command line, he issues the following command...
Page 76 - Types the following in the Parts Filter window:; in the Release field; Closes the Edit Task List window. The Tasks window appears.
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 search forparts across releases, components, or work areas. 2. Types the following in the Parts Filter window: v robot_control in the Release field v 31...
Page 78 - Checking in a part
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 command: teamc part -checkout optics.c -release robot_control -workarea 310 Result A copy of the part optics.c is checked out from TeamConnection and plac...
Page 80 - Verifying and testing part updates; normal
Thus, work area 310 contains the following parts: brain.c leg.c brain.obj leg.obj brain.exe foot.c arm.c foot.obj arm.obj optics.c (modification 1) hand.c optics.obj hand.obj Work area 310 continues to contain the unchanged parts from the requested releaseview, but now the work area is overlaid with...
Page 82 - example” on page 181.; Extracting a part
Note: For a detailed build example, see “Chapter 15. Building an application: an example” on page 181. Extracting a part Next, Alex tests his modifications in the robot prototype in his office. He extracts theexecutable part from the work area 310. GUI From the GUI, he: 1. Selects Parts → Extract fr...
Page 83 - Checking out the part one more time; Does one of the following to display the Check Out Parts window:; Selects Parts
This action places a copy of the part brain.exe in the current directory. Checking out the part one more time Alex then downloads brain.exe to his robot, runs his test, and determines that themodification did not work: the robot slams into the wall. However, Alex thinks he knowswhat the problem is, ...
Page 84 - Checking the part back in; Alex makes his modification and checks the part in.; Does one of the following to display the Check In Parts window:
Checking the part back in Alex makes his modification and checks the part in. GUI From the GUI, he: 1. Does one of the following to display the Check In Parts window: v Selects Parts → Check in from the Actions pull-down menu on the Tasks window. v Selects the entry on his Tasks window that displays...
Page 85 - Freezing the work area
Result Now the work area contains the following parts: brain.c leg.c brain.obj leg.obj brain.exe (contains modification 1) foot.c arm.c foot.obj arm.obj optics.c (modification 2) hand.c optics.obj (modification 1) hand.obj Because Alex did not specify that he wanted to save a copy of the work area b...
Page 86 - Refreshing the work area
Command From a command line, he issues the following command: teamc workarea -freeze 310 -release robot_control Result The freeze command saves the work area 310. Thus, TeamConnection takes asnapshot of the work area, with all its parts and their visible versions, and saves it. Alexcan come back to ...
Page 87 - Building the application; in the Pool field. The other required fields have the correct
Command From a command line, he issues the following command: teamc workarea -refresh 310 -release robot_control Result This action updates work area 310 with any changes from the release, and it alsofreezes work area 310, if it is not already frozen. Now Alex’s work area contains thefollowing versi...
Page 88 - Integrating the work area; window. The Integrate Work Areas window appears.; in the Work areas field and
Command From a command line, he issues the following command: teamc part -build brain.exe -release robot_control -workarea 310 -pool normal Result Fortunately, nothing breaks, so Alex is ready to integrate his changes with the release. Integrating the work area To integrate his changes with the rele...
Page 89 - Closing a defect
Command From a command line, he issues the following command: teamc workarea -integrate 310 -release robot_control Result TeamConnection first determines that Alex’s changes were built against the latestversion of the release. Then TeamConnection makes Alex’s changes visible at therelease level so t...
Page 90 - Verify from the Actions pull-down menu on the Tasks window.; The Verify Defects window appears.; in the Defects field.; Working in concurrent development
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 Defects field. 3. Selects OK. Command From a command line, he issues the following command: teamc defect -verify 310 -release robot_control Result...
Page 91 - The following tasks are required:; Refreshing the work area from the driver; driver name
The following tasks are required: For information about this task, Go to this page. Refreshing the work area from the driver 71 Integrating the work area 72 Resolving differences 73 Refreshing the work area from the driver If Alex and Jenny are working on optics.c at the same time, they must resolve...
Page 92 - From a command line, she issues the following command:; Tasks window. The Complete Fix Records window appears.; in the Work areas field,
From a command line, she issues the following command: teamc workarea -refresh 415 -release robot_control Result This command refreshes her work area with the latest view of the release. Her workarea now contains the following part versions: brain.c (Jenny's modification 3) brain.obj (Jenny's modifi...
Page 93 - Reconciling differences
Command From a command line, she issues the following command: teamc workarea -integrate 415 -release robot_control Result Because Jenny is up-to-date with the latest view of the driver, her changes areintegrated after TeamConnection preserves a copy of the previous version of therelease. Reconcilin...
Page 94 - Record Filter window appears.; Selects OK from the Reconcile Collision Record window.
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 uncommitted version. 2. Extract the latest committed version. 3. Run the merge program against the two parts. 4. Check in the resultant part. However, o...
Page 95 - From a command line, he does the following steps:; alternate; Extracts a copy of optics.c from the release:; relative; Checks out his copy of optics.c from his work area:
Command From a command line, he does the following steps: v Issues a report command to determine which parts are in conflict: teamc report -view collisionView -workarea 310 This report tells him that optics.c is the part that collided and gives the alternate version ID of the part that caused the co...
Page 97 - Chapter 6. Working with component and release processes; is; followed and how to use component processes for features and; driver; monitors and; driver members
Chapter 6. Working with component and release processes The previous chapter described how to work with parts when the release does notfollow a tracking process. This chapter describes how to work with parts when atracking process is followed and how to use component processes for features and defec...
Page 99 - Changing defect ownership; window. The Modify Defect Owner window appears.; in the Defects field and types Alex’s user ID,; alexm; Results
Changing defect ownership Because Carol is the component owner, she is currently defined as the owner of defect456. But the problem is in Alex’s code, so she wants him to own the defect. To reassignownership, she does one of the following: GUI From the GUI, she: 1. Selects Defects → Modify → Owner f...
Page 101 - Approving the fix
Command From a command line, he issues the following command: teamc defect -accept 456 -answer program_defect Results Defect 456 moves to working state, and TeamConnection creates a work area called456. The work area is associated with the release specified on the sizing record, whichin this example...
Page 103 - Checking in the changes
Command From a command line, he issues the following command: teamc part -checkout optics.c -release robot_control -workarea 456 -relative d:\robot\src Results A copy of the part optics.c is checked out from TeamConnection and placed in thedirectory d:\robot\src. If the directory name is not specifi...
Page 104 - Now the work area contains the following part versions:
Note: Alex follows these steps because he knows the exact name of the part that he is checking in. If he does not know the name, or if he is checking in many parts, hecan instead do one of the following to display a list of parts: v Select the entry on his Tasks window that displays the list of part...
Page 106 - in the Pool field. The other required fields are pre-filled with the
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 area is integrated. Building the application Alex now builds the application to verify that the changes he has made have fixed theproblem. He does one o...
Page 107 - Accepting fix records; optics; in the Component field
Alex builds the application and tests the results. The modification seems to solve theproblem. Note: For a detailed build example, see “Chapter 15. Building an application: an example” on page 181. Accepting fix records Alex is satisfied that the changes are complete and the part is ready to be inte...
Page 108 - Integrating changed parts into a release; Adding a driver member; Carol, the project lead, adds work area 456 as a; driver member
Integrating changed parts into a release The changes that Alex has made are now ready to be put into the next set of changesscheduled to be integrated with the release. This set of changes is known as a driver . A driver named 0105 currently exists, and several driver members have already beenadded ...
Page 110 - Reactivating the fix record
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. Reactivating the fix record Currently, the fix record for work area 456 is in the complete state. Alex must reactivatethe fix record to move it back t...
Page 111 - Refreshing the driver
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: v 456 in the Work areas field v robot_control in the Releases field v 0105 in the Source field Command From a command line, h...
Page 112 - Building the driver
2. Types 0105 in the Drivers field and robot_control in the Release field. 3. Selects OK. Command From a command line, she issues the following command: teamc driver -refresh 0105 -release robot_control Results This command refreshes driver 0105 with any committed updates to the release. Building th...
Page 113 - Restricting the driver
Command From a command line, she issues the following command: teamc part -build brain.exe -release robot_control -workarea 0105 -pool normal Results Carol runs some simple regression tests to verify that the application built properly. Sheis satisfied with the results, and is ready for the next ste...
Page 114 - Integrating the parts
Command From a command line, she issues the following command: teamc driver -restrict 0105 -release robot_control Results This command restricts driver 0105 so that only Carol is able to make changes to it.Carol is now ready to build the application. Integrating the parts Carol commits the changes i...
Page 115 - Completing the driver
From a command line, she issues the following command: teamc driver -commit 0105 -release robot_control Results TeamConnection moves the part versions associated with driver 0105 into the release.Other members of the team can now view the changes. Committing a driver commits allwork areas designated...
Page 116 - Testing the built application; field and; from the Environments field.
Testing the built application Annmarie is the tester for the MVS version of the robot application. When she receivesnotification that the test record is in the ready state, she tests the part changes thatwere made within the release by Alex and several of his team members. The testscomplete successf...
Page 123 - Getting started; advanced; and begin testing an integrated database.; About; Using; document
Chapter 7. Introduction to TeamConnection Integrated NotesDatabases The VisualAge TeamConnection Integrated Notes Database feature provides adocumentation facility to support software development. A software development groupcan use this database to communicate with TeamConnection objects from withi...
Page 124 - Prerequisites and dependencies; The TeamConnection Web Client interface is also required.; Using TeamConnection with Lotus Notes; You can also access the TeamConnection client GUI from Notes.; Sources of user information; document is also available from the Help choice on the Navigator
Prerequisites and dependencies In preparation for setting up and administering the Lotus Notes Integration feature,ensure that the machine you are using to implement this feature (generically, the Notes server ) is equipped as follows: v To use this function, the client machine requires Lotus Notes ...
Page 125 - provides a listing of each Notes element (form or view), along; For a view; Database types; Requirements
The About document provides graphical previews for the Requirements, Development, and Test database types. These previews provide a graphical depiction of availabledocuments and the document hierarchy for each database, along with the default setupvalues available to an administrator. The Using docu...
Page 126 - Refer to the database; document for a description of the forms, views, and tasks; Forms and subforms; Common
the design. Documents existing in Notes can be associated with existingfeatures and defects in TeamConnection. Test Case Management and Tracking The Test Case Management and Tracking database assists with test casemanagement and tracking. In this database, test case definitions and theirexecution re...
Page 127 - Views
Table 1. Integrated database forms by database type (continued) Form Use for this form Response to Response Document your response to another’s response to a requirements, design, test case, or basic document. Requirements Requirement Document and open a requirements document in the database. TeamCo...
Page 128 - Views are available through the Navigator and the View menu.
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 features, or all activedefects. Views are available through the Navigator and the View menu. Table 2 provides a listing of all views currently availa...
Page 129 - TeamConnection; Reviews; Document archiving
Table 2. Integrated database views (continued) View Documents accessed (purpose) Execution Records To list all of the execution records in the database. Hierarchy To list test case, execution records, and defects in a hierarchy. My Execution Records To list all of the execution records that you have...
Page 131 - Chapter 8. Creating and Maintaining Integrated Notes Databases; Lotus Notes Database Administrator; for; Important notice to administrators
Chapter 8. Creating and Maintaining Integrated Notes Databases This section and the one that follows (“Chapter 9. Database Design Strategies andAdvanced Customization” on page 121) provide instructions for the members of yourorganization, referred to as the Lotus Notes Database Administrator , or ad...
Page 132 - Initializing the original template and creating a database; template; fhcnotes.ntf to refresh the design of
The flow presented in the figure applies to all potential user databases availablethrough the Notes Integrated Database feature. Initializing the original template and creating a database To help you with developing Notes applications, a database master template is includedon the IBM VisualAge TeamC...
Page 134 - live; Select Feature and Defect push buttons.
Note Setup is a staging process that may require some planning. See“Chapter 9. Database Design Strategies and Advanced Customization” onpage 121 for details on setup strategies and customization options. You will need to decide what type of database you need: Requirements, Designand Development, Tes...
Page 135 - Note: If users will create documents; documents are automatically numbered; necessary; Approved
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 the database is working to your satisfaction (you can go back to the setup several times to make changes and refine it), you are ready to make it av...
Page 136 - Creating customized production databases
Creating customized production databases Now that you have initialized the Integrated Notes Database feature and performed apreliminary setup of the database template for your organization, you can proceed tocustomize the initialized database. See “Using the Customization setup facility” on page 122...
Page 138 - Performing reconciliation; database on the desired Notes client.
Performing reconciliation The Reconciliation facility synchronizes the data in the TeamConnection family and theNotes databases that use it. The reconciliation facility is an agent that should be runregularly. As a default, reconciliation is activated during Setup. It can be run on anestablished sch...
Page 139 - Database maintenance: refreshing design from a template; To refresh a database from a template, do the following:; Important notice to administrators:
Database maintenance: refreshing design from a template In the course of using Notes Integrated databases, you may have occasion to refreshcurrent databases with a template. As you receive code updates from IBM VisualAgeTeamConnection Enterprise Server, it is likely that you will want your current d...
Page 141 - Rules of thumb and general advice; as they are currently named
Chapter 9. Database Design Strategies and Advanced Customization This section include some general strategies for setting up, testing, and tuning yourNotes Integrated Database implementation. The primary administrative functions aredescribed in “Chapter 8. Creating and Maintaining Integrated Notes D...
Page 142 - Using the Customization setup facility
3. Assess and implement any access control/authorization schemes necessary at this level of implementation. 4. Open the newly initialized database. 5. Create test documents for testing. 6. Open features and defects if your database addresses these elements. 7. Determine whether existing (TeamConnect...
Page 143 - Notes Database Customization; Modify Database Optional Information; for a description of documents available for each database type.; Modify the document hierarchy
The Customization setup facility addresses the following areas of databasemanipulation: v Notes Database Customization v Modify TeamConnection Access v Reconciliation of Notes and TeamConnection Data In order to perform the Customization setup, you must set your role to Administrator inthe Access Co...
Page 144 - Modify the states for documents; Modify TeamConnection Access; Modify Family Information; Reconciliation of Notes and TeamConnection Data
response documents for the base documents you defined in the Modify whichdocuments your project will use section. This level of customization allowsyou to control how response documents can build upon a base document andother response documents. Modify the states for documents In the Modify the stat...
Page 145 - Activate Reconcile; about setting up and initiating the reconciliation facility.; Defects and Features; Advanced customization; subforms
Activate Reconcile The Notes Integrated Database feature provides a reconciliation facility thatsynchronizes the data in the TeamConnection family and the Notes databasesthat use it. The reconciliation facility is an agent that should be run regularly.The reconciliation facility can be run on an est...
Page 147 - Part 4. Using TeamConnection to build applications; Chapter 10. Basic build concepts
Part 4. Using TeamConnection to build applications Chapter 10. Basic build concepts . . . . . . . . . . . . . . . . 129 The physical structure of the build function . . . . . . . . . . . . . . 129 The build object model . . . . . . . . . . . . . . . . . . . . . 130 Parent-child relationships in a bu...
Page 149 - The TeamConnection build function has numerous features:; The physical structure of the build function
Chapter 10. Basic build concepts This chapter defines terms and briefly describes the TeamConnection pieces that worktogether in building an application. For more details, continue to the other chapters inthis section. The TeamConnection build function has numerous features: v It builds applications...
Page 150 - The build object model; build tree; (a simplified graphical; TeamConnection part
Build servers are started by a TeamConnection administrator. For more information, see“Chapter 11. Installing, starting, and stopping build servers” on page 137. The build object model Figure 44 on page 133 shows the TeamConnection objects and events that constitutethe build function, as illustrated...
Page 151 - Build script; TeamConnection will re-verify all parser dependencies:; Parent-child relationships in a build tree; Input parts
Build script An object that a builder uses in transforming inputs to outputs; it is essentiallya binding between TeamConnection and a transformation tool, such as a linkeror compiler. In OS/2, Windows, UNIX, or MVS/OE environments, a build scriptis usually a command file, but it can be a string that...
Page 152 - The builder linker1 links hello.obj and bye.obj into msgcat.exe
Though parent-child relationships usually imply that the parent part generates the childpart, in a TeamConnection build it is the opposite. Because TeamConnection places thebuild output at the top of the tree, it refers to the build output as the parent and to thebuild input as the child. To underst...
Page 153 - Working with a build tree
Working with a build tree Software developers must provide the information by which TeamConnectiondetermines the build events that make up a build request. An application’s build treeshows this information graphically. Figure 44. Sample build object model for msgcat.exe Chapter 10. Basic build conce...
Page 155 - Putting the pieces together
Putting the pieces together The table that follows lists the tasks involved in preparing for building an application andin actually building it. Usually an administrator does the preparation steps, but anyonewith the proper authority can do so. For more information about this task, Go to this page. ...
Page 157 - This chapter explains how to install, start, and stop a build server.; Installing the build function; Installation Guide; Creating a build server on MVS
Chapter 11. Installing, starting, and stopping build servers This chapter explains how to install, start, and stop a build server. Installing the build function Before installing build servers, you should be familiar with the build concepts found in“Chapter 10. Basic build concepts” on page 129. For...
Page 158 - On MVS, create data sets with the following characteristics:; hostname
The following are software requirements for the MVS build server: v TCP/IP Version 3.2 for MVS v OS/390 R3 LE To install the build server on MVS, you create MVS data sets and then upload theTeamConnection files to these data sets. Follow these steps: 1. On your TeamConnection server, install the MVS...
Page 159 - Creating a build server on MVS/OE
Note: The file fhbmsg.mvs is installed in the language subdirectory of the \nls\msg directory path in the TeamConnection installation directory, forexample, \nls\msg\en_us for US English. The remaining MVS files areinstalled in the \mvs subdirectory. c. This optional step installs the sample build s...
Page 160 - Starting build servers using teamcbld; teamcbld
2. From the oe subdirectory where TeamConnection is installed, use ftp to upload the following files to MVS/OE, in binary. v rename teamcbld.oe to teamcbld (main executable) v rename fhccmnc.oe to fhccmnc (supporting DLL) v rename fhcrscli.oe to fhcrscli (supporting DLL) v teamcv3.cat (for required ...
Page 161 - The command; Starting an MVS build server; Modify the RUNPGM JCL for your installation.
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 screen using the -sparameter. v -n writes files: – writes the changed environment variables to a file called tcbldenv.lst instead of setting them in pro...
Page 162 - environment
– TC_BUILDMINWAIT - Minimum amount of time to wait (in seconds) between queries for new jobs. Default setting is 5, minimum setting is 3. – TC_BUILDMAXWAIT - Maximum amount of time to wait (in seconds) between queries for new jobs. Default setting is 15, maximum setting is 300. The teamcbld will che...
Page 163 - Starting the MVS/OE build server
v unit_name indicates the default unit type for dynamic data set allocations. VIO is the default. v login_password is required only when the family server authentication level requires a TeamConnection user password. v local_codepage indicates the code set that text data is converted to for the buil...
Page 165 - Stopping the build servers; To stop a build server, do one of the following:; Stopping an MVS build server
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_BUILD_RSSBUILDS_FILEenvironment variable. Stopping the build servers To stop a build server, do one of the following: v Close the window in which the bu...
Page 167 - Chapter 12. Working with build scripts and builders; Creating a builder; To create a builder using the GUI:
Chapter 12. Working with build scripts and builders A builder is an object that can transform one set of TeamConnection parts into anotherby invoking tools such as compilers and linkers. For example, one builder mighttransform a COBOL source file into an object file. Another might transform a set of...
Page 168 - Builder
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 the following: teamc builder -create name -condition RC_expression -environment name -from script_filespec -script name -value RC_value -release nam...
Page 169 - Environment
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. Otherwise, youmust create the builder again in the new release. Script, File type, and Source file These fields work together to define the build script ...
Page 170 - Comparison operator and RC value; The values allowed for Comparison operator are as follows:; , meaning that the build; Parameters; compiling, you might specify a parameter string of; Timeout; Writing a build script
starting, and stopping build servers” on page 137 for more information.) It isrecommended that you follow a naming convention for this attribute, usingvalues such as os2 and mvs . Comparison operator and RC value Together, these two attributes make up a Boolean expression that defines thecriteria us...
Page 171 - Passing parameters to a build script; As attributes of a builder; Note: There is a one-to-one relationship between each object in the
Passing parameters to a build script There are three places where parameters can be specified that affect the outcome of abuild. As attributes of a builder Builder parameters are passed to the build script, after variable substitution isperformed. Variables are substituted based upon the following s...
Page 173 - Writing a simple build script; compiler. You specify the following attributes for the; icc; You can create this builder using the following command:; Writing an executable file for a build script; debug; and set the variable when you start the build. In this case, you
Writing a simple build script This kind of build script is written into the Script attribute of the builder. When youcreate or modify the builder, you specify in this attribute the name of the transformationtool to be invoked. For example, suppose you want to create a builder that compiles a C sourc...
Page 174 - The command issued by the build server is the following:; Testing a build script
debug = VALUE('DEBUG',,environ) if debug = 'YES' then do parms = parms || '/Ti+' end icc parms '/Fo'||output input exit result Windows NT and 95 build scripts must be able to return a value for a return code. Because *.bat command files provide little support for programming logic and cannot return ...
Page 175 - Modifying the contents of a build script; Make your changes at your workstation.; Putting a builder to work; For an existing part, do one of the following:; Modify
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 the current directory, andDEBUG is interpreted correctly. Modifying the contents of a build script Sometimes you need to modify the contents of a build...
Page 176 - Removing a builder from a part; null
v From a command line, type the following and press Enter. teamc part -modify name -Builder name where the part name is the name of the output file to be created by this builder and the builder name is the name of the builder itself. The complete syntax for this command is described in the TeamConne...
Page 177 - When using VisualAge C
v From a command line, type the following: teamc part -modify name -builder null -release name -family name Working with VisualAge C ++ and Templates When using VisualAge C ++ and templates, template-include objects are saved in a subdirectory of the current directory called TEMPINC, so that subsequ...
Page 179 - Chapter 13. Working with MVS build scripts and builders; Creating a builder for MVS builds
Chapter 13. Working with MVS build scripts and builders A builder is an object that can transform one set of TeamConnection parts into anotherby invoking tools such as compilers and linkers. For example, one builder mighttransform a COBOL source file into an object file. Another might transform a se...
Page 180 - To create a builder using the command line:
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 the following: teamc builder -create name -condition RC_expression -environment name -from script_filespec -script name -value RC_value -release name...
Page 181 - text
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 release.Otherwise, you must create it again in the new release. Script, File type, and Source file These fields work together to define the build script t...
Page 182 - mvs
See “Synchronizing the build of unrelated parts” on page 196 for an example. Environment This is the name of the environment supported by the builder, such as MVS. The value that you specify here can be anything you like, but it must exactlymatch the environment value specified in the command used t...
Page 183 - Writing an MVS build script; For more information about JCL syntax, refer to the; JCL User’s Guide; JCL; Calls the MVS assembler
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. Writing an MVS build script The best starting point for an MVS build script is an existing JCL fragment that is usedfor transforming inputs into outputs....
Page 184 - File name conversions for MVS; Lowercase characters are converted to uppercase characters.; Passing parameters to an MVS build script
File name conversions for MVS TeamConnection file names are modified by the MVS build server according to thefollowing rules: v The directory path of a file name is not used. All characters of a file name up to andincluding the rightmost slash (/ or \) are thrown away. v Lowercase characters are con...
Page 185 - TeamConnection syntax for MVS build scripts; xxx; TCOUT
&TCBLDUSR On MVS, can be used in JCL scripts, which will be substituted with the userIDbefore processing the script. &TCINPUT This variable is used for in-stream data. For each build input, the line where&TCINPUT appears is duplicated and the variable &TCINPUT substituted withthe inp...
Page 186 - Supported JCL syntax; Positional parameters:
– Selecting Part → View → View build message from the Actions pull-down menu on the Tasks window Note: More than one ddname can specify TCOUT ; the results are concatenated in the order of appearance. When you add the TCEXT attribute for a ddname specification, you must also specifyother attributes ...
Page 187 - DD STATEMENT; Positional parameters
v PARM='information' , where information is the parameter string passed to the load module. v COND=( code,operator [ ,stepname] ) – code is the value to test against the return code from a previous step – operator is the comparison to be made between the value for code and the return code – stepname...
Page 188 - Example of a build script for a C compile; Compile the source file member in the data set WELLSK.TEAMC.C
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 compile The following JCL can be submitted as a batch job to do the following: v Compile the source file member in the data set WELLSK.TEAMC.C v Produce an object fi...
Page 190 - Example of a build script for a COBOL compile
Example of a build script for a COBOL compile TeamConnection provides a sample build script program for compiling MVS COBOLprograms. This sample is called fhbcobm.jcl. It invokes a JCL procedure called IGYWC,which needs to be in the system PROCLIB concatenation or in the data set identified bythe TE...
Page 191 - Example of a build script for a link; INCLUDE DDNAME
//*------------------------------------------------------ //* PROGRAM: cobolcmp.jcl //* IBM COBOL for MVS //* Compile Only //* //*------------------------------------------------------ //COBOLCMP EXEC PGM=IGYCRCTL,PARM='&TCPARM' //* //* INPUT FILES WITH EXTENSION CBL //* //SYSIN DD TCEXT=CBL,DIS...
Page 192 - ENTRY CEESTART
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 sequential data set associated with the SYSMOD ddname. Otherwise, thecontrol card is embedded in the data set associated with the SYSMOD ddname. Thi...
Page 195 - Chapter 14. Working with parsers; Creating a parser; To create a parser using the GUI:
Chapter 14. Working with parsers This chapter describes how to create a parser. It assumes that you have read“Chapter 10. Basic build concepts” on page 129. Consider the task of defining and maintaining a build tree. One of the moretime-consuming, and error-prone, portions of this task is defining t...
Page 197 - Writing a parser command file; source file
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 theTeamConnection database. During a build, these dependencies must beextracted to a path accessible by the build server. Because a build extractsparts from T...
Page 198 - COPY; Putting a parser to work; input
3. Writes out the list of such files into the dependency list file For example, for a C source file, the program could report a list of all the files includedby the source file (using #include statements). For a COBOL program, COPY statements would be the cue. TeamConnection ships a sample of a comm...
Page 199 - Removing a parser from a part; From the GUI, select Parts
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 attached, the parser willinvoke its command file, which will report back a list of dependencies. Using a parser does not keep you from defining dependencies...
Page 201 - Chapter 15. Building an application: an example
Chapter 15. Building an application: an example This chapter uses an extended example to describe in more detail how each of thecomponents of the build function work together. All commands used in this example aredescribed in detail elsewhere in this publication. This example walks through the contr...
Page 203 - Starting the build servers; testfam; pools; , according to the work he expects to use them for.
Starting the build servers The software development team in our example is building large applications using afamily named testfam, so they set TC_FAMILY to testfam . They plan to spread the work across several build servers, taking advantage of TeamConnection’s ability toperform multiple build even...
Page 204 - mvspool; Creating builders and parsers
mvspool For MVS builds pool1 For normal OS/2 builds pool2 For fast, high-priority OS/2 builds Each pool is formed as Mark starts build servers and assigns them to it. He starts thefollowing build server (bldserv2): teamcbld -b bldserv2 -p pool1 -e os2 The parameters specify the following: -p The bui...
Page 206 - the following illustration:
2. Creates two place-holder parts for the output of compiling the .c files. These parts are the output of the compile step; c_compiler, the builder that manages that step, isattached to both of them. He indicates that they are input to their parent file,msgcat.exe. Using the GUI, he can create these...
Page 207 - Attaches the parser; Properties from the Actions; completing the fields as shown in the following illustration:; file. The part’s contents will be parsed
teamc part -create hello.obj bye.obj -builder c_compiler -binary -empty -release 9503 -workarea 223 -component comp1 -parent msgcat.exe -input teamc part -create hello.h bye.h -release 9503 -workarea 223 3. Attaches the parser c_parser to the .c files. Using the GUI, he can attach the parser to thes...
Page 208 - is displayed from here he can bring up the build tree.
Using the command-line interface, he can connect these parts by issuing thefollowing commands: teamc part -connect hello.c -parent hello.obj -input -release 9503 -workarea 223 teamc part -connect bye.c -parent bye.obj -input -release 9503 -workarea 223 The .h parts are not connected because he expec...
Page 209 - Starting the build on the client
Starting the build on the client After much hard work on his source code, Greg is ready to start building his application. Using the GUI, he can start the build by selecting build from the Actions → Parts menu of the Tasks window, and completing the fields as shown in the followingillustration: Figu...
Page 211 - Unconditional; In our example, Greg specifies; Detail file name; Putting the build scripts to work
Unconditional Builds only parts that are out-of-date but continues processing even iferrors are returned. Note that outputs are not rebuilt for inputs thathave failed. Report Gives a preview of what would be built if you invoked a build. The report identifies what steps would occur without any trans...
Page 214 - Finding out which parts will be built; report; Canceling a build; To cancel a build that is in progress, do one of the following:; name
Finding out which parts will be built Before running a build of a large application, you might want to find out exactly whichparts will be built. If you specify that you want to run in report mode, TeamConnection determines what will be built in a normal build and produces a report showing theresult...
Page 215 - Figure 65 shows part of the build tree for robot.dll:; output; of robot.dll. Here are the commands to set up
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 the build of msgcat.exe when the compile steps havebeen completed, then the link step is not performed. However, the newly compiledhello.obj and bye...
Page 216 - command would also apply to the build; Synchronizing the build of unrelated parts; For example, Tim creates this build tree for the robot application:
teamc part -build robot.dll -workarea 915 -release 9503 The output of this build would be both robot.dll and robot.map. Any parametersspecified in the teamc part -build robot.dll command would also apply to the build of robot.map. Synchronizing the build of unrelated parts An entire application can ...
Page 219 - Part 5. Using TeamConnection to package products; Chapter 16. Using TeamConnection to package a product .
Part 5. Using TeamConnection to package products Chapter 16. Using TeamConnection to package a product . . . . . . . . 201 Setting up your build tree for packaging . . . . . . . . . . . . . . . 202 Setting up a build tree for the gather tool . . . . . . . . . . . . . . 202 Chapter 17. Using the Gath...
Page 221 - Chapter 16. Using TeamConnection to package a product; TeamConnection provides the following:; – Gather - gather.cmd which specifies the; teamcpak gather
Chapter 16. Using TeamConnection to package a product After you have built an application to your satisfaction, it is time to distribute it to users.This chapter describes how you can use TeamConnection to help automate thepackaging and distribution steps. TeamConnection provides the following: v Tw...
Page 222 - Setting up your build tree for packaging; The output of a packaging step might be any of the following:; Setting up a build tree for the gather tool
Setting up your build tree for packaging When TeamConnection builds an application, the application’s build tree identifies theparts to be built and the tools to use in building it. Similarly, when you useTeamConnection for packaging the application, the build tree can define the parts to bepackaged...
Page 225 - Chapter 17. Using the Gather tool; You can build both target directories concurrently.; Using the teamcpak command for the Gather tool
Chapter 17. Using the Gather tool The Gather tool automates the movement of software and data from one directory toanother on the same machine to prepare a package for electronic distribution. It cancopy or erase files; it can create or delete directories. This tool takes a list of input files and m...
Page 226 - gather; Command line flags
teamcpak [-i] [-o "String"] gather Input_file... Where -i Specifies that only one Input_file is specified in the command: an include file containing the list of input files. This parameter is optional. If you specify -i , it must precede the gather flag. -o " String" Specifies that t...
Page 229 - Keywords for a Gather package file; DATA
(DATA (PACKAGEFORMAT gather) (TARGETROOT Filename) (RULE (SOURCE Filename...) (TARGET Path) [(EXITPRIOR String... | EXITREPLACE String... | EXITPOST String...)] ) ) . . [(EXITPRIOR String...)] [(EXITPOST String...)] ) Keywords for a Gather package file DATA This keyword is required. It must be the f...
Page 232 - Any parameters included in the invocation string
(DATA (TARGETROOT f:\demoapp ) . . (RULE (SOURCE *.bin *.dll ) (TARGET bin\files ) ) (RULE (SOURCE *.hlp ) (TARGET targetroot ) ) . . ) EXITPRIOR, EXITPOST, and EXITREPLACE String... These keywords are optional. They specify a user exit program to run as partof the gather operation. To specify an ex...
Page 233 - Using exit keywords: an example; The package file looks like this:
v The resolved SOURCE file specifications v The resolved TARGET specification The exit keyword accepts any executable file or command. The exit program mustreturn an integer return value, zero meaning successful; it must also accept or ignorethe additional Gather parameters added to the end of the i...
Page 235 - Using the teamcpak command with Tivoli Software Distribution; Specifies that only one; inputFile; is specified in the command: an include file
Chapter 18. Using the Tivoli Software Distribution packaging tool The Tivoli Software Distribution packaging tool supports automated distribution betweena single Tivoli Software Distribution server and its TCP/IP-connected clients. The TivoliSoftware Distribution tool works either by itself or in co...
Page 236 - The following are examples of specifying input files.; All of these flags are optional.
-o "string" Specifies that the string listed in quotes be passed to the Tivoli SoftwareDistribution tool. For a list of possible flags to be passed, see “Command lineflags”. inputFile Specifies the files to be copied and the name of the package specification file.You can specify this paramet...
Page 237 - italics
Example of the teamcpak softdist command The following is an example of the teamcpak softdist command. teamcpak -i -o "-a -n -t" softdist Client.lst The -i parameter specifies that the input file Client.lst is to be used. The -o parameterpasses the following options to Tivoli Software Distri...
Page 238 - Keywords for a Tivoli Software Distribution package file; All other keywords are nested within the DATA clause.; PACKAGEFORMAT softdist
[(LOGNODE ManagedNode)] [(LOGFILE directory)] ) ) Keywords for a Tivoli Software Distribution package file DATA This keyword is required. It must be the first keyword in the package file, and itcan be specified only once. All other keywords are nested within the DATA clause. Example: (DATA . . other...
Page 239 - parameter; DISTRIBUTE
(DATA . . (MANAGER Distrib1) . . NODES This keyword specifies the nodes to which the files are to be distributed. Thesemust already have been defined to the profile manager as subscriberManagedNodes or PCManagedNodes. To distribute files to non-subscribers,you need to use Tivoli Software Distributio...
Page 241 - Check Tivoli mail messages generated during the distribution.; Trace facility; for more; Sample package file
Log file Check the file name you specified in the LOGFILE keyword for errormessages. Mail Check Tivoli mail messages generated during the distribution. -k option Run the teamcpak command with the -k option to keep the package file afterthe distribution has been run. This allows you to reprocess a di...
Page 247 - Appendix A. Environment Variables; must be specified for every
Appendix A. Environment Variables You can set environment variables to describe the TeamConnection environment inwhich you are working. You are not required to set your TC_FAMILY environmentvariable for the TeamConnection client command line interface. However, if theTC_FAMILY environment variable i...
Page 254 - Setting environment variables
Table 4. TeamConnection dynamically set build environment variables (continued) Environment variable Purpose Flag Setting Used by TC_LOCATION Directory where build script is invoked. Build server (except MVS build server) Setting environment variables For methods of setting your environment variable...
Page 255 - Appendix B. Importing makefile information into TeamConnection; The parameters are defined as follows:
Appendix B. Importing makefile information into TeamConnection TeamConnection provides a command to help you import makefile information into theTeamConnection database. The fhomigmk command reads a makefile and creates theparts in it. Build tree connections are created based on a rules file. The co...
Page 256 - mymak
found, TeamConnection uses default rules. “Creating a rules file” on page 237 explains the rules, the format of this file, and the default rules. /x Specifies that you want to run the command file that was produced by the /c parameter. /s Specifies that the build tree is to be displayed after the co...
Page 257 - Creating a rules file; file mask
used in the commands is mywork . After the commands are issued, the resulting build tree is shown using the TeamConnection GUI. Creating a rules file The import rules file is a text file that describes how you want TeamConnection tocreate and connect parts. In this file you supply a set of rules, on...
Page 258 - parameters; to indicate no parameters.; component; Columns are separated by spaces.
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 makefile specifiesf:\mysrc\, the content is expected in f:\mysrc\src\abc.cbl. For a file of *.cbl, thecontent is expected in src\abc.cbl relative t...
Page 259 - Appendix C. TeamConnection Merge; tcmerge; is the abbreviation for the replace parameter.; No columns will be ignored in difference calculation.
Appendix C. TeamConnection Merge The TeamConnection VisualMerge provides a way for you to merge two or threeselected files together to make one single file. You can select options for viewingdifferences and collisions, as well as view the composite output of the merged files.Both a command line ( tc...
Page 261 - Creating a TeamConnection-enabled Workframe project; project, and select the Create pushbutton.; Setting up your project options; Select Tools Setup from the project’s Views pull-down menu.; The following options are provided:; Family The TeamConnection family.; The TeamConnection release.; Work area
Appendix D. Enabling an OS/2 Workframe project forTeamConnection TeamConnection lets you create a Workframe version 3 project that hasTeamConnection options as well as a set of TeamConnection actions. For each project,you specify on the Project Options window the values for these options. By doing t...
Page 263 - Part actions; Displays the unprimed TeamConnection Create Parts window.
View part information Displays an unprimed View Part Information window. Edit part Displays an unprimed Edit Part window. Show parts If the project attribute Show filter is not set, issues a query based on theproject attribute’s query mask. If the project attribute Show filter is set,displays the Pa...
Page 264 - Using your project: a simple scenario
Using your project: a simple scenario Suppose you are working on a defect in the family FAMILY1, release REL1_1. Youhave created a TeamConnection work area called SANDBOX to work in. You want touse the Workframe to access your TeamConnection parts. Here is what you might do. 1. Create a TeamConnecti...
Page 265 - Appendix E. Enabling a Workframe/NT project for TeamConnection; TCMERGE FILE1 FILE2; Setting up your project options:
Appendix E. Enabling a Workframe/NT project for TeamConnection TeamConnection lets you create a Workframe/NT project that has TeamConnectionoptions as well as a set of TeamConnection actions. Workframe/NT doesn’t use the TeamConnection dialogues. Instead, WorkFrame/NTuses monitored commands to invok...
Page 269 - Overview of the ENVY/Manager-TeamConnection Bridge; the bridge; in this; parts
Appendix F. Enabling and Using the ENVY/Manager-TeamConnection Bridge Overview of the ENVY/Manager-TeamConnection Bridge ENVY provides a repository with operational support tailored specifically forhighly-interactive, prototyping environments that emphasize iterative development, suchas VisualAge Sm...
Page 270 - Scope of this documentation; Release; are; TeamConnection release; Description of the ENVY/Manager-TeamConnection Bridge; Smalltalk configuration maps
Scope of this documentation This documentation is intended for users and administrators installing and using thebridge. It is assumed that you familiar with both the VisualAge Smalltalk andTeamConnection products. The following subsections describe the mechanics of enabling the ENVY/Manager-TeamConn...
Page 271 - How the bridge communicates with TeamConnection; a configuration map without any of its released applications; Preparing to use the ENVY/Manager-TeamConnection Bridge
How the bridge communicates with TeamConnection The bridge functions are initiated from within the VisualAge Smalltalk environment.Each operation that interacts with TeamConnection runs for some time in the Smalltalkimage, but at some stage will make use of functions built into an appropriate versio...
Page 272 - Before the bridge will work, you must have the following:; Environment variables
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 step instructions aredescribed in “Installing and activating the ENVY/Manager-TeamConnection Bridge” onpage 253 . Usually, the Library Supervisor or...
Page 273 - root; bridge menu; Loading the ENVY/Manager-TeamConnection Bridge; from the Tools pulldown menu.
v TC_COMPONENT is used as the default TeamConnection component for partsstored in TeamConnection through the bridge. If TC_COMPONENT is not defined oris empty, the value root is used. v TC_RELATIVE is used to specify the initial destination path for files retrieved fromTeamConnection through the bri...
Page 274 - Testing the ENVY/Manager-TeamConnection Bridge
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 pushbutton to initiate the import process. During the process of importing the TCEMBR.DAT file into the VisualAge Smalltalk Pro manager.dat file,the Sy...
Page 275 - Using the ENVY/Manager-TeamConnection Bridge; bridge configuration; . Bridge configuration; Setting default properties; Context page; Show this dialog when exporting and importing; checkbox
Using the ENVY/Manager-TeamConnection Bridge You can perform TeamConnection functions on ENVY components, provided that yousupply parameters necessary to identify a bridge configuration . Bridge configuration parameters are defined by the Default Properties notebook, as described in “Settingdefault ...
Page 276 - Operations page; Force; In TeamConnection terms,; force; is an indication that changes should be forced; Locking
Context page The context page is used to specify the TeamConnection family, release, and work areaused as the context for the default bridge configuration. Family Use this field to input the name of your TeamConnection family server. Select the Test Server pushbutton to return an information window ...
Page 277 - Also known as; optimistic; locking, TCCS will attempt to check out the; retained; Import page
cache services (TCCS) on how to manage the locking behavior for parts thatyou are exporting to or importing from the TeamConnection repository. Obtain and release Also known as optimistic locking, TCCS will attempt to check out the part(s) before checking in changes that you have made in the ENVYenv...
Page 278 - Replace existing files; Export page; Storage in TeamConnection; export; When you attempt to import; with; Exporting ENVY components to TeamConnection; Configuration Maps
Replace existing files Files that currently exist in the target directory are automaticallyoverwritten. Export page The Export page provides default settings options for exporting ENVY components orfiles to a TeamConnection database. Storage in TeamConnection The Component field identifies the TeamC...
Page 279 - Default Properties notebook defaults to this behavior.; Export a configuration map that contains several applications.; or; maps that contains the application.; Exporting configuration maps and applications
mismatches. If you make a change to an application, it is important to update all theexported configuration maps that contain the application and to export all of theconfiguration maps again. Note: The Export all required maps too checkbox located on the Export page of the Default Properties noteboo...
Page 281 - and “Part 4. Using TeamConnection to build applications” on; Scenario assumptions
1. Select Configuration Maps, Applications, or Files from the Import cascade menu. 2. If the Show this dialog when exporting and importing option has been set in the default bridge configuration, you will be presented with the Import Propertiesnotebook, which is primed by values in the Default Prope...
Page 283 - Object mapping in TeamConnection; Build generation; Generator’s Guide
BOM file for each application contains an entry (at least the name,edition/timestamp, and TCPart type) for each class and method in eachapplication. Object mapping in TeamConnection After a ENVY/Manager-TeamConnection Bridge export action, the following parts arecreated in TeamConnection in wa1 for ...
Page 284 - Refer to the VisualAge Generator; for more details on the OVR; only if; outputs and dependencies in the build tree.
Refer to the VisualAge Generator Generator’s Guide for more details on the OVR part. 2. In TeamConnection (build function): a. The build administrator selects the EZEPREP collector of the initial build tree of a program proxy in wa1 for f1 , and requests a build. b. TeamConnection places the generat...
Page 285 - Making a change to a member
f. If there are tables and/or map groups used by the program, the generator determines whether there is already a build tree for them. If not, initial build treesare added for them using the program’s OVR part. g. TeamConnection re-examines the build tree of the EZEPREP collector and determines that...
Page 287 - Appendix G. Source Code Control User’s Guide; Visual Basic version 5.0 with SP2 applied; Projects vs Families
Appendix G. Source Code Control User’s Guide Differences between other source code control providers and TeamConnection The purpose of this document is to help Visual Basic, Visual C++, and PowerBuilderusers, make TeamConnection their Visual environments source code control provider.This document as...
Page 288 - Installing the TeamConnection source code control DLL
Components are used to organize the data in a family. Components are arranged in ahierarchical tree structure, with a single top component called root. The componentowns the parts that may be in it, and controls access to the parts. Once you are givenaccess to a component, you have access to all the...
Page 289 - Family, defined by the following attributes:
Note: If you have not already done so, follow the directions and install the TeamConnection client for your workstation. The following directions assume thatyou have successfully installed the TeamConnection client. Connecting TeamConnection to an IDE In order for TeamConnection to be your source co...
Page 290 - Opening a project
– Port Address v Component v Release v WorkArea You also need to know the project name. The project name is used by yourdevelopment tool to relate to the TeamConnection attributes of family, release, workarea, and component by the Source Code Control DLL. Opening a project One of the few differences...
Page 291 - follow may be unavailable.; Get Version
Check-in The 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 icon of a file checkedout to you, brings up a menu that includes the file check-in option. Selecting the filecheckin option opens the Check-In window....
Page 292 - Migrating project data bases; Migrating an existing project:; Settings window will display.
designate TeamConnection as the Source Code Control provider. From theTeamConnection GUI you can create new work areas (if you have the correct authority),retrieve previous versions of a part, open or process defects, and perform many otheractions against parts. Migrating project data bases One key ...
Page 293 - Starting a new project; Starting Visual Basic:; TeamConnection Settings window.
Starting a new project Starting a new project in Microsoft Visual Basic, Visual C++, or PowerBuilder isessentially the same regardless of the source code provider. The only operationaldifference is that the TeamConnection Source Code Control Settings window opensat some point. When the TeamConnectio...
Page 294 - Control option of the Tools menu.; Starting PowerBuilder:; To create a new project under PowerBuilder, do the following:; Select SCC API from the Connect list box, and then select OK.
7. To place the files under source code control, select the Add to Source Code Control option of the Tools menu. Starting PowerBuilder: To create a new project under PowerBuilder, do the following: 1. Start PowerBuilder. 2. Select the Library icon. Note: If TeamConnection Source Code Control is alre...
Page 295 - Appendix H. Supported expandable keywords; TeamConnection supports the following keywords.
Appendix H. Supported expandable keywords TeamConnection supports expandable keywords in text files. When a file containingexpandable keywords is extracted from TeamConnection, the current value of eachkeyword is added to the file. This information can help you identify what version ofsource code is...
Page 296 - Then the expanded keywords will look like:
keyword to appear in the output, add a minus sign (-) after the dollar sign ($). Forexample, if the statement is prepared as follows: static char _filex_hdr[]="$−KW; $−FN; $−Ver; $−ChkD; $−EKW;"; Then the expanded keywords will look like: static char _filex_hdr[]="$@(#) bin/filex.hdr 1:1...
Page 321 - Sample REXX execs
Appendix J. Sample REXX execs, build scripts, and parsers This appendix is composed of the IBM-supplied REXX execs, build scripts, and parsers.Your family administrator can modify these samples to fit the needs of yourorganization. The samples in this appendix may not be available on all platforms. ...
Page 325 - Sample build scripts; fhbmlink
Sample build scripts fhbcob2.cmd Calls the COBOL Visual Set for OS/2 compiler. fhbcob2l.cmd Calls the COBOL Visual Set for OS/2 compiler and link editor. fhbocomp.cmd Calls the VisualAge for C ++ icc compiler. fhbolib.cmd Calls the OS/2 implib utility. fhbolin2.cmd Calls the VisualAge for C ++ icc l...
Page 327 - Customer support; IBM Talklink; keyword TeamConnection to go to the TeamConnection area.; IBM Lotus Passport Advantage Program
Customer support Your options for IBM VisualAge TeamConnection Enterprise Server support, asdescribed in your License Information and Licensed Program Specifications, includeelectronic forums. You can use the electronic forums to access IBM VisualAgeTeamConnection Enterprise Server technical informa...
Page 328 - DB2 service maintenance and technical library
DB2 service maintenance and technical library To download the latest service maintenance for DB2, use the DB2 Service and Supporton the World Wide Web at: v http://www.software.ibm.com/data/db2/db2tech Note: Even though DB2 is bundled with VisualAge TeamConnection you should contact VisualAge TeamCo...
Page 329 - Bibliography; IBM VisualAge TeamConnection Enterprise Server library; Lists the TeamConnection commands along with their syntax.
Bibliography IBM VisualAge TeamConnection Enterprise Server library The following is a list of the TeamConnection publications. For a list of otherpublications about TeamConnection, including white papers, technical reports, a productfact sheet, and the product announcement letter, refer to the IBM ...
Page 330 - TeamConnection technical reports; Discusses basic concepts of DB2 SQL.
TeamConnection technical reports The following is a list of technical reports available for TeamConnection. Refer to theIBM VisualAge TeamConnection Enterprise Server Library home page for the mostup-to-date list of technical reports. 29.2147 SCLM Guide to TeamConnection Terminology 29.2196 Using RE...
Page 331 - Glossary; Related publications
Describes how to monitor DB2 database activity and analyze system performance. v Glossary A comprehensive glossary of DB2 terms. Related publications v Transmission Control Protocol/Internet Protocol (TCP/IP) – TCP/IP 2.0 for OS/2: Installation and Administration (SC31-6075) – TCP/IP for MVS Plannin...
Page 333 - This glossary uses the following cross-references:; Compare to; Contrast with
Glossary This glossary includes terms and definitions fromthe IBM Dictionary of Computing , 10th edition (New York: McGraw-Hill, 1993). If you do not findthe term you are looking for, refer to thisdocument’s index or to the IBM Dictionary of Computing . This glossary uses the following cross-referen...
Page 336 - See also; build dependent; implicit authority
defect. A TeamConnection object used toformally report a problem. The user who opens adefect is the defect originator. delete. If you delete a development object, suchas a part or a user ID, any reference to that objectis removed from TeamConnection. Certain objectscan be deleted only if certain cri...
Page 338 - base authority; explicit authority
automatically granted through inheritance or objectownership. Contrast with base authority and explicit authority . import. To bring in data. In TeamConnection, tobring selected items into a field from a matchingTeamConnection object window. inheritance. The passing of configurationmanagement proper...
Page 343 - Special Characters
Index Special Characters /Ft(dir) builder parameter 157 A Accept Defects window 52 Accept Test Records 96 Activate Fix Records 90 Add Driver Members 88 approval command approving a fix 82 Approval Records window 81 approve state 45 authority basic 26 build 177 for checking in parts 34 for checking o...
Page 353 - Readers’ Comments — We’d Like to Hear from You
Readers’ Comments — We’d Like to Hear from You IBM VisualAge TeamConnection Enterprise ServerUser’s GuideVersion 3.0 Publication No. SC34-4499-03 Overall, how satisfied are you with the information in this book? Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied Overall satisfaction h h...
Page 354 - IBMR; BUSINESS REPLY MAIL
Readers’ Comments — We’d Like to Hear from You SC34-4499-03 SC34-4499-03 IBMR Cut or FoldAlong Line Cut or FoldAlong Line Fold and Tape Please do not staple Fold and Tape Fold and Tape Please do not staple Fold and Tape NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES BUSINESS REPLY MAIL FIRST-CLASS...