1. As system manager, check to see if the ACUCOBOL account exists:
:HELLO MANAGER.SYS
:LISTACCT ACUCOBOL
If you get a message saying "Non-existent account." then create it with the following command:
:NEWACCT ACUCOBOL,MGR
2. See 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 shell with the following commands:
:SETCATALOG HPPXUDC.PUB.SYS;SYSTEM
:SH
3. If you do not have a tape device name set up for your tape drive, you can create one with the following command:
shell/iX> mknod /dev/rmt0 c 0 number
shell/iX> chmod 666 /dev/rmt0
where number is the device number of the tape drive (for example, 7).
4. At the MPE/iX shell prompt, change your directory to /ACUCOBOL/PUB and remove any existing files with the following commands:
shell/iX> cd /ACUCOBOL/PUB
shell/iX> rm -r /ACUCOBOL/PUB/*
The existing files must be removed because "tar" creates byte stream files, and these can conflict with existing file formats.
5. Load the contents of the tape with the following command:
shell/iX> tar xovf device
where device is the tape device name (for example, "/dev/rmt0").
6. After the files are restored, run the install command. For example:
shell/iX> install
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 get
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 the next section, "Printing from the MPE/iX Shell."
Sets file permissions and ownership to the ACUCOBOL account.
Copies a library needed for relinking the runtime to the /lib directory.
7. Read the information files:
Read the "READ_ME" file. It contains updated information about ACUCOBOL-GT and the installation procedure. Read the "RELEASE" file (if present). It contains changes to the compiler not covered in the printed documentation.
You can display either of the two files by using the more command from the shell. For example:
shell/iX> more /ACUCOBOL/PUB/READ_ME
8. To verify the installation, log into your own account. Then:
a. Make sure the account has at least the following capabilities:
Account: ND,SF,BA,IA,PH
User: ND,SF,BA,IA,PH
Group: BA,IA,PH
b. Invoke the MPE/iX shell with the following command (cataloged in step 2):
:SH
c. 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, you can 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/PUB/bin"
shell/iX> export A_TERMCAP="/ACUCOBOL/PUB/etc/a_termcap"
shell/iX> export A_TERM="hp"
d. Copy the "tour.cbl" sample program to your current directory, then compile and run it:
shell/iX> cp /ACUCOBOL/PUB/sample/tour.cbl .
shell/iX> ccbl tour.cbl
shell/iX> runcbl
e. If you get the message "Can't find entry for terminal in termlib'", then you need to configure your terminal for ACUCOBOL-GT. For more information, see Chapter 4 of the ACUCOBOL-GT User's Guide.
9. When you have the sample program running, you should edit the "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 the ACUCOBOL-GT User's Guide, section 2.7, Runtime Configuration.