home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 16 Announce
/
16-Announce.zip
/
294720.zip
/
294720.ANN
Wrap
Text File
|
1994-11-09
|
18KB
|
215 lines
DATA BASE : ALET PAGE: 1
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DATE 941108
CATEGORY LS00, WS00, WS20, WS50, AS20, AS23, GI99
TITLE PREVIEW: IBM IMS CLIENT SERVER OBJECT MANAGER FOR OS/2
ABSTRACT The IMS Client Server Object Manager (IMS CSOM) for OS/2 (R),
middleware that enables object-oriented client access to enterprise
data, combines the benefits of the workstation as a development
environment with access to critical data at the mainframe. IMS CSOM
is an addition to the IMS family.
IMS CSOM middleware consists of three tiers: a client tier, a
server tier, and a datastore tier. It enables an OS/2 client to
access and update mission-critical host IMS/ESA (R) Database Manager
(IMS DB) and IBM DATABASE 2 (TM) for MVS/ESA (TM) (DB2 (R)) data
using an object-oriented API. Client application programs use the
common interface of the Object Management Group's Persistent Object
Service to manipulate objects. This interface features a set of
classes and methods that the client application program uses and
builds upon. Client application programmers can develop applications
with little or no knowledge of the host environment.
On the workstation server tier, IMS CSOM maintains and manages
a recoverable database of persistent objects that can be accessed and
changed by clients of the server. IMS CSOM requests data objects
from the IMS/ESA Transaction Manager (IMS) hosts and routes the
objects to the server on demand. By off-loading information from the
host to local databases, IMS CSOM enables multiple clients to access
and update local data without repeated host requests.
PLANNED AVAILABILITY DATE: Will be announced at a later date.
The product will be made available to a selected set of customers on
December 30, 1994.
(R) Registered trademark of International Business Machines
Corporation
(TM) Trademark of International Business Machines Corporation
(1) OMG is a non-profit, international corporation dedicated to
establishing industry guidelines and object-management
specifications that provide a common framework for distributed
application development.
** Product or company name is a trademark or registered trademark of
its respective holder.
IN BRIEF . . .
IMS CLIENT SERVER OBJECT MANAGER FOR OS/2:
o Stages data from IMS DB and DB2 databases into a local server
cache with update capability
o Provides an object-oriented interface for all languages that
support IBM's System Object Model (SOM)
o Enables users to define data objects that map to IMS DB and DB2
data structures
o Uses the Object Management Group (OMG (1)) Persistent Object
interface to manipulate data objects and is compatible with other
OMG persistent service providers
o Enables multiple client applications to access data on the local
DATA BASE : ALET PAGE: 2
server without repeated host requests
o Supports a network of multiple client and server workstations
running OS/2
o Supports TCP/IP, NetBIOS, and NetWare** IPX/SPX for communication
between the client and local server
o Works with host datastore applications to manage and protect the
host data
PRODNO To be announced in the General Availability announcement.
OVERVIEW DESCRIPTION
Today, workstations provide a superior environment for
developing applications. Customers can use workstation application
development tools and enhance data presentation by using GUIs and
multimedia. More and more, these application developers are turning
to object-oriented technology to help lower the total cost of
computing by improving quality and productivity, and by reducing
development time and maintenance costs. However, the
mission-critical data for the enterprise still exists on the
mainframe. There is a considerable investment in this data and the
applications that maintain it and customers depend on the security
and integrity of the host environment. So the question becomes: How
can you take advantage of the flexibility of object-oriented
workstation application development while preserving the investment
in mainframe enterprise data and applications? IMS Client Server
Object Manager (IMS CSOM) is the answer.
IMS CSOM provides client object access to mission-critical IMS
Database Manager (IMS DB) and DB2 data. It uses a three-tier
architecture consisting of host, server, and client components to
stage the data and distribute processing.
IMS CSOM enables users to define data objects that map to IMS
DB and DB2 data structures. Data is staged from IMS DB and DB2
databases into a local server cache with update capability enabling
multiple client applications to access data on the local server
without repeated host requests. Using IMS CSOM, customers could
create, for example, a travel package application that combines data
from host databases managed by IMS DB and DB2 with graphical imagery
stored on the client workstation. IMS CSOM can be used to simplify
the development of the application by creating a data object
comprised of IMS DB and DB2 data. IMS CSOM stores the data object on
the server. A client application can retrieve the data object and
present it to the user along with graphical imagery. As users make
changes to the object data IMS CSOM can pass those changes up to the
host databases.
IMS CSOM uses IBM's System Object Model (SOM) to implement an
OMG Persistent Object interface to manipulate objects. This
interface features a set of classes and methods that the client
application program uses and builds upon. Client applications can be
written in any language that supports SOM and Distributed System
Object Model (DSOM). DSOM allows applications to access objects that
are not resident in the executing address space. A client
application running in a SOM/DSOM environment can request
information. If that information is not resident in the client
address space, a DSOM request is passed to the server. If the server
DATA BASE : ALET PAGE: 3
has the requested information, it is passed to the client. If not,
the server uses Advanced Program-to-Program Communications (APPC) to
send the request to an IMS Transaction Manager (IMS TM) host, and the
information is retrieved and routed to the server. The server then
satisfies the client request following DSOM protocols. IMS CSOM
supports TCP/IP, NetBIOS, and NetWare IPX/SPX for communication
between the client and server.
IMS CSOM provides value by protecting your investment in and
maintaining the integrity of IMS DB and DB2 data and applications.
It enables access to critical IMS DB and DB2 data while allowing you
to explore new technologies and it enables client application
programmers to develop applications with little or no knowledge of
the host environment. IMS CSOM isolates client application
programmers from the complexities of communication protocols between
clients and servers and decreases host processing time by off-loading
processing to the workstation environment.
HARDWARE REQUIREMENTS
HOST REQUIREMENTS: The host component of IMS CSOM runs on all
processors capable of running IMS/ESA Transaction Manager and
Database Manager Version 4 or later.
SERVER REQUIREMENTS: The server component of CSOM runs on a high-end
486 processor, such as a 486 DX2 processor running at 66MHz. It
requires a minimum of 8MB of memory (RAM); 32MB of memory is
recommended.
CLIENT REQUIREMENTS: The client component of CSOM runs on a 386
processor; a 486 DX2 processor running at 66MHz is recommended for
optimal performance. It requires a minimum of 8MB of memory (RAM);
16MB of memory is recommended.
SOFTWARE REQUIREMENTS: The following are required at their
equivalent or subsequent levels:
HOST REQUIREMENTS:
o MVS/System Product Version 4.3
o IMS/ESA Transaction Manager and Database Manager Version 4.1
o If you want to access DB2 data, IBM DATABASE 2 Version 2.3
o Virtual Telecommunications Access Method (VTAM (R)) Version 3.3
o One or both of the following languages, as supported by IMS/ESA
Transaction Manager:
- IBM COBOL/370 (TM) and IBM Language Environment (R)/370
- IBM Assembler H or IBM High Level Assembler/MVS
o Resource Access Control Facility (RACF (TM))(TM) Version 1.9.2
SERVER REQUIREMENTS:
o IBM Operating System/2 (R) (OS/2) Version 2.1
o IBM DB2/2 (TM) Version 1.2 in the single-user package
o SOMobjects (TM) Workgroup Enabler Version 2.0, including the DSOM
component
o One of the following communications products:
- IBM Transmission Control Protocol/Internet Protocol (TCP/IP)
Version 1.2.1 for OS/2, modified by the UN34109 Corrective
Service Diskette
- NetWare Client for OS/2 2.1 from IBM
- NetBIOS
-- NetBIOS protocol as included in Network Transport
DATA BASE : ALET PAGE: 4
Services/2 (NTS/2)
-- For network file service, OS/2 LAN Requestor Version 3.0
running under OS/2 LAN Server Version 3.0
o Communications Manager/2 Version 2.1 or later
CLIENT APPLICATION PROGRAM DEVELOPMENT REQUIREMENTS:
o IBM OS/2 2.1
o A C or C++ compiler, such as IBM C/C++ Tools Version 2.0 in
conjunction with:
- IBM Developer's Toolkit Version 2.0 or later
- IBM Workframe/2 Version 1.1 or later (optional)
CLIENT APPLICATION PROGRAM RUNTIME ENVIRONMENT REQUIREMENTS:
o IBM OS/2 2.1
o SOMobjects Workgroup Enabler Version 2.0, including the DSOM
component
o One of the following communications products:
- IBM TCP/IP Version 1.2.1 for OS/2, modified by the UN34109
Corrective Service Diskette
- NetWare Client for OS/2 2.1 from IBM
- NetBIOS:
-- NetBIOS protocol as included in NTS/2
o For network file service, OS/2 LAN Requestor Version 3.0 running
under OS/2 LAN Server Version 3.0
DYNAMIC DATA OBJECT (DDO) DEFINITION FACILITY REQUIREMENTS:
o IBM OS/2 2.1
o SOMobjects Developer Toolkit Version 2.0
o If you want to develop OS/2-specific data types, a C or C++
compiler, such as IBM C/C++ Tools Version 2.0 in conjunction
with:
- IBM Developer's Toolkit Version 2.0, or later
- IBM Workframe/2 Version 1.1, or later, (optional)
Ordering information, terms and conditions, and charges will be
announced at a later date.
- - - E N D O F P R I N T O U T - - -