- -Ver option (version option)
- creating for an executable\x0d
- Implementing a `-Ver' Option
- @(#) - (what string prefix)
- creating a what string using\x0d
- Creating a `what' String
- abbreviations
- for commands
- finding the valid\x0d
- Command Abbreviations and Aliases
- abe (audited build executor)
- CR production procedure description\x0d
- Build Auditing and Background Processes
- distributed build use\x0d
- The Audited Build Executor (abe)
- access control
- ct_permissions manual page
- permissions checking and locks described in\x0d
- Permissions Checking and Locks
- distributed builds\x0d
- Overview of Distributed Building
- locks use for\x0d
- Permissions Checking and Locks
- permissions
- checking, hierarchy and characteristics\x0d
- Permissions Checking and Locks
- DOs, practices that enhance sharing\x0d
- Wink-in, Permissions on Derived Objects, and clearcase_bld_umask
- techniques for isolating work\x0d
- Techniques for Maintaining Privacy
- Ada compilers
- incremental update issues\x0d
- Additional Incremental-Update Situations
- administrator
- project leader relationship to\x0d
- Project Leader and ClearCase Administrator
- tasks
- element type consistency among VOBs (footnote)\x0d
- Element Types and Type Managers
- algorithms
- compound object build
- Clearmake issues and alternatives\x0d
- Remedies for the Incremental-Update Problem
- configuration lookup
- comparison with standard make algorithms\x0d
- Why is Configuration Lookup Necessary?
- limitations\x0d
- Explicit Dependencies on `Searched-For' Sources
- aliases
- for commands\x0d
- Command Abbreviations and Aliases
- annotations (meta-data)
- annotate (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- API (ClearCase)
- broadcasting SoftBench messages from\x0d
- Using the ClearCase/SoftBench Integration
- application subsystems
- config specs that select components of\x0d
- Playing Mix-and-Match with Application Subsystems
- apropos
- obtaining cleartool help with\x0d
- Getting Help
- ar(1) command
- building an archive\x0d
- Example: Building an Archive
- architecture(s)
- distributed build (figure)\x0d
- The Audited Build Executor (abe)
- multiple
- building software for (chapter)\x0d
- Building Software for Multiple Architectures
- distributed build setting up for\x0d
- Setting clearcase_bld_conc in a Shell Startup Script
- SoftBench/ClearCase integration\x0d
- Architecture
- ToolTalk/ClearCase integration\x0d
- Architecture
- archives
- building
- incremental build issues and alternatives\x0d
- Example: Building an Archive
- config specs that show the results of nightly builds\x0d
- View That Uses Results of a Nightly Build
- selecting version created by nightly-build\x0d
- View That Uses Results of a Nightly Build
- at-sign characters (@@ - extended naming symbol)
- VOB-extended\x0d
- Extended Naming Scheme for Derived Objects
- at-sign etc. characters @(#) - (what string prefix)
- creating a what string using\x0d
- Creating a `what' String
- attributes (meta-data)
- change set common checkout enforcement\x0d
- Scenario: Change Sets
- configuring a view to select libraries based on
- configuring a view to show\x0d
- Variations on the Theme
- creating
- SoftBench ClearCase menu Make Attribute item description\x0d
- Using the SoftBench Development Manager
- disadvantages of
- for version selection control\x0d
- Can This Configuration Be Used for Development?
- implementing development policies with (chapter)\x0d
- Using Triggers, Attributes, and Locks to Implement Development Policies
- integer-valued
- associating changes with ECOs using (scenario)\x0d
- Scenario: Associating Changes with Change Orders
- searching for through an element
- with find (cleartool subcommand)\x0d
- View That Selects Versions Using `External Criteria'
- tracking file changes\x0d
- Scenario: Tracking State Transitions
- types
- config spec use of, for QA\x0d
- View That Selects Versions Using `External Criteria'
- version string
- adding to an executable (chapter)\x0d
- Adding a Timestamp to an Executable
- auto-make-branch facility
- multiple-level
- View That Implements Multiple-Level Branching
- parallel development environment planning (scenario)\x0d
- Work Environment Planning — Views
- version label use for making branches\x0d
- View That Allows an `Old' Configuration to be Modified
- background processes
- build audit issues\x0d
- Build Auditing and Background Processes
- running clearmake in
- emboldening loss on some architectures\x0d
- Invoking clearmake
- backslash escape character (\\)
- continuing command lines with\x0d
- cleartool Usage Overview
- baselevel
- term definition\x0d
- Project Overview
- baselevel-plus-changes model
- baselevel
- configuration, modifying\x0d
- View That Allows an `Old' Configuration to be Modified
- creating (scenario)\x0d
- Creating Baselevel 1
- describing versions that comprise\x0d
- What versions should the project start with?
- old, frozen configuration use in securing\x0d
- Frozen View, Defined by Version Labels
- creating a config spec that uses\x0d
- Composing Your Own Config Spec
- scenario\x0d
- Project Overview
- BLD_ARCH make-macro
- multiple-architecture development use\x0d
- Handling Build Procedure Differences
- bldserver.control file
- build server host use\x0d
- Server-Side Setup
- BMS (Broadcast Message Server-SoftBench)
- architecture\x0d
- Architecture
- BOS (Build Options Specification) files
- changing the effective build script with\x0d
- Using a Build Options Specification (BOS) File
- GNU make compatibility\x0d
- BOS Files and `Gnu Make' Compatibility
- branches
- advantages over attributes for version selection control\x0d
- Can This Configuration Be Used for Development?
- associating changes with ECOs using
- (scenario)\x0d
- Scenario: Associating Changes with Change Orders
- config specs for work that is to be isolated on\x0d
- View for New Development on a Branch
- creating
- reasons for specifying automatic creation\x0d
- Should branches be created automatically?
- SoftBench ClearCase menu Make Branch item description\x0d
- Using the SoftBench Development Manager
- isolating work on a bugfix with
- (scenario)\x0d
- Scenario: Isolating Work on a Bugfix
- major
- decommissioning (scenario)\x0d
- Decommissioning the `major' Branch
- performing merges from (scenario)\x0d
- Performing the Merges from the `major' Branch
- merging
- of data on (scenario)\x0d
- Merging of Data on Two Branches
- multiple-architecture development use\x0d
- Handling Source Code Differences
- multiple-level
- configuring views for
- View That Implements Multiple-Level Branching
- names
- description considerations\x0d
- On what branch will the project be working?
- obsoleting
- (scenario)\x0d
- Decommissioning the `major' Branch
- parallel development
- baselevel-plus-changes use\x0d
- Use of Branches
- restricting use
- (scenario)\x0d
- Further Restricting Use of the main Branch
- subbranches
- enforcing consistent use of, config specs (example)\x0d
- Work Environment Planning — Views
- isolating work with\x0d
- Techniques for Maintaining Privacy
- types
- config spec that creates instances of\x0d
- Making a Fix in the Program
- creating, for a new view\x0d
- Should branches be created automatically?
- creating, for version-label defined configuration\x0d
- View That Allows an `Old' Configuration to be Modified
- creating, parallel development (scenario)\x0d
- Creating Branch Types
- naming conventions\x0d
- Should branches be created automatically?
- Broadcast Message Server (BMS-SoftBench)
- architecture\x0d
- Architecture
- browsers
- characteristics and types\x0d
- Browsers
- file
- characteristics\x0d
- File Browser
- pointer actions and keystrokes (table)\x0d
- Basic Pointer Actions and Keystrokes
- toolbar item descriptions\x0d
- File Browser Toolbar
- list
- characteristics\x0d
- List Browsers
- pool
- characteristics\x0d
- Pool Browsers
- string
- characteristics\x0d
- String Browsers
- type object
- characteristics\x0d
- Type Object Browsers
- username
- characteristics\x0d
- Username Browsers
- viewtag
- characteristics\x0d
- View-tag Browsers
- xclearcase startup (figure)\x0d
- Starting xclearcase
- vobtag
- characteristics\x0d
- VOB-tag Browsers
- vtree
- characteristics\x0d
- Vtree Browsers
- build (management)
- audit
- background process issues\x0d
- Build Auditing and Background Processes
- corruption hazards\x0d
- Objects Written at More than One Level
- incremental build issues and alternatives\x0d
- Incremental Updating of Derived Objects
- performance procedures, in a non-ClearCase host build\x0d
- Performing an Audited Build in the Export View
- provided in clearaudit use with non-clearmake programs\x0d
- Compatibility between clearmake and Other make Variants
- setting up on a non-ClearCase host (chapter)\x0d
- Setting Up a Build on a
Non-ClearCase Host
- subsession independence of\x0d
- Build Sessions, Subsessions, and Hierarchical Builds
- build controller
- term definition\x0d
- Overview of Distributed Building
- clearaudit
- CR production procedure description\x0d
- Build Auditing and Background Processes
- non-clearmake make programs, recommendations\x0d
- Compatibility between clearmake and Other make Variants
- session, coordinating build reference times with\x0d
- Coordinating Reference Times of Several Builds
- clearmake
- -u option problems\x0d
- Problems with `Forced Builds'
- accomodating the name difference
- Accommodating clearmake's Different Name
- as the utility for\x0d
- Error Logs
- Using clearmake
- compatibility with other make variants (chapter)\x0d
- Compatibility between clearmake and Other make Variants
- imake use with\x0d
- Scenario
- incremental build issues and alternatives\x0d
- Remedies for the Incremental-Update Problem
- makefile optimization (chapter)\x0d
- Makefile Optimization
- overriding makefiles
- Handling Temporary Changes in the Build Procedure
- recording a released configuration\x0d
- Scenario: Recording a Released Configuration
- recording makefile with\x0d
- Configuring the Makefile
- recursive invocation
- Using a Recursive Invocation of clearmake
- scenario (figure)\x0d
- A Simple clearmake Build Scenario
- scenario\x0d
- A Simple clearmake Build Scenario
- SoftBench Builder, configuration to use\x0d
- Using the ClearCase/SoftBench Integration
- SoftBench, setting to run\x0d
- Setting the Build Program
- client
- term definition\x0d
- Overview of Distributed Building
- configuration lookup
- algorithm, comparison with standard make algorithms\x0d
- Why is Configuration Lookup Necessary?
- algorithm, limitations\x0d
- Explicit Dependencies on `Searched-For' Sources
- CR content and use\x0d
- More on CRs and Configuration Lookup
- DO use, with Sun make\x0d
- VPATH: Searches for Both Targets and Dependencies
- reasons for necessity of\x0d
- Why is Configuration Lookup Necessary?
- distributed
- as clearmake function\x0d
- Invoking clearmake
- setting up (chapter)\x0d
- Setting Up a Distributed Build
- starting\x0d
- Starting a Distributed Build
- forced
- object sharing problems\x0d
- Problems with `Forced Builds'
- hosts file
- syntax and use\x0d
- Client-Side Setup
- incremental-update scenario\x0d
- Example: Building an Archive
- layered
- config specs that support\x0d
- View That Uses Results of a Nightly Build
- multiple-architecture development
- handling procedure differences\x0d
- Handling Build Procedure Differences
- nightly
- config specs that show the results of\x0d
- View That Uses Results of a Nightly Build
- non-makefile-based\x0d
- Build Sessions, Subsessions, and Hierarchical Builds
- reference time
- term definition\x0d
- Continuing to Work During a Build / Reference Time
- scripts
- effective, changing with BOS files\x0d
- Using a Build Options Specification (BOS) File
- establishing CR hierarchy links in\x0d
- CR Hierarchies
- revising for an audited non-ClearCase host build\x0d
- Revising the Build Script
- standard makefiles required in\x0d
- Pathnames in Build Scripts
- VPATH substitutions, with Sun make\x0d
- VPATH Substitutions in Build Scripts
- server
- term definition\x0d
- Overview of Distributed Building
- sessions
- term definition\x0d
- Build Sessions, Subsessions, and Hierarchical Builds
- setting up on a non-ClearCase host (chapter)\x0d
- Setting Up a Build on a
Non-ClearCase Host
- SoftBench
- setting\x0d
- Setting the Build Program
- software
- for multiple architectures (chapter)\x0d
- Building Software for Multiple Architectures
- unattended, config specs that show the results of\x0d
- View That Uses Results of a Nightly Build
- starting
- clearmake command examples\x0d
- A Simple clearmake Build Scenario
- strategies
- incremental integration\x0d
- Using Config Spec `Time Rules' to Increase Your View's Isolation
- tracking limitations\x0d
- Explicitly-Declared Source Dependencies
- working during
- reference time facilitation of\x0d
- Continuing to Work During a Build / Reference Time
- C++ compiler
- incremental update issues\x0d
- Additional Incremental-Update Situations
- catcr (cleartool subcommand)
- CR hierarchy handling methods\x0d
- CR Hierarchies
- description (table)\x0d
- cleartool Subcommands
- displaying CR contents with\x0d
- More on CRs and Configuration Lookup
- catcs (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- displaying config specs for reconfigured views\x0d
- Configuring the View
- cautions
- branch use for multiple-architecture development\x0d
- Handling Source Code Differences
- build audit background process issues\x0d
- Build Auditing and Background Processes
- clearmake command -u option problems\x0d
- Problems with `Forced Builds'
- DOs written at multiple build session levels\x0d
- Objects Written at More than One Level
- flag files\x0d
- Explicitly-Declared Source Dependencies
- reference time use\x0d
- Continuing to Work During a Build / Reference Time
- removing shared DOs\x0d
- Explicit Removal of DOs
- SoftBench
- communicating with SoftBench servers on other hosts\x0d
- Using Views
- starting processes\x0d
- Using Views
- symbolic link use\x0d
- View Contexts: Summary
- time rule use\x0d
- Overprecise Use of Time Rules
- ToolTalk
- starting processes\x0d
- Using Views
- CC make-macro
- multiple-architecture development use\x0d
- Handling Build Procedure Differences
- cd (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- CFLAGS environment variable
- (example of use)\x0d
- Handling Temporary Changes in the Build Procedure
- CFLAGS make-macro
- multiple-architecture development use\x0d
- Handling Build Procedure Differences
- changes
- common checkout enforcement
- with attributes\x0d
- Scenario: Change Sets
- notification of
- trigger use for (scenario)\x0d
- Scenario: Customized Change Notification
- Scenario: Customized Change Notification
- checkout-edit-checkin model
- check-in
- controlling the execution of with triggers, monitoring status attribute use\x0d
- Scenario: Tracking State Transitions
- checkin (cleartool subcommand)
- default config spec actions\x0d
- Dynamic `Mainline' View
- description (table)\x0d
- cleartool Subcommands
- checkout (cleartool subcommand)
- canceling, SoftBench ClearCase menu Cancel Checkout item description\x0d
- Using the SoftBench Development Manager
- checking out elements\x0d
- Development Begins
- default config spec actions\x0d
- Dynamic `Mainline' View
- description (table)\x0d
- cleartool Subcommands
- SoftBench ClearCase menu Checkout item description\x0d
- Using the SoftBench Development Manager
- checkouts
- change sets, enforcing group checkout, with attributes\x0d
- Scenario: Change Sets
- CR listing of\x0d
- Listing CRs
- listing records, SoftBench ClearCase menu List Checkouts item description\x0d
- Using the SoftBench Development Manager
- preventing, config specs used for\x0d
- View That Restricts Changes to a Single Directory
- SoftBench ClearCase menu Check In item description\x0d
- Using the SoftBench Development Manager
- chevent (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- revising an event record comment string\x0d
- Examining Event Records
- chpool (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- chtype (cleartool subcommand)
- changing element type\x0d
- Element Types and Type Managers
- description (table)\x0d
- cleartool Subcommands
- clearaudit(1A) command
- non-clearmake make programs
- recommendations\x0d
- Compatibility between clearmake and Other make Variants
- session
- coordinating build reference times with\x0d
- Coordinating Reference Times of Several Builds
- ClearCase
- development strategy issues\x0d
- Development Strategy
- CLEARCASE_BLD_CONC environment variable
- distributed build use\x0d
- Starting a Distributed Build
- CLEARCASE_BLD_UMASK environment variable
- shared DO use of\x0d
- Wink-in, Permissions on Derived Objects, and clearcase_bld_umask
- CLEARCASE_MSG_PROTO environment variable
- SoftBench setting
- one-way messaging enabled by\x0d
- One-Way Messaging
- ToolTalk setting
- one-way messaging enabled by\x0d
- Standalone Notice Forwarding
- $CLEARCASE_PN environment variable
- pre-operation trigger use
- (scenario)\x0d
- Scenario: Enforcing Quality Standards
- .clearcase_profile file
- customizing comment-handling\x0d
- Customizing Comment Handling
- clearencap_sb process
- encapsulator process for SoftBench
- characteristics\x0d
- Architecture
- clearencap_tt process
- encapsulator process for ToolTalk\x0d
- Architecture
- clearmake(1A) command
- -u option
- forcing rebuilds with\x0d
- Problems with `Forced Builds'
- accommodating the name difference
- Accommodating clearmake's Different Name
- BOS file use to change effective build scripts\x0d
- Using a Build Options Specification (BOS) File
- compatibility
- modes\x0d
- `clearmake' Compatibility Modes
- with other make programs (chapter)\x0d
- Compatibility between clearmake and Other make Variants
- CR production procedure description\x0d
- Build Auditing and Background Processes
- increasing the verbosity level
- Increasing clearmake's Verbosity Level
- invoking\x0d
- Invoking clearmake
- MAKEFILE macro\x0d
- Configuring the Makefile
- options
- enhanced functionality\x0d
- Invoking clearmake
- options\x0d
- Invoking clearmake
- recording makefile versions\x0d
- Configuring the Makefile
- recursive invocation
- Using a Recursive Invocation of clearmake
- scenario
- recording a released configuration\x0d
- Scenario: Recording a Released Configuration
- simple build, (figure)\x0d
- A Simple clearmake Build Scenario
- simple build\x0d
- A Simple clearmake Build Scenario
- SoftBench Builder use of\x0d
- Using the ClearCase/SoftBench Integration
- using\x0d
- Using clearmake
- cleartool command
- option syntax
- Command Options
- pathnames in\x0d
- Pathnames in cleartool Commands
- subcommands
- basic set for day-to-day needs\x0d
- cleartool Subcommands
- list and description (table)\x0d
- cleartool Subcommands
- using
- overview\x0d
- cleartool Usage Overview
- using\x0d
- Using the ClearCase
Command Line Interface
- cleartool subcommands
- annotate\x0d
- cleartool Subcommands
- apropos\x0d
- cleartool Subcommands
- catcr\x0d
- More on CRs and Configuration Lookup
- CR Hierarchies
- cleartool Subcommands
- catcs\x0d
- cleartool Subcommands
- Configuring the View
- cd\x0d
- cleartool Subcommands
- checkin\x0d
- Dynamic `Mainline' View
- checkout\x0d
- Using the SoftBench Development Manager
- Dynamic `Mainline' View
- Development Begins
- Using the SoftBench Development Manager
- chevent\x0d
- cleartool Subcommands
- Examining Event Records
- chpool\x0d
- cleartool Subcommands
- chtype\x0d
- cleartool Subcommands
- Element Types and Type Managers
- describe\x0d
- cleartool Subcommands
- diff\x0d
- cleartool Subcommands
- Implementing a New `compare' Method
- diffcr\x0d
- Comparing CRs
- CR Hierarchies
- cleartool Subcommands
- edcs\x0d
- Setting Up the Test View
- cleartool Subcommands
- find\x0d
- Techniques for Maintaining Privacy
- View That Selects Versions Using `External Criteria'
- cleartool Subcommands
- findmerge\x0d
- cleartool Subcommands
- Preparing to Merge
- Performing Merges
- Preparing to Merge from the major Branch
- Preparing to Merge
- help\x0d
- cleartool Subcommands
- ln\x0d
- cleartool Subcommands
- lock\x0d
- Labeling Sources
- Permissions Checking and Locks
- Preparing to Merge from the major Branch
- Implementing a Final Bugfix
- cleartool Subcommands
- Frozen View, Defined by Version Labels
- ls\x0d
- Selecting Versions That Built a Particular Program
- View That Shows Only One Developer's Changes
- cleartool Subcommands
- Frozen View, Defined by Version Labels
- lscheckout\x0d
- Examining Event Records
- Preparing to Merge
- cleartool Subcommands
- Preparing to Merge from the major Branch
- Labeling Sources
- lsdo\x0d
- Zero Reference Counts
- Extended Naming Scheme for Derived Objects
- Promotion of DOs
- cleartool Subcommands
- lshistory\x0d
- cleartool Subcommands
- Examining Event Records
- lslock\x0d
- Examining Event Records
- cleartool Subcommands
- lspool\x0d
- cleartool Subcommands
- Examining Event Records
- lsprivate\x0d
- cleartool Subcommands
- lstype\x0d
- cleartool Subcommands
- Examining Event Records
- lsview\x0d
- cleartool Subcommands
- cleartool Subcommands
- lsvob\x0d
- cleartool Subcommands
- lsvtree\x0d
- cleartool Subcommands
- man\x0d
- Getting Help
- man\x0d
- cleartool Subcommands
- merge\x0d
- cleartool Subcommands
- mkattr\x0d
- cleartool Subcommands
- mkattype\x0d
- Scenario: Tracking State Transitions
- cleartool Subcommands
- mkbranch\x0d
- cleartool Subcommands
- mkbrtype\x0d
- cleartool Subcommands
- View That Allows an `Old' Configuration to be Modified
- Creating Branch Types
- mkdir\x0d
- cleartool Subcommands
- mkelem\x0d
- Element Types and Type Managers
- Element Types and Type Managers
- Where Is the `/main/LATEST' Rule?
- cleartool Subcommands
- mkeltype\x0d
- Predefined and User-Defined Element Types
- cleartool Subcommands
- mkhlink\x0d
- cleartool Subcommands
- mkhltype\x0d
- cleartool Subcommands
- mklabel\x0d
- CR Hierarchies
- Scenario: Recording a Released Configuration
- Labeling Sources
- cleartool Subcommands
- Implementing a Final Bugfix
- mklbtype\x0d
- Labeling Sources
- cleartool Subcommands
- Labeling Sources
- Scenario: Recording a Released Configuration
- mkpool\x0d
- cleartool Subcommands
- mktag\x0d
- Performing an Audited Build in the Export View
- cleartool Subcommands
- Integration and Test
- mktrigger\x0d
- cleartool Subcommands
- mktrtype\x0d
- Scenario: Requiring Good Documentation of Changes
- cleartool Subcommands
- Setting Up the Trigger to Monitor Bugfixing
- mkview \x0d
- Setting Up the Test View
- mkview\x0d
- CLI: Enter a `mkview' Command
- Integration and Test
- Creating, Configuring, and Registering Views
- cleartool Subcommands
- Dynamic `Mainline' View
- mkvob\x0d
- cleartool Subcommands
- mount\x0d
- cleartool Subcommands
- mv\x0d
- cleartool Subcommands
- protect\x0d
- cleartool Subcommands
- protectvob\x0d
- cleartool Subcommands
- pwd\x0d
- cleartool Subcommands
- pwv\x0d
- cleartool Subcommands
- quit\x0d
- cleartool Subcommands
- recoverview\x0d
- cleartool Subcommands
- reformatview\x0d
- cleartool Subcommands
- reformatvob\x0d
- cleartool Subcommands
- register\x0d
- cleartool Subcommands
- reserve\x0d
- cleartool Subcommands
- rmattr\x0d
- cleartool Subcommands
- rmbranch\x0d
- cleartool Subcommands
- rmdo\x0d
- Explicit Removal of DOs
- cleartool Subcommands
- rmelem\x0d
- Frozen View, Defined by Time
- cleartool Subcommands
- rmhlink\x0d
- cleartool Subcommands
- rmlabel\x0d
- cleartool Subcommands
- rmmerge\x0d
- cleartool Subcommands
- rmname\x0d
- cleartool Subcommands
- rmpool\x0d
- cleartool Subcommands
- rmtag\x0d
- cleartool Subcommands
- rmtrigger\x0d
- cleartool Subcommands
- rmtype\x0d
- cleartool Subcommands
- Wrapping Up
- rmver\x0d
- cleartool Subcommands
- Frozen View, Defined by Time
- rmview\x0d
- Deleting the Integration View
- cleartool Subcommands
- rmvob\x0d
- cleartool Subcommands
- rnpool\x0d
- cleartool Subcommands
- rntype\x0d
- cleartool Subcommands
- setcs\x0d
- cleartool Subcommands
- Configuring the View
- Creating, Configuring, and Registering Views
- Variations on the Theme
- setview
- Setting Up an Export View
- setview\x0d
- cleartool Subcommands
- CLI: Enter a setview Command
- Preparing to Merge
- Development Begins
- Labeling Sources
- Preparing to Merge from the major Branch
- shell\x0d
- cleartool Subcommands
- space\x0d
- cleartool Subcommands
- startview
- Setting Up an Export View
- startview\x0d
- cleartool Subcommands
- umount\x0d
- cleartool Subcommands
- uncheckout\x0d
- cleartool Subcommands
- Using the SoftBench Development Manager
- unlock\x0d
- Further Restricting Use of the main Branch
- Wrapping Up
- Implementing a Final Bugfix
- Performing Merges
- cleartool Subcommands
- unregister\x0d
- cleartool Subcommands
- unreserve\x0d
- cleartool Subcommands
- wink-in\x0d
- cleartool Subcommands
- winkin\x0d
- Extended Naming Scheme for Derived Objects
- Wink-In without Configuration Lookup / The `winkin' Command
- xdiff\x0d
- cleartool Subcommands
- xlsvtree\x0d
- cleartool Subcommands
- Using the SoftBench Development Manager
- xmerge\x0d
- cleartool Subcommands
- clients
- distributed build
- controls\x0d
- Overview of Distributed Building
- host file syntax and use\x0d
- Client-Side Setup
- clock skew
- term definition\x0d
- Continuing to Work During a Build / Reference Time
- color schemes
- setting\x0d
- Setting Your Color Scheme
- command line interface (CLI)
- command-line processing
- cleartool\x0d
- Command-Line Processing
- enter a `setview' command\x0d
- CLI: Enter a setview Command
- interactive mode
- cleartool use\x0d
- cleartool Usage Overview
- Command-Line Processing
- single-command mode
- cleartool command-line processing\x0d
- Command-Line Processing
- using
- (chapter)\x0d
- Using the ClearCase
Command Line Interface
- commands
- cleartool subcommands
- list and description (table)\x0d
- Using cleartool
- comment string options\x0d
- Event Records and Comments
- names
- abbreviations and aliases for\x0d
- Command Abbreviations and Aliases
- options
- creating what version option\x0d
- Implementing a `-Ver' Option
- syntax and use\x0d
- Command Options
- substitution
- cleartool does not perform\x0d
- Command-Line Processing
- syntax summary
- displaying\x0d
- Getting Help
- comments
- adding to event records\x0d
- Event Records and Comments
- customizing\x0d
- Customizing Comment Handling
- strings
- command options\x0d
- Event Records and Comments
- compare methods
- implementing a new version\x0d
- Implementing a New `compare' Method
- compatibility
- clearmake and other make programs (chapter)\x0d
- Compatibility between clearmake and Other make Variants
- make
- limitations\x0d
- Compatibility Limitations
- compound object build algorithm
- Clearmake issues and alternatives\x0d
- Remedies for the Incremental-Update Problem
- config specs
- attribute type use in\x0d
- View That Selects Versions Using `External Criteria'
- auto-make-branch
- parallel development environment planning (scenario)\x0d
- Work Environment Planning — Views
- characteristics, creation, and modification\x0d
- Configuring the View
- configuration rules
- -config qualifier\x0d
- Selecting Versions That Built a Particular Program
- Selecting Versions That Built a Set of Programs
- Making a Fix in the Program
- -file qualifier\x0d
- Can This Configuration Be Used for Development?
- View That Selects Versions Using `External Criteria'
- -mkbranch qualifier\x0d
- Making a Fix in the Program
- Where Is the `/main/LATEST' Rule?
- Can This Configuration Be Used for Development?
- View for New Development on a Branch
- View That Allows an `Old' Configuration to be Modified
- -nocheckout qualifier\x0d
- View That Restricts Changes to a Single Directory
- Frozen View, Defined by Time
- Frozen View, Defined by Version Labels
- -time qualifier\x0d
- Variations on the Theme
- Variations on the Theme
- CHECKEDOUT, characteristics\x0d
- The Standard Configuration Rules
- CHECKEDOUT, not used by frozen configurations\x0d
- Frozen View, Defined by Version Labels
- CHECKEDOUT, reasons for not using\x0d
- View That Shows Only One Developer's Changes
- CHECKEDOUT\x0d
- Can This Configuration Be Used for Development?
- listing with ls command\x0d
- View That Shows Only One Developer's Changes
- /main/LATEST, -nocheckout qualifier\x0d
- Frozen View, Defined by Time
- /main/LATEST, -time qualifier\x0d
- Frozen View, Defined by Time
- /main/LATEST, characteristics\x0d
- The Standard Configuration Rules
- /main/LATEST, when not to use\x0d
- Where Is the `/main/LATEST' Rule?
- /main/LATEST\x0d
- View That Shows Only One Developer's Changes
- ordering considerations\x0d
- Selecting Versions That Built a Set of Programs
- pattern matching in\x0d
- View That Restricts Changes to a Single Directory
- restricting directory selection\x0d
- View That Restricts Changes to a Single Directory
- selecting application subsystems\x0d
- Playing Mix-and-Match with Application Subsystems
- standard, characteristics\x0d
- The Standard Configuration Rules
- time, cautions on overprecise and inappropriate use of\x0d
- Inappropriate Use of Time Rules
- time, rolling back the clock with\x0d
- Using Config Spec `Time Rules' to Increase Your View's Isolation
- creating
- for a new view\x0d
- Creating, Configuring, and Registering Views
- project-standard (scenario)\x0d
- Creating Project-Standard Config Specs
- questions to consider when\x0d
- Composing Your Own Config Spec
- default
- characteristics\x0d
- Dynamic `Mainline' View
- explanation of appropriate use\x0d
- Configuring the View
- parallel development environment planning (scenario)\x0d
- Work Environment Planning — Views
- editing
- SoftBench ClearCase menu Edit Configuration Specification item description\x0d
- Using the SoftBench Development Manager
- examples and uses
- (chapter)\x0d
- Defining View Configurations
- for new development on a branch\x0d
- View for New Development on a Branch
- include facility
- setting up standard sets of configuration rules (example)\x0d
- Scenario: Isolating All Users from Each Other
- include facility\x0d
- Variations on the Theme
- Configuring the View
- isolating
- users from each other, (example)\x0d
- Scenario: Isolating All Users from Each Other
- work on a bugfix with (scenario)\x0d
- Scenario: Isolating Work on a Bugfix
- mixing application subsystems\x0d
- Playing Mix-and-Match with Application Subsystems
- modifying
- a view with\x0d
- Modify the View's Config Spec
- to reconfigure a view\x0d
- Configuring the View
- multiple-level branching
- View That Implements Multiple-Level Branching
- parallel development environment planning
- (scenario)\x0d
- Work Environment Planning — Views
- project-specific
- reconfiguring a view using\x0d
- Configuring the View
- quality assurance\x0d
- View That Selects Versions Using `External Criteria'
- restricting to single directory\x0d
- View That Restricts Changes to a Single Directory
- selecting
- a particular program\x0d
- Selecting Versions That Built a Particular Program
- a set of programs\x0d
- Selecting Versions That Built a Set of Programs
- showing
- one developer's changes\x0d
- View That Shows Only One Developer's Changes
- the results of nightly builds\x0d
- View That Uses Results of a Nightly Build
- time rules
- rolling back the clock with\x0d
- Using Config Spec `Time Rules' to Increase Your View's Isolation
- version label use\x0d
- View That Allows an `Old' Configuration to be Modified
- view
- creating strategies\x0d
- Planning the View
- configuration(s)
- dynamic
- config spec example\x0d
- Dynamic `Mainline' View
- frozen
- config spec, defined by time\x0d
- Frozen View, Defined by Time
- config spec, defined by version labels\x0d
- Frozen View, Defined by Version Labels
- unfreezing\x0d
- Variations on the Theme
- HP VUE
- Configuring HP VUE
- lookup
- algorithm, comparison with standard make algorithms\x0d
- Why is Configuration Lookup Necessary?
- algorithm, limitations\x0d
- Explicit Dependencies on `Searched-For' Sources
- as clearmake function\x0d
- Invoking clearmake
- CR content and use\x0d
- More on CRs and Configuration Lookup
- DO use, with Sun make\x0d
- VPATH: Searches for Both Targets and Dependencies
- reasons for necessity of\x0d
- Why is Configuration Lookup Necessary?
- maintaining old\x0d
- Frozen View, Defined by Version Labels
- makefiles\x0d
- Configuring the Makefile
- management
- config specs that support different goals, (chapter)\x0d
- Defining View Configurations
- SoftBench integration with ClearCase\x0d
- Architecture
- modifying
- version-label use for\x0d
- View That Allows an `Old' Configuration to be Modified
- of views
- with element types\x0d
- Using Element Types to Configure a View
- released
- recording, with label types\x0d
- Scenario: Recording a Released Configuration
- SoftBench Development Manager
- for ClearCase\x0d
- Configuring the Development Manager for ClearCase
- construct_version method
- characteristics and use in creating a new type manager\x0d
- The `construct_version' Method
- cpp(1) C preprocessor
- macros
- defining architecture-specific\x0d
- Defining Architecture-Specific CPP Macros
- imake use\x0d
- Alternative Approach, Using `imake'
- multiple-architecture development use\x0d
- Issues in Multiple-Architecture Development
- cpp(1) macros
- DATE
- timestamp generation with\x0d
- Creating a `what' String
- CR (configuration records)
- (chapter)\x0d
- Derived Objects and Configuration Records
- comparing
- SoftBench ClearCase menu Compare Configuration Records item description\x0d
- Using the SoftBench Development Manager
- with diffcr\x0d
- Comparing CRs
- created by clearaudit use with non-clearmake programs\x0d
- Compatibility between clearmake and Other make Variants
- creating
- as clearmake function\x0d
- Invoking clearmake
- on a non-ClearCase host (chapter)\x0d
- Setting Up a Build on a
Non-ClearCase Host
- displaying
- SoftBench ClearCase menu Cat Configuration Record item description\x0d
- Using the SoftBench Development Manager
- displaying\x0d
- More on CRs and Configuration Lookup
- forcing the recording of objects in
- through explicit declarations\x0d
- Explicitly-Declared Source Dependencies
- hierarchies
- methods for handling\x0d
- CR Hierarchies
- not automatically created during a build\x0d
- No Automatic Creation of Configuration Record Hierarchy
- information contained in
- (annotated figure)\x0d
- Listing CRs
- listing
- SoftBench ClearCase menu Cat Configuration Record item description\x0d
- Using the SoftBench Development Manager
- with catcr\x0d
- More on CRs and Configuration Lookup
- management of\x0d
- Management of DOs and CRs
- per-target
- incremental update issues\x0d
- Additional Incremental-Update Situations
- selecting versions from\x0d
- Selecting Versions That Built a Particular Program
- storage structures\x0d
- Storage of DOs and CRs
- version labeling use of\x0d
- Scenario: Recording a Released Configuration
- create_version method
- characteristics and use in creating a new type manager\x0d
- The `create_version' Method
- customization
- files (chapter)\x0d
- Type Managers and Customized Processing of File Elements
- SoftBench
- environment, through adding items to the ClearCase menu\x0d
- Using the ClearCase/SoftBench Integration
- SoftBench\x0d
- Customization
- data
- container
- term definition\x0d
- Storage of DOs and CRs
- freezing
- lock use for\x0d
- Scenario: Freezing Certain Data
- handling
- file type, element type, and type manager interactions (figure)\x0d
- Element Types and Type Managers
- structures
- CRs (chapter)\x0d
- Derived Objects and Configuration Records
- DOs (chapter)\x0d
- Derived Objects and Configuration Records
- types
- browsers, that can display (table)\x0d
- Browsers and Data Types
- DATE macro
- timestamp generation with\x0d
- Creating a `what' String
- debugging
- -time qualifier use to restore a previous environment\x0d
- Variations on the Theme
- bugfixing
- during final release validation (scenario)\x0d
- Final Validation - Creating Release 2.0
- implementing, (scenario)\x0d
- Implementing a Final Bugfix
- isolating work on a (scenario)\x0d
- Scenario: Isolating Work on a Bugfix
- managing (scenario)\x0d
- Project Overview
- time rules use for incompatible change handling\x0d
- Techniques for Maintaining Privacy
- trigger use for monitoring, (scenario)\x0d
- Setting Up the Trigger to Monitor Bugfixing
- config specs
- converting build config specs to development config specs for\x0d
- Making a Fix in the Program
- rolling back the clock with config spec time rules\x0d
- Using Config Spec `Time Rules' to Increase Your View's Isolation
- CRs
- comparing, with diffcr\x0d
- Comparing CRs
- forced builds
- object sharing problems\x0d
- Problems with `Forced Builds'
- freezing configurations to restore a previous environment\x0d
- Frozen View, Defined by Time
- getting help\x0d
- Getting Help
- standard make compatibility problems\x0d
- Compatibility Limitations
- wrong-version-checked-out problem
- avoiding
- Can This Configuration Be Used for Development?
- dependencies
- build tool\x0d
- Explicit Dependencies on `Searched-For' Sources
- build-order\x0d
- Build-Order Dependencies
- explicit
- declaring input files as, for an audited non-ClearCase host build\x0d
- Revising the Build Script
- necessity for in searched-for sources\x0d
- Explicit Dependencies on `Searched-For' Sources
- specifying makefile versions in\x0d
- Configuring the Makefile
- incremental
- Clearmake issues and alternatives\x0d
- Incremental Updating of Derived Objects
- list
- specifying makefile versions in\x0d
- Configuring the Makefile
- monet project development (list)\x0d
- Project Overview
- MVFS files
- automatic detection of\x0d
- Listing CRs
- non-MVFS files
- CR listing of explicitly declared\x0d
- Listing CRs
- source
- CR provision of complete list, after a DO rebuild\x0d
- Declaring Source Dependencies in Makefiles
- declaring in makefiles\x0d
- Declaring Source Dependencies in Makefiles
- explicit declaration, reasons for\x0d
- Explicitly-Declared Source Dependencies
- on MVFS files, automatic detection of\x0d
- Listing CRs
- target/dependencies line
- establishing CR hierarchy links in\x0d
- CR Hierarchies
- tools
- (figure)\x0d
- Explicitly-Declared Source Dependencies
- VOB, eliminating explicit dependency declarations with\x0d
- Explicitly-Declared Source Dependencies
- VPATH macro
- use with Sun make\x0d
- VPATH: Searches for Both Targets and Dependencies
- when to use\x0d
- Explicit Dependencies on `Searched-For' Sources
- describe (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- development
- conditional compilation
- multiple-architecture development use\x0d
- Issues in Multiple-Architecture Development
- distributed
- build management (chapter)\x0d
- Setting Up a Distributed Build
- management
- scenario (chapter)\x0d
- Using ClearCase to Organize and Implement Parallel Development
- milestones
- element evolution (figure)\x0d
- Use of Branches
- perusing changes since\x0d
- View That Shows Only One Developer's Changes
- multiple architecture targets
- issues\x0d
- Issues in Multiple-Architecture Development
- parallel
- build, as clearmake function\x0d
- Invoking clearmake
- environment, isolating users from each other, (example)\x0d
- Scenario: Isolating All Users from Each Other
- environment, organization and implementation (chapter)\x0d
- Using ClearCase to Organize and Implement Parallel Development
- synchronizing, (scenario)\x0d
- Synchronizing Ongoing Development
- strategy issues\x0d
- Development Strategy
- testing
- (scenario)\x0d
- Integration and Test
- view
- changing config specs to\x0d
- Making a Fix in the Program
- diff (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- implementing a new compare method for\x0d
- Implementing a New `compare' Method
- diffcr (cleartool subcommand)
- comparing
- CRs\x0d
- Comparing CRs
- CR hierarchy handling methods\x0d
- CR Hierarchies
- directories
- comparing
- with xcleardiff\x0d
- Comparing Directories
- config specs that restrict changes to a single\x0d
- View That Restricts Changes to a Single Directory
- creating
- SoftBench ClearCase menu Make Directory item description\x0d
- Using the SoftBench Development Manager
- current working
- changing to another view\x0d
- Working Directory View
- elements
- disallowing automatic creation of, config specs (example)\x0d
- Work Environment Planning — Views
- inheritance list, attaching triggers to (scenario)\x0d
- Scenario: Customized Change Notification
- type, differences between file element types and (footnote)\x0d
- Element Types and Type Managers
- type manager
- creating\x0d
- Creating the Type Manager Directory
- /usr/atria/examples/mkeltype
- element type shell scripts contained in\x0d
- Predefined and User-Defined Element Types
- /usr/atria/lib/mgrs
- predefined type managers found in\x0d
- Predefined and User-Defined Type Managers
- versions
- listing with catcr -long\x0d
- Listing CRs
- view storage
- naming considerations\x0d
- Choose a Name
- views implemented as\x0d
- Choose a Location
- DISPLAY environment variable
- SoftBench and ClearCase values required to be the same\x0d
- Error Conditions
- ToolTalk and ClearCase values required to be the same\x0d
- Standalone Notice Forwarding
- DOs (derived objects)
- (chapter)\x0d
- Derived Objects and Configuration Records
- accessing
- standard software restrictions\x0d
- Extended Naming Scheme for Derived Objects
- through extended pathnames\x0d
- Derived Objects and Configuration Records
- transparency impact on\x0d
- Setting a View
- automatic deletion of related information from the VOB\x0d
- Derived Object Scrubbing
- avoiding multiple source file versions\x0d
- Selecting Versions That Built a Set of Programs
- cleartool subcommands for working with (table)
- cleartool Subcommands
- cleartool Subcommands
- converting view-private files into
- in a non-ClearCase host build\x0d
- Revising the Build Script
- CR (configuration records)
- displaying, with catcr\x0d
- More on CRs and Configuration Lookup
- relationship\x0d
- Storage of DOs and CRs
- CR (configuration records)\x0d
- Selecting Versions That Built a Particular Program
- creating
- as clearmake function\x0d
- Invoking clearmake
- incremental build issues\x0d
- Incremental Updating of Derived Objects
- simple scenario\x0d
- A Simple clearmake Build Scenario
- DO-ID
- accessing DOs with\x0d
- Extended Naming Scheme for Derived Objects
- config spec that includes\x0d
- Selecting Versions That Built a Particular Program
- executable
- adding timestamps to (chapter)\x0d
- Adding a Timestamp to an Executable
- hard links\x0d
- DO Reference Counts
- listing
- with lsdo\x0d
- Extended Naming Scheme for Derived Objects
- managing\x0d
- Management of DOs and CRs
- multiple-architecture development handling\x0d
- Issues in Multiple-Architecture Development
- multiple-architecture development issues\x0d
- Segregating the Derived Objects of Different Variants
- permissions
- practices that enhance sharing\x0d
- Wink-in, Permissions on Derived Objects, and clearcase_bld_umask
- promotion
- term definition and characteristics\x0d
- Promotion of DOs
- reference counts\x0d
- DO Reference Counts
- removing
- explicitly\x0d
- Explicit Removal of DOs
- removing\x0d
- Derived Object Scrubbing
- reuse
- (figure)\x0d
- A Simple clearmake Build Scenario
- vs. wink-in\x0d
- A Simple clearmake Build Scenario
- shared
- forced build problems\x0d
- Problems with `Forced Builds'
- storage structures\x0d
- Storage of DOs and CRs
- versions
- config specs that check in\x0d
- View That Uses Results of a Nightly Build
- versions\x0d
- Selecting Versions That Built a Particular Program
- VPATH search
- with Sun make\x0d
- VPATH: Searches for Both Targets and Dependencies
- written at multiple build session levels
- cautions and workarounds\x0d
- Objects Written at More than One Level
- ECOs
- associating changes with
- attribute, branches, and triggers use for (scenario)\x0d
- Scenario: Associating Changes with Change Orders
- edcs (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- editing config specs\x0d
- Setting Up the Test View
- element(s)
- as instances of element types\x0d
- Element Types and Type Managers
- creating
- during modification, configuration rule that permits\x0d
- Where Is the `/main/LATEST' Rule?
- SoftBench ClearCase menu Make Element item description\x0d
- Using the SoftBench Development Manager
- creating\x0d
- Will you be creating new elements?
- development
- evolution, during (scenario example)\x0d
- Use of Branches
- evolution, milestones (figure)\x0d
- Use of Branches
- directory
- disallowing automatic creation of, config specs (example)\x0d
- Work Environment Planning — Views
- inheritance list, attaching triggers to (scenario)\x0d
- Scenario: Customized Change Notification
- preventing creation of
- with frozen configurations\x0d
- Frozen View, Defined by Time
- Frozen View, Defined by Version Labels
- state transition model
- tracking, with attributes, branches, locks, version labels, and triggers (scenarios)\x0d
- Scenario: Tracking State Transitions
- tracking changes in
- attributes, branches, locks, version labels, and triggers (scenarios)\x0d
- Scenario: Tracking State Transitions
- types
- applications\x0d
- Other Applications of Element Types
- configuring views with\x0d
- Using Element Types to Configure a View
- consistency among VOBs, as manual administrative task (footnote)\x0d
- Element Types and Type Managers
- converting\x0d
- Installing and Using the Type Manager
- Installing and Using the Type Manager
- creating\x0d
- Predefined and User-Defined Element Types
- Installing and Using the Type Manager
- determining for a newly created element (example)\x0d
- Element Types and Type Managers
- directories (footnote)\x0d
- Element Types and Type Managers
- mechanisms compared with file-typing mechanisms\x0d
- Element Types and Type Managers
- predefined, characteristics\x0d
- Predefined and User-Defined Element Types
- processing files with\x0d
- Processing Files by Element Type
- type managers and\x0d
- Element Types and Type Managers
- ellipsis characters (...)
- branch name use\x0d
- On what branch will the project be working?
- encapsulation
- SoftBench
- ClearCase integration\x0d
- Architecture
- using (chapter)\x0d
- Using the ClearCase/SoftBench Integration
- environment
- development
- monet project specifications\x0d
- Defining View Configurations
- parallel, isolating users from each other, (example)\x0d
- Scenario: Isolating All Users from Each Other
- parallel, organization and implementation (chapter)\x0d
- Using ClearCase to Organize and Implement Parallel Development
- parallel, planning (scenario)\x0d
- Work Environment Planning — Views
- previous
- -time qualifier use to restore\x0d
- Variations on the Theme
- freezing configurations to restore a\x0d
- Frozen View, Defined by Time
- SoftBench
- customization, through adding items to the ClearCase menu\x0d
- Using the ClearCase/SoftBench Integration
- variables
- CFLAGS\x0d
- Handling Temporary Changes in the Build Procedure
- CLEARCASE_BLD_CONC\x0d
- Starting a Distributed Build
- CLEARCASE_BLD_UMASK\x0d
- Wink-in, Permissions on Derived Objects, and clearcase_bld_umask
- CLEARCASE_MSG_PROTO\x0d
- One-Way Messaging
- Standalone Notice Forwarding
- $CLEARCASE_PN\x0d
- Scenario: Enforcing Quality Standards
- DISPLAY\x0d
- Standalone Notice Forwarding
- Error Conditions
- MAGIC_PATH (footnote)\x0d
- Element Types and Type Managers
- multiple-architecture development use\x0d
- Handling Build Procedure Differences
- non-expansion by cleartool\x0d
- Command-Line Processing
- errors
- error logs
- Error Logs
- SoftBench\x0d
- Error Conditions
- event records (meta-data)
- comment strings
- customizing\x0d
- Customizing Comment Handling
- trigger to enforce\x0d
- Scenario: Requiring Good Documentation of Changes
- comment strings\x0d
- Event Records and Comments
- detailed discussion of\x0d
- Event Records and Comments
- displaying\x0d
- Examining Event Records
- examining\x0d
- Examining Event Records
- events
- history
- displaying, SoftBench ClearCase menu List History item description\x0d
- Using the SoftBench Development Manager
- examples
- attributes
- tracking file changes\x0d
- Scenario: Tracking State Transitions
- state transition tracking
- with attributes, branches, locks, version labels, and triggers (scenarios)\x0d
- Scenario: Tracking State Transitions
- triggers
- pre-operation, monitoring event record comment strings\x0d
- Scenario: Requiring Good Documentation of Changes
- pre-operation, status checking script\x0d
- Scenario: Tracking State Transitions
- pre-operation, tracking file changes\x0d
- Scenario: Tracking State Transitions
- executables
- adding timestamps to (chapter)\x0d
- Adding a Timestamp to an Executable
- multiple-architecture development handling\x0d
- Issues in Multiple-Architecture Development
- exiting
- cleartool command
- exit status\x0d
- Exit Status
- file(s)
- architecture-dependent template
- multiple-architecture development use\x0d
- Alternative Approach, Using `imake'
- bldserver.control
- build server host use\x0d
- Server-Side Setup
- BOS
- changing the effective build script with\x0d
- Using a Build Options Specification (BOS) File
- GNU make compatibility\x0d
- BOS Files and `Gnu Make' Compatibility
- browsers
- characteristics\x0d
- File Browser
- pointer actions and keystrokes (table)\x0d
- Basic Pointer Actions and Keystrokes
- toolbar item descriptions\x0d
- File Browser Toolbar
- classifying (chapter)\x0d
- Type Managers and Customized Processing of File Elements
- .clearcase_profile
- customizing comment-handling\x0d
- Customizing Comment Handling
- comparing
- with xcleardiff\x0d
- Comparing Files
- configuration rules
- -file qualifier\x0d
- Can This Configuration Be Used for Development?
- View That Selects Versions Using `External Criteria'
- customized handling (chapter)\x0d
- Type Managers and Customized Processing of File Elements
- flag
- importance of using view-private files as\x0d
- Explicitly-Declared Source Dependencies
- graphically comparing and merging with xcleardiff (chapter)\x0d
- Comparing and Merging Files Graphically with xcleardiff
- header
- config specs that select application subsystems use of\x0d
- Playing Mix-and-Match with Application Subsystems
- include facility
- config spec use\x0d
- Variations on the Theme
- magic
- file typing capabilities\x0d
- File Typing
- MAGIC_PATH environment variable (footnote)\x0d
- Element Types and Type Managers
- revising\x0d
- Installing and Using the Type Manager
- merging
- with xcleardiff\x0d
- Merging Files
- nroff
- type manager for\x0d
- Type Manager for Manual Page Source Files
- pattern matching\x0d
- View That Restricts Changes to a Single Directory
- processing
- using element types\x0d
- Processing Files by Element Type
- source
- tracking changes to, with attributes and triggers\x0d
- Scenario: Tracking State Transitions
- stdin description
- not supported by clearmake\x0d
- Standard `make' Command Line Options Not Supported
- template
- architecture-dependent, multiple-architecture development use\x0d
- Alternative Approach, Using `imake'
- tracking changes in
- with attributes and triggers\x0d
- Scenario: Tracking State Transitions
- types
- handling\x0d
- File Typing
- mechanisms compared with element-typing mechanisms\x0d
- Element Types and Type Managers
- /usr/adm/atria/ti_server_log
- SoftBench messages logged in\x0d
- Error Conditions
- ToolTalk messages logged in\x0d
- Standalone Notice Forwarding
- /usr/atria/default_config_spec
- default config spec location\x0d
- Dynamic `Mainline' View
- /usr/atria/lib/mgrs/mgr_info.h
- type manager information contained in\x0d
- Predefined and User-Defined Type Managers
- .Xdefaults
- SoftBench entries\x0d
- Configuring the Development Manager for ClearCase
- Setting the Build Program
- find (cleartool subcommand)
- configuring views with\x0d
- Techniques for Maintaining Privacy
- description (table)\x0d
- cleartool Subcommands
- enforcing development policies with\x0d
- Scenario: Change Sets
- searching for attributes throughout an element\x0d
- View That Selects Versions Using `External Criteria'
- findmerge (cleartool subcommand)
- -whynot option
- verifying merge completion (scenario)\x0d
- Performing Merges
- description (table)\x0d
- cleartool Subcommands
- determining which elements require merges\x0d
- Preparing to Merge from the major Branch
- locating elements that need merging
- (scenario)\x0d
- Preparing to Merge
- log file characteristics
- (scenario)\x0d
- Preparing to Merge
- flag files
- forced rebuild use\x0d
- Problems with `Forced Builds'
- importance of using view-private files as\x0d
- Explicitly-Declared Source Dependencies
- Gmake program
- Gnu make support by\x0d
- Supported `Gnu make' Features
- GNU make
- BOS file compatibility\x0d
- BOS Files and `Gnu Make' Compatibility
- clearmake emulation option\x0d
- `clearmake' Compatibility Modes
- supported features (list)\x0d
- Supported `Gnu make' Features
- graphical user interface (GUI)
- basic usage model\x0d
- Basic Usage Model
- creating a new view with the view browser\x0d
- GUI: Use the View Browser to Create a New View
- selecting a view from the view browser\x0d
- GUI: Select the View from the View Browser
- using (chapter)\x0d
- Using the ClearCase Graphical User Interface
- help
- help (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- using\x0d
- Getting Help
- on-line
- accessing\x0d
- Getting Help
- permuted index\x0d
- Getting Help
- hierarchies
- CRs
- methods for handling\x0d
- CR Hierarchies
- permissions checking\x0d
- Permissions Checking and Locks
- host
- build
- client, term definition\x0d
- Overview of Distributed Building
- server, setting up\x0d
- Server-Side Setup
- server, term definition\x0d
- Overview of Distributed Building
- non-ClearCase
- setting up a build on (chapter)\x0d
- Setting Up a Build on a
Non-ClearCase Host
- hosts
- SGI
- pmake program, supported features (list)\x0d
- Supported SGI `pmake' Features
- smake program, clearmake emulation options\x0d
- `clearmake' Compatibility Modes
- smake program, supported features (list)\x0d
- Supported SGI `smake' Features
- HP VUE
- configuring
- Configuring HP VUE
- hyperlinks (meta-data)
- names
- cleartool treatment same as for pathnames\x0d
- Pathnames in cleartool Commands
- requirements tracing use\x0d
- Scenario: Requirements Tracing
- icons
- customizing\x0d
- Icon Usage by GUI Browsers
- idleness threshold
- distributed build priority setting with\x0d
- Handling of the Idleness Threshold
- imake utility
- multiple-architecture development use
- (example)\x0d
- Multiple-Architecture Example, Using `imake'
- multiple-architecture development use\x0d
- Alternative Approach, Using `imake'
- include statement
- copying files into a config spec\x0d
- Configuring the View
- inference rules (standard make)
- not supported by clearmake\x0d
- Standard `make' Description File Features Not Supported
- init(1M)-started processes
- view-extended pathname use to process VOB data\x0d
- Using a Working Directory View without a Set View
- instances
- command option distinguishing between types and\x0d
- Command Options
- IRIX systems
- clearmake emulation options\x0d
- `clearmake' Compatibility Modes
- ToolTalk process starting requirements\x0d
- Using Views
- keyboard
- file browser keystrokes
- (table)\x0d
- Basic Pointer Actions and Keystrokes
- LATEST label
- dangers of using in defining a baselevel\x0d
- How can this set of versions be described in terms of ClearCase meta-data?
- lint(1) command
- config specs that require\x0d
- View That Selects Versions Using `External Criteria'
- list browsers
- characteristics\x0d
- List Browsers
- ln (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- lock (cleartool subcommand)
- (scenario)\x0d
- Implementing a Final Bugfix
- description (table)\x0d
- cleartool Subcommands
- locking
- branches\x0d
- Preparing to Merge from the major Branch
- label types\x0d
- Frozen View, Defined by Version Labels
- labels\x0d
- Labeling Sources
- temporary access control provided by\x0d
- Permissions Checking and Locks
- locks
- explicit
- creating, with lock command\x0d
- Permissions Checking and Locks
- freezing data with\x0d
- Scenario: Freezing Certain Data
- implementing development policies with (chapter)\x0d
- Using Triggers, Attributes, and Locks to Implement Development Policies
- obsoleting branches with
- (scenario)\x0d
- Decommissioning the `major' Branch
- protecting
- branches during merges\x0d
- Preparing to Merge
- label type definition with\x0d
- Labeling Sources
- released configuration labels with\x0d
- Scenario: Recording a Released Configuration
- temporary access control provided by\x0d
- Permissions Checking and Locks
- unlocking a major branch
- (scenario)\x0d
- Performing Merges
- ls (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- distinguishing developers with\x0d
- View That Shows Only One Developer's Changes
- no version selected annotation
- meaning of\x0d
- Frozen View, Defined by Version Labels
- "no version selected" message\x0d
- Selecting Versions That Built a Particular Program
- lscheckout (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- event record display by\x0d
- Examining Event Records
- tracking checked out elements
- (scenario)\x0d
- Preparing to Merge
- Labeling Sources
- verifying checkin with\x0d
- Preparing to Merge from the major Branch
- lsdo (cleartool subcommand)
- -zero option
- list zero reference count DOs\x0d
- Zero Reference Counts
- accessing
- which views shared a DO\x0d
- Promotion of DOs
- description (table)\x0d
- cleartool Subcommands
- listing
- DOs with\x0d
- Extended Naming Scheme for Derived Objects
- lshistory (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- event record display by\x0d
- Examining Event Records
- lslock (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- event record display by\x0d
- Examining Event Records
- lspool (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- event record display by\x0d
- Examining Event Records
- lsprivate (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- lstype (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- event record display by\x0d
- Examining Event Records
- lsview (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- cleartool Subcommands
- lsvob (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- lsvtree (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- macros
- cpp
- defining architecture-specific\x0d
- Defining Architecture-Specific CPP Macros
- DATE\x0d
- Creating a `what' String
- make-macros
- imake use\x0d
- Alternative Approach, Using `imake'
- multiple-architecture development use\x0d
- Handling Build Procedure Differences
- MAKEFILE\x0d
- Configuring the Makefile
- VPATH\x0d
- Explicit Dependencies on `Searched-For' Sources
- VPATH: Searches for Both Targets and Dependencies
- VPATH Substitutions in Build Scripts
- magic files
- file typing capabilities\x0d
- File Typing
- MAGIC_PATH environment variable (footnote)\x0d
- Element Types and Type Managers
- revising\x0d
- Installing and Using the Type Manager
- MAGIC_PATH environment variable
- search path facility provided through (footnote)\x0d
- Element Types and Type Managers
- make (standard)
- command line options not supported (list)\x0d
- Standard `make' Command Line Options Not Supported
- compatibility
- between clearmake and (chapter)\x0d
- Compatibility between clearmake and Other make Variants
- limitations\x0d
- Compatibility Limitations
- description file features not supported\x0d
- Standard `make' Description File Features Not Supported
- disabling built-in rules
- with clearmake -r\x0d
- Compatibility Limitations
- term definition\x0d
- `clearmake' Compatibility With Standard `make'
- makefiles
- $(MAKEFILE) macro
- specifying makefile versions\x0d
- Configuring the Makefile
- creating
- a new version\x0d
- Configuring the Makefile
- multiple-architecture development (example)\x0d
- Creating Makefiles in the Source and Build Directories
- elaborated GNU
- saving\x0d
- Supported `Gnu make' Features
- hierarchies
- CR hierarchy relationships (figure)\x0d
- CR Hierarchies
- optimization (chapter)\x0d
- Makefile Optimization
- overriding
- Handling Temporary Changes in the Build Procedure
- recording in config rec\x0d
- Configuring the Makefile
- standard
- view- and version-extended not permitted in\x0d
- Pathnames in Build Scripts
- version labeling\x0d
- Configuring the Makefile
- man (cleartool subcommand)
- accessing
- manual reference pages with\x0d
- Getting Help
- description (table)\x0d
- cleartool Subcommands
- manual pages
- cleartool
- accessing\x0d
- Getting Help
- menu(s)
- file
- menu items description (table)\x0d
- The File Menu
- items
- grayed out, meaning\x0d
- Basic Usage Model
- navigation
- pointer actions and keystrokes (table)\x0d
- Basic Pointer Actions and Keystrokes
- merging
- branches
- data on two, (scenario)\x0d
- Merging of Data on Two Branches
- development work
- (scenario)\x0d
- Integration and Test
- files with xcleardiff\x0d
- Merging Files
- incremental
- Clearmake issues and alternatives\x0d
- Remedies for the Incremental-Update Problem
- term definition\x0d
- Incremental Updating of Derived Objects
- merge (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- multi-way support
- (scenario)\x0d
- Creating Baselevel 2
- performing
- baselevel merges (scenario)\x0d
- Performing Merges
- from the main branch (scenario)\x0d
- Performing the Merges from the `major' Branch
- preparing for
- (scenario)\x0d
- Deleting the Integration View
- two-way
- (scenario)\x0d
- Creating Baselevel 2
- versions
- SoftBench ClearCase menu Merge Versions item description\x0d
- Using the SoftBench Development Manager
- message passing
- one-way
- enabling for SoftBench\x0d
- One-Way Messaging
- enabling for ToolTalk\x0d
- Standalone Notice Forwarding
- SoftBench and ClearCase DISPLAY environment variable values required to be the same\x0d
- Error Conditions
- meta-data
- configuring a view to select libraries based on
- configuring a view to show\x0d
- Variations on the Theme
- describing baselevel versions in terms of\x0d
- How can this set of versions be described in terms of ClearCase meta-data?
- disadvantages of using to control version-selection\x0d
- Can This Configuration Be Used for Development?
- methods
- compare
- implementing a new version\x0d
- Implementing a New `compare' Method
- construct_version
- characteristics and use in creating a new type manager\x0d
- The `construct_version' Method
- create_version
- characteristics and use in creating a new type manager\x0d
- The `create_version' Method
- directory element inheritance list
- attaching triggers to (scenario)\x0d
- Scenario: Customized Change Notification
- type manager
- inherited\x0d
- Inheriting Methods from Another Type Manager
- mkattr (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- mkattype (cleartool subcommand)
- creating attribute types
- status change\x0d
- Scenario: Tracking State Transitions
- description (table)\x0d
- cleartool Subcommands
- mkbranch (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- mkbrtype (cleartool subcommand)
- creating branch types
- (scenario)\x0d
- Creating Branch Types
- creating branch types\x0d
- View That Allows an `Old' Configuration to be Modified
- description (table)\x0d
- cleartool Subcommands
- mkdir (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- mkelem (cleartool subcommand)
- -mkbranch qualifier effect on\x0d
- Where Is the `/main/LATEST' Rule?
- description (table)\x0d
- cleartool Subcommands
- element typing performed by
- (example)\x0d
- Element Types and Type Managers
- element typing performed by\x0d
- Element Types and Type Managers
- mkeltype (cleartool subcommand)
- defining element types with\x0d
- Predefined and User-Defined Element Types
- description (table)\x0d
- cleartool Subcommands
- mkhlink (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- mkhltype (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- mklabel (cleartool subcommand)
- (scenario)\x0d
- Implementing a Final Bugfix
- attaching release labels to versions (scenario)\x0d
- Deleting the Integration View
- CR hierarchy handling methods\x0d
- CR Hierarchies
- creating labels with\x0d
- Scenario: Recording a Released Configuration
- description (table)\x0d
- cleartool Subcommands
- mklbtype (cleartool subcommand)
- creating label types
- (scenario)\x0d
- Labeling Sources
- creating label types\x0d
- Labeling Sources
- Scenario: Recording a Released Configuration
- description (table)\x0d
- cleartool Subcommands
- mkpool (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- mktag (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- registering views on remote hosts
- (scenario)\x0d
- Integration and Test
- registering views on remote hosts\x0d
- Performing an Audited Build in the Export View
- mktrigger (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- mktrtype (cleartool subcommand)
- creating trigger types
- (scenario)\x0d
- Setting Up the Trigger to Monitor Bugfixing
- pre-operation type to monitor event record comment strings\x0d
- Scenario: Requiring Good Documentation of Changes
- mkview (cleartool subcommand)
- creating views
- NFS-accessible (scenario)\x0d
- Integration and Test
- creating views\x0d
- Creating, Configuring, and Registering Views
- Setting Up the Test View
- CLI: Enter a `mkview' Command
- default config spec actions\x0d
- Dynamic `Mainline' View
- description (table)\x0d
- cleartool Subcommands
- mkvob (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- monet project
- development
- environment specifications\x0d
- Defining View Configurations
- Release 2.0 process (scenario)\x0d
- Project Overview
- project plan (figure)\x0d
- Project Overview
- mount (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- mv (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- MVFS (multiversion file system)
- mvfsstorage utility
- determining DO data contained pathname\x0d
- Storage of DOs and CRs
- objects
- dependencies (figure)\x0d
- Explicitly-Declared Source Dependencies
- DOs, copying with winkin command\x0d
- Extended Naming Scheme for Derived Objects
- operating on with file browsers\x0d
- File Browser
- naming conventions
- branch types\x0d
- On what branch will the project be working?
- label types\x0d
- On what branch will the project be working?
- NFS
- creating a view that is accessible by
- (scenario)\x0d
- Integration and Test
- export facilities
- mounting a VOB\x0d
- Mounting the VOB through the Export View
- setting up an export view with\x0d
- Setting Up an Export View
- notice forwarding
- SoftBench
- ClearCase integration\x0d
- Architecture
- ToolTalk
- ClearCase integration\x0d
- Standalone Notice Forwarding
- nroff files
- type manager for\x0d
- Type Manager for Manual Page Source Files
- pathnames
- can acquire a view context in several ways\x0d
- View Contexts: Summary
- extended
- cleartool use\x0d
- Pathnames in cleartool Commands
- full
- cleartool use\x0d
- Pathnames in cleartool Commands
- in makefile build scripts\x0d
- Pathnames in Build Scripts
- relative
- cleartool use\x0d
- Pathnames in cleartool Commands
- recommendation for symbolic links\x0d
- View Contexts: Summary
- standard
- cleartool use\x0d
- Pathnames in cleartool Commands
- required in makefile build scripts\x0d
- Pathnames in Build Scripts
- version-extended
- cleartool use\x0d
- Pathnames in cleartool Commands
- not permitted in standard makefiles\x0d
- Pathnames in Build Scripts
- view context relationship\x0d
- View Contexts: Summary
- view-extended
- accessing other views with\x0d
- Working Directory View
- cleartool use\x0d
- Pathnames in cleartool Commands
- Pathnames in cleartool Commands
- not permitted in standard makefiles\x0d
- Pathnames in Build Scripts
- VOB-extended
- accessing DOs with, restrictions on\x0d
- Extended Naming Scheme for Derived Objects
- cleartool use\x0d
- Pathnames in cleartool Commands
- permissions
- checking
- hierarchy and characteristics\x0d
- Permissions Checking and Locks
- DOs
- practices that enhance sharing\x0d
- Wink-in, Permissions on Derived Objects, and clearcase_bld_umask
- platforms (multiple)
- building software for\x0d
- Building Software for Multiple Architectures
- distributed build setting up for\x0d
- Setting clearcase_bld_conc in a Shell Startup Script
- pmake program
- clearmake emulation option\x0d
- `clearmake' Compatibility Modes
- supported features (list)\x0d
- Supported SGI `pmake' Features
- pointers
- basic actions and keystrokes (table)\x0d
- Basic Pointer Actions and Keystrokes
- portability
- importance of declaring dependency for\x0d
- Declaring Source Dependencies in Makefiles
- standard make
- recommendations for\x0d
- `clearmake' Compatibility With Standard `make'
- priorities
- distributed build
- idleness threshold use\x0d
- Handling of the Idleness Threshold
- process control
- bugfix isolation
- config spec use (scenario)\x0d
- Scenario: Isolating Work on a Bugfix
- change
- associating with ECOs, using attribute, branches, and triggers (scenario)\x0d
- Scenario: Associating Changes with Change Orders
- isolation, config spec use (scenario)\x0d
- Scenario: Isolating All Users from Each Other
- development
- parallel, management scenario (chapter)\x0d
- Using ClearCase to Organize and Implement Parallel Development
- using triggers, attributes, and locks to manage (chapter)\x0d
- Using Triggers, Attributes, and Locks to Implement Development Policies
- enforcing policies
- attribute tagging of element status, using attributes\x0d
- Scenario: Tracking State Transitions
- change set common checkout, with attributes\x0d
- Scenario: Change Sets
- event record commenting, using triggers\x0d
- Scenario: Requiring Good Documentation of Changes
- no-directory-branching policy, config spec modification for\x0d
- Variations on the Theme
- quality assurance standards, with pre-operation triggers (scenario)\x0d
- Scenario: Enforcing Quality Standards
- freezing data
- lock use for\x0d
- Scenario: Freezing Certain Data
- reporting
- customizing notification, with triggers (scenario)\x0d
- Scenario: Customized Change Notification
- released configuration identification, version label use\x0d
- Scenario: Recording a Released Configuration
- requirements tracing
- hyperlink use\x0d
- Scenario: Requirements Tracing
- processes
- background
- build audit issues\x0d
- Build Auditing and Background Processes
- running clearmake in, emboldening loss on some architectures\x0d
- Invoking clearmake
- init(1M)-started
- view-extended pathname use to process VOB data\x0d
- Using a Working Directory View without a Set View
- programs
- config specs that select versions that built particular\x0d
- Selecting Versions That Built a Particular Program
- /proj/monet VOB-tag
- config specs examples using
- (chapter)\x0d
- Defining View Configurations
- projects
- config specs
- project-specific, reconfiguring a view using\x0d
- Configuring the View
- project-standard, creating (scenario)\x0d
- Creating Project-Standard Config Specs
- leader
- relationship to administrator\x0d
- Project Leader and ClearCase Administrator
- monet
- development environment specifications\x0d
- Defining View Configurations
- project plan (figure)\x0d
- Project Overview
- Release 2.0 process (scenario)\x0d
- Project Overview
- protect (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- protectvob (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- pwd (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- pwv (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- QA (quality assurance)
- config specs for\x0d
- View That Selects Versions Using `External Criteria'
- enforcing standards with pre-operation triggers
- Scenario: Enforcing Quality Standards
- question option (standard make)
- not supported by clearmake\x0d
- Standard `make' Command Line Options Not Supported
- quitting
- quit (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- recovering
- recoverview (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- reference count
- term definition, characteristics, and handling\x0d
- DO Reference Counts
- reformatview (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- reformatvob (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- register (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- registry
- view storage
- verification when creating a view
- Verify the View's Registry-Level Information
- releases
- development process (scenario)\x0d
- Project Overview
- past
- isolating work on (scenario)\x0d
- Scenario: Isolating Work on a Bugfix
- released configurations
- recording, with label types\x0d
- Scenario: Recording a Released Configuration
- validation (scenario)\x0d
- Final Validation - Creating Release 2.0
- reporting
- customizing change notification with post-operation triggers (scenario)\x0d
- Scenario: Customized Change Notification
- requirements tracing
- hyperlink use\x0d
- Scenario: Requirements Tracing
- reserve (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- reuse
- derived objects
- (figure)\x0d
- A Simple clearmake Build Scenario
- vs. wink-in\x0d
- A Simple clearmake Build Scenario
- rmattr (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rmbranch (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rmdo (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- explicitly removing DOs\x0d
- Explicit Removal of DOs
- rmelem (cleartool subcommand)
- changing frozen configurations with\x0d
- Frozen View, Defined by Time
- description (table)\x0d
- cleartool Subcommands
- rmhlink (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rmlabel (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rmmerge (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rmname (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rmpool (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rmtag (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rmtrigger (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rmtype (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- removing global element trigger type
- (scenario)\x0d
- Wrapping Up
- rmver (cleartool subcommand)
- changing frozen configurations with\x0d
- Frozen View, Defined by Time
- description (table)\x0d
- cleartool Subcommands
- rmview (cleartool subcommand)
- deleting views
- (scenario)\x0d
- Deleting the Integration View
- description (table)\x0d
- cleartool Subcommands
- rmvob (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rnpool (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rntype (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- rolling back the clock
- with config spec time rules\x0d
- Using Config Spec `Time Rules' to Increase Your View's Isolation
- root user
- permissions hierarchy position of\x0d
- Permissions Checking and Locks
- sb_nf_server process
- notice forwarder process for SoftBench
- characteristics\x0d
- Architecture
- SCCS
- make inference rules not supported\x0d
- Standard `make' Description File Features Not Supported
- schemes (resource)
- setting color for GUI utilities\x0d
- Setting Your Color Scheme
- scripts
- build
- changing with BOS files\x0d
- Using a Build Options Specification (BOS) File
- establishing CR hierarchy links in\x0d
- CR Hierarchies
- pathnames in\x0d
- Pathnames in Build Scripts
- revising for an audited non-ClearCase host build\x0d
- Revising the Build Script
- VPATH substitutions, with Sun make\x0d
- VPATH Substitutions in Build Scripts
- element type shell
- contained in the /usr/atria/examples/mkeltype directory\x0d
- Predefined and User-Defined Element Types
- status checking
- pre-operation triggers in\x0d
- Scenario: Tracking State Transitions
- trigger action (example)\x0d
- Scenario: Customized Change Notification
- scrubbing
- term definition\x0d
- Derived Object Scrubbing
- search path facility
- MAGIC_PATH environment variable used for (footnote)\x0d
- Element Types and Type Managers
- servers
- distributed build controls\x0d
- Overview of Distributed Building
- setcs (cleartool subcommand)
- -current option\x0d
- Variations on the Theme
- description (table)\x0d
- cleartool Subcommands
- reconfiguring views\x0d
- Configuring the View
- setting new config specs\x0d
- Creating, Configuring, and Registering Views
- setview (cleartool subcommand)
- accessing views on a remote host
- Setting Up an Export View
- changing current working directory to a VOB directory with\x0d
- CLI: Enter a setview Command
- description (table)\x0d
- cleartool Subcommands
- setting views
- (scenario)\x0d
- Preparing to Merge
- setting views\x0d
- Labeling Sources
- Development Begins
- Preparing to Merge from the major Branch
- SGI hosts
- pmake program
- supported features (list)\x0d
- Supported SGI `pmake' Features
- smake program
- clearmake emulation options\x0d
- `clearmake' Compatibility Modes
- supported features (list)\x0d
- Supported SGI `smake' Features
- shells
- shell (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- smake program
- clearmake emulation option\x0d
- `clearmake' Compatibility Modes
- supported features (list)\x0d
- Supported SGI `smake' Features
- snapshot
- config specs that create\x0d
- View That Shows Only One Developer's Changes
- SoftBench
- build program
- setting\x0d
- Setting the Build Program
- Builder
- configuring to use clearmake\x0d
- Using the ClearCase/SoftBench Integration
- cautions
- communicating with SoftBench servers on other hosts\x0d
- Using Views
- starting processes\x0d
- Using Views
- ClearCase
- integration architecture\x0d
- Architecture
- support (chapter)\x0d
- Using the ClearCase/SoftBench Integration
- Development Manager
- ClearCase menu item descriptions\x0d
- Using the SoftBench Development Manager
- configuring for ClearCase\x0d
- Configuring the Development Manager for ClearCase
- one-way messaging\x0d
- One-Way Messaging
- softbuild(1) program
- setting up to run clearmake\x0d
- Setting the Build Program
- source code
- labeling
- (scenario)\x0d
- Labeling Sources
- multiple-architecture differences
- handling\x0d
- Issues in Multiple-Architecture Development
- searched-for sources
- explicit dependencies required for\x0d
- Explicit Dependencies on `Searched-For' Sources
- tree
- restricting changes to specific areas of\x0d
- View That Restricts Changes to a Single Directory
- space (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- special characters
- backslash escape character (\\)\x0d
- cleartool Usage Overview
- ellipsis characters (...)\x0d
- On what branch will the project be working?
- extended naming symbol (@@)\x0d
- Extended Naming Scheme for Derived Objects
- what string prefix - @(#) characters\x0d
- Creating a `what' String
- start-up
- views
- SoftBench ClearCase menu Start View item description\x0d
- Using the SoftBench Development Manager
- startview (cleartool subcommand)
- accessing views on a remote host
- Setting Up an Export View
- description (table)\x0d
- cleartool Subcommands
- state transition model
- elements
- tracking, with attributes, branches, locks, version labels, and triggers (scenarios)\x0d
- Scenario: Tracking State Transitions
- status
- elements
- tracking changes in with attributes and triggers\x0d
- Scenario: Tracking State Transitions
- stdin description file
- not supported by clearmake\x0d
- Standard `make' Command Line Options Not Supported
- storage pools
- browsers
- characteristics\x0d
- Pool Browsers
- source
- type manager methods for handling\x0d
- Inheriting Methods from Another Type Manager
- type manager handling of (footnote)\x0d
- Element Types and Type Managers
- VOB
- DO, (figure)\x0d
- Storage of DOs and CRs
- DO, accessing\x0d
- Zero Reference Counts
- DO, assigning\x0d
- Approach 1: Use Architecture-Specific Subdirectories
- DO, scrubbing\x0d
- Derived Object Scrubbing
- DO, wink-in use for storing shared DO data containers\x0d
- Promotion of DOs
- strings
- browsers
- characteristics\x0d
- String Browsers
- subcommands
- cleartool
- list and description (table)\x0d
- Using cleartool
- subsessions
- term definition and characteristics\x0d
- Build Sessions, Subsessions, and Hierarchical Builds
- Sun
- make program
- supported features (list)\x0d
- Supported Sun `make' Features
- Solaris
- clearmake emulation option\x0d
- `clearmake' Compatibility Modes
- SunOS system
- clearmake emulation option\x0d
- `clearmake' Compatibility Modes
- ToolTalk process starting requirements\x0d
- Using Views
- supertype
- term definition\x0d
- Predefined and User-Defined Element Types
- System V Release 3 make(1)
- clearmake compatibility\x0d
- `clearmake' Compatibility With Standard `make'
- targets
- build scripts
- changing, with BOS files\x0d
- Using a Build Options Specification (BOS) File
- rebuild
- term definition
- Build Sessions, Subsessions, and Hierarchical Builds
- subtargets
- coordinating build reference times using\x0d
- Coordinating Reference Times of Several Builds
- term definition\x0d
- Build-Order Dependencies
- Sun
- clearmake use of VPATH search list use to find\x0d
- VPATH: Searches for Both Targets and Dependencies
- templates
- architecture-dependent
- multiple-architecture development use\x0d
- Alternative Approach, Using `imake'
- incremental update issues\x0d
- Additional Incremental-Update Situations
- terminal emulation window
- compared with list browsers
- Text Output and Terminal Emulation Windows
- text output window
- compared with list browsers
- Text Output and Terminal Emulation Windows
- tilde (~) rules (standard make)
- not supported by clearmake\x0d
- Standard `make' Description File Features Not Supported
- time
- configuration rules
- -time qualifier\x0d
- Frozen View, Defined by Time
- Variations on the Theme
- Variations on the Theme
- cautions on overprecise and inappropriate use of\x0d
- Inappropriate Use of Time Rules
- incompatible change handling\x0d
- Techniques for Maintaining Privacy
- rolling back the clock with\x0d
- Using Config Spec `Time Rules' to Increase Your View's Isolation
- configuring
- frozen views with\x0d
- Frozen View, Defined by Time
- snapshot views with\x0d
- View That Shows Only One Developer's Changes
- reference
- build session relationship to\x0d
- Build Sessions, Subsessions, and Hierarchical Builds
- coordinating for several builds\x0d
- Coordinating Reference Times of Several Builds
- term definition\x0d
- Continuing to Work During a Build / Reference Time
- timestamps
- adding to an executable (chapter)\x0d
- Adding a Timestamp to an Executable
- configuration lookup compared with algorithms based on\x0d
- Why is Configuration Lookup Necessary?
- toolbar
- file browser
- item descriptions\x0d
- File Browser Toolbar
- ToolTalk
- cautions
- starting processes\x0d
- Using Views
- ClearCase support (chapter)\x0d
- Using the ClearCase/ToolTalk Integration
- Session Server
- architecture\x0d
- Architecture
- touch option (standard make)
- reasons why not supported by clearmake\x0d
- Standard `make' Command Line Options Not Supported
- transcript pad
- characteristics\x0d
- The File Menu
- menu options description (table)\x0d
- Transcript Menu
- triggers (meta-data)
- associating changes with ECOs using
- (scenario)\x0d
- Scenario: Associating Changes with Change Orders
- enforcing
- attribute tagging of state transitions with\x0d
- Scenario: Tracking State Transitions
- event record commenting enforcement using\x0d
- Scenario: Requiring Good Documentation of Changes
- implementing development policies with (chapter)\x0d
- Using Triggers, Attributes, and Locks to Implement Development Policies
- monitoring bugfixing with
- (scenario)\x0d
- Setting Up the Trigger to Monitor Bugfixing
- post-operation
- customizing change notification with (scenario)\x0d
- Scenario: Customized Change Notification
- pre-operation
- enforcing attribute tagging of state transitions with\x0d
- Scenario: Tracking State Transitions
- quality assurance standard enforcement with (scenario)\x0d
- Scenario: Enforcing Quality Standards
- tt_nf_server process
- notice forwarder process for ToolTalk
- characteristics\x0d
- Architecture
- type(s)
- attribute
- config spec use of, for QA\x0d
- View That Selects Versions Using `External Criteria'
- creating to track element status changes\x0d
- Scenario: Tracking State Transitions
- attribute\x0d
- Browsers and Data Types
- branch
- config spec that creates instances of\x0d
- Making a Fix in the Program
- creating, for a new view\x0d
- On what branch will the project be working?
- creating, for version-label defined configuration\x0d
- View That Allows an `Old' Configuration to be Modified
- creating, parallel development (scenario)\x0d
- Creating Branch Types
- naming conventions\x0d
- On what branch will the project be working?
- branch\x0d
- Browsers and Data Types
- Browsers and Data Types
- browsers that operate on\x0d
- Type Object Browsers
- data
- browsers that can display (table)\x0d
- Browsers and Data Types
- distinguishing between instances and
- command option for\x0d
- Command Options
- elements
- applications\x0d
- Other Applications of Element Types
- creating\x0d
- Predefined and User-Defined Element Types
- Installing and Using the Type Manager
- determining for a newly created element (example)\x0d
- Element Types and Type Managers
- mechanisms compared with file-typing mechanisms\x0d
- Element Types and Type Managers
- predefined\x0d
- Predefined and User-Defined Element Types
- processing files with\x0d
- Processing Files by Element Type
- type managers and\x0d
- Element Types and Type Managers
- elements\x0d
- Browsers and Data Types
- files
- handling\x0d
- File Typing
- mechanisms compared with element-typing mechanisms\x0d
- Element Types and Type Managers
- hyperlink\x0d
- Browsers and Data Types
- managers
- creating, procedure (example)\x0d
- Type Manager for Manual Page Source Files
- customized handling of files using (chapter)\x0d
- Type Managers and Customized Processing of File Elements
- different from supertype, specifying with -manager option\x0d
- Predefined and User-Defined Element Types
- inheriting methods from\x0d
- Inheriting Methods from Another Type Manager
- installing\x0d
- Installing and Using the Type Manager
- predefined, characteristics\x0d
- Predefined and User-Defined Type Managers
- term definition and characteristics\x0d
- Element Types and Type Managers
- testing\x0d
- Testing the Type Manager
- parameterized
- incremental update issues\x0d
- Additional Incremental-Update Situations
- supertype
- term definition\x0d
- Predefined and User-Defined Element Types
- trigger
- creating (scenario)\x0d
- Setting Up the Trigger to Monitor Bugfixing
- creating to track element status changes\x0d
- Scenario: Tracking State Transitions
- trigger\x0d
- Browsers and Data Types
- version label
- creating, for source identification, (scenario)\x0d
- Labeling Sources
- creating, to record a released configuration\x0d
- Scenario: Recording a Released Configuration
- locking, with lock command\x0d
- Frozen View, Defined by Version Labels
- Frozen View, Defined by Version Labels
- naming conventions\x0d
- On what branch will the project be working?
- version label\x0d
- Browsers and Data Types
- umask(1) setting
- changing\x0d
- Adjust Your `umask'
- view accessibility impact\x0d
- Adjust Your `umask'
- umount (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- uncheckout (cleartool subcommand)
- -keep option\x0d
- Using the SoftBench Development Manager
- -rm option\x0d
- Using the SoftBench Development Manager
- description (table)\x0d
- cleartool Subcommands
- unlock (cleartool subcommand)
- (scenario)\x0d
- Implementing a Final Bugfix
- description (table)\x0d
- cleartool Subcommands
- unlocking branches
- (scenario)\x0d
- Wrapping Up
- Performing Merges
- unlocking branches\x0d
- Further Restricting Use of the main Branch
- unregister (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- unreserve (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- USERNAME
- browsers
- characteristics\x0d
- Username Browsers
- users
- profiles
- customizing profile files described in user-profile manual page\x0d
- Customizing Comment Handling
- root
- permissions hierarchy position of\x0d
- Permissions Checking and Locks
- /usr/adm/atria/ti_server_log file
- SoftBench messages logged in\x0d
- Error Conditions
- ToolTalk messages logged in\x0d
- Standalone Notice Forwarding
- /usr/atria/bin/Gmake program
- Gnu make support by\x0d
- Supported `Gnu make' Features
- /usr/atria/default_config_spec file
- default config spec location\x0d
- Dynamic `Mainline' View
- /usr/atria/doc/man/apropos
- accessing
- apropos files with\x0d
- Getting Help
- /usr/atria/doc/man/permuted_index
- accessing
- the permuted index with\x0d
- Getting Help
- /usr/atria/examples/mkeltype directory
- element type shell scripts contained in\x0d
- Predefined and User-Defined Element Types
- /usr/atria/lib/mgrs directory
- predefined type managers found in\x0d
- Predefined and User-Defined Type Managers
- /usr/atria/lib/mgrs/mgr_info.h file
- type manager information contained in\x0d
- Predefined and User-Defined Type Managers
- /usr/softbench/app-defaults/softdm
- setting the SoftBench build program\x0d
- Setting the Build Program
- validation
- releases
- (scenario)\x0d
- Final Validation - Creating Release 2.0
- variants
- architecture-specific
- issues surrounding the development of\x0d
- Issues in Multiple-Architecture Development
- version control
- set view capability impact on\x0d
- Setting a View
- version labels (meta-data)
- attaching
- to makefiles\x0d
- Configuring the Makefile
- configuring views with\x0d
- Selecting Versions That Built a Particular Program
- View That Allows an `Old' Configuration to be Modified
- creating
- SoftBench ClearCase menu Make Label item description\x0d
- Using the SoftBench Development Manager
- defining baselevels with\x0d
- Project Overview
- libraries\x0d
- Variations on the Theme
- source identification
- (scenario)\x0d
- Labeling Sources
- Labeling Sources
- types
- browsers that can display (table)\x0d
- Browsers and Data Types
- creating, to record a released configuration\x0d
- Scenario: Recording a Released Configuration
- locking, to freeze a configuration\x0d
- Frozen View, Defined by Version Labels
- locking, with lock command\x0d
- Frozen View, Defined by Version Labels
- Frozen View, Defined by Version Labels
- naming conventions\x0d
- On what branch will the project be working?
- version-extended pathname use\x0d
- Pathnames in cleartool Commands
- versions
- checked-out
- CR listing of\x0d
- Listing CRs
- comparing
- SoftBench ClearCase menu Compare Versions item description\x0d
- Using the SoftBench Development Manager
- conflicts
- avoiding\x0d
- Selecting Versions That Built a Set of Programs
- creating
- construct_version method, characteristics and use in creating a new type manager\x0d
- The `construct_version' Method
- create_version method, characteristics and use in creating a new type manager\x0d
- The `create_version' Method
- directories
- listing, with catcr -long\x0d
- Listing CRs
- displaying information about
- SoftBench ClearCase menu Describe item description\x0d
- Using the SoftBench Development Manager
- Using the SoftBench Development Manager
- elements
- created during a build session, status of\x0d
- Versions of Elements Created During a Build Session
- type manager handling of\x0d
- Element Types and Type Managers
- listing
- SoftBench ClearCase menu Cleartool List item description\x0d
- Using the SoftBench Development Manager
- merging
- SoftBench ClearCase menu Merge Versions item description\x0d
- Using the SoftBench Development Manager
- selecting
- that built a particular program\x0d
- Selecting Versions That Built a Particular Program
- string
- adding to an executable (chapter)\x0d
- Adding a Timestamp to an Executable
- tracking changes in
- with attributes and triggers\x0d
- Scenario: Tracking State Transitions
- trees
- browser characteristics\x0d
- Vtree Browsers
- displaying, SoftBench ClearCase menu Display Version Tree item description\x0d
- Using the SoftBench Development Manager
- version-ID
- version-extended pathname use\x0d
- Pathnames in cleartool Commands
- version_selector manual page
- pathname documentation\x0d
- Pathnames in cleartool Commands
- views
- cleartool subcommands for working with (table)
- cleartool Subcommands
- views (workspace management)
- accessing
- with view-extended pathnames\x0d
- Working Directory View
- browsers
- characteristics\x0d
- View-tag Browsers
- configuring
- (chapter)\x0d
- Defining View Configurations
- by attribute query\x0d
- View That Selects Versions Using `External Criteria'
- by query\x0d
- View That Shows Only One Developer's Changes
- by time\x0d
- Frozen View, Defined by Time
- by version label\x0d
- Selecting Versions That Built a Particular Program
- Frozen View, Defined by Version Labels
- for debugging\x0d
- Making a Fix in the Program
- for multiple-level branching
- View That Implements Multiple-Level Branching
- for new development\x0d
- View for New Development on a Branch
- for QA\x0d
- View That Selects Versions Using `External Criteria'
- parallel development (scenario)\x0d
- Creating, Configuring, and Registering Views
- preventing version conflicts\x0d
- Selecting Versions That Built a Set of Programs
- to restore a previous environment\x0d
- Variations on the Theme
- to restrict changes to a single directory\x0d
- View That Restricts Changes to a Single Directory
- to select application subsystems\x0d
- Playing Mix-and-Match with Application Subsystems
- to show only one developer's changes\x0d
- View That Shows Only One Developer's Changes
- to show results of a nightly build\x0d
- View That Uses Results of a Nightly Build
- using version labels\x0d
- View That Allows an `Old' Configuration to be Modified
- with element types\x0d
- Using Element Types to Configure a View
- with find (cleartool subcommand)\x0d
- Techniques for Maintaining Privacy
- configuring\x0d
- Configuring the View
- context
- establishing, term definition\x0d
- Starting to Use the View
- specifying explicitly with view-extended pathnames\x0d
- Using a Working Directory View without a Set View
- summary of use\x0d
- View Contexts: Summary
- view-extended pathnames use with, SoftBench\x0d
- Using Views
- view-extended pathnames use with, ToolTalk\x0d
- Using Views
- creating
- an NFS-accessible view\x0d
- Integration and Test
- parallel development (scenario)\x0d
- Creating, Configuring, and Registering Views
- creating\x0d
- Creating the View
- development
- changing config specs to\x0d
- Making a Fix in the Program
- export
- setting for non-ClearCase access\x0d
- Choose a Location
- term definition and setup\x0d
- Setting Up an Export View
- extended pathnames
- accessing DOs with\x0d
- Extended Naming Scheme for Derived Objects
- accessing other views with\x0d
- Working Directory View
- cleartool use\x0d
- Pathnames in cleartool Commands
- SoftBench use requirement\x0d
- Using Views
- SoftBench use, cautions\x0d
- Using Views
- ToolTalk use requirement\x0d
- Using Views
- view context relationship\x0d
- View Contexts: Summary
- freezing
- cautions against using time rules for\x0d
- Inappropriate Use of Time Rules
- frozen
- defined by time\x0d
- Frozen View, Defined by Time
- defined by version labels\x0d
- Frozen View, Defined by Version Labels
- historical
- configuring\x0d
- Omitting the Standard Configuration Rules
- isolating users from each other
- (config spec examples)\x0d
- Scenario: Isolating All Users from Each Other
- isolating work with\x0d
- Techniques for Maintaining Privacy
- location considerations\x0d
- Choose a Location
- multiple-architecture development use\x0d
- Approach 2: Use Different Views
- naming\x0d
- Choose a Name
- parallel development environment planning
- (scenario)\x0d
- Work Environment Planning — Views
- perusal
- contrasted with development views\x0d
- View That Shows Only One Developer's Changes
- planning considerations\x0d
- Planning the View
- reconfiguring\x0d
- Configuring the View
- registering
- parallel development (scenario)\x0d
- Creating, Configuring, and Registering Views
- selecting a location for\x0d
- Choose a Location
- server process
- term definition\x0d
- Choose a Location
- set
- term definition\x0d
- Starting to Use the View
- view context relationship\x0d
- View Contexts: Summary
- setting
- (chapter)\x0d
- Setting Up a View
- simple clearmake build scenario\x0d
- A Simple clearmake Build Scenario
- term definition\x0d
- Setting a View
- unexpected behavior if you have not\x0d
- View Contexts: Summary
- up for final validation (scenario)\x0d
- Setting Up the Test View
- setting\x0d
- Setting a View
- sparse
- config spec that creates\x0d
- Selecting Versions That Built a Particular Program
- starting
- SoftBench ClearCase menu Start View item description\x0d
- Using the SoftBench Development Manager
- to use\x0d
- Starting to Use the View
- storage
- directory, term definition\x0d
- Choose a Location
- storage registry
- verification when creating a view
- Verify the View's Registry-Level Information
- transparency
- derived objects included in\x0d
- Setting a View
- DOs accessible through standard UNIX pathnames\x0d
- Extended Naming Scheme for Derived Objects
- set view capability\x0d
- Setting a View
- term definition and description\x0d
- Pathnames in cleartool Commands
- umask setting impact on accessibility of\x0d
- Adjust Your `umask'
- view-private objects
- dependencies (figure)\x0d
- Explicitly-Declared Source Dependencies
- viewtags
- naming considerations\x0d
- Choose a Name
- starting views with, SoftBench ClearCase menu Start View item description\x0d
- Using the SoftBench Development Manager
- VOB location relative to\x0d
- Choose a Location
- working directory
- characteristics and use\x0d
- Working Directory View
- term definition\x0d
- Starting to Use the View
- view context relationship\x0d
- View Contexts: Summary
- VOB (versioned object base)
- accessing
- from init(1M)-started processes, with view-extended pathname\x0d
- Using a Working Directory View without a Set View
- automatic deletion of DO-related information from the\x0d
- Derived Object Scrubbing
- browsers
- characteristics\x0d
- VOB-tag Browsers
- changing
- event record creation triggered by\x0d
- Event Records and Comments
- element types defined on a per-VOB basis\x0d
- Element Types and Type Managers
- event records
- comment strings, enforcing the use of\x0d
- Scenario: Requiring Good Documentation of Changes
- Scenario: Requiring Good Documentation of Changes
- comment strings\x0d
- Event Records and Comments
- creation, triggered by VOB changes\x0d
- Event Records and Comments
- lscheckout, displaying\x0d
- Examining Event Records
- lshistory, displaying\x0d
- Examining Event Records
- lslock, displaying\x0d
- Examining Event Records
- lspool, displaying\x0d
- Examining Event Records
- lstype, displaying\x0d
- Examining Event Records
- extended pathnames
- cleartool use\x0d
- Pathnames in cleartool Commands
- links
- parent-child, establishing for CR hierarchy\x0d
- CR Hierarchies
- symbolic, caution on use of\x0d
- View Contexts: Summary
- symbolic, relative pathnames recommended for\x0d
- View Contexts: Summary
- symbolic, set view importance\x0d
- View Contexts: Summary
- symbolic, type manager, linking across the network\x0d
- Installing and Using the Type Manager
- symbolic, type manager, use for inheritance\x0d
- Inheriting Methods from Another Type Manager
- Predefined and User-Defined Type Managers
- mounting
- through export view\x0d
- Mounting the VOB through the Export View
- objects
- DOs as\x0d
- Storage of DOs and CRs
- remote access
- through NFS export views
- Setting Up an Export View
- separate branch type sets maintained for\x0d
- Creating Branch Types
- tags
- VOBTAG data type, browsers that can display (table)\x0d
- Browsers and Data Types
- tools
- eliminating explicit dependency declarations with\x0d
- Explicitly-Declared Source Dependencies
- view location relative to\x0d
- Choose a Location
- VOB-extended pathname
- accessing DOs with, restrictions on\x0d
- Extended Naming Scheme for Derived Objects
- VPATH macro
- dependency declarations
- when to use\x0d
- Explicit Dependencies on `Searched-For' Sources
- specifying directories to be searched with\x0d
- Explicit Dependencies on `Searched-For' Sources
- Sun make program
- clearmake actions\x0d
- VPATH: Searches for Both Targets and Dependencies
- substitutions in build scripts\x0d
- VPATH Substitutions in Build Scripts
- what(1) command
- creating a string for\x0d
- Creating a `what' String
- four character string prefix (@(#))\x0d
- Creating a `what' String
- whatis file
- accessing
- Getting Help
- wildcards
- controlling use
- (scenario)\x0d
- Scenario: Change Sets
- windows
- terminal emulation
- compared with list browsers
- Text Output and Terminal Emulation Windows
- text output
- compared with list browsers
- Text Output and Terminal Emulation Windows
- wink-in
- (figure)\x0d
- A Simple clearmake Build Scenario
- handling differences between standard build avoidance algorithms and
- Accommodating clearmake's Build Avoidance
- manually handling with winkin command\x0d
- Wink-In without Configuration Lookup / The `winkin' Command
- not provided in clearaudit use with non-clearmake programs\x0d
- Compatibility between clearmake and Other make Variants
- optimizing
- Optimizing Wink-In by Avoiding Pseudo-Targets
- permission settings that facilitate\x0d
- Wink-in, Permissions on Derived Objects, and clearcase_bld_umask
- reuse compared with\x0d
- A Simple clearmake Build Scenario
- winkin (cleartool subcommand)
- copying DO file system data with\x0d
- Extended Naming Scheme for Derived Objects
- description (table)\x0d
- cleartool Subcommands
- manually winking in a DO with\x0d
- Wink-In without Configuration Lookup / The `winkin' Command
- wrong-version-checked-out problem
- avoiding by using branches in the config spec\x0d
- Can This Configuration Be Used for Development?
- X Windows
- .Xdefaults file
- SoftBench entries\x0d
- Setting the Build Program
- SoftBench/ClearCase entries\x0d
- Configuring the Development Manager for ClearCase
- xclearcase command
- starting
- Starting xclearcase
- using
- (chapter)\x0d
- Using the ClearCase Graphical User Interface
- xcleardiff utility
- accessing from SoftBench\x0d
- Using the SoftBench Development Manager
- graphically comparing and merging files (chapter)\x0d
- Comparing and Merging Files Graphically with xcleardiff
- invoking\x0d
- Invoking xcleardiff
- .Xdefaults file
- SoftBench entries\x0d
- Configuring the Development Manager for ClearCase
- Setting the Build Program
- xdiff (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- xlsvtree (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- SoftBench ClearCase menu Display Version Tree item description\x0d
- Using the SoftBench Development Manager
- xmerge (cleartool subcommand)
- description (table)\x0d
- cleartool Subcommands
- ~ (tilde) rules (standard make)
- not supported by clearmake\x0d
- Standard `make' Description File Features Not Supported