-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document recommended Workload Management setup for ZWE* #3840
Comments
Following is excerpt from z/OSMF documentation on the topic of WLM setup. Setup an appropriate performance goal on WLMIn z/OS system, we usually using Workload Management (WLM) define performance goals for workloads in z/OSMF workload can also benefit from WLM by setting up an appropriate performance goal. The following will First, confirm the WLM feature is enabled. Usually z/OSMF already defined this feature in the server.xml file Second, create the classification rules for z/OSMF. The CB classification rule is defined for WAS related
Third, create the required service classes. We create two service classes for z/OSMF, IZUGHTTP and IZUGWOR.
If the workload performance can’t satisfy your expectation you can tuning the performance goal by changing the The last, install and active the WLM policy. You can use both WLM panel and z/OSMF web UI to finish this step. |
Put Zowe into TSOMED WLM policy and make sure it applies to ZWE* jobs. This is still a robust service class, but lower than the regular TSO user community. Previously these tasks were ending up in TSO service class and that was negatively impacting the entire user community because these TSO foreground tasks are at the "top of the food chain" and your z/OSMF foreground tasks tend to be CPU heavy due to the fact you're querying the system. Now these OTX tasks are lower to start with and will fall to a lower period of the multi-period service class sooner. |
Is your request for enhancement related to a problem? Please describe.
The zowe startup takes all the available resources within the system.
Describe the solution you'd like
One correct way to solve the problem is to properly set up the class within the Workload Manager, which limits the resources available to the Job. We should document the recommended configuration for the Workload Management Setup.
Related doc pages
It's going to be a new one within the Installation procedure.
Additional context
The work probably will need to happen together with the server squads.
The text was updated successfully, but these errors were encountered: