Timothy, Thanks. That is very good information and I am saving a copy for future use. Unfortunately manglement is dragging it's collective heels in letting us move z/OS 1.4 to production. So any solutions involving z/OS are pretty far out on the radar right now. Our currently contrained hardware is z800, so that knocks out the other solutions. I do anticipate we will upgrade our hardware (and necessarily the OS also) before too awfully long. When we do, I plan to lobby hard for at least a zIIP (zAAP too if I can).
On Thu, 23 Mar 2006 23:58:03 -0700, Timothy Sipples <[EMAIL PROTECTED]> wrote: >Terry Linsley writes: >>Our DDF traffic is 1/3 MS Access, >>1/3 DB2 connect, and 1/3 locally developed java apps. Of the three, MS >>Access causes the most pain hands down. > >Off on a slight tangent here, there are some things you can do to take the >DDF temperature down. I'll list these in order of timeliness to your >current situation -- first what's possible with OS/390 V2R10, then moving >beyond. (As it happens the OS/390 options are reusable and apply to z/OS, >so there's no danger of "throwaway" effort.) > >OS/390 Possibilities: > >1. Put DB2 Connect on Linux on the mainframe. Having a local connection >between DB2 Connect and DB2 (even if it isn't a Hipersocket) should shave >some milliseconds out of each connection, and that'll help DB2 work more >efficiently. Try sending your Microsoft Access and Java clients in via >this DB2 Connect on mainframe Linux and see how that works, too. > >2. Move some/all of your Java applications (particularly the data >intensive ones) up to mainframe Linux. Same principle as #1: proximity has >workload benefits. > >z/OS Possibilities: > >3. Add a Hipersocket between DB2 Connect (mainframe Linux) and DB2. >Requires z/OS 1.2 or higher and z900 or higher. > >4. Evaluate DB2 V8 to see whether you have requests that could benefit >from multi-row fetch/multi-row insert. Microsoft Access might very well be >in that category. Requires z/OS 1.3 or higher and z900 or higher. (Combine >with DB2 Connect for Linux on mainframe.) > >5. Add a zAAP and move the Java applications into the same LPAR as DB2. >(The most proximate solution.) Requires z990, z890, or System z9. Requires >z/OS 1.6 or higher. > >6. Add a zIIP for the remaining inbound traffic arriving from outside the >LPAR. Requires z/OS 1.6 or higher, DB2 V8, and System z9. This option >becomes available later in 2006. > >Hope that helps! > >- - - - - >Timothy F. Sipples >Consulting Enterprise Software Architect, z9/zSeries >IBM Japan, Ltd. >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
