Browse Prior Art Database

OS/2 Database Manager Import Export Utility Message Handling in Client Server Environment

IP.com Disclosure Number: IPCOM000103598D
Original Publication Date: 1993-Jan-01
Included in the Prior Art Database: 2005-Mar-18
Document File: 8 page(s) / 352K

Publishing Venue

IBM

Related People

Alexander, VL: AUTHOR [+2]

Abstract

Client/server computing introduces special problems related to message processing. In particular, it is desirable that messages be composed in both the code page and language of the client application. This article describes methods which address these concerns for the Import/Export Utilities of the OS/2* Database Manager, with allowances for the following variances: - message log type: file versus table - message log location: client versus server - utility execution location: client versus remote procedure at server.

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

OS/2 Database Manager Import Export Utility Message Handling in Client Server Environment

       Client/server computing introduces special problems
related to message processing.  In particular, it is desirable that
messages be composed in both the code page and language of the client
application.  This article describes methods which address these
concerns for the Import/Export Utilities of the OS/2* Database
Manager, with allowances for the following variances:
- message log type: file versus table
- message log location: client versus server
- utility execution location: client versus remote procedure at
server.

      OS/2 Database Manager (DBM), which is part of the IBM OS/2
Extended Services program product,  provides utilities to export data
from a database and import data into a database - these utilities are
henceforth called the DBM Import/Export utilities.  The DBM
Import/Export utilities, together with a database server, produce
error messages and return them to the invoking application.  In most
cases, it is desired that these messages conform to the language and
code page environment of the invoking application.

      In a standalone database environment, the application, DBM
Import/Export utilities and Database Manager typically share
identical code page and language environments.  Regardless of where
an error message originates (utility or server), the message will be
in the common language and code page of the system environment.

      In the emerging dominant client/server computing paradigm, the
assumption of common language and code page environment is not
reliable.  Rather, the client application can use one language and
code page, the database server another, and the DBM Import/Export
utilities can execute in either the client or server environment
transparent to the application.  Regardless, the application's
expectation of messages is the same - that they arrive in its
language and code page.

      This article presents a design whereby the OS/2 Database
Manager Import/Export utilities can execute in a client/server
configuration and yet meet the application requirement that messages
be composed in the application language and code page.  The database
server can be either an OS/2 Database Manager or a host-based member
of the IBM SAA* relational database family (DB2*, SQL/DS*, or
SQL/400*).  Execution of the DBM Import/Export utilities at both
client and server locations is considered.  The proposal adds
flexibility to the solution in that the message log (e.g.,
repository) is allowed to be either a flat file or a database table.
PROPOSAL DESCRIPTION
Assumptions

      This proposal does not describe a total design for enabling DBM
Import/Export utilities operation in a client/server environment, but
rather addresses one of the concerns of this larger problem: message
handling.

      This proposal utilizes the message services of the OS/2
Database Manager; this function is...