There are two main components to the TOP product, a client component ("TOP") which runs on the PC and a server component ("MIP") which runs on the NonStop server. Both components can be downloaded from here.

The TOP download is a windows executable which installs TOP. You may need administrator rights on your machine to install it.

The installation of MIP and the license file is now also available using as a windows executable, available from here.

If you want to install the MIP program without using the installer, or if you have problems then this page gives details of how to do a basic installation. More detailed instructions are supplied in the MIP readme file.

Download MIP software package to PC and expand it

The following files should have been extracted:

Note:  The version of the TOPSH file you should use depends on what type of NonStop server you have.

3. You should also have a license file, probably called "license.txt". This file will need to be installed with the mip software. If you don't have a license yet, you may request an evaluation license here.

Copy files to NonStop server 

1. Use ftp or any other file transfer tool you have to move files to a single subvolume on your NonStop server. If you are installing to a virtual disk volume, then refer to the readme.txt when you want to configure access to OSS. Assuming you were copying files to subvol $vol.subvol, then transfer files as follows:

Note: Logon to the NonStop and use the following command to set the mip file code:

FUP ALTER MIP, code 100

Secure files on NonStop server

1. Issue the following commands to secure the server programs:

2. As SUPER.SUPER issue the following command:

Choose a TCP/IP process for MIP

MIP communicates with TOP over TCP/IP. You must choose which TCP/IP process MIP will use. The default is $ZTC0, but this may not be appropriate. If you don't know which process to specify, ask your system administrator.

If you access the NonStop using a terminal emulator over TCP/IP, you may want to use the same TCP/IP process as that connection. To find out which process this is:

1. Type "WHO" at the TACL prompt

2. The output  contains a line starting with "Home terminal:", which looks like this:

Home terminal: $ZN019.#PTX3AFF
        

3. Use the process name from that output in the SCF command "info process <process>, detail"

SCF - T9082G02 - (06JAN06) (31OCT05) - 11/30/2006 14:10:02 System \DOC
(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.
TELSERV Detailed Info PROCESS \DOC.$ZN019
PCPU................... 0 BCPU................... 1
PPIN................... 343 BPIN................... 328
TACL................... ON Transport Process..... $ZB019
*Menu................... ON Transport Type......... TCP/IP
*Timeout Value.......... N/A Port................... 23
*Banner Timeout Value... N/A Total Services......... 2
*Max Terminals.......... 256 Total Terminals........ 1
Program................ \DOC.$SYSTEM.SYS00.TELSERV
*CPU List............... 0 ,1 ,2 ,3 ,4 ,5 ,6 ,7 ,8 ,9 ,10 ,11 ,12 ,13
,14 ,15
*DROPCR................. ON
Total Errors = 0 Total Warnings = 0
        

The "Transport Process" is the TCP/IP process being used for your terminal emulator - it may be the right process to use.

Choose a TCP/IP port for MIP

MIP listens for connections from TOP on a specific port. The default port is 2345.  If this port can't be used for some reason, then you can specify any other port number that isn't in use.

Start the MIP process

To start up a MIP process, logon to your NonStop server and volume to where the MIP software has been installed.

Assuming that your port number is <port> and your TCP/IP process is <tcpip_process> then the startup command is:

RUN MIP/NOWAIT, NAME $MIP, PFS 512, CPU 0/1 <port>
    <tcpip_process>

This assumes that CPUs 0 and 1 are available and that $MIP is going to be the process name.

Example

run mip/name $asmip,pfs 512,nowait,pri 150,cpu 1/0 1402 $Zb019

Check that MIP started OK

MIP may encounter problems when it starts. Check that your MIP process is still running with a status command:
STATUS $MIP

If  the mip process has stopped, then check EMS messages logged to $0 during startup. If there was a problem with the license then the message should be documented here otherwise it may be one of these messages.

If the message doesn't help to correct the problem, then send the message to Gresham support.

Check that you can logon with TOP

If your MIP process started with no error messages, then you should be able to logon through TOP.

The IP address that you enter in TOP must match an IP address that the TCPIP process, specified at startup, can reach. This will often be the same IP address that you use for terminal emulation (telnet) and ftp sessions.

The port that you specify in TOP must match the port number specified when you start the MIP.

If any of these details doesn't match, or MIP isn't started, then when you try to logon, you will see one of the following messages:

"Error checking license: connection refused"
"Error checking license: connection forcefully rejected"
"Error checking license: Winsock error 0" (after a timeout)