Problems Running the Software Parts Manager (Unix)

Article ID: 789
Last updated: 01 Feb, 2008
Article ID: 789
Last updated: 01 Feb, 2008
Revision: 1
Views: 2680
Posted: 03 Jun, 1999
by Dean J.
Updated: 01 Feb, 2008
by Dean J.
Problem


Unable to run the Software Parts Manager correctly on a Unix platform.


Cause





Action


The following items list the solutions for several problems commonly encountered when using SPM in a Unix environment

Running the install.sh script:

When trying to run the install.sh file, the following error results:

crasher% install.sh
user_location=/tmp: Command not found
PROD=PS: Command not found
PS_EXEC=partmgr: Command not found
PS_DESC=Software Parts Manager v1.2: Command not found
THIS_INSTALL=install.sh: Command not found
DEFAULT_NAME=spm: Command not found
DEFAULT_NAME: Undefined variable

The shell script install.sh requires sh or its derivative ksh in order to install the SPM. Other scripts used later in the install process require the korn shell ksh, so it is the preferred shell to use at all points while installing or using the SPM. You can switch to the korn shell by typing "ksh" at the command prompt.


Starting the partmgr executable:

  • Make sure that you are running the partmgr in the main SPM directory and NOT the partmgr in SPM/bin directory.
  • If you are getting a "Repository Read Error" or if the SPM stops running immediately after it starts, you do not have your permissions set corectly. This is usually caused by installing the SPM as "root" and then trying to execute it as a user without root permissions. You can test this by typing "touch file" when in the main SPM directory. If this returns an error, you do not have the permissions set correctly. You need to talk to your system administrator to set the permissions correctly.
  • If you are getting a "Can't Find Display" error, you should check to make sure your DISPLAY variable is set correctly. On some Unix systems, you need to set the DISPLAY to the actual IP address of the machine that you are using. An example of this would be "10.40.1.120:0"


Unlocking Products From the partmgr executable:

  • If you are unable to unlock a product, the most likely cause is an incorrect customer tracking number. Each unlock code is only valid with a specific customer tracking number. You can check the customer tracking number by selecting "Customer Information" under the "Misc" menu item.


Installing Products From the partmgr executable:

If you are getting the following error when installing products in the SPM:

Tools.h++ v070A Unix exam.tar: Could not open file dd/products/tls070au/src/ ...

If you are trying to install Rogue Wave products directly from the CD you need to make sure that the CD is actually in the drive and mounted correctly. This error can also be caused by an incorrect setting in the psinfo.in file located in the main SPM directory. The SPM uses the cddrive variable to locate the files needed to install Rogue Wave products. The correct path should be pointing to either your cdrom device or to the directory containing the installation tar files.

Building Products From the partmgr executable:

There are numerous reasons why a build script can fail. The most common problem is incorrect environment variables. The Software Parts Manager uses the environment variables to determine the location of the compiler and database client (if you are building DBTools or other database related product). Make sure that your compiler directory is in your PATH variable. You can check this by typing the compiler name ("cc", for example) at the main SPM directory. If you get an error like "Can't find cc" then your PATH variable is not set up correctly.

This article was:   Helpful | Not helpful
Report an issue
Article ID: 789
Last updated: 01 Feb, 2008
Revision: 1
Views: 2680
Posted: 03 Jun, 1999 by Dean J.
Updated: 01 Feb, 2008 by Dean J.

Others in this category