What is the real goal? Cost reduction? The conventional wisdom is that you won't reduce costs.
The application is the data. The supporting software is, well, just that. Trying to replicate data and keep it in sync is an expensive nightmare. Therefore, I would agree with Timothy and keep the database in one place then use data sharing facilities. You could try to invent your own, but why not exploit proven methods? By the way, the term 'open platform' seems to have fallen out of favor a while back. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Fermat Ma Sent: Tuesday, June 23, 2009 5:34 AM To: [email protected] Subject: Re: Any one using JDBC type 4 to access IMS DB?? Hello Timothy, Thanks for replying. Actually, the goal is to migrate an application off to open platform. And the data updated on open platform also needs to be synch back to IMS. Therefore, we were thinking about using JDBC Type 4 driver. With that, there should be no need to develop mainframe programs. Fermat On Tue, Jun 23, 2009 at 2:30 PM, Timothy Sipples <[email protected]> wrote: > It sounds like you have data-intensive applications, including batch and > online. If the goal is to add a Java environment to your application > runtime collection, then you have a couple choices. (And the choices can be > used in combination also.) > > One is that IMS Transaction Manager supports Java programming and has for > nearly 10 years now (since IMS V7), with progressive improvements as Java > has evolved. Java support is a base, standard feature provided with IMS and > z/OS at no additional charge. So if you want to write Java, go write Java. > You don't even have to phone IBM. (The same is true of CICS Transaction > Server and z/OS itself.) Just crack open the documentation and go for it. > It's darn easy, too: just 4 APIs from what I gather. With CICS look for > "JCICS" in your CICS documentation, and for z/OS look for the "JZOS > Cookbook" (Web search will find it) to get started. All this stuff is > standard, base function available at no additional charge. You've already > got it. > > Another is WebSphere Application Server for z/OS. The reason you should > consider WAS z/OS here very strongly (as opposed to WAS running elsewhere) > is that data-intensity you mentioned. You really want to try to avoid > taking trips over the wire for data access if you can avoid it. (Sometimes > you cannot avoid it, but you can certainly avoid it in this case.) Also, > financially you're very likely to do much better this way, at least in any > moderately responsible and competent cost analysis. > > - - - - - > Timothy Sipples > IBM Consulting Enterprise Software Architect > Based in Tokyo, Serving IBM Japan / Asia-Pacific > E-Mail: [email protected] > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
