You may need to define non‑CA Top Secret resource classes in the following situations:
IBM products that requirement a non‑fixed or installation‑defined resource class name.
OEM software packages that have unique resource class names not defined by CA Top Secret.
Installation‑written security with its own resource classes, and any other customized site applications with resources and security of its own. For example, a site‑written application may require the definition of a resource class of $PROC to provide JCL procedure security as checked by an installation‑written JES exit.
Installation‑written security may require separate naming conventions and access levels.
