I agree. The keyword there is "OUGHT" . I was timing out, had to logon with
a different ID to cancel my user ID, then logoff and log on again. Reconnect
didn't work. I changed it, now i'm working fine.
Bill
From: Paul Gilmartin <[EMAIL PROTECTED]>
Reply-To: IBM Mainframe Discussion List <[email protected]>
To: [email protected]
Subject: Re: TSO RECONNECT (Was: Interrupting DSLIST)
Date: Mon, 15 Jan 2007 16:02:29 -0700
In a recent note, Bill Wilkie said:
> Date: Mon, 15 Jan 2007 20:40:36 +0000
>
> When I went to Z/OS 1.7, I started timing out. The vendor I have
recommended
> changing the VISTA.INI file to add KeepAliveTime=60. This will simulate
some
> activity to keep it active. Otherwise reconnect doesn't work and you'll
need
> another ID to cancel yourself.
>
That design is just plain wrong. Whatever timer expires making it
impossible to reconnect ought also cancel the session which has
become inaccessible and is only an obstacle to logging in again.
Of course, this is just one of many problems that would be
alleviated if multiple concurrent TSO sessions weren't prohibited.
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
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
_________________________________________________________________
Communicate instantly! Use your Hotmail address to sign into Windows Live
Messenger now. http://get.live.com/messenger/overview
----------------------------------------------------------------------
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
