We have something similar.
We have a CICSPlex that spans 2 Sysplexes. There are TOR's on SYSPLEX1 (in
GR1) and TOR's on SYSPLEX2 (in GR2). All TOR's on each Sysplex are members
of their local VTAMGR. The TOR's on SYSPLEX1 only have MRO/XM and MRO/XCF
connections to their "local" AOR's (no problems connecting). The TOR's on
SYSPLEX2 however have MRO/XM and MRO/XCF connections to the "local" AOR's AND
LU6.2 connections to some of the AOR's on SYSPLEX1 (similar problems as yours).
We found if we bounce the TOR's on SYSPLEX2, they will not reconnect to the
AOR's on SYSPLEX1, but if we bounce the AOR's on SYSPLEX1, everything
reconnects fine. Since these 2 sysplexes have different maintenance windows with
different SLA's, this was a problem. We discovered as you did that the VTAMGR
is passed as part of the bind and the VTAMGR name from SYSPLEX2 is unknown on
SYSPLEX1 (as should be expected).
To get around this we did a couple things:
1. Setup automation to send CEMT S ACQ commands to the target AOR's on
SYSPLEX1 after the TOR's on SYSPLEX2 get their "control given".
2. Setup a new PLTSI program for the AOR's on SYSPLEX1 that checks and
attempts to reacquire these connections hourly if they are not connected.
Hope This Helps,