> ODBA programs must execute on the same MVS image (LPAR) as > the IMS system(s). Since GSAM databases are allocated by the dependent > region (local), not by IMS subsystem, GSAM databases are not allowed for ODBA. ODBA is just another form of IMS region (perhaps we should call it an IMS "independent" region). The commit co-ordinator is MVS RRS. But within IMS it runs as another IMS PST. ODBA, therefore, must be in the same MVS as IMS.
> We have DB2 on one machine and IMS on other machine. > Can we still use ODBA? Not from DB2 stored procs. The DB2 subsystem would need to be on the same MVS. IMS connect - the TCP/IP to IMS DC option can run anywhere in the MVS sysplex, since it uses MVS XCF to connect to IMS. That is the most likely route that Linux for S/390 or zSeries folks would use to access IMS. Comes into IMS through an OTMA TPIPE and runs a transaction in an IMS MPR, IFP or MD-BMP to access the IMS database through normal DL/I. That is supported by the WebSphere/JAVA CCF (common connector framework). The Linux hackers can use a raw socket program and a specialised exit in IMS Connect to do their own thing. For IMS specific questions folks might want to sign up to [EMAIL PROTECTED] by posting the usual arcane incantations (subscribe IMS-L forename surname) to mailto:[EMAIL PROTECTED]. Regards, Dougie Lawson -- ITS Technical Support Enterprise/ASSIST IMS, DB2 & Linux
