We did this on a z9. The CTC is just a single piece of fiber from one Escon channel directly into a separate Escon channel. Just long enough to reach, actually inside the box itself. One chp is defined as CTC, the other as CNC.
The hardest part was figuring out the HCD to cross connect the LPARs correctly. Can post that Monday when I get back in the office. Shared DASD, basic sysplex. First implemented on z/OS 1.8, now on 1.12. No real problems seem. But we are a primitive shop, nothing fancy. On Sep 13, 2013 9:34 AM, "Jim Blalock" <[email protected]> wrote: > Hi folks, > > We have a single z10, and would like to split its main partition into > production and developer partitions. Capacity should be ok. We're looking > at all the stuff we need to worry about sharing, like GRS, spool, RACF, > RMM, HSM, catalogs, virtual tape, etc etc. But underneath it all, we > probably need to set up a sysplex. > > Keep in mind that we've never set up a sysplex before or done any real > sharing beyond shared DASD, so there will be dumb questions. > > I think a basic sysplex will be enough, that way we won't need a coupling > facility. We will need a way for them to talk to each other (and probably > with one or two sandbox lpars), so I'm looking into CTCs. The question I > haven't found an answer to is how to use CTCs without an escon or ficon > switch; we have spare channels and I want to do this on the cheap if I can. > > I'm still reading about it, but any insight would be appreciated. Thanks! > > -- > -- Jim Blalock > z/OS Support Manager > CCIT, Clemson University > (864) 656-3680 > > ------------------------------**------------------------------**---------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
