Classification rules
WLM uses classification rules to map work coming into the system to a service class. This classification is based upon work qualifiers. The first (mandatory) qualifier is the subsystem type that receives the work request. Table 1 lists the subsystem types that can receive z/OS® Explorer workloads.
| Subsystem type | Work description |
|---|---|
| ASCH | The work requests include all APPC transaction programs scheduled by the IBM-supplied APPC/MVS transaction scheduler, ASCH. |
| JES | The work requests include all jobs that JES2 or JES3 initiates. |
| OMVS | The work requests include work processed in z/OS UNIX System Services forked children address spaces. |
| STC | The work requests include all work initiated by the START and MOUNT commands. STC also includes system component address spaces. |
Table 2 lists additional qualifiers that can be used to assign a workload to a specific service class. Refer to MVS Planning: Workload Management (SA22-7602) for more details on the listed work qualifiers.
| ASCH | JES | OMVS | STC | ||
|---|---|---|---|---|---|
| AI | Accounting Information | x | x | x | x |
| LU | LU Name (*) | ||||
| PF | Perform (*) | x | x | ||
| PRI | Priority | x | |||
| SE | Scheduling Environment Name | x | |||
| SSC | Subsystem Collection Name | x | |||
| SI | Subsystem Instance (*) | x | |||
| SPM | Subsystem Parameter | x | |||
| PX | Sysplex Name | x | x | x | x |
| SY | System Name (*) | x | x | x | |
| TC | Transaction/Job Class (*) | x | x | ||
| TN | Transaction/Job Name (*) | x | x | x | x |
| UI | User ID (*) | x | x | x | x |
Note: For the qualifiers marked with (*), you can specify classification
groups by adding a G to the type abbreviation. For example, a transaction
name group would be TNG.