IBM Workload Automation, Version 9.3

Processor Value Unit license model

About this task

IBM® License Metric Tool generates reports to help you maintain compliance with your Processor Value Unit (PVU) sub-capacity license terms. License Metric Tool can calculate PVU consumption only when software identification tags exist and are activated by the customer. The optman global option licenseType must be set to ws (default value) to activate Processor Value Unit consumption tracking.

License Metric Tool automatically detects the following IBM Workload Scheduler V9.3.0 chargeable components that are part of the product:
Table 1. Chargeable software components automatically detected by License Metric Tool
Chargeable Software Components
IBM Workload Scheduler agent V9.3.0
IBM Workload Scheduler agent for z/OS V9.3.0

To detect and count remote nodes that are managed by IBM Workload Scheduler chargeable components, you must manually deploy software tags because no product code is present on those nodes. License Metric Tool generates and assigns dedicated software tags during the creation of the Readiness Package for the latest release of IBM Workload Scheduler.

The following IBM Workload Scheduler Version 9.3.0 chargeable components require manual deployment of software tags:
Table 2. Chargeable software components that require software tag deployment on managed nodes
Chargeable Software Components Assigned Software tags
IBM Workload Scheduler agent-less 9.3.0 1986-03.com.ibm_IBM_Workload_Scheduler_agent-less-9.3.0.swidtag
IBM Workload Scheduler for third-party Applications 9.3.0 1986-03.com.ibm_IBM_Workload_Scheduler_for_Third_Party_Applications-9.3.0.swidtag
IBM Workload Scheduler for IBM Applications 9.3.0 1986-03.com.ibm_IBM_Workload_Scheduler_for_IBM_Applications-9.3.0.swidtag
Note: For information about how to match chargeable software components with the IBM Workload Scheduler access methods and application plug-ins, see table Table 3
Complete the following procedure to manually deploy dedicated software tags on each managed node and calculate PVU consumption:
  1. Identify the remote nodes that are managed by each of your chargeable components. For example, the remote nodes that are managed by the application server that you are connecting to, with IBM Workload Scheduler plug-in for IBM InfoSphere DataStage.
  2. Extract assigned software tags from the ILMT_IWS_for_Applications_and_agentless.zip file that is included in your Agent installation media.
  3. Place the assigned software tag anywhere on the managed node.
  4. Wait for the next software scan in License Metric Tool to have the chargeable software components reported.
  5. It is recommended that you check whether License Metric Tool reporting matches with currently managed nodes before signing each License Metric Tool report.
The master domain manager centrally maintains the history of the plug-in jobs that you run in your environment. The history can be used:
  • During audits to verify which systems are actually managed by IBM Workload Scheduler.
  • To check periodically the result of your License Metric Tool reporting.
  • To verify your PVU license entitlement.

An SQL query is provided to access the history in the database. You can run the query either from the command-line interface of your database or by creating your custom SQL report tasks from the Dynamic Workload Console.

For each job definition in the database, the SQL query returns the:
  1. Type of the plug-in job.
  2. Name of the workstation on which the job is defined.
  3. Name of the job.
  4. XML file containing the name of the remote server on which the job ran. If the XML file does not contain the name of the remote server, you can find it in the plug-in properties file in the TWS/JavaExt/cfg agent folder.
  • For DB2, IDS, MSSQL database types:
    SELECT JOD_TASK_TYPE as Job_type, WKC_NAME as Workstation_name, JOD_NAME as Job_name, 
JOD_TASK_STRING as Job_definition
FROM MDL.JOD_JOB_DEFINITIONS J inner join MDL.WKC_WORKSTATION_CLASSES W on J.WKC_ID=W.WKC_ID
WHERE JOD_BY_JSDL='Y' and UPPER(JOD_TASK_TYPE) NOT IN ('EXECUTABLE', 'DISTRIBUTEDSHADOWJOB', 
'ZSHADOWJOB')
ORDER BY JOD_TASK_TYPE, WKC_NAME, JOD_NAME
  • For Oracle database type:
    SELECT JOD_TASK_TYPE as Job_type, WKC_NAME as Workstation_name, JOD_NAME as Job_name, 
JOD_TASK_STRING as Job_definition
FROM twsuser.JOD_JOB_DEFINITIONS J inner join twsuser.WKC_WORKSTATION_CLASSES W 
on J.WKC_ID=W.WKC_ID
WHERE JOD_BY_JSDL='Y' and UPPER(JOD_TASK_TYPE) NOT IN ('EXECUTABLE', 'DISTRIBUTEDSHADOWJOB', 
'ZSHADOWJOB')
ORDER BY JOD_TASK_TYPE, WKC_NAME, JOD_NAME
    where twsuser is the name of the IBM Workload Scheduler schema.
The following example shows you the query output for a Datastage job type:
datastage	NY_1	DS_JOB	<?xml version="1.0" encoding="UTF-8"?>
<jsdl:jobDefinition xmlns:jsdl="http://www.ibm.com/xmlns/prod/scheduling/1.0/jsdl" 
xmlns:jsdldatastage="http://www.ibm.com/xmlns/prod/scheduling/1.0/jsdldatastage" 
name="DATASTAGE">
  <jsdl:application name="datastage">
    <jsdldatastage:datastage>
			<jsdldatastage:DataStageParameters>
				<jsdldatastage:DataStagePanel>
					<jsdldatastage:Logon>
						<jsdldatastage:Domain>nc004175.romelab.it.ibm.com:9080</jsdldatastage:Domain>
				  <jsdldatastage:Server>nc004175</jsdldatastage:Server>
						<jsdldatastage:UserName>isadmin</jsdldatastage:UserName>
						<jsdldatastage:password>{aes}ScWNLDAHuN9X5sbtvAVky3RVd7gOkJqNerDbFbpwrDg=</jsdldatastage:password>
					</jsdldatastage:Logon>
					<jsdldatastage:JobDefinitionGroup>
						<jsdldatastage:ProjectNameGroup>
							<jsdldatastage:ProjectName>tws4apps</jsdldatastage:ProjectName>
						</jsdldatastage:ProjectNameGroup>
						<jsdldatastage:JobNameButtonGroup>
							<jsdldatastage:JobNameRadioButton>
								<jsdldatastage:JobName>dsj01_succ</jsdldatastage:JobName>
							</jsdldatastage:JobNameRadioButton>
						</jsdldatastage:JobNameButtonGroup>
						<jsdldatastage:FileRemotePath/>
					</jsdldatastage:JobDefinitionGroup>
					<jsdldatastage:JobExecutionGroup/>
				</jsdldatastage:DataStagePanel>
				<jsdldatastage:OptionsPanel>
					<jsdldatastage:JobOptionsGroup>
						<jsdldatastage:WarningLimitButtonGroup>
							<jsdldatastage:NoWarningLimitButton/>
						</jsdldatastage:WarningLimitButtonGroup>
						<jsdldatastage:RowLimitButtonGroup>
							<jsdldatastage:NoRowLimitButton/>
						</jsdldatastage:RowLimitButtonGroup>
						<jsdldatastage:OperationalMetadataGroup>
							<jsdldatastage:UseDefault/>
						</jsdldatastage:OperationalMetadataGroup>
					</jsdldatastage:JobOptionsGroup>
				</jsdldatastage:OptionsPanel>
			</jsdldatastage:DataStageParameters>
		</jsdldatastage:datastage>
  </jsdl:application>
</jsdl:jobDefinition>
Table 3. IBM Workload Scheduler chargeable access methods and application plug-ins
IBM Workload Scheduler access methods and application plug-ins Chargeable Software Components
Remote Command, IBM Workload Scheduler agent-less V9.3.0
Unixssh
SAP R/3 IBM Workload Scheduler for third-party Applications V9.3.0
SAP PI Channel
SAP BusinessObjects BI
PeopleSoft
Oracle E-Business Suite
Informatica PowerCenter
Salesforce
Hadoop Map Reduce
Hadoop Distributed File System
Apache Oozie
IBM Sterling Connect:Direct IBM Workload Scheduler for IBM Applications V9.3.0
IBM WebSphere MQ
IBM InfoSphere DataStage
IBM Cognos
IBM BigInsights
IBM Cloudant
z/OS Paid by PVU, manually counted, ILMT not available
Parent topic: License Management in IBM License Metric Tool