I'm not sure if this is the same problem, but we've been seeing these orphaned recovery files for some time - at least back to z/OS 1.5 (we're 1.7 now).
Some of the files seem to be completely orphaned while others appear to be hanging around in ML2 status until the owner opens the wrong PDS member and has to wait for the recovery file to be recalled - giving them ample to call us and complain. However, if we let SMS delete the files instead of migrating them the user gets a message saying ISPF was unable to recover their previous edit session. This also generates a phone call. Sorry I don't have an answer for you, but if this is the same problem you're having, I'm not so sure it was introduced in z/OS 1.8. Thanks, Carey Morris -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Conley Sent: Thursday, May 24, 2007 5:33 PM To: [email protected] Subject: Fix for orphan ISPF edit recovery files yet? Did anybody ever get a fix for the orphan ISPF edit recovery files? I got a boatload of them on z/OS V1R8. I'm totally non-SMS, so please don't tell me how I can use SMS to mask this ISPF bug, just tell me if there's an APR and a PTF. I was not able to find anything on IBMLink. Regards, Tom Conley ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
