Generic decollating is not mandatory, but BMC recommends that you use it, especially for processing the output of the MSGCLASS job.

The generic decollating missions classes are part of CTDPARM.

If an output class is specified, it is constantly monitored by Control‑D. When a (non‑held) job output appears on one of the specified classes, Control‑D attempts to match its job name with scheduled generic decollating missions. If a generic decollating mission is present, Control‑D processes output from these classes.

For more information about generic decollating missions, see the Control‑D and Control‑V chapter in the INCONTROL for z/OS Administrator Guide.

Generic classes are used to define the output classes for generic decollating missions for each Control‑D monitor. Use the existing library and member name, or specify a different member to be edited.

Specify up to 15 sets of classes where each set defines 1–8 generic output classes for Control‑D monitor: one set for the first monitor, a second set for the second monitor, and so on.

When assigning values for the classes, note the following:

1. The same class can be specified for the first Control‑D monitor, the second monitor, and so on.
2. If no output classes exist for a specific monitor, a comma must be specified for this monitor under some conditions. The following example illustrates the position where output classes are present only for the second and fourth monitors:

   GENCLAS=(,DEF,,XY),