RE: Is there a way to prevent iSeries Access exit before 5250 sessionlogoff?

There's a related "issue".

Certain users say "I know I keyed that in." "When I got
done, they system had assigned an order # which I wrote on
the customer input paperwork." "There is something wrong
with the data in the system, or the software, that needs
fixing, because it is "losing" customer orders."

Come to watch the user at work to see what they doing
wrong, or catch the system in the act of doing what the user
claims is going wrong ... at the very end of data entry for
an order or group of ordersthere's command keys to ACCEPT and
POST their work, or to CANCEL .... and apparently this is
such a common problem that there have been threads in BPCS-L
on how to either disable the CANCEL command function key, or
convert it into an "are you sure?"

Depending on how the software is structured, it is possible
to sign back onto a discontinued session, and resume where we
left off. But that only helps for users who know they X'd
out by accident.

---- Original message ----

From: "Mike Cunningham"
Subject: RE: Is there a way to prevent iSeries Access exit

before 5250 sessionlogoff?

Except unless you build in some way to notify the user that

their

changes were not committed they will not know that it was

not updated.