Creating Workspaces

Each writer creates his and her own child workspaces. Each child contains the same files as the parent workspace man_pages.

1. Jane selects the man_pages icon on the Workspace Graph pane and chooses Transactions > Bringover > Create (see Figure 11-2).

   Figure 11-2 Opening the Bringover Create Transactions Window

   
   

2. The Bringover Create pane of the Transactions window opens (see Figure 11-3).

   Figure 11-3 Transactions Window -- Bringover Create of man_pages_jane

   
   

3. Jane enters the following information:

   • The path name of the child workspace in the To Child Workspace Directory text box

   • The directory man/ in the File List pane using the Add Files dialog box opened by the Add button (see Figure 11-4).

     ---

     Note -

     The character "." (representing all of the workspace) could have been specified in the file list pane instead of man/. Because all SCCS files are located beneath man/, the two are equivalent.

     ---

   Figure 11-4 Add Files Dialog Box

   
   

4. Jane clicks Bringover to initiate the Bringover Create transaction.

5. Bob repeats the process to create his workspace named man_pages_bob.

Figure 11-5 show the output produced during the Bringover Create transaction.

Figure 11-5 Output From Bringover Create of man_pages_jane

The output includes the following important information:

• Examined files: 13

  During the initial examination phase of the Bringover transaction, Configuring determined that 13 files differed in the parent and child. In this case, since the child is being created and thus contains no files, all files contained in the parent are considered for the transaction.

• Bringing over contents changes: 13

  Configuring has determined that the 13 files in the list should be brought over from the parent to the child workspace.

• Contents Summary: 13 Create

  This line indicates that 13 files were created (as opposed to updated) in the child. In the Bringover Create transaction, all transferred files fall into this category.

• 13 update children's name history

  The name history is a file that assists Configuring in tracking file names. It is used to speed up the processing of renamed files.