Previous Next Contents Index Doc Set Home


Troubleshooting Versioning
and FreezePointing

18

This chapter describes some of the most common problems in Versioning and FreezePointing. It indicates where to look for information on how to overcome the problem. It is organized into the following sections:

Troubleshooting Checklist

page 209

Reporting Problems

page 210

Error Messages

page 210

Troubleshooting Checklist

If you are having problems using Versioning or FreezePointing, use the following checklist to rule out some of the most common reasons for the problem:

o Is the tool installed correctly?

If not, contact your system administrator. You can also read Sun Workshop Installation and Licensing Guide.

o Is /opt/bin in your PATH?

If not, see Sun Workshop Installation and Licensing Guide for information on how to add /opt/bin to your PATH.

o Is /usr/lang in your PATH?

If not, see Sun Workshop Installation and Licensing Guide for information on how to add /usr/lang to your PATH.

o Is the HELPPATH environment variable set?

Versioning relies on finding the vertool.info file in or near the directory that contains vertool. FreezePointing relies on finding the freezepoint.info file in or near the directory that contains freezepoint. On-line help is available for each control, window, pane, and error message displayed on the screen. See "Error Messages" for a list of the Versioning and FreezePointing error messages and instructions on what to do next.

o Do you have enough swap space?

If you receive a message stating "Request for xxx bytes of memory failed," you have run out of swap space. Use the mkfile(8) and swapon (8) commands to create more swap space or abort some existing processes (windows) to free up swap space. To determine which processes occupy significant swap space, use the ps uagx command and look in the SZ column. To determine how much swap space you have, use the pstat -s command.

o Does your window system have enough resources?

If Versioning or FreezePointing cannot activate a pop-up window, your window system may be running out of resources. Contact your system administrator for help.

Reporting Problems

If you have gone through the checklist and are still having problems, call your local service office. Have the version number of the tool ready to give to the dispatcher. To display the version number of any TeamWare component, type toolname -V at the prompt. For example:

twversion -V

Error Messages

Versioning and FreezePointing display messages to provide you with information or tell you about an error.

Display Problems

If you experience difficulties in color display in any of the services, you can copy the pertinent part of the resource files in the app-defaults directory. These files adjust color, fonts, mnemonics, and several other attributes for each TeamWare component.

These files are under the directory in which you have TeamWare installed, according to the language you are using. If you use CDE the files are in: TW2.0/lib/locale/<lang>/app-defaults/CDE. The resource files are listed according to component, preceded by X. For example:

...TW2.0/lib/locale/C/app-defaults/CDE/XCodeManager

If you use OpenWindows or any other non-CDE windowing system, the files are in ...TW2.0/lib/locale/C/app-defaults/non-CDE.

To make changes to your display:

1. Look at the resource file you want to change, and copy the appropriate lines.

For example, if you want to change the foreground color of the Configuring window, copy the line: 

XCodeManager*foreground: black

2. Append the pertinent lines to your own ~/.Xdefaults file.

Change it, for example, to: 

XCodeManager*foreground: green

3. Type xrdb < ~/.Xdefaults

4. Restart the application.

The window foreground color will be set.



Previous Next Contents Index Doc Set Home