> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of McKown, John
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List
> > [mailto:[email protected]] On Behalf Of Veilleux, Jon L
> > Sent: Friday, December 09, 2011 2:01 PM
> > To: [email protected]
> > Subject: Re: TSO on z/OS 1.12 with LOGONHERE and multisystem logon
> >
> > I'm not sure why it would cause an issue. We have had it on for over
a
> > year and I have logged on to multiple systems in a sysplex many
times.
>
> I couldn't think of any reason it would be a problem. But I just was
too anxious to wait to see on the
> 18th. I wanted to test this weekend, but did not get ready in time to
put in the request. And, around
> here, you get "dinged" if you do something without a request. And you
also get "dinged" if you put in
> a request to test something, and then don't do it. So it's difficult
to get permission to "test, if
> I'm ready, but not test if I'm not ready". And doing a test which
"fails" also gets a "ding". FVSO
> "fail". Because if you don't get a failure when you want one, your
test failed to fail, which is a
> failure? I get so confused some times.
Sounds like that old song title, "Forgot to remember to forget". :-)
We've had LOGONHERE enabled since we first discovered it in z/OS 1.11.
I routinely log on to TSO on all three images in our sysplex. Indeed,
with RECONNECT "permanently" selected on the logon panel, if my emulator
window "hiccups" and blows my connection away, I can reconnect to tn3270
(gets a different terminal ID), then logon and get my TSO session
"restored" like I had never left.
-jc-
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
