Index

access file manager:

To create or open an access file

To display an access record

3.3.3 Using the Access File Manager

To start the access file manager

To remove an access record

To modify an access record

access file manager:creating an access file:

To create or open an access file

access file manager:default values:

3.3.3 Using the Access File Manager

access file manager:displaying records:

To display an access record

access file manager:modifying a record:

To modify an access record

access file manager:removing a record:

To remove an access record

access file manager:starting:

To start the access file manager

access file manager:using:

3.3.3 Using the Access File Manager

access records:

To add an access record

3.3.2 Access Records

access records:defined:

3.3.2 Access Records

access records:examples:

3.3.2 Access Records

access records:fields:

3.3.2 Access Records

access records:most permissive:

3.3.2 Access Records

access records:password:

To add an access record

access records:wildcards in:

3.3.2 Access Records

ACCESS_FILE:

3.4.1 ACCESS_FILE

Acu_Client_Password:

3.6.1 Passwords

6 Managing the System - 6.3.4 Invalid Password - Diagnostics

6.3.4 Invalid Password

Acu4GL:

1.1 Overview

AcuAccess:

3.4 Creating a Server Configuration File

3.4.7 SERVER_START_port #

1.3.1 AcuConnect Configuration Files

3.6 AcuConnect Connection Logic

To install AcuConnect on a Windows NT or Windows 2000 server

4.2.5 Setting Up the User Name

3.3.1 The Server Access File

3.3.3 Using the Access File Manager

To display an access record

3.4.1 ACCESS_FILE

3.3.2 Access Records

acuconnect -kill:

To stop AcuConnect on a UNIX server

acuconnect -start:

5.2.1 UNIX Startup

acuconnect, use under MPE/iX:

Running AcuConnect on HP MPE/iX systems

acuconnect:

3.3 Establishing System Security

3.3.1 The Server Access File

5.2.2 Windows NT and Windows 2000 Startup

A.1 The "acuconnect" Command

To start AcuConnect on unrestricted UNIX sites

A.2 "acuconnect" Command Formats

acuconnect:automatic startup on UNIX:

To start AcuConnect on unrestricted UNIX sites

acuconnect:automatic startup on Windows NT/2000:

5.2.2 Windows NT and Windows 2000 Startup

acuconnect:command:

A.1 The "acuconnect" Command

acuconnect:error log:

A.2 "acuconnect" Command Formats

acuconnect:installing the Windows NT service:

A.2 "acuconnect" Command Formats

acuconnect:removing the Windows NT service:

A.2 "acuconnect" Command Formats

acuconnect:starting the access file manager:

A.2 "acuconnect" Command Formats

acuconnect:starting:

A.2 "acuconnect" Command Formats

acuconnect:stopping:

A.2 "acuconnect" Command Formats

acuconnect:version number:

A.2 "acuconnect" Command Formats

acuconnect:will not start:

3.3.1 The Server Access File

3.3 Establishing System Security

ACUCONNECT_CLOSE_AFTER_CANCEL:

1.3.1 AcuConnect Configuration Files

ACUCONNECT_CLOSE_AFTER_CANCEL

4.3 Creating a Client Configuration File

ACUCONNECT_CONFIGURATION_FILE:

1.3.1 AcuConnect Configuration Files

ACUCONNECT_CONFIGURATION_FILE

ACUCONNECT_RUNTIME_FLAGS:

ACUCONNECT_RUNTIME_FLAGS

1.3.1 AcuConnect Configuration Files

AcuConnectAccess:

To create or open an access file

3.3 Establishing System Security

3.4.1 ACCESS_FILE

3.3.3 Using the Access File Manager

AcuServer:

1.1 Overview

acushare:

5.2.1 UNIX Startup

To start AcuConnect on restricted UNIX sites

acuthread:

To relink the server runtime under Windows NT or Windows 2000

1.3 Theory

To install AcuConnect on a Windows NT or Windows 2000 server

3.2.2 Using AcuConnect as a Stand-Alone Runtime

application design:

2.1 Designing Your Application

application distribution:

6.1.1 Distribution Considerations

asynchronous CALLs:

1.3.2 Process Flow

2.3 Synchronous or Asynchronous Execution?

batch processing:

2.1 Designing Your Application

6.1.1 Distribution Considerations

C$ASYNCPOLL:

2.7 Sample Programs

2.3.2 CALLing C$ASYNCPOLL

2.2.1 Terminating the Remote Application

C$ASYNCRUN:

1.3.2 Process Flow

2.7 Sample Programs

2.3.2 CALLing C$ASYNCPOLL

5.5.1 Results

2.3 Synchronous or Asynchronous Execution?

2.3.1 CALLing C$ASYNCRUN

2.2.1 Terminating the Remote Application

C$CALLERR:

2.2.2 Exception Handling

CALL verb:

2.2 Embedding COBOL CALLs

CANCEL ALL:

2.2.1 Terminating the Remote Application

CANCEL:

ACUCONNECT_CLOSE_AFTER_CANCEL

cblconfig:

1.3.1 AcuConnect Configuration Files

CHAIN command:

2.4 Memory and Environment Issues

client component:

1.4 Getting Started

2.1 Designing Your Application

client configuration file:

2.2 Embedding COBOL CALLs

1.3.1 AcuConnect Configuration Files

4.2.4 Setting Up the Host Name

4.3 Creating a Client Configuration File

2.6 Creating a Runtime Configuration File

4.1 Preparing the Client(s)

client user name:

3.3.2 Access Records

To add an access record

client.cfg:

1.3.1 AcuConnect Configuration Files

clntstub:

4.2.2 Removing AcuConnect Client Support From the Runtime

code name alias:

4.3.1.2 Code Name Aliases

4.2.4 Setting Up the Host Name

CODE_MAPPING variable:

4.3.1.2 Code Name Aliases

CODE_PREFIX:

4.2.4 Setting Up the Host Name

4.3.1.1 CODE_PREFIX

1.3.1 AcuConnect Configuration Files

configuration file variables, standard:

4.3.2 Other Variables

configuration files:

1.3.1 AcuConnect Configuration Files

configuration variables:

3.4 Creating a Server Configuration File

1.3.1 AcuConnect Configuration Files

configuration variables:client:

1.3.1 AcuConnect Configuration Files

configuration variables:server:

3.4 Creating a Server Configuration File

connection refused:

6.3.3 Connection Refused

connection validation logic:

3.6 AcuConnect Connection Logic

creating an access file:

To create or open an access file

DEFAULT_MAP_FILE:

DEFAULT_MAP_FILE

2.5 International Character Handling

DEFAULT_USER:

3.6 AcuConnect Connection Logic

3.4 Creating a Server Configuration File

To add an access record

To install AcuConnect on a Windows NT or Windows 2000 server

3.3.2 Access Records

3.4.2 DEFAULT_USER

6.3.3 Connection Refused

6 Managing the System - 6.3.3 Connection Refused - UNIX Diagnostics

6 Managing the System - 6.3.3 Connection Refused - Windows Diagnostics

distributed computing environment:

6.1.1 Distribution Considerations

1.1 Overview

environment inheritance:

2.4 Memory and Environment Issues

error log:

A.2 "acuconnect" Command Formats

exception handling:

2.2.2 Exception Handling

EXTERNAL data items:

2.4 Memory and Environment Issues

fat client:

6.1.1 Distribution Considerations

file trace:

A.2 "acuconnect" Command Formats

foreground, running acuconnect in:

A.2 "acuconnect" Command Formats

foreign language characters:

2.5 International Character Handling

host name of client system:

6 Managing the System - 6.3.3 Connection Refused - Windows Diagnostics

6 Managing the System - 6.3.2 Unexpected User Name - Windows Diagnostics

6 Managing the System - 6.3.3 Connection Refused - UNIX Diagnostics

6 Managing the System - 6.3.2 Unexpected User Name - UNIX Diagnostics

installing the client:

4.4 Installing Client Programs

installing the server:

3.5 Installing Server Programs

international character handling:

server_MAP_FILE

2.5 International Character Handling

Internet usage:

4.3.1.1 CODE_PREFIX

linking:

1.3 Theory

machine failures:

6.2 Machine Failures

map file, character:

DEFAULT_MAP_FILE

2.5 International Character Handling

memory usage:

2.4 Memory and Environment Issues

memory/environment issues:

2.4 Memory and Environment Issues

memory/environment issues:CHAIN command:

2.4 Memory and Environment Issues

memory/environment issues:environment inheritance:

2.4 Memory and Environment Issues

memory/environment issues:EXTERNAL data items:

2.4 Memory and Environment Issues

memory/environment issues:memory usage:

2.4 Memory and Environment Issues

memory/environment issues:open connections:

2.4 Memory and Environment Issues

memory/environment issues:runtime usage:

2.4 Memory and Environment Issues

MPE/iX, running AcuConnect in:

Running AcuConnect on HP MPE/iX systems

multiple runtime instances:

1.3 Theory

2.2.3 CALLing Multiple Programs

network services:

4.2.6 Confirming Network Services

on exception phrase:

2.2.2 Exception Handling

open connections:

2.4 Memory and Environment Issues

ownerships and permissions:

3.3 Establishing System Security

password:

To add an access record

6.3.4 Invalid Password

password:field in access record:

To add an access record

password:invalid, connection refused:

6.3.4 Invalid Password

PASSWORD_ATTEMPTS:

3.4.3 PASSWORD_ATTEMPTS

3.6.1 Passwords

passwords:

1.3.1 AcuConnect Configuration Files

4.2.3 Passwords for Clients

3.3.2 Access Records

To add an access record

3.6.1 Passwords

platform support:

1.2 Platform Support

process flow:

1.3.2 Process Flow

relinking:

4.2.1 Relinking the Client Runtime

3.2.1 Relinking the Server Runtime

relinking:relinking the client runtime:

4.2.1 Relinking the Client Runtime

relinking:relinking the server:

3.2.1 Relinking the Server Runtime

remote application path:

4.3.1 Defining Remote Application Path

removing client support:

4.2.2 Removing AcuConnect Client Support From the Runtime

runtime configuration file:

2.6 Creating a Runtime Configuration File

1.3.1 AcuConnect Configuration Files

ACUCONNECT_CONFIGURATION_FILE

runtime usage:

2.4 Memory and Environment Issues

runtime:

3.2.2 Using AcuConnect as a Stand-Alone Runtime

runtime:using AcuConnect as a stand-alone:

3.2.2 Using AcuConnect as a Stand-Alone Runtime

sample client.cfg:

4.3.3 Sample "client.cfg" file

sample code:

2.7 Sample Programs

sample files:

3.4.8 Sample "server.cfg" file

sample program, results:

5.5.1 Results

sample programs, running:

5.5 Running the Sample Programs

security:

3.3 Establishing System Security

server access file:

3.3.1 The Server Access File

3.3.2 Access Records

server access file:access records:

3.3.2 Access Records

server access file:default name:

3.3.1 The Server Access File

server component:

6.1 Modifying Application Distribution

1.4 Getting Started

2.6 Creating a Runtime Configuration File

3.2.2 Using AcuConnect as a Stand-Alone Runtime

2.1 Designing Your Application

server configuration file, specifying at startup:

A.2 "acuconnect" Command Formats

server configuration file:

3.4 Creating a Server Configuration File

To install AcuConnect on a Windows NT or Windows 2000 server

3.1 Preparing the Server

6 Managing the System - 6.3.3 Connection Refused - UNIX Diagnostics

1.4 Getting Started

3.3 Establishing System Security

3.4.7 SERVER_START_port #

To install AcuConnect on a UNIX server

6 Managing the System - 6.3.3 Connection Refused - Windows Diagnostics

A.2 "acuconnect" Command Formats

1.3.1 AcuConnect Configuration Files

server configuration variables:

3.4 Creating a Server Configuration File

server.cfg:

1.3.1 AcuConnect Configuration Files

SERVER_IP:

3.4 Creating a Server Configuration File

3.4.4 SERVER_IP

server_MAP_FILE:

server_MAP_FILE

2.5 International Character Handling

SERVER_NAME:

3.4.5 SERVER_NAME

3.4 Creating a Server Configuration File

SERVER_PORT:

3.4.6 SERVER_PORT

3.4 Creating a Server Configuration File

SERVER_PORT

SERVER_START_:

3.4.7 SERVER_START_port #

3.4 Creating a Server Configuration File

smart client:

6.1.1 Distribution Considerations

software installation:

4.2 Installing the ACUCOBOL-GT Runtime

software installation: client:

4.2 Installing the ACUCOBOL-GT Runtime

special characters:

2.5 International Character Handling

stand-alone runtime:

3.2.2 Using AcuConnect as a Stand-Alone Runtime

standard configuration file variables:

4.3 Creating a Client Configuration File

starting AcuConnect:

5.2 Starting AcuConnect on the Server

5.2.1 UNIX Startup

5.2.2 Windows NT and Windows 2000 Startup

A.2 "acuconnect" Command Formats

starting AcuConnect:-start options:

A.2 "acuconnect" Command Formats

starting AcuConnect:UNIX start-up:

5.2.1 UNIX Startup

starting AcuConnect:Windows NT/2000 start-up:

5.2.2 Windows NT and Windows 2000 Startup

starting/stopping services, problems with:

6.3.6 Problems Starting and Stopping Services

start-up failure:

6.3.5 AcuConnect Fails to Start

stop run command:

2.4 Memory and Environment Issues

stopping AcuConnect:

To stop AcuConnect on a UNIX server

A.2 "acuconnect" Command Formats

To stop AcuConnect on a Windows NT or Windows 2000 server

synchronous CALLs:

2.3 Synchronous or Asynchronous Execution?

1.3.2 Process Flow

system security:

3.5 Installing Server Programs

3.3 Establishing System Security

terminating the remote application:

2.2.1 Terminating the Remote Application

TEXT configuration variable:

TEXT

theory of operation:

1.3 Theory

thin client:

6.1.1 Distribution Considerations

trace file:

A.2 "acuconnect" Command Formats

troubleshooting:

6.3.4 Invalid Password

6.3.3 Connection Refused

6.3.5 AcuConnect Fails to Start

6.3.2 Unexpected User Name

6.3.6 Problems Starting and Stopping Services

troubleshooting:AcuConnect fails to start:

6.3.5 AcuConnect Fails to Start

troubleshooting:connection refused:

6.3.3 Connection Refused

troubleshooting:invalid password:

6.3.4 Invalid Password

troubleshooting:problems starting/stopping services:

6.3.6 Problems Starting and Stopping Services

troubleshooting:unexpected user name:

6.3.2 Unexpected User Name

unexpected user name on server:

6.3.2 Unexpected User Name

UNIX:

To relink the server runtime under UNIX

UNIX:relinking the runtime:

To relink the server runtime under UNIX

USER environment variable:

3.3.2 Access Records

To add an access record

user ID under MPE/iX:

Running AcuConnect on HP MPE/iX systems

user license:

To start AcuConnect on unrestricted UNIX sites

To start AcuConnect on restricted UNIX sites

user license:restricted:

To start AcuConnect on restricted UNIX sites

user license:unrestricted:

To start AcuConnect on unrestricted UNIX sites

USERNAME:

3.3.2 Access Records

validating service requesters:

3.6 AcuConnect Connection Logic

version:

A.2 "acuconnect" Command Formats

version:displaying acuconnect release version:

A.2 "acuconnect" Command Formats

wildcards in access records:

3.3.2 Access Records

Windows NT/2000 services:

5.2.2 Windows NT and Windows 2000 Startup

Windows services, deleting them:

To stop AcuConnect on a Windows NT or Windows 2000 server

Windows services, stopping them:

5.4 Stopping AcuConnect

5.3 Executing Programs on the Client

Windows, relinking the client runtime:

To relink the client runtime under Windows

Windows, relinking the server runtime:

To relink the server runtime under Windows NT or Windows 2000