Re: STRPASTHR sessions via AnyNet timeouts (CPF8907)

i would make sure the controller description timers on both systems are
set with values for WAN, not the default LAN timers.
This is a set of values i've used for wan over internet (several years ago)
LAN frame retry                  LANFRMRTY   30

LAN connection retry                        LANCNNRTY     30

LAN response timer                       LANRSPTMR   40

LAN connection timer                       LANCNNTMR   250

LAN acknowledgement timer                  LANACKTMR   3

LAN inactivity timer                       LANINACTMR  255

LAN acknowledgement frequency                LANACKFRQ   1

LAN max outstanding frames                LANMAXOUT   3
jim

----- Original Message ----- 
From: "Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Saturday, December 06, 2003 7:09 PM
Subject: Re: STRPASTHR sessions via AnyNet timeouts (CPF8907)


> Hi, Neil:
>
> Try checking what is their default for TCP "keep alive" ...
>
> Prompt the CHGNETA command on their system; the first parameter
> is TCPKEEPALV ... you might need to increase this value... (but I am
> not sure how this may or may not "interact" with AnyNet...)
>
> Hope that might help? (no guarantees, though)...
>
> Mark
>
> ----- Original Message -----
> From: "Neil Palmer" <neilp@xxxxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Saturday, December 06, 2003 10:27 AM
> Subject: STRPASTHR sessions via AnyNet timeouts (CPF8907)
>
>
> > We have a few customers with Internet connections that have allowed only
> > port 397 for AnyNet to come in to their iSeries, and only from the
> > specific IP address of our system.  We therefore have to use STRPASTHR
to
> > get an interactive session on their system, and SNADS also runs via
> > AnyNet.  We have no problem with SNADS - files are sent without problem,
> > but the interactive sessions seem to constantly "timeout" after several
> > minutes and the session is ended (with a CPF8907 at the originating
> > system).  Has anyone found a way to prevent this timeout problem with
> > STRPASTHR via AnyNet?  I have used the default MODE(BLANK) and also
> > MODE(#INTER) with no difference.  I'm wondering if there are some
specific
> > settings on a mode description that might help, or some other way of
> > solving this.  At one customer site we had to resort to opening a
specific
> > port for TELNET - and the timeout problem disappeared.  We would however
> > prefer to use just port 397 for AnyNet if we can solve this annoying
> > timeout problem.
> >
> > Neil Palmer      DPS Data Processing Services Canada Ltd.