Frank Rodegeb presented the recovery characteristics of MVS/ESA. It turns out that IBM has done a lot of work on recovery, and the differences between ESA and our little old MVS/370 system are becoming broader by the month.
First we had to endure a ritual incantation and gratuitous overhead display, to-wit:
"The following are trademarks of the IBM Corporation
MVS/SP MVS/ESA PR/SM MVS/XA"
"Indiscriminate installation of OCO software on your MVS/SP
system can introduce trojan-horse programs beyond your control.
By-the-way, MVS/SP is a trademark of the IBM Corporation,
and Trojans is a trademark of..."
A new function in ESA is "Component Trace", or CTRACE. It provides a central mechanism for system components to record and analyze their own internal diagnostic traces. IPCS supports CTRACE.
ESA now supports a PAGEDEL command (you have always been able to dynamically add page datasets, but you couldn't get rid of them without IPLing).
ESA fixes a bug in WAIT/POST where VTAM would ABEND with an S202 when a VTAM application shut down. This is a continuing thorn in my side in MVS/370.
IPCS has gained new respect at IBM and is ballyhooed as "the strategic dump analysis tool for MVS/ESA". It now completely replaces AMDPRDMP, and contains a number of new canned routines to validity-check system dumps. SVC dump has gotten a bunch of new operands and can be tailored more completely. GTF has enjoyed a "major performance improvement".
Not much of it applies here. Yet.