Suprtool Pre-Release
Installation Instructions

You may want to print this page, for reference.

FTP upload of binary file to HP-UX

Once you have downloaded the binary file to your PC, you need to upload it to the HP 9000.

Please note that the file you downloaded ended in a .Z, however, some browsers especially IE will try and help you and rename file file to be .tgz. Simply rename the file back to .Z when you upload the file or after you upload to your server.

Using your favorite FTP utility, connect as root, and use a binary transfer to PUT the file to the HP-UX server.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Download>ftp dev.robelle.com
Connected to dev.robelle.com.
220 HP ARPA FTP Server 
User (dev.robelle.com:(none)): root
31 Password required for root.
Password:
230 User root logged on
ftp> binary
200 Type set to I.
ftp> cd /tmp
ftp> put amxwpre.Z
ftp> quit
221 Server is closing command connection

The .Z problem

Some ftp clients do not preserve the case in the filename and end up upshifting or downshifting the filename depending on the settings of your ftp client. Some customers have ftp'ed the amxwpre.Z file only to end up with the filename as amxwpre.z.

This impacts our installation, as compress does not find the file to decompress; or worse, if a file of the same name exists that does have the capital Z at the end, then that (typically older) file is used and you end up installing an older version.

To insure that the following steps work properly please double check that the file you just ftp'ed is placed on the server with the proper name and has a .Z (dot Capital Z) and not the small ".z".

Preparing for Install

Backup the Account (Optional)

You can save your current files in the /opt/robelle account using the following steps.

Logon as root.
su -
tar cvf robbackup /opt/robelle/*

Check Your Codes

Before proceeding you should insure that the CPU Id codes that we send match the CPU/SPU-id for your machine. Please note that we sometimes use the term CPU-ID, SPU-id and HPSUSAN to mean the same thing. When you receive codes from Robelle they typically look like this:
(Please note that the following codes are not valid)

Extend codes to add CPU Id 999999999
                 and Model L3000800/A400-44
Product Verification Code:  111111111
        Verification Code:  222222222
        Verification Code:  333333333

You can determine your CPU-ID/SPU-ID with the uname command.

uname -i
999999999

Make sure Suprtool is not Running

In order to install Suprtool for HP-UX you must be sure that no one else is running Suprtool. You can check this normally with a:

	ps -ef | grep suprtool

If Suprtool is running you will need to either kill the process or trace who or what is running and wait for the process to be finished before restoring the files.

Installing the Software

Once you have the file on your HP 9000, you need to install it:

Restore the files.
Apply the license codes.

Save the current files

Logon as root.

su -
cd /tmp

Decompress the download:

compress -d amxwpre

Create the directory where the Suprtool files will reside. Obviously if the directory already exists then there is no need to make the directory.

mkdir /opt/robelle

Wait to be contacted by Robelle with the authorization codes.

Unpack the Robelle files:

cd /opt/robelle
tar xvf /tmp/amxwpre

Apply the license codes

Now you can apply the license codes that you made sure matched your machine in the Preparing to Install steps.

cd /opt/robelle/bin
./extend
Product Verification code: n
Verification code: n
Verification code: n

You can now run Suprtool and you should test that Suprtool runs by doing:

/opt/robelle/bin/suprtool

Cleanup

If Suprtool runs and you like to keep things clean like we do, we recommend that you remove the tar file with:

	rm /tmp/sxpre

Checking Permissions

When signing on as root on a security hardened system and creating the robelle directory it may be that only the root user who can run whatever software you are installing.

You can tell a system that has been hardened typically with a umask command, which will return:

What ends up happening when you make a directory with mkdir is the permissions end up being 700 or rwx for root, --- for group, and --- for user. The solution to this is to change the permissions:

chmod -R 755 /opt/robelle

Symbolic Links and Running Suprtool for AMXW

If this is an upgrade then it is likely that all the symbolic links have been setup and you can skip this section.

You can set up various symbolic links, which allows you to run SUPRTOOL from the /opt/robelle/bin, install location and have SUPRTOOL run from the PUB.ROBELLE space in AMXW.

Consult Speedware and AMXW for setting of NLROOTDIR variable and the AMXW environment if not done already.
Logon to AMXW, but do not go inside the nlsh shell.
If necessary, create /ROBELLE/PUB under the NLROOTDIR. If this is an update this and the following steps may not need to be done. If you do cd $NLROOTDIR/ROBELLE/PUB, and it doesn't work, then you may need to create the Directory, but this is normally on new installs.
To Create the Directory
```
mkdir $NLROOTDIR/ROBELLE/PUB
```
To move to the ROBELLE/PUB directory
```
cd $NLROOTDIR/ROBELLE/PUB
```

Set up the softlinks to point from PUB.ROBELLE to where Suprtool for AMXW and it's components are installed.

ln -s /opt/robelle/bin/suprtool suprtool
ln -s /opt/robelle/bin/suprlink suprlink
ln -s /opt/robelle/bin/stexport stexport
ln -s /opt/robelle/bin/suprtool SUPRTOOL
ln -s /opt/robelle/bin/suprlink SUPRLINK
ln -s /opt/robelle/bin/stexport STEXPORT

You may need to add info to the HPPATH variable, such that it contains a reference to PUB.ROBELLE.

	SETVAR HPPATH "!HPPATY,PUB.ROBELLE"

You will then be able to run suprtool thru AMXW using:

suprtool

SUPRTOOL

RUN SUPRTOOL.PUB.ROBELLE

Setting up Environment Variables

If this is an upgrade then it is likely that all the environment variables have been setup and you can skip this section.

You can set up various environment variables to make running any of the Robelle products easier. The four variables that we recommend setting for Suprtool are: SHLIB_PATH, ROBELLE, PATH, MANPATH, and NLROOTDIR.

Consult Speedware and AMXW for setting of NLROOTDIR variable and the AMXW environment.
If you have Eloquence you need to set the SHLIB_PATH variable to tell Suprtool where the libeqdb.sl and libimage3k.sl files are located.
The ROBELLE variable tells the Robelle products where it's supporting files are located.
The PATH variable, when set, allows the user to run Qedit by just typing "suprtool" instead of the fully qualified program name.
The MANPATH variable, when set, allows users to access the manpage (Help page) for Suprtool.

ROBELLE, PATH and MANPATH

The easiest way to add variables accessible to all users is to set the variables in the global exec file for the shell you use.

For the Bourne, Korn and Posix Shells we recommend the following additions to the /etc/profile file.

export ROBELLE=/opt/robelle
export PATH=$PATH:$ROBELLE/bin
export MANPATH=$MANPATH:$ROBELLE/man

For the C Shell we recommend that you add the following commands after any existing PATH or MANPATH statements in the /etc/csh.login file:

setenv ROBELLE /opt/robelle
set path=($path $ROBELLE/bin)
setenv MANPATH "$MANPATH":$ROBELLE/man

SHLIB_PATH

Suprtool dynamically loads the Eloquence libraries libeqdb.sl and libimage3k.sl. If you do not have Eloquence you do not have to set the SHLIB_PATH variable. You you will receive the following warning messages, Suprtool, however, will continue to run fine, except the Base command will cause Suprtool to fail.

  Warning: Could not load Eloquence image library.
  Warning: Could not load Eloquence scan library.

Typically you can add the line below to the

/etc/profile

file and every user that uses the Bourne, Korn and Posix shells will have the variable for each of their sessions.

   export SHLIB_PATH=/opt/eloquence6/lib/pa11_32

Suprtool also uses SHLIB_PATH or LD_LIBRARY_PATH variables when loading the Oracle libraries, typically this variable is already set as part of the Oracle installation, however you could set the variable as such:

   export SHLIB_PATH=$ORACLE_HOME/lib32

Configuring different Shells

When you log on to HP-UX, a program is run called the shell. The shell program interprets commands, executes them, and controls command execution. Making configuration changes requires that you know which shell you are using and what files are automatically executed.

Bourne, Korn and Posix Shells

the Bourne, Korn and Posix shells execute the file /etc/profile when you log on to HP-UX. They then look for a file in your home directory called .profile. If it exists, it is executed. If you use SAM to add new users, the file /etc/d.profile is automatically copied to the home group of the new user. If you want to make global changes to the commands that are executed at login in time you typically have to make the changes to the /etc/profile file, and check that the /etc/d.profile (the file that becomes the users .profile file), does not counteract any of the changes that you have made to the global file, such as Path, Manpath or Robelle. You also have may have to warn existing Bourne and Korn shell users to change their .profile file in their home directories.

C Shell

The C shell executes the file /etc/csh.login when you log on to HP-UX. It then looks for the file .login in your home directory. If it exists, it is executed. Next, the C shell executes the file .cshrc in your home directory (also executed any time you invoke a new copy of /bin/csh). If you use SAM to add new users, the files /etc/d.login and /etc/d.cshrc are automatically copied to the home group of the new users. You may need to make changes to /etc/d.login and /etc/d.schrc, so that new users do not override your changes. You may also have to warn existing C shell users to change their .login and .cshrc files in their home directories.

Documentation

See the change notice for full documentation on the new release, including the setting of environment variables.

Suprtool Pre-ReleaseInstallation Instructions