About Robelle

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. Using your favorite FTP utility, connect as root, and use a binary transfer to PUT the file to the HP-UX server.

(Example using Reflection FTP Client)

(Example using MS-DOS FTP Client)

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 sxpre.Z file only to end up with the filename as sxpre.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". You can always rename the file with the .z over top of the file with the .Z with the following: 

mv sxprod.z sxprod.Z

Suprtool Pre-Release 4.8.11

This new pre-release version of Suprtool attempts to dynamically load the Oracle client library, first by using the SHLIB_PATH directory and attempts to load libclntsh.sl, then libclntsh.so, and then final manually uses $ORACLE_HOME/lib32/libclntsh.sl If Oracle option is enabled and library cannot be found you may get the error: 

Warning: Your oracle library could not be loaded.
This means that any access to Oracle functions will not work. If you do not have Oracle and encounter this error, Suprtool will continue to function normally.

If for some reason, you still get this error message after installing Suprtool on a production machine, that stops production, I would suggest that you copy the new program file to the name testsupr and restore the old version of Suprtool.

In order to debug, this we would need to see the run of the copied testsupr program as well as the result of an env command to look at all your environment variables and e-mail to support@robelle.com

Installing the Software

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

  1. Save the current set of files.
  2. Restore the files.
  3. Apply the license codes.

Save the current files

Logon as root.

su -

Save current version(if applicable)

tar cvf sxbackup /opt/robelle/*

Decompress the download:

compress -d sxpre

Create the directory where the Suprtool files will reside:

mkdir /opt/robelle

Wait to be contacted by Robelle with the authorization codes.

Unpack the Robelle files:

cd /opt/robelle
tar xvf /home/root/sxpre

Apply the license codes

Once you get the codes you can apply them:

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

You can now run the pre-release:

/opt/robelle/bin/suprtool

Setting up Environment Variables

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 and MANPATH.

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.