The product is shipped on tape or floppy disk using either TAR or CPIO format, depending on the target machine. The media label shows which format is used, along with any other pertinent information. You will need to extract the files before installation.
Extracting files from the tape or floppy disk
1. Insert the tape into the appropriate drive.
2. Create a new directory for the product.
3. Move to this directory on your machine and then type one of the following commands depending on the archive type indicated on the tape or floppy disk label:
tar xfv device
or
cpio -icvBd < device
where device is the appropriate hardware device name (for example, "/dev/rfd0" or "/dev/rmt0").
Texas Instruments System 1500
Sites using Texas Instruments System 1500 should add an uppercase "T" to the cpio options ("-icvBdT").
HP cartridge tapes
For HP cartridge tapes, use the command:
tcio -ivrS 32 device | cpio -icv
For instance, if your device is /dev/rmt0, the command would be:
tcio -ivrS 32 /dev/rmt0 | cpio -icv
Important information for sites running DEC OSF/1 AXP
The DEC OSF/1 AXP operating system does not buffer disk writes by default. This results in file update times that are much slower than usual for UNIX machines. To increase performance for write operations, you must modify the system kernel parameter "delay_wbuffers".
WARNING: Modifying or patching the system kernel is extremely risky. If a mistake is made or if an improperly configured kernel is installed, the system may crash or fail to boot. Modifications to the kernel should be performed only by a qualified system administrator. One way to enable "delay_wbuffers" is to use the UNIX debugger utility "dbx" to patch the kernel. Using "dbx" you could enter the following commands:
dbx -k /vmunix (dbx) assign delay_wbuffers=1 (dbx) patch delay_wbuffers=1 (dbx) q
Installing the products and the license file
To install a product once the contents of the tape or floppy disk have been extracted, perform the following steps:
1. First read the "READ_ME" file. The "READ_ME" file describes the files included with the product. The "RELEASE" file (if present), contains changes to the compiler not covered in the documentation.
2. For compiler installation, add the ACUCOBOL-GT "bin" subdirectory to your
system path. (Or copy the "ccbl", "runcbl", "logutil", "vutil", "vio" and
"activator" files to a directory mentioned in your execution path. These
executable files should be set to have "execute" permission for everyone who is
using the compiler or runtime system.)
4. The remaining files can be left in the directory in which they were loaded.
5. If you are using the C-shell, type "rehash".
6. After the products are installed, start the Activator from the "/bin" subdirectory.
7. 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.
8. Start the acushare license manager service by typing "acushare -start" in the command line.
9. Move to the directory that contains the sample programs and try compiling and running the tour program with the following commands:
ccbl tour.cbl
runcbl tour.acu
10. If you get the message "Can't find entry for 'terminal' in 'term-lib'", you need to configure your terminal for ACUCOBOL-GT. Refer to Appendix A of the ACUCOBOL-GT manual set if you need to do this.
11. Once you have the sample program running, you may want to edit the "cblconfig" file supplied with ACUCOBOL-GT to meet the needs of your site. In particular, you should configure it to support the printers you have attached to your system. The chapter called "Compiler and Runtime" in the ACUCOBOL-GT User's Guide contains details about the configuration file.
12. If you are using shared memory, see the instructions for configuring acushare that are located in section 2.11 of the ACUCOBOL-GT User's Guide.