On Tue, 6 Jul 2010 19:10:45 -0500, Mark Zelden <[email protected]> wrote:
>... Even with a single engine you can create more than one >CF LPAR and share that engine. As long as you weren't using it for true >data sharing (like DB2) you would be just fine (especially with the speed of z9 >and z10 engines). I've worked in quite a few sites set up with "priceplex" >aka "shamplex" that worked quite well with multiple CF LPARs sharing engines. > >Of course the standard YMMV disclaimer applies. Our Mileage Varied. Be mindful of the DYNDISP setting CF LPARs and where your ISGLOCK (GRS Star) structure resides. Sharing between a sandbox and production should be OK - we set DYNDISP OFF and simply weight the LPARs appropriately. We had two production CF's sharing an ICF engine and were forced to set DYNDISP ON, or both complexes suffered. ISGLOCK for our 9- way suffered until we moved it to another CF with DYNDISP OFF. Response times went from milliseconds to microseconds, and far fewer SYNCH to ASYNCH conversions. ISGLOCK for the 2-way was impacted until we could get another ICF engine, dedicate engines, and turn DYDISP OFF. BTW, no DB2/IMS data sharing here. Only XCF signaling, GRS, ECS, and Operlog for one JesPlex are active. FWIW, Art Gutowski Ford Motor Company ---------------------------------------------------------------------- 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
