Re: Problems with Symbol Radios and the AS/400

Patrick,

just a note that the CHGTCPA takes effect immediately.
the chgtelna takes effect next time strtcpsvr *telnet executes (not immed)
let us know what it takes to make this work
jim


----- Original Message -----
From: "Shrader, Patrick" <pshrader@xxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, April 15, 2003 9:35 AM
Subject: RE: Problems with Symbol Radios and the AS/400


> Jim,
>
> I am having my firewall vendor check the timemark packets.
>
> The TCP keep alive was showing 120 minutes, the default. I changed this to
1
> (hopefully to continuously poll the radios).
>
> The session keep alive timeout is set to 0 -- no timeout.
>
> The QDSCJOBITV is set to 60 minutes.
>
> One trouble I've had with the high disconnect values is that when the job
> loses contact with the radio, it takes a long time to automatically end
the
> job, forcing more calls to operations to manually end these jobs.
>
> I changed these values this morning; hopefully no one will call throughout
> the day. I'll know very soon...
>
> Any other hints are greatly appreciated.
>
> Patrick
>
>
>
> -----Original Message-----
> From: Jim Franz [mailto:franz400@xxxxxxxxxxxx]
> Sent: Monday, April 14, 2003 10:18 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Problems with Symbol Radios and the AS/400
>
>
> Patrick - is some of your network equipment not routing the telnet
timemark
> packets. There are some router settings that will "spoof", telling the
> server the the other device is still connected, yet not send the packet to
> the devices.
>
> Check TCP Attributes (CGHTCPA) and following parm
> TCP keep alive . . . . . .
>
> Check the telnet attributes (CHGTELNA) and the following parm Session keep
> alive timeout .
>
> You may need to check the following system value:
> QDSCJOBITV Time interval before disconnected jobs end
> hth
> jim
> ----- Original Message -----
> From: "Shrader, Patrick" <pshrader@xxxxxxxx>
> To: "Midrange Mail List" <MIDRANGE-L@xxxxxxxxxxxx>
> Sent: Monday, April 14, 2003 1:31 PM
> Subject: Problems with Symbol Radios and the AS/400
>
>
> > I hope someone on this list can help me.
> >
> > I have been using Symbol Radios with Spectum24 for over a year on a
> > wide-area-network with frame-relay lines. I recently converted the
> > network from frame-relay to a VPN scenario. All of my network
> > connections are working fine, with the exception of the radios. The
> > radios are using ROI System's Avalanche products.
> >
> > Previously when the radios timed out, the user would simply activate
> > the radio and they would resume their session on the AS/400. Since we
> > have installed the new network connections, the user pulls the trigger
> > on the radio after a timeout and gets a "cannot connect" message. The
> > radio
> appears
> > to have lost connection with the original job on the 400 and is
> > attempting to start a new connection -- to which the AS/400 refuses.
> > When I end the original job the user is given a sign-on screen and can
> > resume their
> normal
> > tasks.
> >
> > The radios work fine until they are set down and allowed to
> > "time-out".
> Then
> > they cannot reconnect to their original job on the AS/400. Ending the
> > job allows the radios to reconnect just fine instantly.
> >
> > The system worked fine with this configuration on the frame-relay.
> > There
> are
> > no abnormal entries in any job log that I can find. I have upgraded
> > the firmware in the symbol radios, and increased the timeout values on
> > the radios, but they have not had any noticeable affects on the
> > system.
> >
> > Thanks in advance,
> > Patrick
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives at
> > http://archive.midrange.com/midrange-l.
> >
> >
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe,
> or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>