Windows NT Server and Windows Client Installations

Complete the following steps to install the Acu4GL product on a Windows NT server machine.

Step 1: Install SQL Server

Sybase, version 11.0 or later, must be installed and configured on the Windows NT server machine before you install Acu4GL for Sybase on the client machine. Follow the instructions from your RDBMS vendor.

The 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 is a tool that can 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.

Micro Focus does not provide these products.

Step 2: Copy the batch file

The file “syb_inst.cmd” is a batch file from Micro Focus that will create the “syb_inst.sql” file, which is the collection of stored procedures necessary for executing the Acu4GL product. Copy “syb_inst.cmd” to your server machine into a directory of your choice.

Step 3: Execute the batch file

To execute the batch file, enter

SYB_INST LockDatabase

where LockDatabase is the database you want to use for the internal ACUCOBOL GT lock tables. If this database does not already exist, it will be created.

Everyone who will use the Acu4GL for Sybase product must have write access to this database. This step creates “syb_inst.sql”, which is the collection of stored procedures necessary for executing the Acu4GL product.

Step 4: Install the ACUCOBOL-GT stored procedures

You must have Database Administrator privileges to do this step. You need to enter the password for the Database Administrator.

Type:

ISQL -USA -Ppassword  <  SYB_INST.SQL

Another way to accomplish the same result is to use ISQL/W to execute syb_inst.sql as a query. See your Sybase documentation for how to do this.

By default, the stored procedures are installed into the master or sybsystemprocs databases. However, you may choose another database in which to store them. Follow these steps if you want to install the stored procedures in a database other than the default:

  1. Before you execute the “syb_inst.sql” query, modify the query file to use the desired database instead of the master or sybsystemprocs database. After you have modified the query file, execute it as described above.
  2. Create in each database that contains tables accessed by Acu4GL the stored procedures that were previously in the master or sybsystemprocs database. Note that the stored procedures are executed without being prefixed by a database name, and Sybase requires that such stored procedures must be in the master or sybsystemprocs database.

The interface also searches for and executes the sp_AcuInit stored procedure from this location. This stored procedure is executed when a connection is made to the database; therefore, sp_AcuInit should reside in the default database for each user if it is not created in the master database. See Built-in Stored Procedures for information on the sp_AcuInit stored procedure.

This completes the setup on the UNIX or Windows NT server machine.

Note:

If you are upgrading from an earlier version of Acu4GL, be sure to install the new stored procedures. We always upgrade 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. Your new version of Acu4GL for Sybase may not run properly without the corresponding stored procedures.

It can be difficult to maintain multiple copies of stored procedures; therefore, we recommend that you continue to create the stored procedures in the master or sybsystemprocs database. If your installation does not permit this, you do have the flexibility to create the stored procedures elsewhere. However, to facilitate maintenance of the stored procedures, we recommend that you create as few databases as possible.