Edward Jaffe wrote:
Steve Comstock wrote:
Walt Farrell wrote:
Also, to get RECONNECT working again, have your network system
programmers look at the TN3270 parms. There's one in there (sorry, I
don't know which one) that affects detection of disconnected
terminals that should allow faster detection of your disconnection,
and thus allow RECONNECT to work.
Walt
Tested it out, worked like a champ! Thanks for that
little technique, Walt.
What technique? What was the name of the TN3270 parameter you changed?
What had you coded before? What have you coded now?
Please make this information available/useful to those with enough
patience to claw through and actually read these posts ...
No, no, you snipped too late; it was this part I was
referring to:
"A LOGON RECONNECT would not help you in this case, of course, because
you'd just be back to the same spot in your session, waiting for the
DSLIST to complete. You need a true logoff. Press your SYSREQ key then
LOGOFF or possibly LOGOFF TYPE(UNCOND) or LOGOFF TYPE(FORCE)."
That's what worked like a champ: using the SYSREQ and entering
LOGOFF TYPE(UNCOND) rather than logging on with a different id
and using operator cancel. I found that handy and wasn't aware
of it before; I have not looked in my TN3270 parms.
Kind regards,
--
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
-- to be included in our opt-in list of announcements of
-- new courses and other products and services from The
-- Trainer's Friend, send an email to [EMAIL PROTECTED]
----------------------------------------------------------------------
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
