Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Office Initialization User Configurable Error Handling

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

Publishing Venue

IBM

Related People

Cox, D: AUTHOR [+3]

Abstract

This article describes a method for OS/2* Office to allow users to configure how to handle error conditions encountered during OS/2 Office Initialization.

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

Office Initialization User Configurable Error Handling

      This article describes a method for OS/2* Office to allow
users to configure how to handle error conditions encountered during
OS/2 Office Initialization.

      OS/2 Office Initialization is a series of steps run to bring up
and connect to Office subsystems.  OS/2 Office Initialization is also
configurable.  Any number of integrated Office applications may be
started, and any number of non-integrated applications may be
configured to start via the Office Initialization process.  Some of
these steps may be considered critical to the user, and some may not.
Therefore, initialization should not necessarily shut down as soon as
any failure is encountered.

      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, as well as parameters which describe specific details of how
Office should run.

      OS/2 Office solved the error handling problem by allowing the
user to configure how to handle errors in the OFFICE.SYS file. When
an error is encountered, Office initialization will always display
the error to the user, and write a log record to the syslog. Then, if
initialization is configured to GO on an error, the next step of
initialization is kicked off.  If Initialization is configured to
STOP on an error, then a message indicating that "Initiali...