This sounds like a user training problem. Users should be taught in the
scenario you describe to use EDIT on the new member name, within EDIT
use COPY to pull in the old member contents, then do editing. The
design intent of VIEW is to view without altering the original contents,
and default attributes such as RECOVERY should be expected to be set OFF
accordingly for VIEW. They should not be using VIEW when intending
extensive modifications, but should instead be using EDIT, and have only
themselves (and their trainer) to blame when they lose data using VIEW
in an inappropriate context. It shouldn't take a whole lot of thought
to realize that the commands are named differently for a reason, and
that the names actually do convey the intended use!
J. C. Ewing
On 03/03/2012 10:27 AM, chen lucky wrote:
YES, this is one option. But some user have the habit that do a lot of
edition in view mode, then create a new member on behalf of it. So if the
user can reconnect to the remain session after connection failure, this
should be the best choice.
thanks.
2012/3/3 [email protected]<[email protected]>
If the data to be saved is from ISPF Edit, have you considered setting the
Recover option for your users?
----- Original Message -----
From: "chen lucky"<[email protected]>
To: [email protected]
Sent: Saturday, March 3, 2012 2:08:17 AM
Subject: IKT100I USERID CANCELED immediately after TN3270 connection fail
Hi List,
Thanks for your help.
Recently I encounter a problem that IKT100I USERID CANCELED immediately
after TN3270 connection fail, and It is unacceptable in our shop, because
users will lose their work that do not save in time.
...
--
Joel C. Ewing, Bentonville, AR [email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
