RE: 5250 sessions killing the system

Rob,

We had individual sessions for each user, some users had 3 or 4.
When we migrated to ACS, I changed to using &COMPN*= for the session id.
Session name now equals PC name, with a letter suffix for each additional one launched.
One HOD session can launch as many as needed.
QAUTOCFG must be set to 1=on.
Also had to add some wildcard names to the interactive subsystem.

Session maintenance eliminated.

Paul



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Monday, November 18, 2019 8:34 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: 5250 sessions killing the system

And, apparently minimizing sessions is really popular on shop floor PC's where multiple users have their own 5250 sessions and are strictly forbidden to use a session that someone else is logged on to and must start their own.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Monday, November 18, 2019 8:29 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: 5250 sessions killing the system

Ok, we think we know how this happens now.
User has a session, let's use ROBS1 for an example.
He minimizes ROBS1 and cannot find it.
So he starts it again and now has two ROBS1 sessions.
The second one cannot connect because that session is in use. However, if you have autoconnect turned on, it never stops trying.
Wham: Denial Of Service.

Rob Berendt