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: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
