contents.gifindex.gifprev1.gifnext1.gif

Microsoft SQL Server: Installation steps on a Windows NT server machine

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

Step One: Install SQL Server

Microsoft SQL Server, version 6.0 or later, must be installed and configured on the Windows NT server machine before you install Acu4GL for Microsoft SQL Server 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 interface does not need isql after installation, but it is 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.

These products are not provided by Acucorp.

Step Two: Copy the batch file

MS_INST.CMD is a batch file from ACUCOBOL-GT that will create the MS_INST.SQL file, which is the collection of stored procedures necessary for executing the Acu4GL interface. Copy MS_INST.CMD to your server machine into a directory of your choice.

Step Three: Execute the batch file

To execute the batch file, enter

MS_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 Microsoft SQL Server interface will need to have write access to this database.

This step creates MS_INST.SQL, which is the collection of stored procedures necessary for executing the Acu4GL interface.

Step Four: 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 < MS_INST.SQL

SA represents the name of your system administrator. Be sure to enter the name appropriate for your site.

Another way to accomplish the same result is to use ISQL/W to execute MS_INST.SQL as a query. See your Microsoft SQL Server documentation for how to do this.

This completes the setup on the Windows NT server machine.