Subject: TCP/IP Disconnected Sessions with Rumba -- MIDRANGE-L

Richard,   

Under our Chgtelna the inactivity timeout is *none.  I believe that is how it 
was shipped to us, because I do not remember changing that parameter.  And our 
QINACTITV  is set at 0.   As we are now really using straight Client Access, 
does this make for problems?     
<snip>

David,

I'm postive the sessions were set up for straight 
TCP/IP  connections.  However, and there always is a however, or a but - 
Some could have been set up for TCP via Anynet.   And the version, I'll 
have to double check on tomorrow when I get in to the office.   I know we 
renewed it for the 2nd time this summer, (of course, they haven't asked for 
payment yet).    For alot of items, the Rumba product was good.   Less of a 
install hassle, what with all the reboots of the Client Access one.   And 
with the problem pc's I believe it's still the better way to do a fast 
connect.   I have been having difficulty though with  new pc's with Win98 
on them.   I guess there's not going to be a fix for that.     I tried 
different Sysvals for disconnected jobs and ended up creating havoc with 
people who would do a temporary signoff at lunch..   But this was fixed 
this past week.   I'll let you know the version tomorrow

MaryLou Atwell
Interboro School District

- ------------------------------
Date: Thu, 6 Jan 2000 21:22:53 +1300
From: "DAVID BULOG" <d2ba@xtra.co.nz>
Subject: Re: TCP/IP Disconnected Sessions With Rumba
Thanks MaryLou,
I cant help feeling that the Walldata product is flakey in that area.
I have to hardcode in the HLLAPI error handling for disconnected sessions.
My question to you is what version of Rumba ie 95/NT and were they
configured fot TCP/IP.
cheers Dave
- - ----------
 >.us>
  > Hi,
 >
 > Our district used Rumba for quite some time after IBM dropped it from the
 > Client Access line some time ago. It did provide alot easier set up for
 > the printer emulations. I did find though that there was difficulty on a
 > user reconnecting if for whatever reason the session ended. Be it a pc
 > lock up or some sort of disconnect. The only way I was ever able to
fix
 > it was to have the user call me, then I would go thru "wrkcfgsts *dev
Find
 > that pc description, and vary it off, and then vary it back on. After
 > calls to WallData, it was never fixed, and I was quite unhappy with that
 > aspect of the product. Yes, there are parts that are great, however, in
a
 > WAN of 400 pc's, and they might all disconnect at the same time,
 > well.... I have switched back to Client Access for that among other
 > reasons. I'm not totally thrilled with Client Access but, at least
 > I'm supported with it in some ways. I just was never given a reason or
a
 > way to fix it...
 >
 >
  > > Happy New Year all
 > > At work on our big boxs we are using Rumba Office/95 connected via
TCP/IP
 > > as a term emulator.I am having a problem where out of the blue the
Rumba
 > > Session gets disconnected (you get a blank screen-no sign on).Upon
queri
 > > the AS/400 my session still shows varied on.
 > > I was wondering if I can have a list of commands to check any
suggested
 > > parameters on a "Virtual Controller".
 > > Using Netsoft Elite via SNA does not give us any problems only TCP/IP
!!
 > 
 > > +---
 
 
| 

+---
|
i
> 







+---
|ist!
| 







Date: Sun, 9 Jan 2000 21:30:33 -0600
From: rgh@us.ibm.com 
Subject: Re: TCP/IP Disconnected Sessions With Rumba

David,
One reason a display session would disconnect is the inactivity timer.  At
V4R3 and earlier, this is set in CHGTELNA with the inactivity timeout
parameter and the system value QINACTITV.   The lower value is the
inactivity time for the session.  You should set CHGTELNA inactivity to 0
which forces the session inactivity timer to use the system
value(QINACTITV).  In V4R4 the inactivity parameter in CHGTELNA was
eliminated.

MaryLou describes printer emulations that disconnected when the client PC
loses power with active sessions.   The telnet server uses timemark(Set in
CHGTELNA timemark parameter) to see if the client session using that device
is still active.  At V4R3 and before, the timemark was enhanced to allow it
to free up the device when a PC workstation with an active session powered
down.  There are 5769TC1 PTFs at V4R3 and earlier that allow the timemark
to operate faster when a lost session is disconnected.   The cover letter
of the PTF tells how to activate the enhanced timemark.   At V4R4, the
telnet server uses the TCP protocol keep alive logic to determine if a
session is not responding.   This would end the job on a display or printer
device seconds after detecting the host is not responding.   And since it
is TCP, it works on any network environment.

The net is Inactivity time is the amount of time a session can be inactive
before being disconnected or ended.  Inactivity timer only applies to
display sessions.     The timemark is used to determine when a host is no
longer responding that will frrree up the device.  Timemark can be used for
printer or display devices.

Richard G. Hartmann  AS/400 TCP/IP, Telnet Server/Client, Workstation
Gateway, Print Server development
e-mail: rgh@us.ibm.com 

 > Date: Sat, 08 Jan 2000 18:10:48 -0500
 > From: MaryLou Atwell <matwell@interboro.k12.pa.us>
 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---