Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!JHUVM.BITNET!L64A0110 From: L64A0110@JHUVM.BITNET (Jim Jones) Newsgroups: comp.protocols.ibm Subject: VM/Passthru to VTAM host (was Re: (none) ) Message-ID: <9009261526.AA02534@lilac.berkeley.edu> Date: 26 Sep 90 15:16:19 GMT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Jim Jones Organization: The Internet Lines: 32 On Tue, 25 Sep 90 13:55:15 GMT you said: >In article <9009241831.AA26211@lilac.berkeley.edu> William Joyce 914-633-2646 > writes: ... > ... VSE/VTAM supports Bisync communications and >:PASSTHRU can emulate a remote 3274 controller, but I don't know if I'm trying >:to do the impossible by attempting to have them communicate over a CTCA. ... >CTCA is one of the most common ways to run Passthru. In systems where >multiple OS's (like VM and MVS) share the CPU, a Virtual Channel to >Channel Adaptor is the preferred connection. ... Except that VM/Passthru won't talk to anything but another VM/Passthru via CTCA (or virtual CTCA). I'd love to hear someone tell me otherwise, but as far as I can tell you are "trying to do the impossible". The IBM response would seem to be: Just run VM/VTAM. A suggestion that I find quite repulsive... :-) >Dan Mercer >Reply-To: mercer@npdiss1.StPaul.NCR.COM (Dan Mercer) >"MAN - the only one word oxymoron in the English Language" -jj BTW -- That's why we have our VM/SP and MVS/SP guest operating systems talking to each other over a bisync link that goes out one 3705 line set, into a modem eliminator, and into another 3705 line set! In all fairness, the two 3705's used to be attached to different CPU's. But now that MVS and VM both run on one CPU under VM/XA, I'd really like to do something more reasonable. Which of course leaves out VM/VTAM. :-)