Acucobol Release Notes


Acucobol Windows Client
Acucobol Windows Server
Acucobol Visual Basic Client
Acucobol SCO Unix Server

Acucobol Windows Client

Version 1.1

Installation

Windows 3.1

Follow these steps to install Cobol-RPC on a client under Windows 3.1:

Windows 95

Use one of the following methods to install Cobol-RPC on a client under Windows 95:

When installation of the client software is complete, a Cobol-RPC folder will be created which contains the following icons:

Icon Action
Sample Client Runs a Cobol-RPC COBOL client demonstration program.
Cobol-RPC Help Displays on-line documentation for Cobol-RPC.
Client Readme Displays the client Readme file.

The file readmecl.txt lists and describes each of the files that are installed.

Running the Sample Programs

A sample client program named CLIENT.CBL is installed with the client software. The source and executable files for three sample server programs are installed with the Cobol-RPC server software. These programs are called SERVER1.CBL, SERVER2.CBL, and SERVER3.CBL. These programs demonstrate how Cobol-RPC executes remote program calls. The source code for these programs is also installed.

To execute the sample program follow these steps:

  1. Make sure TCP/IP is installed and configured properly.
  2. Make sure the IP address of the server is contained in the DefaultServer item of the ClientConfig section of the COBOLRPC.INI file on the client.
  3. Follow the instructions for preparing the server in the Cobol-RPC server release notes.
  4. Double click the Sample Client icon in the Cobol-RPC folder on the client to start the sample program.
  5. Follow the on-screen prompts.

Redirected CALL Statements

The Acucobol version of Cobol-RPC supports redirected CALL statements as described in the Cobol-RPC User's Guide. This means ordinary CALL statements can be configured to function as remote program calls.

REMOTEPROGRAM Function

Acucobol clients can use the simplified version of the REMOTEPROGRAM function as described in Chapter 4 of the Cobol-RPC User's Guide.

Non-Portable Data Types

The following data types may not be portable between all types of clients and servers. No data items of these types should be passed when making remote program calls.

COMP-5
BINARY (When using the compiler's -D5 option)
POINTER
FLOATING-POINT
SIGNED-SHORT
SIGNED-INT
SIGNED-LONG
UNSIGNED-SHORT
UNSIGNED-INT
UNSIGNED-LONG

Special Considerations With Program Names

Cobol-RPC matches the names of called programs with the names of programs in the cobolrpc.ini file to determine what programs to call remotely. The flexibility available in using extensions with program names requires special consideration.

Always include the same name in the RemotePrograms section of cobolrpc.ini that is used in the CALL statement. If the program name includes an extension in the CALL statement, include the extension in the cobol.ini file. If no extension is used the in the CALL statement, do not include an extension in the cobolrpc.ini file.

Even if you are using the CODE_SUFFIX configuration option, follow this rule. The CODE_SUFFIX option does not affect Cobol-RPC when it is determining what program to call remotely.

However, the CODE_SUFFIX option on the server will affect the way Cobol-RPC loads the remotely called program. If you make a CALL to a program name without an extension and the program should be loaded with an extension, include the CODE_SUFFIX option in the server's COBOL configuration file.

Acucobol Windows Server

Version 1.1

Installation

Windows 3.1

Follow these steps to install Cobol-RPC on a server under Windows 3.1:

Windows 95

Use one of the following methods to install Cobol-RPC on a server under Windows 95:

When installation of the server software is complete, a Cobol-RPC folder will be created which contains the following icons:

Icon Action
Cobol-RPC Server Starts the Cobol-RPC server.
Cobol-RPC Help Displays on-line documentation for Cobol-RPC.
Server Readme Displays the server Readme file.

The file readmesv.txt lists and describes each of the files that are installed.

Running the Sample Programs

The source and executable files for three server programs are installed with the Cobol-RPC server software. These programs are called SERVER1.CBL, SERVER2.CBL, and SERVER3.CBL. These programs demonstrate how Cobol-RPC executes remote program calls.

The sample programs are executed from the client, not the server. Before the client can execute these programs perform the following steps.

  1. Make sure TCP/IP is installed and configured.
  2. Start the Cobol-RPC Server Program by double clicking it's icon.
  3. Follow the instructions in the client release notes to run the sample programs.

[ServerConfig]
StartupCommand=

The StartupCommand entry in the [ServerConfig] section of the COBOLRPC.INI file specifies the command that will be used to start the COBOL runtimes that respond to remote program calls. Everything to the right of the equal sign is the beginning of the command that will be used for handling remote program calls. The server will append information to this command specific to the call.

The first time a client connects to a server, the server will use this command to start a COBOL runtime on the server. This runtime will remain dedicated to the client until the client terminates, and will execute all remote programs called by the client.

In practice, complete path names should be included for all files. This makes them insensitive to the working directory the server is initiated from. A configuration file and other COBOL runtime parameters can be included in this entry. The entry should look like this:

[ServerConfig]
StartupCommand=wruncbls rpcinit.cob

wruncbls is a Cobol-RPC enabled Acucobol server runtime. It must be used because it contains the specialized logic needed to communicate with the client. rpcinit.cob is a small Cobol program that initializes the runtime to work with the client.

Debugging Server Programs

To debug a server program just include the D option in the StartupCommand entry in the COBOLRPC.INI file. When the server runtime is started the debugger will be initiated.

Redirected CALL Statements

The Acucobol version of Cobol-RPC supports redirected CALL statements as described in the Cobol-RPC User's Guide. This means ordinary CALL statements can be configured to function as remote program calls.

REMOTEPROGRAM Function

Acucobol clients can use the simplified version of the REMOTEPROGRAM function as described in Chapter 4 of the Cobol-RPC User's Guide.

Non-Portable Data Types

The following data types may not be portable between all types of clients and servers. No data items of these types should be passed when making remote program calls.

COMP-5
BINARY (When using the compiler's -D5 option)
POINTER
FLOATING-POINT
SIGNED-SHORT
SIGNED-INT
SIGNED-LONG
UNSIGNED-SHORT
UNSIGNED-INT
UNSIGNED-LONG

Hiding the Cobol Window

To prevent the Cobol window from being displayed on the server, include the -b option in the StartupCommand.

Acucobol Visual Basic Client

Version 1.1

Installation

Windows 3.1

Follow these steps to install Cobol-RPC on a client under Windows 3.1:

Windows 95

Use one of the following methods to install Cobol-RPC on a client under Windows 95:

When installation of the client software is complete, a Cobol-RPC folder will be created which contains the following icons:

Icon Action
Sample Client Runs a Cobol-RPC COBOL client demonstration program.
Cobol-RPC Help Displays on-line documentation for Cobol-RPC.
Client Readme Displays the client Readme file.

The file readmevb.txt lists and describes each of the files that are installed.

Components

There are two components whose names are unique to this version of Cobol-RPC. The first is the Visual Basic module that contains the Cobol-RPC functions and declarations. It is called ACUCBRPC.BAS and is installed in the Cobol-RPC directory. The other is the DLL that interfaces between Visual Basic and Cobol. It is called ACURPCVB.DLL and is installed in the Windows directory.

Running the Sample Programs

A sample project vbclient is installed in the Cobol-RPC directory. It includes the source and executable files for a sample program. This sample project calls sample programs installed with the server version of Cobol-RPC. The server version of Cobol-RPC must be installed before the project is executed.

To execute the sample project follow these steps:

  1. Make sure TCP/IP is installed and configured.
  2. Make sure the IP address of the server is contained in the DefaultServer entry of the ClientConfig section of the COBOLRPC.INI file on the client.
  3. Follow the instructions for preparing the server in the Cobol-RPC server release notes.
  4. Double click the Visual Basic Sample Client icon in the Cobol-RPC folder on the client to start the sample program.
  5. Follow the on-screen prompts.

Acucobol SCO Unix Server

Version 1.1

Installation

Installing Files

To install Cobol-RPC on a server computer under UNIX:

The file readmesv.txt lists and describes each of the files that are installed.

Relinking the COBOL runtime

After installing the Cobol-RPC software, it must be linked with the Cobol runtime. The process for doing this is quite straightforward. Just follow these steps:

Running the Sample Programs

The source and executable files for three sample programs are installed with the Cobol-RPC server software. These programs are called SERVER1.CBL, SERVER2.CBL, and SERVER3.CBL. These programs demonstrate how Cobol-RPC server programs handle remote program calls. The sample programs are run from the client, not the server, so follow the instructions in the client release notes to execute these programs.

Before Cobol-RPC can begin handling remote program calls the Acucobol license manager program must be started. The following command should be executed on the server before attempting to run the sample program on the client:

/acu/bin/acushare -start

After starting the Acucobol license manager program, follow the instructions in the client release notes to run the sample programs.

Debugging

Use the following command to debug a server program:

/cobolrpc/rpcdebug

This command will start the runtime in debug mode.

Set the desired breakpoints before issuing the G debugger command. The terminal will freeze until a client connects.

Redirected CALL Statements

The Acucobol version of Cobol-RPC supports redirected CALL statements as described in the Cobol-RPC User's Guide. This means ordinary CALL statements can be configured to function as remote program calls.

REMOTEPROGRAM Function

Acucobol clients can use the simplified version of the REMOTEPROGRAM function as described in Chapter 4 of the Cobol-RPC User's Guide.

Non-Portable Data Types

The following data types may not be portable between all types of clients and servers. No data items of these types should be passed when making remote program calls.

COMP-5
BINARY (When using the compiler's -D5 option)
POINTER
FLOATING-POINT
SIGNED-SHORT
SIGNED-INT
SIGNED-LONG
UNSIGNED-SHORT
UNSIGNED-INT
UNSIGNED-LONG

Starting the Runtime from the Command Line

In order to see the effect of DISPLAY statement or use any ACCEPT statements in server programs the runtime must be started from the command line as follows:

/cobolrpc/rpcdirect

After typing this command and pressing RETURN the terminal will freeze until a client connects. Then the remote program called by the client will be executed and the display will be updated.


Home | About | Products | Contact
Distributors | Library | Register

Copyright 1996 by England Technical Services, Inc.