Workload Classification in WebSphere XD Compute Grid on z/os V.8

Transcription

1 Workload Classification in WebSphere XD Compute Grid on z/os V.8 This document describes the mechanisms for classifying batch jobs running in WebSphere XD Compute Grid Version 8 on z/os. There are actually two different Classification Mechanisms for Batch Jobs in Compute Grid: 1. A Job Class can be specified by a job in the xjcl, and can be used by the Job Scheduler to dispatch jobs to Endpoint Servers, based on: Availability of Servers to accept new work. Number of currently running jobs below the maximum threshold for the Job Class A Maximum Execution Time can also be assigned based on the Job Class. 2. The z/os Workload Manager (WLM) controls dispatching of CPU cycles & I/O to jobs in execution according to: Service class goals assigned to work based on: Importance and Response Time objectives or Velocity goals. Service Class assigned based on the Cluster Name (CN), and Transaction Class assigned by the Scheduler. On a continuing basis, WLM adjusts the dispatching priority of work based on: Availability of CPU (& other) resources The attainment of work in the service class meeting their Goals. Other work in the sysplex. Overview of this sample exercise to demonstrate batch job classification: 1. Create a job class of Compute for Compute-Intensive jobs. 2. Create Classification rules for Compute Intensive work and XDCGIVT jobs. 3. Submit 3 SimpleCI and 3 XDCGIVT long-running jobs from the JMC. 4. Observe the results using SDSF and RMF. Background: Workload Classification for WebSphere work There are several different types of work in WebSphere: STC (Started Tasks) Daemons, Controllers, Servant address spaces OMVS work - spawned processes (e.g., applyptf.sh) Resource Managers (DB2, CICS, IMS, MQ, other) 'CB' (WebSphere Transactions) Cluster Name (CN) This is the Cluster transition name of the server. Transaction Class (TC) This is the differentiator for WebSphere transactions. Workload Classification in WebSphere XD Compute Grid w3.ibm.com/support/techdocs/td Page 1 of 5

2 Here is a simple example of the Workload manager CB Classification Rules for transactions in the XXCell: Default service class is CBCLASS Qualifier Qualifier Service Report # type name Class Class CN XX* CBFAST XXBAT 2. TC. TCOMP CBSLOW XXBATCI 2. TC. TCXDIVT CBCLASS XXXDIVT You can set these rules in the TSO WLM application: ISPF Option 6 (SO command > type IWMARIN0 > (enter) > 2 (Extract definition from WLM couple data set) > 6 (Classification rules) > 3 (Modify) on the CB Classification rules. In WebSphere Application Servers on z/os, the Transaction Class can be set by the Workload classification file for the following types of work: HTTP Host, Port, URI IIOP Application name, Module, Comp, Method MDB Endpoint, Listener port SIP, SIB Request, & Internal Classification Asynchronous Beans can be classified using a Transaction class assigned in the Work Manager definitions in the Administrative Console (ISC). If not specified, the Transaction class of the enclave is used, or a default Transaction class of ASYNCBN is assigned for non-enclave threads. For more information on the above classification mechanisms, see Techdoc WP However, for Compute Grid Batch Work, the Transaction Class is assigned by the Job Scheduler Classification Rules which is described below. Job Class for Batch Work Let us diverge from WLM classification to describe the Job Class used by Compute Grid. Job classes specify limits for resource consumption by batch jobs. A job class defines a set of rules for resource consumption such as execution time, number of concurrent jobs, and joblogs. Here is an example how you would define a job class named Compute for compute-intensive batch work, to set a maximum of one job in execution at a time: Log on to the ISC at Go to System administration > Job scheduler > Job classes Define a New Job Class Compute for compute-intensive jobs. Set a Maximum of 1 jobs executing at once. Click OK and Save. Workload Classification in WebSphere XD Compute Grid w3.ibm.com/support/techdocs/td Page 2 of 5

3 Classify Compute Class Jobs & XDCGIVT Jobs The Job Class can be specified in the xjcl, as in this example: <?xml version="1.0" encoding="utf-8"?> <!-- (C) Copyright IBM Corp All Rights Reserved. --> <job name="simpleciear" class="compute" xmlns:xsi=" Here is an example showing how to assign a Transaction class in the job Scheduler to jobs with a Job class of Compute or based on their Job Name. Go to System administration > Job scheduler > Classification Rules Assign jobs with a Job Class of Compute to a Transaction Class of TCOMP : 1. Click Add Rule (1) 2. Click Subexpression builder (2) 3. Select operand Job Class (3) 4. Select Equals (=) in the Operator pull-down.(4) 5. Enter Compute in Value box.(5) 6. Click on Generate subexpression (6) 7. Click on Append, (7) 8. click Close (8) Enter TCOMP in the Then classify to transaction class box. Click Validate Rule Workload Classification in WebSphere XD Compute Grid w3.ibm.com/support/techdocs/td Page 3 of 5

4 Assign jobs with a Job Name of XDCGIVT% to a Transaction Class of TCXDIVT by performing the following steps: Click Add Rule Click Subexpression builder Select operand Jobname Select Like (LIKE) in the Operator pull-down. Enter XDCGIVT% in Value box (without quote marks.) Click on Generate subexpression Click on Append, then click Close Enter TCXDIVT in the Then classify to transaction class box. Click on the Validate button to make sure the values are saved properly. Delete the other rules, or move them down, so your new rules are tested first. Verify your settings as shown above, then click OK and save. Re-cycle the Dispatcher & Endpoint servers for these to take. Verify that Job classification is working Edit the xjcl file for the SimpleCIEar job using a text editor, such as Notepad or PFE: A copy can be found in the following location: /shared/zwebspherecg/v8r0/stack_products/wcg/longrunning/simpleciear.xml Change line # 14 to include class= Compute : <job name="simpleciear" class="compute" xmlns:xsi=" Save the job's xjcl in a directory on your workstation. Logon to the Job Management Console (JMC) at and submit the following jobs: SimpleCI should run with a WLM Report Class of XXBATCI XDCGIVT should run with a WLM Report Class of XXXDIVT Log onto the JMC at Submit 2 SimpleCI jobs from the workstation directory which you just edited. Click on View jobs in the JMC. Workload Classification in WebSphere XD Compute Grid w3.ibm.com/support/techdocs/td Page 4 of 5

5 Find the second of the 2 SimpleCI jobs you just submitted click on the joblog. Scroll to the bottom of the joblog where you should see: CWLRS0493I: Job SimpleCIEar:000xx cannot be dispatched at this time as its job class Compute is running with full capacity. Look at the WLM Classification: Go to your TSO / SDSF session and type ENC on the Command Input line. When the SimpleCI jobs are running, you should find transactions running in the CBSLOW Service Class, and in the XXBATCI Report Class using the SDSF ENC panel. Test the XDCGIVT Job Classification: From the JMC, submit 2 XDCGIVT jobs from... Set the substitution property NumberRecords to 5000 so it runs for a while. When XDCGIVT job is running, you should see transactions running in the CBCLASS Service Class, and in the XXXDIVT Report Class using the SDSF ENC panel. Look at the RMF Monitor III report: In TSO, start RMF Monitor III: Select RMF > 3 > Sysplex > 1 (SYSSUM) You should find transactions running in the above service and report classes. Workload Classification in WebSphere XD Compute Grid w3.ibm.com/support/techdocs/td Page 5 of 5