On a similar note.  We are able to use ODBC to access Image/SQL, but why
not use ODBC from the HP to access relational databases on other
platforms?
 
 
Eric Schubert ([log in to unmask]) wrote:
:  Many vendors have written gateways to Image (Oracle, Image/SQL, ODBC) all
: take the viewpoint of the "outside looking in" to Image.  How about turning
: the tables and create an IMAGE-API to RDBMS at the intrinsic layer?
 
:  What I have in mind is the typical "intercept" technique of replacing
: DBOPEN, DBCLOSE, DBPUT, DBUPDATE, DBINFO, DBGET...etc, with equivalent calls
: to [for example] Oracle SQL over a network.
 
:  The approach to "make a less featured DBMS", such as Image, behave as a
: full featured RDBMS is logically impossible - but the approach to make a
: full featured RDBMS behave like Image would be much simpler.
 
:  [IMAGE intrinsic layer] <--> [network API/SQL] <--> [Oracle RDBMS]
 
: So, in this layout, Legacy applications on the 3000 actually think they are
: making IMAGE calls, but in reality, are accessing Oracle across the network.
 
: Since Oracle has kerberos V network security modules and DCE integration,
: legacy MPE applications could continue to function but we can keep and
: maintain a single copy of data and reap the rewards of RDBMS on the network
: for global enterprise-wide data access.
 
: Has anyone given thought to this idea or anyone doing it?  What this model
: turns out to be is the reverse of the Quest IMAGE NETBASE client for Sun
: Solaris.  It would become an MPE "Image Client" for Oracle RDBMS.
 
--
Kevin D. Joseph              University Computing Services
Database Administrator       University of Maryland Baltimore County
voice: (410) 455-3981        Library Room 005
fax:   (410) 455-1069        1000 Hilltop Circle
email: [log in to unmask]      Baltimore MD, 21250