Integrating batch features in z/OS operating systems
Use these tasks to integrate batch features into the z/OS environment.
Tasks
- Manage multi-user Workload Manger (WLM) environments. See Manage multi-user WLM environments for more information.
- Manage worker threads. See Manage worker threads for more information.
Subtopics
- z/OS workload management and service policies
If users who work in a multi-user address space are assigned to the same service policy, normal WLM behavior is assured. All user work in such an address space receives equal treatment. In an operating system dispatcher queue priority, the z/OS workload management (WLM) manages running work at the address space level.- Transaction class propagation on z/OS operating systems
Service policies contain one or more transaction class definitions. The service policy creates the goal, while the job transaction class is used to connect the job to that goal. When working with z/OS resident applications, the goal defined in the service policy is only used for monitoring and reporting rather than active workload management. The transaction class also serves the purpose of providing the TCLASS value that is propagated to the request and used by Workload Manager for z/OS (WLM).- Manage multi-user WLM environments
Use the WAS workload management (WLM) to control the performance of and the number of application server regions in z/OS.- Manage worker threads
Support Object Request Broker (ORB) service advanced settings. The workload profile specifies the server workload profile, which can be ISOLATE, IOBOUND, CPUBOUND, or LONGWAIT.- Enable job usage information
The job scheduler records usage data for charge-back accounting when enabled through the administrative console. This function is available for all operating systems and can be enabled and disabled through configuration settings. Job usage information is not enabled by default.
Related:
z/OS workload management and service policies Transaction class propagation on z/OS operating systems