we have done this...
and, while they do "pause", there is no "gasp", just a second click.

On 3/13/2012 11:48 AM, Jeff Young wrote:
You can at least warn them that they will be exiting the session by
clicking on the "X" using the Edit - Preferences - Exit meun.
If you select Confirm on Exit Session or Confirm on Exit All, they will get
a warning box that they must respond to.
This will not prevent them from clicking on the "X", but may give them
pause and make them (gasp!) think about what they are doing.

On Tue, Mar 13, 2012 at 12:26 PM, Coy Krill<coyk@xxxxxxxxxx> wrote:

We had this exact thing happening over and over again. Turned out to be
a saturated switch that was flaking out in one of our hub locations.
iSeries Access was NOT recovering gracefully and actually crashed and
closed on the users machines in many instances. The message you mention
is the message we saw in their joblogs. They could be telling you the
truth and you have a network issue. Took our network guys a couple of
weeks of sleuthing to find the problem because it was transient.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gqcy
Sent: Tuesday, March 13, 2012 08:45
To: midrange-l@xxxxxxxxxxxx
Subject: Client Access - users clicking the red X while still signed on

F%*&n users!!!!
I see in their job log the CPF5140 message "Session stopped by a request
from device...."

but when users are asked about it, the say the window "just
disappeared", or adamantly claim they didn't hit the red X.

Is there a sure fire way to tell that the user "red x'ed" the session?

-btw, there is a user policy setting to remove the red x, but that is
too drastic (at this point).

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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 [javascript protected email address].