ContentsIndexPreviousNext

E.3.5 Installation Steps on the UNIX Server Machine

To install the Acu4GL for Sybase diskette on a UNIX server machine:

Step One: Install Sybase

The Sybase RDBMS, version 11.0 or later, must be installed and configured before you install Acu4GL for Sybase. Follow the Sybase installation instructions in your Sybase documentation.

Sybase's isql product, which is an interactive query tool, is also necessary for installing the ACUCOBOL-GT stored procedures.

The Acu4GL product does not need isql after installation, but it's a tool that will give you quite a bit of flexibility. It allows you to do database work outside of COBOL, including interactive queries, table creation, table modification, and creation of views, constraints, and relationships between tables.

Acucorp does not provide these products.

Step Two: Copy files

Copy "syb_inst", "syb_cfg.in", and "syb_inst.in" to your UNIX server machine.

Step Three: Create stored procedures

The file "syb_inst" is an interactive shell script that generates the SQL script used to install ACUCOBOL-GT stored procedures. In the instructions below, bold italicized text within a message indicates that the script will insert what you had previously typed.

Execute the shell script "syb_inst" by entering the following command on your server machine:

     sh  syb_inst

Note: You may exit the script at any time by pressing the system interrupt key (usually CTRL+C).

If you entered just syb_inst instead of the full command, this message may appear:

VAL=0: command not found
VAL:  Undefined variable

This can be fixed by entering sh syb_inst.

When the script begins executing, you will see the following message:

During the execution of this script, we will create an SQL script which you
will need to execute from isql, using a command like:
"isql -Usa -Ppassword < syb_inst.sql"
This script will add some stored procedures, and create some tables in a
database that you specify during the execution of this script.

In order to implement locking from ACUCOBOL-GT, we need to create a lock table. This should be a pretty small table, but we need to decide which database to create this table in. You should now enter the name of the database you want the lock tables created in. If the database does not exist, it will be created.

The following question is asked until you enter a valid database name:

Which database would you like to create this table in?

This database will eventually be located on your server machine. Enter a valid database name. (Invalid names are master, model, temp, or sybsystemprocs.) Names must start with a letter or underscore, must contain only letters, digits, and underscores, and may be up to 30 characters long. Any other entry will be modified.

Next you will see the following message:

Saving any old version of syb_inst.sql...

Old versions of "syb_inst.sql" are saved to "syb_instnnn.sql" where nnn starts at 001 and goes to 999. If a file "syb_inst.sql" exists, you see:

Saving syb_inst.sql as syb_instnnn.sql

for some value of nnn. Then you see:

Creating syb_inst.sql...

This uses the file "syb_inst.in" as a template, and creates "syb_inst.sql", using the database name you entered above.

You also see:

Creating cblconfig.syb...

This is a sample file of configuration variables you may want to add to your cblconfig file.

You then see the following message:

Do you want to set up the Makefile for this system?

Type "n" or "N" to quit the script.

Step Four: Install the ACUCOBOL-GT stored procedures

You must have database administrator privileges to install the ACUCOBOL-GT shared procedures on the server. (You need to enter the password for the database administrator.) Enter the following command:

     isql -Usa -Ppassword  <  syb_inst.sql

This completes the installation steps on the UNIX server machine. You are now ready to complete the installation on the client machine.


Note: If you are upgrading from an earlier version of Acu4GL, be sure to install the new stored procedures. Acucorp always upgrades stored procedures in such a way that they are compatible with older versions of the product, so installing new stored procedures over old ones does not affect your ability to run with an older version of the interface software.