I was going to write what Gordon said, but he beat me to it. :-)
One point to add -
I did not use to have real CTCs that connected an LPAR
to *itself* (until I did my big multi-lpar CTC study about
a year ago), but I *did* have 2 VM nodes in different LPARs.
By attaching one local end of the CTC to the virtual machine
hosting the second-level VM (in System-B), I basically created
a linear network like this:
Node B ------- Node A---------Node X
(1st level) (1st level) (2nd level)
Node X accessed my 1st level SFS (in Node B)
via Node A, with no problems whatsoever.
It felt a bit funny sending data on a two-way
round trip to Node A, just to get it into the
2nd-level VM, but it was still as fast as ever. :-)
Note that the ACTIVATE ISLINK commands were done in
nodes X and A, nothing at all was done in B. If you
already have such a CTC, the whole setup is about
a minute! (One ATTACH to give a CTC address to the
2nd level host machine, and two ACTIVATE commands).
Shimon
Quoting "Wolfe, Gordon W" <[EMAIL PROTECTED]>:
> A great way to do this that takes a little setup is to do the following:
>
> Set up a real channel-to-channel on your system with two addresses that talk
> to each other on the same LPAR. A virtual channel-to-channel will not work
> with a first-level system.
>
> DEDICATE or ATTACH one end of the CTC to your second-level system.
>
> Start up an ISFC connection between first and second level over the CTC.
> This requires only two CP commands, One command on each system.
>
> Set up the first level shared file pool server as a remote filepool.
>
> Then you can trade files back and forth using this filepool.
>
> I've been doing this for years and it works great!
>
