Once your products are installed, you can verify that the installation was successful by compiling and running the "TOURHP" program. (Refer to Chapter 4 in Transitioning to ACUCOBOL-GT for detailed information about compiling and running programs in the HP e3000 environment.)
To test your installation, log into your own account. Make sure that the account has the PH capabilities described in the topic Before Installing extend Products (if needed) and that "ACUUDC.PUB.ACUCOBOL" has been cataloged. Then compile and run the "TOURHP" program.
TOURHP is a special sample program for HP e3000 users that demonstrates how to use the ACUCOBOL-GT compiler and runtime and creates a small KSAM file:
:CHDIR /ACUCOBOL/sample
:ccbl "-cp -gd -v TOURHP"
Most of the ACUCOBOL-GT files are case-sensitive. Be sure that "ccbl" is lowercase.
In the command shown above,
When you press Enter after typing this command, you should see the following messages:
Start TOURHP Data Division Procedure Division Including Debugging Info Writing Code Addresses Compilation complete
If you get an error similar to the following:
Unknown command name. (CIERR 975)
It is probably because the path for "ccbl" was not added to your HPPATH environment variable. You can check this by typing:
:SHOWVAR HPPATH
If the HPPATH is incorrect, you might see the following:
HPPATH = !HPGROUP,PUB,PUB.SYS,ARPA.SYS
Normally when ACUUDC is cataloged it will add "/ACUCOBOL/bin" to your path. Verify that ACUUDC is cataloged. If you don't want to add "/ACUCOBOL/bin" to HPPATH, you will have to specify the full or relative pathname as follows:
:/ACUCOBOL/bin/ccbl "-cp -gd -v TOURHP"
If you don't want to use ACUUDC, and prefer to type commands that are in the "/ACUCOBOL/bin" directory without having to enter the full or relative pathname, you can type:
:SETVAR HPPATH "!HPPATH,/ACUCOBOL/bin"
to set the HPPATH variable.
Use the LISTFILE command to display the compiled object:
:LISTFILE ./TOURHP@
If you use the wildcard as shown, this should display "TOURHP" (the source COBOL program) and "TOURHP.acu" (the compiled object). The compiled object is ready to run using the ACUCOBOL-GT runtime system. No linking is required. If you use the following LISTFILE command:
:LISTFILE NEWKFILE,2
you should get a message indicating that the file "NEWKFILE" does not exist. This is the expected behavior. It simply means that the KSAM file that will be created by running the TOURHP program does not yet exist.
:runcbl "-c CNFGVAR TOURHP"
In this case, the "-c" option tells the runtime to look for the configuration file named "CNFGVAR". This file sets the variable "DEFAULT_HOST" to "KSAM", causing the runtime to create KSAM files instead of Vision files. The runtime automatically selects a file with the ".acu" extension. If you run the same LISTFILE command indicated in step 3, you will see that a KSAM file named "NEWKFILE" has been created.
If you get the message "Can't find entry for terminal in /ACUCOBOL/etc/a_termcap", you need to configure your terminal for ACUCOBOL-GT. This is set in the ACUUDC with the following command:
:SETVAR A_TERM "hp"
You can verify this by typing:
:SHOWVAR A_TERM
For more information on configuring your terminal for ACUCOBOL-GT, see ACUCOBOL-GT User's Guide > Terminal Manager.
:LISTFILE /ACUCOBOL/RE@
You can display it on the screen using the PRINT command. For example:
:PRINT /ACUCOBOL/RELEASE