Progress
Client Deployment
Guide


Running PROBUILD on UNIX

Run PROBUILD on UNIX to create a link script from which you will generate a customized executable.

NOTE: Some executables you customize with PROBUILD require that you set the set-userid bit. To set the set-userid bit, log in as root or enter the root password when prompted.

To create a link script on UNIX:

  1. Run PROBUILD by entering the following command on the command line:
  2. $PROLOAD/eucapp/probuild 
    

    The Progress EUC dialog box appears:

  3. In the Install Link Script Into field, type the name of the directory in which PROBUILD will put the link script, and ultimately, the customized executable. Your current directory is the default. If you enter a directory that does not exist, the utility creates it for you.
  4. Choose Continue. The Product List dialog box appears:
  5. The product list contains the products that you are licensed to build. Table A–2 presents all the Progress products you can build on UNIX organized in order of appearance.

    Table A–2: PROBUILD Product List on UNIX
    Product
    Description
    Progress Client
    The standard Progress client executable. The Progress Client includes the Progress 4GL Compiler.
    Default link script name: ldpro
    Default executable name: _progres
    Small Progress Client
    A run-time version of the standard Progress Client executable. The Small Progress Client does not include the Progress 4GL Compiler.
    Default link script name: ldprort
    Default executable name: _progres
    ESQL/C Large Client (Full)
    A full Progress Client executable that contains ESQL-89 application code and includes the SQL compiler. The ESQL/C Large Client processes static and dynamic SQL requests directly.
    Default link script name: ldesqlc
    Default executable name: fullesql
    SQL Preprocessor
    An executable that converts ESQL-89 source files to C source files that you can compile and link into an executable.
    Default link script name: ldsqlcpp
    Default executable name: sqlcpp
    Progress Database Server
    The standard Progress database server executable that provides a client with access to a Progress database.
    Default link script name: ldprosrv
    Default executable name: _mprosrv
    PROSHUT
    A utility executable that lets you stop server and broker processes. PROSHUT also lets you disconnect users before shutting down a database.
    Default link script name: ldprshut
    Default executable name: _mprshut
    Database Utility (PROUTIL)
    A utility executable that lets you perform various database administration operations on a Progress database, such as:
    • Index maintenance
    • Database conversion
    • Database state and usage inquiry
    Default link script name: ldproutl
    Default executable name: _proutil
    Remote DataServer Broker
    A broker executable that provides a client with access to non-Progress database servers. The Remote DataServer Broker starts the appropriate type of database server for a client based on the type of client request.
    Default link script name: ldprobrkr
    Default executable name: _probrkr
    Remote ORACLE DataServer
    A database server executable that provides a client with access to an ORACLE database.
    Default link script name: ldorasrv
    Default executable name: _orasrv
    Open Interface Driver
    A server executable that processes static and dynamic SQL requests for an ESQL/C Small Client.
    Default link script name: ldoidrvr
    Default executable name: _prooidv
    ESQL/C Small Client
    A Progress Client executable that contains ESQL-89 application code and Progress client communications modules that provide access to the Progress Open Interface Driver (OID). The ESQL/C Small Client does not include the SQL compiler, it relies on the OID to process static and dynamic SQL requests.
    Default link script name: ldesqlnet
    Default executable name: esqlnet
    Progress AppServer
    The standard Progress application server executable. The Progress AppServer processes remote procedure requests for a client or another application server.
    Default link script name: ldapsv
    Default executable name: _proapsv
    HLC/ESQL/C Client
    A client executable that accesses Progress through an HLC or ESQL-89 interface.
    Default link script name: ldprol
    Default executable name: _progrsl

  6. Select the product you want to customize from the product list. Use the arrow keys to scroll through the list. Press ENTER to select the product. Press TAB to move to a button, then press ENTER to execute.
  7. NOTE: You can create a link script for only one product at a time. After you create a link script for one product, you can create link scripts for additional products individually.

  8. Choose Continue. The Link Script/Executable Names dialog box appears:
  9. In the Link Script Name field, type a name for the link script or accept the default name.
  10. The link script name is the name of the link script that PROBUILD creates and that you use to generate the customized executable. PROBUILD uses a different default link script name for each type of executable on each supported operating system. For example, ldpro is the default name for the Progress Client link script on UNIX systems.

  11. In the Executable Name field, type a name for the executable or accept the default name.
  12. The executable name is the name of the customized executable. PROBUILD does not generate this executable. PROBUILD inserts the name you specify here into the link script, which you run to generate the executable image. You can change the executable name later by editing the link script directly. PROBUILD uses a different default executable name for each type of executable on each supported operating system. For example, _progres is the default name for the Progress Client executable on UNIX systems.

  13. Choose Continue. The Configurable Elements dialog box appears:
  14. The configurable elements list contains the optional capabilities that you are licensed to build into the currently selected product. Each product has its own combination of appropriate configurable elements. Table A–3 presents all the Progress configurable elements you can build on UNIX organized in order of appearance.

    Table A–3: Configurable Elements on UNIX
    Configurable
    Element

    Purpose
    ORACLE DataServer
    Include in the client executable to access a local ORACLE DataServer.
    TCP/IP Network Protocol
    Include in the executable to provide support for the TCP/IP network protocol.
    HLC Application
    Include in the client executable to provide support for calling C routines from within Progress 4GL code.
    Remote ORACLE DataServer
    Include in the client executable to access a remote ORACLE DataServer.
    Named Pipes
    Include in the executable if you want a Progress application to read from or write to a named pipe.
    Remote DB2/400 DataServer
    Include in the client executable to access a remote DB2/400 DataServer.
    User-defined Sort Routine
    Include in the executable if the collation techniques provided by Progress do not meet your needs.
    DataServer Library
    Include in the client executable to access a local or remote ODBC DataServer.
    No Debugger Comm Modules
    Include in the executable if the executable will not support 4GL debugging capabilities. Debugging capabilities require networking software. This element excludes the dependence on networking.

  15. Select the configurable elements you want to build into the currently selected product. Use the SPACEBAR or the mouse to deselect an item.
  16. Choose Continue.
  17. If you selected a product or configurable element that requires one or more object files that you developed and compiled separately, PROBUILD prompts you to identify these object files in the Object Files dialog box:

    Type in the object filenames, including the file extension required on the operating system, and choose Continue. PROBUILD includes these objects in the link script.

    NOTE: If you are not prepared to list an object file, enter a comment line in the object field. PROBUILD includes the comment line in the link script. You can edit the link script later to replace the comment line with the actual object filename. Use comment characters if you want to run the link script before you replace the comment line. The link script might not run if you use only placeholder text for the comment line.

    PROBUILD creates the specified link script. It also returns to the Product List dialog box where you can create another link script, or choose Return to return to the Progress EUC dialog box.

  18. From the Progress EUC dialog box, you can enter another link script directory or choose Exit to exit PROBUILD.

Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095