Network Issues Only Dropping PC5250 Sessions That Are Not Frequently Used

1050 pts.
Tags:
AS/400
IBM PC5250 Emulator
iSeries Access
PC5250 Emulator
V5R3
    We currently have a site that is occasionally having a network issue(PING commands shows connection verification stats of 2 of 5, 3 of 5, etc. or round trip speed in the 150 - 300 range instead of normal 50 - 80 range).     In this scenario User A uses the AS/400 all the time and doesn't get dropped.   User B uses the AS/400 sparingly and will get dropped.    I see this each and every time a particular site has a slow connection speed for whatever reason.    Why doesn't User A get dropped as well?    We do not end sessions that are inactive, since we have learned that it can cause file corruption, but these are the types of sessions that will end when we have a shaky network connection.    Any insight?   Thank you. 



Software/Hardware used:
iSeries Access V5R3

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 8  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Splat
    Have you checked the system values QINACTITV and QINACTMSGQ?
    7,665 pointsBadges:
    report
  • Batman47
    It's 90 and a message queue. We don't perform any actiion on users that remain inactive except log it to the message queue.
    1,050 pointsBadges:
    report
  • Splat
    I don't understand the different outcomes for active and casual users but I believe a CA session maintains active communications with the iSeries, user input or no. It may be that the network issues are garbling the communication and triggering a termination request.
    7,665 pointsBadges:
    report
  • Batman47
    Yes, this remote office location is continuing to have spikes on the network and the user only gets dropped if she doesn't use her session for several minutes. Our network guys are not jumping on this because my active user at that location never gets dropped. Any telnet setting I should be looking at?
    1,050 pointsBadges:
    report
  • Splat
    I don't know that Client Access uses telnet (assuming you're using Client Access). I've used Tn5250 in certain circumstances, but it has few configurable options. I'm don't know but what there may be PC settings for telnet that can be tweaked.
    7,665 pointsBadges:
    report
  • Splat
    That last sentence was intended to read 'I don’t know but what there may be PC settings for telnet that can be tweaked.' Insufficient caffeine.
    7,665 pointsBadges:
    report
  • Splat
    You may want to follow this thread also.
    7,665 pointsBadges:
    report
  • TomLiotta
    It's pretty much guaranteed that the drops aren't from QINACTITV. It's most likely related to "keep alives". Two attributes on the AS/400 are involved. First, TCP/IP has an attribute that you change with CHGTCPA TCPKEEPALV(). It defaults to 120 minutes, which is probably okay. But telnet also has its own mechanism. Change it with CHGTELNA TIMMRKTIMO(). The default is 600 seconds, and that might be too low for remote connections, especially if packets are dropped. A larger value might be better if infrequent activity is common. Maybe best is that it's possible to send "keep alives" from the client. Open the iSeries Access PC5250 workstation file (the *.WS file) in Notepad. Find the section labeled [Telnet5250] and add a line after it that says "KeepAlive=Y" (minus the quotes). Even beyond that, the PC OS generally can send keep-alives if necessary. It may require a registry edit to get it done, so it's not for the casual user. But it might be worth it to dig out how to set it on a particular system in extreme cases. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following