And until you either CANCEL or allow edit recovery to occur, there are
TWO copies of the member in question: the one in the PDS (which does not
contain the edits at time of TSO/ISPF abnormal termination) and the copy
in an edit-recovery dataset under your userid (which does contain those
edits). If you know the prior edits were unimportant and not needed,
you should CANCEL recovery.
Only the user with an active edit recovery dataset for the member will
see this message and have the option of recovery. One of the dangers of
letting this condition persist is that someone else may edit and save a
new version of the PDS member, or you might even do this by deferring
recovery. If that happens, and then you later perform the Edit
Recovery, any newer updates that were only in the physical member and
not in your Edit-Recovery dataset will be lost. (If you know this has
potentially occurred, you can rename the PDS member, allow Edit Recovery
to proceed and save that version of the member, then compare the two
versions and reconcile differences).
Even if you are the only person that will ever update this member, be
sure this is not a member that you continually edit, never explicitly
save, and are always editing when your TSO session times out for
inactivity. I have actually known of cases where someone inadequately
trained in ISPF got in the habit of doing this and had several months of
activity log updates that were only retained in an edit-recovery dataset
and not in the PDS. Eventually their edit-recovery dataset filled up,
they got a message which was ignored that said Edit Recovery was turned
off, and the next time their TSO session timed out they lost several
months of updates!
J C Ewing
On 03/11/2013 08:22 AM, Lizette Koehler wrote:
As suggested, PF1 is helpful with ISPF issues.
If the popup panel you see has the following actions
CANCEL
DEFER
ENTER
END
Then as indicated, when you were in ISPF last time and had RECOVERY ON (REC
ON) your TSO Session or ISPF session died. When you went back into any PDS
member, you should have a pop up panel that states which Dataset(member) you
were last editing that needs action.
So, did you get the full menu with CANCEL DEFER END ENTER, or something
else?
The other issue is the last time you were in and terminated, your ISR
dataset for recovery was deleted. So if you select DEFER or ENTER it might
give you another error.
I think the ISPF User's Guide Vol1 and 2 could help you understand this
condition more.
Please post any full error information you need further help
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf
Of mf db
Sent: Monday, March 11, 2013 2:13 AM
To: [email protected]
Subject: Edit Automatic Recovery - Clarification
Hello Group,
While editing a member in a PDS I get the below error message. Any Idea on
what
basis this error do Pop Up ?
*****************************************
* EDIT AUTOMATIC RECOVERY *
*****************************************
The following data set was being edited or viewed when a system failure or
task abend
occurred:
Could someone please enlighten me about the above message.
Peter
--
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
