I don't believe there is a feature/function in ENDEVOR, but I have asked for one before.
We have multiple techniques for dealing with the scenario of code becoming redundant but also facing the challenge of audit that it needs to be actually archived as well as deleted in production.
This year we came up with a fully automated solution to delete first and then archive afterwards.
This process was important (to us) as with the agile world people tend to perform less impact analysis and just request deletes (for things like JCL and programs) and then get called that their stuff has failed and need it back again (hurray for backout).
The other requirement was it should be fully automated and under end user control. Our team do not have the time to support this process in any kind of manual way as we have millions of elements.
So, it can be done. It certainly wasn't easy and we spent a lot of time coding and complaining and found out a number of issues with ENDEVOR about what we could and couldn't do (especially as you would imagine around the area of packages). Full automation meant creating archive environments and datasets on the fly and ensuring housekeeping cleared it all up. it's been live now for 5 months and stable.
Having said all of that, I'm not in a rush to roll out this solution to other instances of ENDEVOR. Although we try to design and build once for multiple instance deployment, we feel there could be a far better solution in the wings from the vendor. It starts with requirements though and I feel this is a bigger area than just knocking up an ideation.