Logon reconnect doesn't usually work if you're connected with TCP/IP and
TN3270.
That's just a bug that IBM can't be bothered fixing.
I don't consider myself an IBM apologist, but with respect to Mr. Woren, I
don't believe it's an IBM problem.
This problem is simple to recreate, provided
PROTECTED]
Sent: Friday, June 10, 2005 9:49 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Kill a TSO session to Logon (Without 2nd Username)
Logon reconnect doesn't usually work if you're connected with TCP/IP and
TN3270.
That's just a bug that IBM can't be bothered fixing.
I don't consider myself
http://bama.ua.edu/cgi-bin/wa?A2=ind0009L=ibm-mainP=R15338I=1
http://gsf-soft.com/Products/IKJEFLN2.shtml
Best Regards,
Sam Knutson, GEICO
Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office)
behavior?
Peter
-Original Message-
From: Knutson, Sam [mailto:[EMAIL PROTECTED]
Sent: Friday, June 10, 2005 10:06 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Kill a TSO session to Logon (Without 2nd Username)
http://bama.ua.edu/cgi-bin/wa?A2=ind0009L=ibm-mainP=R15338I=1
http://gsf
In [EMAIL PROTECTED], on
06/10/2005
at 08:50 AM, Kinney, Kevin [EMAIL PROTECTED] said:
The mainframe (and by extension, IBM) couldn't know this since IP
is stateless.
IP is stateless but TCP is not.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
[EMAIL PROTECTED] wrote:
There is a RECONNECT parameter to the LOGON command... Maybe this
would be more suitable to your need than killing the session.
Logon reconnect doesn't usually work if you're connected with TCP/IP and
TN3270.
--
Ulrich Boche
SVA GmbH, Germany
IBM Premier Business
On Thu, Jun 09, 2005 at 08:05:01PM +0200, Ulrich Boche ([EMAIL PROTECTED])
wrote:
Logon reconnect doesn't usually work if you're connected with TCP/IP and
TN3270.
That's just a bug that IBM can't be bothered fixing. There are closed
APARs on this topic telling you to use some IBM session
7 matches
Mail list logo
