Service policies defined in the WebSphere Extended Deployment environment
are not automatically defined in the z/OS workload management (WLM). You must
first configure the service classes in z/OS WLM before defining the service
policies in WebSphere Extended Deployment. Use this task to define service
classes in z/OS WLM.
Before you begin
You must be using the WebSphere Extended Deployment for z/OS Compute
Grid component in combination with the WebSphere Extended Deployment for z/OS
Operations Optimization component to work with service policies.
About this task
After defining the service classes in z/OS WLM, the corresponding
service policies and transaction classes in WebSphere Extended Deployment
must be defined. Perform the following steps to configure z/OS WLM:
Procedure
- To extract the current z/OS workload management service definition,
choose option 2:
File Help
--------------------------------------------------------------------------
Command ===> _____________________________________________________________
Choose Service Definition
Select one of the following options.
2_
1. Read saved definitions
2. Extract definition from WLM
3. Create new definition
- Choose option 2 to create a workload:
File Utilities Notes Options Help
--------------------------------------------------------------------------
Functionality LEVEL011 Definition Menu WLM Appl LEVEL017
Command ===> ______________________________________________________________
Definition data set . . : none
Definition name . . . . . ZWASAXXX (Required)
Description . . . . . . . WLM Setup for WebSphere for z/OS
Select one of the following options. . . . . 2__
1. Policies
2. Workloads
3. Resource Groups
4. Service Classes
5. Classification Groups
6. Classification Rules
7. Report Classes
8. Service Coefficients/Options
9. Application Environments
10. Scheduling Environments
- Name it WASXD:
Workload Xref Notes Options Help
--------------------------------------------------------------------------
Workload Definition Menu WLM Appl LEVEL017
Modify a Workload
Command ===> ______________________________________________________________
Enter or change the following information:
Workload name . . . . . WASXD
Description . . . . . . WebSphere XD Workload
- Navigate to the definition menu. Choose option 4 to create a service
class called SIMPLECI under the workload WASXD and goal discretionary:
Service-Class Notes Options Help
--------------------------------------------------------------------------
Functionality LEVEL011 Definition Menu WLM Appl LEVEL017
Create a Service Class
Command ===> ______________________________________________________________
Service Class Name . . . . . . . SIMPLECI (Required)
Description . . . . . . . . . . . WimpleCI Jobs Service Class
Workload Name. . . . . . . . . . . WASXD (name or ?)
Base Resource Group . . . . . . . ________
Cpu Critical . . . . . . . . . . . NO (YES or NO)
Specify BASE GOAL information. Action Codes: I=Insert new period,
E=Edit period, D=Delete period.
- - - - Period - - - - - - - - - - - - - Goal - - - - - - - -
Action # Duration Imp. Description
___
___ 1 Discretionary
- Navigate back to the definition menu. Choose option 6 to create
a classification rule. The classification rule maps to WebSphere
Extended Deployment transaction classes to WLM service classes.
- Navigate to the definition menu. Choose option 9 to change the
application environment definition. In the application environment definition
screen, select option 3 in the WebSphere for z/OS Application Server. Here,
the name is BBOC001.
Application-Environment Notes Options Help
--------------------------------------------------------------------------
Application Environment Selection List Row 1 to 11 of 11
Command ===> ____________________________________________________________________
Action Codes: 1=Create, 2=Copy, 3=Modify, 4=Browse, 5=Print, 6=Delete,
/=Menu Bar
Action Application Environment Name Description
____ BB0C001 WebSphere for z/OS App Server
____ BB0DMGR WebSphere for z/OS DM Server
____ DSN7PSM1 for running rexx job to build
____ DSN7WLM1 WLM for SQL procedures
____ DSN7WLM2 WLM for SQL procedures
____ DSN8PSM1 for running rexx job to build
____ DSN8WLM1 WLM for SQL procedures
____ DSN8WLM2 WLM for SQL procedures
____ FRCAHTTP Fast Cache Accelorator env
____ WEBCGI CGI Application Env
____ WEBDOCUMENTS
____ ******************************* Bottom of data ********************************
- Select option 1. When the application environment is
set to no limit, you can control the minimum and maximum number of WebSphere
Application Server servant regions.
Application-Environment Notes Options Help
--------------------------------------------------------------------------
Modify an Application Environment
Command ===> ______________________________________________________________
Application Environment Name . . . . . . . : BB0C001
Description . . . . . . . . . . . . . . . . . WebSphere for z/OS App Server
Subsystem Type . . . . . . . . . . . . . . . . CB
Procedure Name . . . . . . . . . . . . . . . WS50ASR
Start Parameters . . . . . . . . . . . . . . . JOBNAME=&IWMSSNM.S,ENV=BC1.BB0N1..&IWMSS
NM_______________________________________
_________________________________________
Starting of server address spaces for a subsystem instance:
1____
1. Managed by WLM
2. Limited to a single address space per system.
3. Limited to a single address space per sysplex
- Navigate to the definition menu to install and activate the definition. Press ENTER in the Utilities menu item, then select option 1
to install the definition. Select option 3 to activate it:
What to do next
After defining the service classes in WLM on z/OS, use the WebSphere
Extended Deployment administrative console to define the corresponding service
policies and transaction classes. Although the order in which the service
classes are defined is not important, defining them first in WLM on z/OS ensures
that the transaction class qualifier selected complies with the eight-character
WLM on z/OS limitation. This value will be entered as the transaction class
name for the corresponding service policy’s transaction class in WebSphere
Extended Deployment. This is the TCLASS that will be propagated, indicating
to WLM the classification that occurred in the job scheduler.