1.6.2.2 Installing products within the POSIX shell

1. Begin by seeing if you have the HPPXUDC.PUB.SYS UDC cataloged with the following command:

    :showcatalog

If HPPXUDC.PUB.SYS is not cataloged, or you get a message saying "No user-

defined command catalogs in use," catalog it at the system level and invoke the MPE/iX POSIX shell with the following commands:

    :setcatalog hppxudc.pub.sys;append;system
    :sh

Note: If you are installing from a CD-ROM: mount the CD-ROM, find the "mpeix_60.tar" file in the "/archives" directory, FTP the file to your HP e3000 machine and proceed with step 2 below.

2. Extract the contents of the TAR archive with the following command:

    shell/iX> cd /ACUCOBOL
    shell/iX> tar xovf name

where name is the tape device name (for example, "/dev/rmt0") or the name of the TAR file ("mpeix_60.tar").

Note: TAR format creates byte stream files which may conflict with existing file formats. You may want to remove any existing files from the destination directory before installing your Acucorp products.

3. After the files are installed, run the mpinst command. For example:

     shell/iX> mpinst

The install script:

Alters the capabilities and access for the ACUCOBOL account. Other accounts that use ACUCOBOL-GT should have, at least, the following capabilities:

Account: ND,SF,BA,IA,PH
User: ND,SF,BA,IA,PH
Group: BA,IA,PH

If necessary, converts the files read from the TAR archive to what MPE/iX expects. It converts the files because files read from archives in TAR format are created as byte stream files on MPE/iX.
Sets up a link needed for printing from the MPE/iX shell. For more information on printing, see section 1.6.3 Printing from the MPE/iX POSIX Shell.
Sets file permissions and ownership to the ACUCOBOL account.
Copies a library needed for relinking the runtime to the "/lib" directory.

4. Once your products have been installed, start the Activator from the "/bin" subdirectory.

    shell/iX> /ACUCOBOL/bin/activator

5. At the prompt, type the product code and product key that came with your product package. When you press <ENTER> after typing in each code and key pair, the license file is created. Repeat this cycle until the code/key pairs for each product you have ordered are entered.

6. Log into your own account. Then make sure the account has the capabilities for "Account," "User," and "Group" established in step 3.

7. Verify the installation.

a. Invoke the MPE/iX shell with the following command (cataloged in step 2):

:SH

b. The following environment variables may be set in your ".profile" file so that you do not have to type them each time you invoke the Shell. But for now, just type them in at the shell prompt (on the third line below, "hp" is just an example; substitute the correct name of the terminal you are using):

shell/iX> export PATH="$PATH:/ACUCOBOL/bin"
shell/iX> export A_TERMCAP="/ACUCOBOL/etc/a_termcap"
shell/iX> export A_TERM="hp"

c. Go to the sample directory and compile and run the tour program:

shell/iX> cd /ACUCOBOL/sample
shell/iX> ccbl tour.cbl
shell/iX> runcbl tour.acu

d. If you get the message "Can't find entry for terminal in /ACUCOBOL/etc/a_termcap ", then you need to configure your terminal for ACUCOBOL-GT. For more information, see Chapter 4 of the ACUCOBOL-GT User's Guide.

8. When you have the sample program running, you should edit the "/ACUCOBOL/etc/cblconfig" file supplied with ACUCOBOL-GT and change it to match your site. In particular, you should configure it to support the printers you have attached to your system. For more information about the configuration file, see section 2.7 of the ACUCOBOL-GT User's Guide.

9. Read the information files. The "READ_ME" file contains a list of files installed with the products. The "RELEASE" file (if present) contains changes to the products not covered in the documentation.

You can display either of the two files using the more command from the shell. For example:

     shell/iX> more /ACUCOBOL/READ_ME