Judith, If you are referring to Timothy's "DB2 data Sharing", this requires a Parallel Sysplex.
Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Nelson, Judith > Sent: 20 September, 2017 16:15 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: LPAR to LPAR access > > Hi Timothy, > Adding DB2 to the other LPAR sounds more and more the way to go. > > Thanks for your response. > > Judith Nelson > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Timothy Sipples > Sent: Wednesday, September 20, 2017 12:19 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: LPAR to LPAR access > > You can configure your CICS "File Owning Region" (FOR) in CICS TS in the > LPAR with DB2, then access that FOR from any interconnected CICS regions > -- and from interconnected TXSeries, for that matter. The folks in the > CICS-L mailing list likely can provide more details if you need them. > Basically, just put the CICS programs that make DB2 calls in CICS in the > DB2 LPAR, then run whatever non-DB2 CICS programs (that call the DB2- > related CICS > programs) you want in your other CICS LPAR(s). It's classic, tried and > true "TOR/AOR/FOR" separation. (As an aside, nowadays there are also > "Rules Owning Regions," "Channel Owning Regions," "Mobile Owning > Regions," and whatever other "owning" regions you want to have as > architectural best > practices.) > > For batch, CICS's EXCI (external call interface) works via the same > path. > If you're using Java (or mixed Java) batch then you can use the JDBC > Type 4 driver, to pick another example. > > HiperSockets and SMC-D LPAR-to-LPAR connectivities are recommended, if > you can. > > It's best if you do some careful analysis to determine whether avoiding > adding DB2 to this particular LPAR is the right approach. For > "occasional" > DB2 access, it's probably OK. For more intensive DB2 access, DB2 data > sharing is likely going to perform better and be more cost efficient. > > ------------------------------------------------------------------------ > -------------------------------- > Timothy Sipples > IT Architect Executive, Industry Solutions, IBM z Systems, AP/GCG/MEA > E-Mail: sipp...@sg.ibm.com > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > The information contained in this message is confidential, protected > from disclosure and may be legally privileged. If the reader of this > message is not the intended recipient or an employee or agent > responsible for delivering this message to the intended recipient, you > are hereby notified that any disclosure, distribution, copying, or any > action taken or action omitted in reliance on it, is strictly prohibited > and may be unlawful. If you have received this communication in error, > please notify us immediately by replying to this message and destroy the > material in its entirety, whether in electronic or hard copy format. > Thank you. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
