When you have a Windows PC, let's say JRZPC01 for example. And someone is logged in on that PC as JUAN. Now there are multiple users who access that after it is logged on to use 5250 sessions: JUAN, MARIA, JAVIER. Using Paul's method each session would be JRZPC01S1... Using Steve's method each session would be JUANS1..., right?
This may be a workaround. Another workaround may be turning off autoreconnect.
However this doesn't solve the root problem. Stopping it at the server. Once you start to rely upon stopping it at each client you still leave yourself open to a Denial Of Service attack.
Latest service updates from IBM after I explained the situation to them:
IBM: That would make sense. I will close this out.
My reply to that: Yes, I published this on LinkedIn as a simple way to perform a Denial Of Service attack on IBM i. I'm getting some likes from foreign nationals.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.