Endevor temporary datasets are being orphaned.

Products

• Endevor

Issue/Introduction

Temporary datasets (C1USERID.ELEMENT.SN.SYSID.C1TYPE) that are created during various Endevor activity (i.e. Browse) are not always getting deleted and are left orphaned until a manual clean-up effort is completed.  Why does this occur? 

Environment

All Supported Releases

Resolution

Endevor automatically deletes the temp file after the user hits PF3 from the Browse element session. So temp data sets can only get orphaned if the user didn't have a chance to hit PF3 before the address space (or at least the respective ISPF split screen) terminates.

The possible scenarios include:
User's TSO session times out
User's TSO session is manually canceled
User's TSO session is canceled during an IPL
User's TSO session abends causing the Quick Edit session to not terminate cleanly

It's advised to review user behavior to see if any of these causes can be reduced or avoided.