Aborting the DFO/DFG Utility (not the detached process doing the defragging
as specified in the script) via Control-C (or Control-Y) has 2 disadvantages.

1 (minor) is doesn't restore the (previously turned off) cursor and you must
turn it on again (eg. via Reset Terminal in DECterm) by hand.

2 (major) if you reenter the defragger utility, it can no longer be aborted
and is stuck (you need to kill the process/job). Seems the image rundown
has similar problems like the freeware FIND utility (on Alpha) has.

Using DFG on a daily basis (per script) but rarely by hand (to monitor, show
or modify scripts) I'm not able to tell for sure how long this error exists.


Did you perhaps noticed this behaviour/error ?
Did you tell VMS engineering (via support channel) ?
Will it be fixed with V2.9 ?

TIA

-- 
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail  peter@langstoeger.at
A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist