Warnings Messages

2601 

Could not remove backup directory old_dir_name, so it was renamed to new_dir_name

Meaning: Configuring attempted to clear the backup area old_dir_name so that it could backup a new transaction. Configuring was not able to clear the backup directory by deleting it, but it was able to rename it out of the way to the name new_dir_name. The most likely cause is that file permissions were changed for the directory.

Remedy: Check directory permissions for old_dir_name. Default Configuring permissions for this directory are 777. Delete the contents of new_dir_name.

2602 

File file_name is not under SCCS in either workspace - ignored

Meaning: Configuring could not find an SCCS history file in either workspace for file_name.

Remedy: The file name was probably entered incorrectly, re-execute the command. 

2603 

Zero length filename - ignored

Meaning: A file name specified as an argument on the command-line (or in the Codemgr_wsdata/args file) contained no characters ("").

Remedy: Re-execute the command and re-specify the file name argument. If the problem persists, check the arguments listed in the args file.

2604 

Filename file_name has whitespace characters in it - ignored

Meaning: A file name specified as an argument on the command-line (or in the Codemgr_wsdata/args file) contained whitespace characters. Configuring commands do not accept file names that contain whitespace characters.

Remedy: Re-execute the command and re-specify the file name argument. If the problem persists, check the arguments listed in the args file.

2605 

Not used 

2606 

File file_name not brought over because it is a file_type in workspace workspace_name and a file_type in workspace workspace_name

Meaning: A file name has a different file type (regular file vs. directory vs. symbolic link) in the parent and child workspaces.  

Remedy: Take whatever action is appropriate to make the listed files the same type, or change one of the names. 

2607 

Not used 

2608 

Workspace child_ws_name is a child of parent_ws_name. Could not update its parent file

Meaning: During a workspace delete or workspace move operation involving child_ws_name, the command found that the children file in the workspace's parent (parent_ws_name) did not contain an entry specifying child_ws_name as a child of that parent.

Remedy: Advisory only: the command corrects the discrepancy, however, this could indicate that the parent's children file was corrupted.

2609 

Not used 

2610 

directory_name is not a workspace

Meaning: The directory specified in the command is not a Configuring workspace. Configuring workspaces are distinguished by the presence of the Codemgr_wsdata directory in the top level directory.

Remedy: Specify a different workspace name or use the CLI workspace create command or GUI File Create Workspace menu item to convert the directory into a workspace.

2611 

file_name does not exist in either workspace - ignored

Meaning: The file file_name was not found in either the parent or child workspace.

Remedy: Check to be sure the name was specified correctly. 

2612 

Not used 

2613 

Filename file_name has too many ".." path components in it - ignored

Meaning: Possible causes include that the Configuring command cannot resolve the path name into a: 

• workspace-relative file name

• fully qualified workspace name

Remedy: Specify the path name with fewer (or no) ".." path name components

2614 

Line line_number too long or unexpected end of file in file_name

Meaning: While reading the Codemgr_wsdata/nametable file, a line was encountered that contained too many characters for a Configuring command to buffer. The maximum line length is 1024 characters. This indicates that nametable has been corrupted.

Remedy: Configuring automatically rebuilds the nametable. This takes some time. 

2615 

Line line_number has bad format in file_name

Meaning: This indicates that the Codemgr_wsdata/nametable file has been corrupted.

Remedy: Configuring automatically rebuilds the nametable. This takes some time. 

2616 

Not used 

2617 

Unexpected name table editlog record type type_number - ignored

Meaning: A Configuring command was reading a temporary log file left over from an aborted Bringover or Putback operation and encountered a malformed record. This indicates that the file has been corrupted. 

Remedy: Execute the workspace updatenames command to rebuild nametable and then re-execute the command.

2618 

Can't open file_name - can't send mail notification

Meaning: The Configuring notification facility failed to open the file file_name. As a result, notification mail is not sent for the current operation.

Remedy: Check file permissions for file_name.

2619 

Not used 

2620 

Can't fork process to send notification

Meaning: Lack of system resources (memory, swap space) prevented the Configuring notification facility from sending notification mail. 

Remedy: Check system resources. 

2621 

Not used 

2622 

Filename file_name contains a comment character (#) - ignored

Meaning: A file name specified as an argument to a command (or in the Codemgr_wsdata/args file) contains the # character. Configuring reserves this character to denote comments.

Remedy: Change the name of the file so that its file name does not contain the # character. If the problem persists, check the arguments listed in the args file.

2623 

Read-lock left in workspace or Write-lock left in workspace

Meaning: A Configuring command was unable to remove locks in workspace_name. This may indicate that there is insufficient disk space, or that permissions on the file Codemgr_wsdata/locks were changed since the lock was originally written.

Remedy: Remove the locks by using the GUI Options Workspace menu item and selecting Locks in Category list box in the Workspace Properties dialog box, or by using the CLI workspace locks command.

2624 

File file_name is checked out in workspace workspace_name. The changes in the checked out file will not be brought over

Meaning: The file file_name is checked out in the parent workspace. You are being advised that any changes in the g-file were not brought over as part of the Bringover transaction.

Remedy: Not applicable. 

2625 

File file_name is not in conflict according to the SCCS file. Removing it from the conflict file

Meaning: The information in the SCCS history file indicates that the file contains no unresolved conflicts, however, the Codemgr_wsdata/conflicts file in the workspace lists it as being in conflict. The command removed it from the conflicts file.

Remedy: Not applicable. 

2626 

File file_name not brought over because it is unresolved in workspace workspace_name

Meaning: The file file_name was not brought over because it contains an unresolved conflict in workspace_name.

Remedy: Use the GUI Resolve transaction or the CLI resolve command to resolve the conflict and then re-execute the Bringover transaction.

2627 

Directory directory_name is mounted read-only.

Meaning: Before beginning Bringover and Putback transactions, Configuring checks to determine whether the destination workspace root (top-level) directory is accessible for writing. This is not treated as an error condition because lower level directories within the workspace could be mounted from different areas and they may be accessible for writing. This warning is issued as an early warning that directory permissions might be set incorrectly. 

Remedy: If write access is not intentionally denied, change the root directory permissions. 

2628 

Not updating g-files because get command couldn't be found in PATH search_path

Meaning: The g-files could not be updated as part of a Bringover or Putback transaction because the SCCS get command could not be executed; it was not found in your search path.

Remedy: If you want g-files to be updated as part of transactions, include the get command in your search path.

2629 

Will not be able to run twmerge or filemerge

Meaning: The resolve command was not able to connect with the ToolTalk message service. The ToolTalk service is used by the resolve command to communicate with Merging.

Remedy: The ToolTalk service is normally installed as part of CDE or OpenWindows. Check the CDE or OpenWindows documentation to determine why the ToolTalk service is not present or responding. 

2630 

This workspace is being created over an existing directory

Meaning: You are converting an already existing directory into a Configuring workspace. Creating a workspace from an existing directory hierarchy consists of creating the Codemgr_wsdata metadata directory in the top-level directory. Once the directory becomes a workspace, its contents can be deleted using the Configuring workspace delete command.

Remedy: Not applicable. 

2631 

File file_name not brought over because it is checked out and not writable in workspace workspace_name

Meaning: The file file_name was not brought over as part of the Bringover transaction because it is checked out (p-file exists) and writable in the child workspace workspace_name. The unusual state of this file indicates that it is safer not to process the file.

Remedy: Reconcile the write permissions with its SCCS status. 

2632 

Omitting contents change to file file_name because of rename error

Meaning: An error was encountered while processing the name of file_name. As a result, the change in the file from the source workspace could not be propagated to the destination workspace.

Remedy: Correct the rename problem (see the rename error text) and re-execute the Configuring transaction.