|
The only way I'm aware of to copy data from IMS into Rdb/VMS is to
use VAXlink, but it works in batch mode only. You can select certain
tables, rows from a menudriven interface on the VAX and send this
request to the IBM side where it will processed in batch mode. The
result will be send on the users request on the VAX into a Rdb/VMS
database.
Georg
|
|
Another possibility might be a piece of software that provides on-line access
to IMS under CICS from the VAX/VMS.
This is (just becoming) an asset and is (to my knowledge) written and
supported by MATHIAS SCHMITZ @HBF, called IMH.
A local customer uses this s/w and is quite happy with it!
Cheers,
Andreas
|
| Seems like to me you could/should/would use SQL services to access the
VAX resident database. Then use the same program (or a separate
program) to to access the IMS databases and extract the record(s) and
place them in the Rdb tables and/or global memory/sections for the
Mac based application to retrieve. You didn't mention how you planned
to enter the IBM host, eg CICS, IMS/DC, or VTAM. This is important to
know to determine what API's and LU protocols can be used.
Further, it seems you would like a VIDA for IMS but this doesn't seem
to make much sense due to IMS's structure. Sorry, but this sounds like
customer code on the VAX to talk to the Mac and the IMS database no
matter what entry point or IBM protocol you select.
-- gerry
|
| We don't have, and don't plan to build, a "VIDA" for IMS product.
After all, IBM has been struggling for years to build a SQL interface
to IMS. If they can't do it, I doubt we would be particularly more
proficient.
Ingres claims to have a read-only gateway to IMS. I'm not sure how
it works, but they claim to be able to support VAX-based SQL requests
to IMS. I don't believe that they have the ability to access IMS
from the Macintosh.
Sybase provides a client/server programming environment allowing
MAC-based applications to access a Sybase Server. As far as I know,
they don't have the ability to access IMS.
As for the IMH product. I checked with Mathias Schmitz to get some
more information. IMH does not provide a gateway to IMS databases.
IMH (IMS Message Handler) is a program-to-program application
interface, like the APPC/LU6.2 PI, 3270 DSPI or FPI. IMS APPC
communications requires the use of a proprietary communications protocol,
called SLU-P. FPI is our programming interface which supports SLU-P.
IMH is written using the FLASH programming interface (FPI), providing a
transaction monitor environment connecting VAX/VMS applications with
IMS/DC applications. IMH reduces the complexity of VAX to IMS/DC
application communications to the simplicity of communications between
two VAX/VMS applications on the same system.
Note: There's a difference between IMS/DB and IMS/DC. IMS/DB is the
heirarchical database environment. IMS/DC is a message-based
teleprocessing environment, similar to CICS.
SQL/Services could conceivably be used to interface with an IMH
application, but it would definitely not a trivial task. Even if you
did modify the SQL/Services server in Rdb to allow you to call an IMH
application, we still don't have any code which would convert SQL
commands to IMS DL/I commands. So I'm not convinced that IMH would be
the right answer for this situation. You might want to investigate
third party connectivity products. Perhaps TechGnosis's SequeLink
provides access to IMS from the MAC. You wouldn't route all commands
through the VAX server, but at least you could get the required
connections. SequeLink can also be used to access Rdb.
Regards,
Anne
|