Invoking the Command Line Tool in a Local Client Configuration
- Last Updated: May 12, 2026
- 1 minute read
- OpenAccess SDK
- Version 9.0
- Documentation
In a local configuration, you work directly on the configuration file with the command line tool, using the –d configuration_file option:
oacla [-nologo] [-i <script file>] [-o <output file>] [-e <error file>] [ -d configuration_file | -l | -r <host:port> ]
[ -uid <user id> -pwd <password>] [-m <message file>] [-h <help file>] [command]
Example A: Connecting to OpenAccess SDK**
This example opens the configuration file of the OpenAccess SDK Local Client for ODBC and IP SDK. The administrator can now enter any OpenAccess SDK Manager command described in OpenAccess SDK Manager Commands.
C:\Program Files\Progress\DataDirect\oaodbclocal90\admin>oacla -d ..\cfg\oadm.ini
DataDirect OpenAccess SDK Manager Version 9.0.0.0000
Copyright 1995-2025 Progress Software Corporation. All rights reserved.
oacla> sl
| Name | Host | Status | Description |
| OpenAccessSDK900_C | BELG-GEERTP7 | inactive | Service for C/C++ |
| OpenAccessSDK900_Java | BELG-GEERTP7 | inactive | Service for Java |
| OpenAccessSDK810_NET | BELG-GEERTP7 | inactive | Service for .NET |
| OpenAccessSDK900_C_SQL | BELG-GEERTP7 | inactive | Service for C/C++ |
| OpenAccessSDK900_Java_SQL | BELG-GEERTP7 | inactive | Service for Java |