Browse Prior Art Database

Office Initialization Configuration

IP.com Disclosure Number: IPCOM000121613D
Original Publication Date: 1991-Sep-01
Included in the Prior Art Database: 2005-Apr-03
Document File: 2 page(s) / 84K

Publishing Venue

IBM

Related People

Cox, D: AUTHOR [+3]

Abstract

This article describes a method for OS/2* Office to easily tailor and order the specific set of steps which should be run during OS/2 Office Initialization on a specific machine.

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

Office Initialization Configuration

      This article describes a method for OS/2* Office to
easily tailor and order the specific set of steps which should be run
during OS/2 Office Initialization on a specific machine.

      OS/2 Office Initialization is a series of steps run to bring up
and connect to office subsystems. This series of steps could be
different on a machine by machine and user by user basis.  For
instance, Office Initialization on a server machine may consist of
bringing up a Mail Server and/or a Calendar Server.  On a requester
machine, Office Initialization may need to logon to the LAN, run the
Global Initialization transaction and open the Office Window. Any
number of integrated office applications may be started based on the
machine (server or requester) and on what services the user wishes to
have access to. Additionally, since OS/2 Office is a base platform
which external applications will hook in to, any number of
non-integrated applications may also wish to be started by the Office
Initialization process.

      OS/2 Office Initialization provides a way to easily add, change
and delete steps to be run during initialization, to guarantee their
order of start-up during the initialization process, and to start
certain steps only after other steps have completed.

      OS/2 Office Initialization is configured by adding keywords to
a file called the OFFICE.SYS file.  All initialization steps, for
both integrated and non-integrated applications are provided in this
file.  A number of keywords provided in this file give power to
Initialization and make this more than simply a startup.cmd file:
o    OFFICEINIT= This keyword will allow any exported function from
any Dynalink to be loaded and executed as a part of the main Office
Initialization thread. Functions executed in this way are run to
completion before the next OFFICEINIT= keyword is executed.
OFFICEINIT= keywords are executed in the order encountered as the
OFFICE.SYS file is processed, so the order of initialization tasks
can be guaranteed with this keyword. Also, sinc...