On Wed, 22 Jan 2014 22:50:58 -0500, Tony Harminc wrote:
>
>> What makes the difference? We'd like to spare the overhead of running
>> VTAM on a separate (VM, in this case) host.
>
>Ah - I suspect you mean that you are using virtual local 3270s provided by VM.
>
>Regardless, you can't connect to TSO without VTAM (or conceivably
>TCAM!); there is no direct TCP/IP to TSO connection. You need VTAM and
>TCAS in the loop, unless IBM has slipped a big change past me
>recently.
>
OK, then, TCP/IP to z/OS vs. TCP/IP to VM, then VTAM to z/OS. I'm pretty
sure that in the former case TCP/IP goes directly to z/OS. Well, perhaps
there's an OSA in there somewhere (I can't bear to think).
But the victim did some research and discovered his own solution:
Now after some reading and testing, I've found a way to get TSO/E
to keep my natively connected session active when I need to shutdown
my laptop which involves issuing 2 VTAM commands as follows (which
can easily be done in a REXX exec).
D NET,TSOUSER,ID=iiiiiii
V NET,TERM,LU1=lllll,TYPE=UNCOND
where iiiiiii is my userid and,
lllll is the ACB name that is output by the first command.
[ ... screen shots redacted ... ]
After issuing these commands, I was then able to reconnect back to
my T790575 session.
I understand none of this, least of all why that setup isn't the default,
which is why I referred the question to IBM-MAIN.
"natively connected"?
Thanks,
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
