The JADE 2022 release meets tomorrow’s business demands.
A class defined in a super-schema may no longer be used but is unable to be removed because it has methods or constants declared in one or more sub-schemas.
I don't know of anyway to identify which schemas where this class has sub-schema copies.
The only way seems to be to go into each sub-schema and inspect the class.
Nice idea. I've encountered this situation a few times myself, and used a script similar to the following to find the schemas which have subschema copies of the class of interest: