Defining classification rules as needed

A classification rule is rule used by the workload manager to assign a service class. Specify the classification rules needed to separate daemons (for example, inetd) from other forked child processes.

Example: This example is a sample classification for subsystem type OMVS:

* Subsystem Type OMVS

  Classification:

    Default service class is OMVS
    There is no default report class.

      Qualifier  Qualifier      Starting       Service  Report
    # type       name           position       Class    Class
    - ---------- -------------- ---------      -------- --------
    1 UI         OMVSKERN                      OMVSKERN

Forked spaces can be classified by transaction name.

If you do not define any classification rules, OMVS and BPXOINIT will run under the rules for subsystem type STC, which typically is defined to have high priority. If needed, you can define a classification rule for subsystem type STC to ensure that the kernel, the initialization process, BPXOINIT, and the DFSMS buffer manager, SYSBMAS, run as a high-priority started tasks.

Example: In this example, STC1 is a service class for high-priority started tasks:

* Subsystem Type STC

  Classification:

    Default service class is STC2.
    There is no default report class.

      Qualifier  Qualifier      Starting       Service  Report
    # type       name           position       Class    Class
    - ---------- -------------  -------------  -------- -------
     1 TN         OMVS                          STC1
     1 TN         BPXOINIT                      STC1
     1 TN         SYSBMAS                       STC1
     . .          .                             STC1
     . .          .                             ...