Re: CPF8907 on STRPASTHR over AnyNet

[Gord Hutchinson <ghutchinson@xxxxxxxxxxxxxxx>]

On Thu, 8 Jul 2004 12:58:18 -0400, Neil Palmer <NeilP@xxxxxxxxxxx> wrote:

>Unfortunately I can't offer a solution, only a "me too".  We have AnyNet 
>connections configured to many customer systems.  On most it works fine, 
>you can STRPASTHR and leave a session connected for hours.  On a few 
>customer systems the pass-thru session will end after around 5 minutes 
>(whether it's been idle, or even if you are actively keying sometimes). 
>We've found that a TELNET session over the same Internet connection will 
>stay connected.  WIth a few customers the Telnet sessions were ending, but 
>changing either the TCPKEEPALV (on CHGTCPA) or the TIMMRKTIMO (on 
>CHGTELNA) would solve the problem.  It seems that AnyNet STRPASTHR 
>sessions must use some sort of timeout value from somehwere, but I've 
>never had any luck in finding where they get the values from, or how to 
>change them.  If you ever do find a solution, please post it to the list.
>
>...Neil


We had this problem a year or so ago.  I was sent the following and it has
solved the problem for us.

Hope it helps.

Gord



>                           -
>
>
>IBM Support Line
>Technical Document
>
>   Document Number:   18575047
> ____________________________________________________________
> Functional Area:                       Communications-SNA
> SubFunctional Area:               AS/400-to-AS/400 Connectivity
> SubSubFunctional Area:       AnyNet
> ____________________________________________________________
> Product:  Operating System/400 - OS400 COMM BASE/APPN (5769SS1CM)
> Release:  V4R4M0; V4R5M0; V5R1M0
>
> Classification:       Entitled/Advanced
>
> Keywords:            ANYNET
>____________________________________________________________
>Document Title:AnyNet Keep Alive Timers
>Document Description:
> With V4R1 and later OS/400 installed, at the start-up of AnyNet, the
>default values for the AnyNet timers will be overridden if the following
>QUSRSYS data areas were created.
>
>The Keep Alive Timer Value:
>
>CRTDTAARA DTAARA(QUSRSYS/QZPAIKPATM)  TYPE(*CHAR)  LEN(5) +
>VALUE('xxxxx')
>
>where xxxxx is a value from 5 to 65535 seconds.
>
>The Keep Alive Retries Number:
>
>CRTDTAARA DTAARA(QUSRSYS/QZPAIKPANR)  TYPE(*CHAR)  LEN(5) +
>VALUE('xxxxx')
>
>where xxxxx is a value from 1 to 65535
>
>The Keep Alive Retry Timer:
>
>CRTDTAARA DTAARA(QUSRSYS/QZPAIKPART)  TYPE(*CHAR)  LEN(5) +
>VALUE('xxxxx)
>
>where xxxxx is a value from 5 to 65535 seconds.
>
>Notes:
> 
>
>1   If these data areas are not created or if there is a problem using
>
>    them, the default values are used.
>
> 
>
>2   If values below the minimum or above the maximum are specified, the
>
>    minimum or maximum is used.
>
> 
>
>3   If the timers are set to a very small interval and if you have many
>
>    AnyNet users, performance can be negatively impacted.
>
> 
>
>4   OS/400 AnyNet may become sensitive to temporary network problems (5-
>
>    to 20-second delays) that were previously ignored when the Time
>Alive 
>    Timer interval was 180 seconds.
>
> 
>
>
>
>If you look at the detailed messages in the QAPPCTCP job log, there will
>be
>a MSGCPIAF60 for any Data Area processed with:
>
>Message .................: QUSRSYS/QZPAIKATM  : xxxxx , showing the data
>area name found and the new value read from it.
>
>This provides a means of verifying that the OS/400 AnyNet is using the
>new
>timer values.
>
>To enable the new values entered in the Data Area(s) created, issue the
>CHGNETA ALWANYNET(*NO) CL command.  Wait for the QAPPCTCP job in the
>QSYSWRK subsystem to end.  Then, run the CHGNETA ALWANYNET(*YES) CL
>command
>to restart the QAPPCTCP job with the new values read from the data
>areas.
-- 
Gord Hutchinson
Database Administrator, IT
TST Overland Express
ghutchinson@xxxxxxxxxxxxxxx
905-212-6330
fax: 905-602-8895