Browse Prior Art Database

Generic Program for Starting Executables

IP.com Disclosure Number: IPCOM000121001D
Original Publication Date: 1991-Jul-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 53K

Publishing Venue

IBM

Related People

Cox, D: AUTHOR [+3]

Abstract

This article describes a method for OS/2* Office to start programs without requiring an EXE file for the OS/2 Loader to load and start.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 63% of the total text.

Generic Program for Starting Executables

      This article describes a method for OS/2* Office to start
programs without requiring an EXE file for the OS/2 Loader to load
and start.

      Code residing in a DLL (Dynalink Library) cannot be started
without an executable (.EXE) program to invoke it. That program may
be nothing more than a "main", and perhaps the processing of the
command line parameters.  Reusing a single executable to start
different functions would reduce programming time and also save on
DASD resource requirements (fewer .EXE files required).

      OS/2 Office solved this problem by writing a generic executable
program to facilitate starting a procedure within a Dynalink library
(DLL). This program processes the command line parameters passed to
it to determine what DLL to load and what function within that DLL to
execute.  The program is responsible for loading the requested DLL,
obtaining the address to the procedure name requested, and calling
the procedure, passing any additional parameters which were on the
command line.

      By reusing this generic program to start procedures, OS/2
Office reduces the number of required executables, which also saves
on DASD requirements.

      Additionally, specific executable programs do not need to be
written for each task which is to run as a separate process.
Procedure code is written without a "main" and can, therefore, be
started by the generic program or by any other program wishing...