Your products are shipped on tape 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.
- Insert the tape into the appropriate drive.
- Create a new directory for the product.
- Move to this directory on your machine and then type one of the following commands depending on the archive type indicated
on the label:
tar xfv device
or
cpio -icvBd < device
where
device is the appropriate hardware device name (for example, "/dev/rfd0" or "/dev/rmt0"). This extracts your product files and install
them on your machine.
- After the products are installed, start the Activator from the "/bin" subdirectory.
Note: Each product searches for its license file in the same directory in which its executable resides. If you move the product's
executable to a new directory, you must move its license file to the same location.
- 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.
- Start the acushare license manager service by entering
acushare -start on the command line.
- 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
Note:
If you get the message "Can't find entry for 'terminal' in 'term-lib'", you need to configure your terminal for ACUCOBOL-GT.
See the topic
Configuring Your Terminals.
- 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.
- If you are using shared memory, see the instructions for configuring acushare that are located inACUCOBOL-GT User's Guide > Compiler and Runtime > Acushare Utility Program.
Please read the "RELEASE" file. The "RELEASE" file (if present) describes changes to the product that are not covered in the
documentation.