On 12/23/2014 05:39 AM, Hobart Spitz wrote:
In the interest of conserving disk resources, some installations create
DASD management rules that delete ISPF edit backup files prematurely,
defeating RECOVERY ON. Depending on your site's policies, it may (or may
not) be possible to address the issue by pre-allocating your backup
datasets to perm packs before you enter ISPF.
Note that depending on your SPLIT NEW limit, you may have to pre-allocation
anywhere from 8 to 32 such datasets for RECOVERY ON to work in all logical
windows.
<SNIPPAGE>
This is not my problem.
My problem is, ISPF did recognize the backup file and I told it I
wanted to defer the recovery.
When I was ready to edit and pickup from where I had been, it now
does not recognize that any recovery is needed, yet the backup
data set is still there.
My point about splitting is I just run a typical split with "top"
and "bottom". I do not used named splits, rings, etc. Just a
single simple split.
Regards,
Steve Thompson
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
