IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello again ;-)

You are correct that I am using BigFix and although the Initiate Software Scan fixlet was already active I have stopped everything and started again from scratch.

After running the Initiate Software Scan and waiting for it to complete I downloaded the MustGather data and within the zip file I have located the slmtagsearch_xxx_slmtag.zip file under the sha1_files folder. The contents of the slmtag*.zip is 2 files - a file named "1" that contains the content of the slmtag file for IWS Workload Automation (10_MONTHLY_JOBS) in XML format and a file named "list.txt" which contains the full path to the slmtag file itself (original location).

I then ran the import manually in ILMT and that appears to have worked successfully - the messages relating the the slmtag file import are

2023-11-20 14:43:17 (+0:00:00.000) INFO: Running LMT ETL SlmTagImport: Start
2023-11-20 14:43:18 (+0:00:00.234) WARN:  (ImportSlmTags-Thread:0) Some resource utilization metric values for ResourceUtilizationItem [persistentId=3303c35cbc08435080502d621d5cdbff, name=IBM Workload Automation, instanceId=/opt/IBM/TWA, publisher=null, version=null, type=10_MONTHLY_JOBS, subType=null] on computer 1 are from the future (after Mon Nov 20 14:43:18 UTC 2023). Discarding them and continue.
2023-11-20 14:43:19 (+0:00:00.845) INFO:  (ImportThread) com.ibm.license.mgmt.etl.core.actions.SlmTagImportStep::printStatistics::STATISTICS: Number of Slm import threads = 1, Number of computers = 1, Number of processed computers = 1, Number of processed good Slm archives = 1, Number of processed broken Slm archives = 0, Number of processed good Slm files = 1, Number of skipped (no valid metrics) Slm files = 0, Number of processed broken Slm files = 0, Number of updated first measured times = 0, Number of updated last measured times = 0, Number of updated rollups = 1
2023-11-20 14:43:19 (+0:00:00.014) INFO: Running LMT ETL SlmTagImport: Success

The future date is because of the end of this month being set - these are usually discarded until the first of the next month.

I'm not sure what else to check, but if you need more information please let me know.

regards, Pete

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello Pete,

It seems that you've misunderstood my latest update.
Your issue is not slmtag related...
The problem is a missing ISO tag (represented by a file with .swidtag extension), like following :
com.ibm_IBM_Workload_Automation_Agent-xxx.swidtag
ibm.com_IBM_Workload_Automation-xxx.swidtag
ibm.com_IBM_Workload_Scheduler_Agent_xxx.swidtag

A blind guess is that none of those ISO tags has ever been discovered by software scan.

As I wrote before,
'Mustgather' package (sha1 folder) should include some isotagsearch_xxx_isotag.zip file.
The question is which components has been discovered...

At last, you are welcome to open up the support ticket to give us a chance to look into Mustgather and verify additional logs & traces.

Hello again ;-)

You are correct that I am using BigFix and although the Initiate Software Scan fixlet was already active I have stopped everything and started again from scratch.

After running the Initiate Software Scan and waiting for it to complete I downloaded the MustGather data and within the zip file I have located the slmtagsearch_xxx_slmtag.zip file under the sha1_files folder. The contents of the slmtag*.zip is 2 files - a file named "1" that contains the content of the slmtag file for IWS Workload Automation (10_MONTHLY_JOBS) in XML format and a file named "list.txt" which contains the full path to the slmtag file itself (original location).

I then ran the import manually in ILMT and that appears to have worked successfully - the messages relating the the slmtag file import are

2023-11-20 14:43:17 (+0:00:00.000) INFO: Running LMT ETL SlmTagImport: Start
2023-11-20 14:43:18 (+0:00:00.234) WARN:  (ImportSlmTags-Thread:0) Some resource utilization metric values for ResourceUtilizationItem [persistentId=3303c35cbc08435080502d621d5cdbff, name=IBM Workload Automation, instanceId=/opt/IBM/TWA, publisher=null, version=null, type=10_MONTHLY_JOBS, subType=null] on computer 1 are from the future (after Mon Nov 20 14:43:18 UTC 2023). Discarding them and continue.
2023-11-20 14:43:19 (+0:00:00.845) INFO:  (ImportThread) com.ibm.license.mgmt.etl.core.actions.SlmTagImportStep::printStatistics::STATISTICS: Number of Slm import threads = 1, Number of computers = 1, Number of processed computers = 1, Number of processed good Slm archives = 1, Number of processed broken Slm archives = 0, Number of processed good Slm files = 1, Number of skipped (no valid metrics) Slm files = 0, Number of processed broken Slm files = 0, Number of updated first measured times = 0, Number of updated last measured times = 0, Number of updated rollups = 1
2023-11-20 14:43:19 (+0:00:00.014) INFO: Running LMT ETL SlmTagImport: Success

The future date is because of the end of this month being set - these are usually discarded until the first of the next month.

I'm not sure what else to check, but if you need more information please let me know.

regards, Pete

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello Oktawian,

Thanks for your explanation - I was concentrating on the slmtag files. The MustGather data contains an empty isotagsearch_xxx_isotag.zip file. I think this is because the slmtag generated from the IBM supplied query is located on a system that does not have any IWS software installed so there won't be a swidtag found on that system. This wasn't clear in the IWS documentation about where the slmtag file should be stored - only that it needed access to the IWS database.

I will move the slmtag file to a system that has IWS software installed (and will have an swidtag file present) and run the tests again. I'll update you with the results when I have them.

thanks for your help.

regards, Pete

Hello Pete,

It seems that you've misunderstood my latest update.
Your issue is not slmtag related...
The problem is a missing ISO tag (represented by a file with .swidtag extension), like following :
com.ibm_IBM_Workload_Automation_Agent-xxx.swidtag
ibm.com_IBM_Workload_Automation-xxx.swidtag
ibm.com_IBM_Workload_Scheduler_Agent_xxx.swidtag

A blind guess is that none of those ISO tags has ever been discovered by software scan.

As I wrote before,
'Mustgather' package (sha1 folder) should include some isotagsearch_xxx_isotag.zip file.
The question is which components has been discovered...

At last, you are welcome to open up the support ticket to give us a chance to look into Mustgather and verify additional logs & traces.

Hello again ;-)

You are correct that I am using BigFix and although the Initiate Software Scan fixlet was already active I have stopped everything and started again from scratch.

After running the Initiate Software Scan and waiting for it to complete I downloaded the MustGather data and within the zip file I have located the slmtagsearch_xxx_slmtag.zip file under the sha1_files folder. The contents of the slmtag*.zip is 2 files - a file named "1" that contains the content of the slmtag file for IWS Workload Automation (10_MONTHLY_JOBS) in XML format and a file named "list.txt" which contains the full path to the slmtag file itself (original location).

I then ran the import manually in ILMT and that appears to have worked successfully - the messages relating the the slmtag file import are

2023-11-20 14:43:17 (+0:00:00.000) INFO: Running LMT ETL SlmTagImport: Start
2023-11-20 14:43:18 (+0:00:00.234) WARN:  (ImportSlmTags-Thread:0) Some resource utilization metric values for ResourceUtilizationItem [persistentId=3303c35cbc08435080502d621d5cdbff, name=IBM Workload Automation, instanceId=/opt/IBM/TWA, publisher=null, version=null, type=10_MONTHLY_JOBS, subType=null] on computer 1 are from the future (after Mon Nov 20 14:43:18 UTC 2023). Discarding them and continue.
2023-11-20 14:43:19 (+0:00:00.845) INFO:  (ImportThread) com.ibm.license.mgmt.etl.core.actions.SlmTagImportStep::printStatistics::STATISTICS: Number of Slm import threads = 1, Number of computers = 1, Number of processed computers = 1, Number of processed good Slm archives = 1, Number of processed broken Slm archives = 0, Number of processed good Slm files = 1, Number of skipped (no valid metrics) Slm files = 0, Number of processed broken Slm files = 0, Number of updated first measured times = 0, Number of updated last measured times = 0, Number of updated rollups = 1
2023-11-20 14:43:19 (+0:00:00.014) INFO: Running LMT ETL SlmTagImport: Success

The future date is because of the end of this month being set - these are usually discarded until the first of the next month.

I'm not sure what else to check, but if you need more information please let me know.

regards, Pete

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello again Oktawian,

I have rebuilt my BigFix/ILMT test setup and reinstalled the BigFix agents to start from a completely blank sheet. IBM Workload Scheduler (IWS) is running in containers under docker (2 x DB2 containers, 1 x IWS server, 1 x DWC web console, 1 x AIDA) on clynelish-dca.

After running the scan the results are 

This shows that the scan has found swidtags for the various IWS components but none of them match the Product Name of IBM Workload Automation as shown by the Resource Utilization.

So is it simply a question of selecting all of these IWS components and assigning them to the IBM Workload Automation 10_MONTHLY_JOBS from the software catalog?

Note that one instance of WebSphere Liberty is bundled with IWS server and another with the DWC (web console)

Thanks in advance for your help.

regards, Pete

Hello Oktawian,

Thanks for your explanation - I was concentrating on the slmtag files. The MustGather data contains an empty isotagsearch_xxx_isotag.zip file. I think this is because the slmtag generated from the IBM supplied query is located on a system that does not have any IWS software installed so there won't be a swidtag found on that system. This wasn't clear in the IWS documentation about where the slmtag file should be stored - only that it needed access to the IWS database.

I will move the slmtag file to a system that has IWS software installed (and will have an swidtag file present) and run the tests again. I'll update you with the results when I have them.

thanks for your help.

regards, Pete

Hello Pete,

It seems that you've misunderstood my latest update.
Your issue is not slmtag related...
The problem is a missing ISO tag (represented by a file with .swidtag extension), like following :
com.ibm_IBM_Workload_Automation_Agent-xxx.swidtag
ibm.com_IBM_Workload_Automation-xxx.swidtag
ibm.com_IBM_Workload_Scheduler_Agent_xxx.swidtag

A blind guess is that none of those ISO tags has ever been discovered by software scan.

As I wrote before,
'Mustgather' package (sha1 folder) should include some isotagsearch_xxx_isotag.zip file.
The question is which components has been discovered...

At last, you are welcome to open up the support ticket to give us a chance to look into Mustgather and verify additional logs & traces.

Hello again ;-)

You are correct that I am using BigFix and although the Initiate Software Scan fixlet was already active I have stopped everything and started again from scratch.

After running the Initiate Software Scan and waiting for it to complete I downloaded the MustGather data and within the zip file I have located the slmtagsearch_xxx_slmtag.zip file under the sha1_files folder. The contents of the slmtag*.zip is 2 files - a file named "1" that contains the content of the slmtag file for IWS Workload Automation (10_MONTHLY_JOBS) in XML format and a file named "list.txt" which contains the full path to the slmtag file itself (original location).

I then ran the import manually in ILMT and that appears to have worked successfully - the messages relating the the slmtag file import are

2023-11-20 14:43:17 (+0:00:00.000) INFO: Running LMT ETL SlmTagImport: Start
2023-11-20 14:43:18 (+0:00:00.234) WARN:  (ImportSlmTags-Thread:0) Some resource utilization metric values for ResourceUtilizationItem [persistentId=3303c35cbc08435080502d621d5cdbff, name=IBM Workload Automation, instanceId=/opt/IBM/TWA, publisher=null, version=null, type=10_MONTHLY_JOBS, subType=null] on computer 1 are from the future (after Mon Nov 20 14:43:18 UTC 2023). Discarding them and continue.
2023-11-20 14:43:19 (+0:00:00.845) INFO:  (ImportThread) com.ibm.license.mgmt.etl.core.actions.SlmTagImportStep::printStatistics::STATISTICS: Number of Slm import threads = 1, Number of computers = 1, Number of processed computers = 1, Number of processed good Slm archives = 1, Number of processed broken Slm archives = 0, Number of processed good Slm files = 1, Number of skipped (no valid metrics) Slm files = 0, Number of processed broken Slm files = 0, Number of updated first measured times = 0, Number of updated last measured times = 0, Number of updated rollups = 1
2023-11-20 14:43:19 (+0:00:00.014) INFO: Running LMT ETL SlmTagImport: Success

The future date is because of the end of this month being set - these are usually discarded until the first of the next month.

I'm not sure what else to check, but if you need more information please let me know.

regards, Pete

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello Pete,

The problem is that Resource Utilization report itself doesn't allow to unequivocally confirm if that 'IBM Workload Automation' entry is a product (less probable) or just a component.
'IBM Workload Automation' name can reflect both.
Re-assigning those components would make sense only if that Resource Utilization report entry represent a product.

I'd need to get this slm tag file to import that on my own and see how it's being mapped...
So, either please open up the support ticket to us (preferable mainly due to security concerns) or attach here that slm tag for investigation...

Hello again Oktawian,

I have rebuilt my BigFix/ILMT test setup and reinstalled the BigFix agents to start from a completely blank sheet. IBM Workload Scheduler (IWS) is running in containers under docker (2 x DB2 containers, 1 x IWS server, 1 x DWC web console, 1 x AIDA) on clynelish-dca.

After running the scan the results are 

This shows that the scan has found swidtags for the various IWS components but none of them match the Product Name of IBM Workload Automation as shown by the Resource Utilization.

So is it simply a question of selecting all of these IWS components and assigning them to the IBM Workload Automation 10_MONTHLY_JOBS from the software catalog?

Note that one instance of WebSphere Liberty is bundled with IWS server and another with the DWC (web console)

Thanks in advance for your help.

regards, Pete

Hello Oktawian,

Thanks for your explanation - I was concentrating on the slmtag files. The MustGather data contains an empty isotagsearch_xxx_isotag.zip file. I think this is because the slmtag generated from the IBM supplied query is located on a system that does not have any IWS software installed so there won't be a swidtag found on that system. This wasn't clear in the IWS documentation about where the slmtag file should be stored - only that it needed access to the IWS database.

I will move the slmtag file to a system that has IWS software installed (and will have an swidtag file present) and run the tests again. I'll update you with the results when I have them.

thanks for your help.

regards, Pete

Hello Pete,

It seems that you've misunderstood my latest update.
Your issue is not slmtag related...
The problem is a missing ISO tag (represented by a file with .swidtag extension), like following :
com.ibm_IBM_Workload_Automation_Agent-xxx.swidtag
ibm.com_IBM_Workload_Automation-xxx.swidtag
ibm.com_IBM_Workload_Scheduler_Agent_xxx.swidtag

A blind guess is that none of those ISO tags has ever been discovered by software scan.

As I wrote before,
'Mustgather' package (sha1 folder) should include some isotagsearch_xxx_isotag.zip file.
The question is which components has been discovered...

At last, you are welcome to open up the support ticket to give us a chance to look into Mustgather and verify additional logs & traces.

Hello again ;-)

You are correct that I am using BigFix and although the Initiate Software Scan fixlet was already active I have stopped everything and started again from scratch.

After running the Initiate Software Scan and waiting for it to complete I downloaded the MustGather data and within the zip file I have located the slmtagsearch_xxx_slmtag.zip file under the sha1_files folder. The contents of the slmtag*.zip is 2 files - a file named "1" that contains the content of the slmtag file for IWS Workload Automation (10_MONTHLY_JOBS) in XML format and a file named "list.txt" which contains the full path to the slmtag file itself (original location).

I then ran the import manually in ILMT and that appears to have worked successfully - the messages relating the the slmtag file import are

2023-11-20 14:43:17 (+0:00:00.000) INFO: Running LMT ETL SlmTagImport: Start
2023-11-20 14:43:18 (+0:00:00.234) WARN:  (ImportSlmTags-Thread:0) Some resource utilization metric values for ResourceUtilizationItem [persistentId=3303c35cbc08435080502d621d5cdbff, name=IBM Workload Automation, instanceId=/opt/IBM/TWA, publisher=null, version=null, type=10_MONTHLY_JOBS, subType=null] on computer 1 are from the future (after Mon Nov 20 14:43:18 UTC 2023). Discarding them and continue.
2023-11-20 14:43:19 (+0:00:00.845) INFO:  (ImportThread) com.ibm.license.mgmt.etl.core.actions.SlmTagImportStep::printStatistics::STATISTICS: Number of Slm import threads = 1, Number of computers = 1, Number of processed computers = 1, Number of processed good Slm archives = 1, Number of processed broken Slm archives = 0, Number of processed good Slm files = 1, Number of skipped (no valid metrics) Slm files = 0, Number of processed broken Slm files = 0, Number of updated first measured times = 0, Number of updated last measured times = 0, Number of updated rollups = 1
2023-11-20 14:43:19 (+0:00:00.014) INFO: Running LMT ETL SlmTagImport: Success

The future date is because of the end of this month being set - these are usually discarded until the first of the next month.

I'm not sure what else to check, but if you need more information please let me know.

regards, Pete

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello Oktawian,

Thank you again for your help with this. The slmtag file produced by the IBM supplied query only contains a set of numbers representing the "peak" of successfully executed jobs per month over the previous 12 month period. As my test IWS system doesn't really have that level of information, I have used a copy from a real production IWS system and "fabricated" the numbers for my testing requirements so I am happy to post the content here as there isn't any sensitive information contained therein. The contents are included below.

 <SchemaVersion>2.1.1</SchemaVersion>  <SoftwareIdentity>  <Name>IBM Workload Automation</Name>  <PersistentId>3303c35cbc08435080502d621d5cdbff</PersistentId>  <InstanceId>/opt/IBM/TWA</InstanceId>  </SoftwareIdentity>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>90</Value>  <Period><StartTime>2022-10-01T00:00:01+00:00</StartTime>  <EndTime>2022-10-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>91</Value>  <Period><StartTime>2022-11-01T00:00:01+00:00</StartTime>  <EndTime>2022-11-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>89</Value>  <Period><StartTime>2022-12-01T00:00:01+00:00</StartTime>  <EndTime>2022-12-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>93</Value>  <Period><StartTime>2023-01-01T00:00:01+00:00</StartTime>  <EndTime>2023-01-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>85</Value>  <Period><StartTime>2023-02-01T00:00:01+00:00</StartTime>  <EndTime>2023-02-28T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>97</Value>  <Period><StartTime>2023-03-01T00:00:01+00:00</StartTime>  <EndTime>2023-03-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>92</Value>  <Period><StartTime>2023-04-01T00:00:01+00:00</StartTime>  <EndTime>2023-04-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>84</Value>  <Period><StartTime>2023-05-01T00:00:01+00:00</StartTime>  <EndTime>2023-05-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>73</Value>  <Period><StartTime>2023-06-01T00:00:01+00:00</StartTime>  <EndTime>2023-06-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>106</Value>  <Period><StartTime>2023-07-01T00:00:01+00:00</StartTime>  <EndTime>2023-07-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>88</Value>  <Period><StartTime>2023-08-01T00:00:01+00:00</StartTime>  <EndTime>2023-08-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>89</Value>  <Period><StartTime>2023-09-01T00:00:01+00:00</StartTime>  <EndTime>2023-09-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>98</Value>  <Period><StartTime>2023-10-01T00:00:01+00:00</StartTime>  <EndTime>2023-10-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>102</Value>  <Period><StartTime>2023-11-01T00:00:01+00:00</StartTime>  <EndTime>2023-11-30T23:59:00+00:00</EndTime>  </Period></Metric>

Please let me know if you require any additional information.

regards, Pete

Hello Pete,

The problem is that Resource Utilization report itself doesn't allow to unequivocally confirm if that 'IBM Workload Automation' entry is a product (less probable) or just a component.
'IBM Workload Automation' name can reflect both.
Re-assigning those components would make sense only if that Resource Utilization report entry represent a product.

I'd need to get this slm tag file to import that on my own and see how it's being mapped...
So, either please open up the support ticket to us (preferable mainly due to security concerns) or attach here that slm tag for investigation...

Hello again Oktawian,

I have rebuilt my BigFix/ILMT test setup and reinstalled the BigFix agents to start from a completely blank sheet. IBM Workload Scheduler (IWS) is running in containers under docker (2 x DB2 containers, 1 x IWS server, 1 x DWC web console, 1 x AIDA) on clynelish-dca.

After running the scan the results are 

This shows that the scan has found swidtags for the various IWS components but none of them match the Product Name of IBM Workload Automation as shown by the Resource Utilization.

So is it simply a question of selecting all of these IWS components and assigning them to the IBM Workload Automation 10_MONTHLY_JOBS from the software catalog?

Note that one instance of WebSphere Liberty is bundled with IWS server and another with the DWC (web console)

Thanks in advance for your help.

regards, Pete

Hello Oktawian,

Thanks for your explanation - I was concentrating on the slmtag files. The MustGather data contains an empty isotagsearch_xxx_isotag.zip file. I think this is because the slmtag generated from the IBM supplied query is located on a system that does not have any IWS software installed so there won't be a swidtag found on that system. This wasn't clear in the IWS documentation about where the slmtag file should be stored - only that it needed access to the IWS database.

I will move the slmtag file to a system that has IWS software installed (and will have an swidtag file present) and run the tests again. I'll update you with the results when I have them.

thanks for your help.

regards, Pete

Hello Pete,

It seems that you've misunderstood my latest update.
Your issue is not slmtag related...
The problem is a missing ISO tag (represented by a file with .swidtag extension), like following :
com.ibm_IBM_Workload_Automation_Agent-xxx.swidtag
ibm.com_IBM_Workload_Automation-xxx.swidtag
ibm.com_IBM_Workload_Scheduler_Agent_xxx.swidtag

A blind guess is that none of those ISO tags has ever been discovered by software scan.

As I wrote before,
'Mustgather' package (sha1 folder) should include some isotagsearch_xxx_isotag.zip file.
The question is which components has been discovered...

At last, you are welcome to open up the support ticket to give us a chance to look into Mustgather and verify additional logs & traces.

Hello again ;-)

You are correct that I am using BigFix and although the Initiate Software Scan fixlet was already active I have stopped everything and started again from scratch.

After running the Initiate Software Scan and waiting for it to complete I downloaded the MustGather data and within the zip file I have located the slmtagsearch_xxx_slmtag.zip file under the sha1_files folder. The contents of the slmtag*.zip is 2 files - a file named "1" that contains the content of the slmtag file for IWS Workload Automation (10_MONTHLY_JOBS) in XML format and a file named "list.txt" which contains the full path to the slmtag file itself (original location).

I then ran the import manually in ILMT and that appears to have worked successfully - the messages relating the the slmtag file import are

2023-11-20 14:43:17 (+0:00:00.000) INFO: Running LMT ETL SlmTagImport: Start
2023-11-20 14:43:18 (+0:00:00.234) WARN:  (ImportSlmTags-Thread:0) Some resource utilization metric values for ResourceUtilizationItem [persistentId=3303c35cbc08435080502d621d5cdbff, name=IBM Workload Automation, instanceId=/opt/IBM/TWA, publisher=null, version=null, type=10_MONTHLY_JOBS, subType=null] on computer 1 are from the future (after Mon Nov 20 14:43:18 UTC 2023). Discarding them and continue.
2023-11-20 14:43:19 (+0:00:00.845) INFO:  (ImportThread) com.ibm.license.mgmt.etl.core.actions.SlmTagImportStep::printStatistics::STATISTICS: Number of Slm import threads = 1, Number of computers = 1, Number of processed computers = 1, Number of processed good Slm archives = 1, Number of processed broken Slm archives = 0, Number of processed good Slm files = 1, Number of skipped (no valid metrics) Slm files = 0, Number of processed broken Slm files = 0, Number of updated first measured times = 0, Number of updated last measured times = 0, Number of updated rollups = 1
2023-11-20 14:43:19 (+0:00:00.014) INFO: Running LMT ETL SlmTagImport: Success

The future date is because of the end of this month being set - these are usually discarded until the first of the next month.

I'm not sure what else to check, but if you need more information please let me know.

regards, Pete

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello Pete,

I've checked that slm tag file and definitely that 'IBM Workload Automation' entry is being discovered as a component (as vast majority of the slm tag discoveries).

So, we are back at square one...
What you need is a corresponding ISO tag (with PersistentId/GUID: 3303c35cbc08435080502d621d5cdbff) which should be discovered during software scan.
Than you will see dedicated entry on Software Classification panel...

You would have to ask their product support team why such ISO tag is not being placed at the location where IWS software is being installed.

Hello Oktawian,

Thank you again for your help with this. The slmtag file produced by the IBM supplied query only contains a set of numbers representing the "peak" of successfully executed jobs per month over the previous 12 month period. As my test IWS system doesn't really have that level of information, I have used a copy from a real production IWS system and "fabricated" the numbers for my testing requirements so I am happy to post the content here as there isn't any sensitive information contained therein. The contents are included below.

 <SchemaVersion>2.1.1</SchemaVersion>  <SoftwareIdentity>  <Name>IBM Workload Automation</Name>  <PersistentId>3303c35cbc08435080502d621d5cdbff</PersistentId>  <InstanceId>/opt/IBM/TWA</InstanceId>  </SoftwareIdentity>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>90</Value>  <Period><StartTime>2022-10-01T00:00:01+00:00</StartTime>  <EndTime>2022-10-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>91</Value>  <Period><StartTime>2022-11-01T00:00:01+00:00</StartTime>  <EndTime>2022-11-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>89</Value>  <Period><StartTime>2022-12-01T00:00:01+00:00</StartTime>  <EndTime>2022-12-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>93</Value>  <Period><StartTime>2023-01-01T00:00:01+00:00</StartTime>  <EndTime>2023-01-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>85</Value>  <Period><StartTime>2023-02-01T00:00:01+00:00</StartTime>  <EndTime>2023-02-28T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>97</Value>  <Period><StartTime>2023-03-01T00:00:01+00:00</StartTime>  <EndTime>2023-03-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>92</Value>  <Period><StartTime>2023-04-01T00:00:01+00:00</StartTime>  <EndTime>2023-04-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>84</Value>  <Period><StartTime>2023-05-01T00:00:01+00:00</StartTime>  <EndTime>2023-05-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>73</Value>  <Period><StartTime>2023-06-01T00:00:01+00:00</StartTime>  <EndTime>2023-06-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>106</Value>  <Period><StartTime>2023-07-01T00:00:01+00:00</StartTime>  <EndTime>2023-07-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>88</Value>  <Period><StartTime>2023-08-01T00:00:01+00:00</StartTime>  <EndTime>2023-08-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>89</Value>  <Period><StartTime>2023-09-01T00:00:01+00:00</StartTime>  <EndTime>2023-09-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>98</Value>  <Period><StartTime>2023-10-01T00:00:01+00:00</StartTime>  <EndTime>2023-10-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>102</Value>  <Period><StartTime>2023-11-01T00:00:01+00:00</StartTime>  <EndTime>2023-11-30T23:59:00+00:00</EndTime>  </Period></Metric>

Please let me know if you require any additional information.

regards, Pete

Hello Pete,

The problem is that Resource Utilization report itself doesn't allow to unequivocally confirm if that 'IBM Workload Automation' entry is a product (less probable) or just a component.
'IBM Workload Automation' name can reflect both.
Re-assigning those components would make sense only if that Resource Utilization report entry represent a product.

I'd need to get this slm tag file to import that on my own and see how it's being mapped...
So, either please open up the support ticket to us (preferable mainly due to security concerns) or attach here that slm tag for investigation...

Hello again Oktawian,

I have rebuilt my BigFix/ILMT test setup and reinstalled the BigFix agents to start from a completely blank sheet. IBM Workload Scheduler (IWS) is running in containers under docker (2 x DB2 containers, 1 x IWS server, 1 x DWC web console, 1 x AIDA) on clynelish-dca.

After running the scan the results are 

This shows that the scan has found swidtags for the various IWS components but none of them match the Product Name of IBM Workload Automation as shown by the Resource Utilization.

So is it simply a question of selecting all of these IWS components and assigning them to the IBM Workload Automation 10_MONTHLY_JOBS from the software catalog?

Note that one instance of WebSphere Liberty is bundled with IWS server and another with the DWC (web console)

Thanks in advance for your help.

regards, Pete

Hello Oktawian,

Thanks for your explanation - I was concentrating on the slmtag files. The MustGather data contains an empty isotagsearch_xxx_isotag.zip file. I think this is because the slmtag generated from the IBM supplied query is located on a system that does not have any IWS software installed so there won't be a swidtag found on that system. This wasn't clear in the IWS documentation about where the slmtag file should be stored - only that it needed access to the IWS database.

I will move the slmtag file to a system that has IWS software installed (and will have an swidtag file present) and run the tests again. I'll update you with the results when I have them.

thanks for your help.

regards, Pete

Hello Pete,

It seems that you've misunderstood my latest update.
Your issue is not slmtag related...
The problem is a missing ISO tag (represented by a file with .swidtag extension), like following :
com.ibm_IBM_Workload_Automation_Agent-xxx.swidtag
ibm.com_IBM_Workload_Automation-xxx.swidtag
ibm.com_IBM_Workload_Scheduler_Agent_xxx.swidtag

A blind guess is that none of those ISO tags has ever been discovered by software scan.

As I wrote before,
'Mustgather' package (sha1 folder) should include some isotagsearch_xxx_isotag.zip file.
The question is which components has been discovered...

At last, you are welcome to open up the support ticket to give us a chance to look into Mustgather and verify additional logs & traces.

Hello again ;-)

You are correct that I am using BigFix and although the Initiate Software Scan fixlet was already active I have stopped everything and started again from scratch.

After running the Initiate Software Scan and waiting for it to complete I downloaded the MustGather data and within the zip file I have located the slmtagsearch_xxx_slmtag.zip file under the sha1_files folder. The contents of the slmtag*.zip is 2 files - a file named "1" that contains the content of the slmtag file for IWS Workload Automation (10_MONTHLY_JOBS) in XML format and a file named "list.txt" which contains the full path to the slmtag file itself (original location).

I then ran the import manually in ILMT and that appears to have worked successfully - the messages relating the the slmtag file import are

2023-11-20 14:43:17 (+0:00:00.000) INFO: Running LMT ETL SlmTagImport: Start
2023-11-20 14:43:18 (+0:00:00.234) WARN:  (ImportSlmTags-Thread:0) Some resource utilization metric values for ResourceUtilizationItem [persistentId=3303c35cbc08435080502d621d5cdbff, name=IBM Workload Automation, instanceId=/opt/IBM/TWA, publisher=null, version=null, type=10_MONTHLY_JOBS, subType=null] on computer 1 are from the future (after Mon Nov 20 14:43:18 UTC 2023). Discarding them and continue.
2023-11-20 14:43:19 (+0:00:00.845) INFO:  (ImportThread) com.ibm.license.mgmt.etl.core.actions.SlmTagImportStep::printStatistics::STATISTICS: Number of Slm import threads = 1, Number of computers = 1, Number of processed computers = 1, Number of processed good Slm archives = 1, Number of processed broken Slm archives = 0, Number of processed good Slm files = 1, Number of skipped (no valid metrics) Slm files = 0, Number of processed broken Slm files = 0, Number of updated first measured times = 0, Number of updated last measured times = 0, Number of updated rollups = 1
2023-11-20 14:43:19 (+0:00:00.014) INFO: Running LMT ETL SlmTagImport: Success

The future date is because of the end of this month being set - these are usually discarded until the first of the next month.

I'm not sure what else to check, but if you need more information please let me know.

regards, Pete

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello Oktawian,

Thanks for the update. 

I have just scanned the various IWS software installation images looking for "tag" files and the only ones present in any of the installation images are swidtag files. Are these the same as the ISO tag files you are referring to?

I can't find any swidtag files that contain the PersistentID you refer to above - all of them specify a different value

Would it be possible to explain the difference between the different tag files i.e. isotag, swidtag and slmtag? 

regards, Pete

Hello Pete,

I've checked that slm tag file and definitely that 'IBM Workload Automation' entry is being discovered as a component (as vast majority of the slm tag discoveries).

So, we are back at square one...
What you need is a corresponding ISO tag (with PersistentId/GUID: 3303c35cbc08435080502d621d5cdbff) which should be discovered during software scan.
Than you will see dedicated entry on Software Classification panel...

You would have to ask their product support team why such ISO tag is not being placed at the location where IWS software is being installed.

Hello Oktawian,

Thank you again for your help with this. The slmtag file produced by the IBM supplied query only contains a set of numbers representing the "peak" of successfully executed jobs per month over the previous 12 month period. As my test IWS system doesn't really have that level of information, I have used a copy from a real production IWS system and "fabricated" the numbers for my testing requirements so I am happy to post the content here as there isn't any sensitive information contained therein. The contents are included below.

 <SchemaVersion>2.1.1</SchemaVersion>  <SoftwareIdentity>  <Name>IBM Workload Automation</Name>  <PersistentId>3303c35cbc08435080502d621d5cdbff</PersistentId>  <InstanceId>/opt/IBM/TWA</InstanceId>  </SoftwareIdentity>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>90</Value>  <Period><StartTime>2022-10-01T00:00:01+00:00</StartTime>  <EndTime>2022-10-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>91</Value>  <Period><StartTime>2022-11-01T00:00:01+00:00</StartTime>  <EndTime>2022-11-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>89</Value>  <Period><StartTime>2022-12-01T00:00:01+00:00</StartTime>  <EndTime>2022-12-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>93</Value>  <Period><StartTime>2023-01-01T00:00:01+00:00</StartTime>  <EndTime>2023-01-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>85</Value>  <Period><StartTime>2023-02-01T00:00:01+00:00</StartTime>  <EndTime>2023-02-28T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>97</Value>  <Period><StartTime>2023-03-01T00:00:01+00:00</StartTime>  <EndTime>2023-03-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>92</Value>  <Period><StartTime>2023-04-01T00:00:01+00:00</StartTime>  <EndTime>2023-04-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>84</Value>  <Period><StartTime>2023-05-01T00:00:01+00:00</StartTime>  <EndTime>2023-05-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>73</Value>  <Period><StartTime>2023-06-01T00:00:01+00:00</StartTime>  <EndTime>2023-06-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>106</Value>  <Period><StartTime>2023-07-01T00:00:01+00:00</StartTime>  <EndTime>2023-07-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>88</Value>  <Period><StartTime>2023-08-01T00:00:01+00:00</StartTime>  <EndTime>2023-08-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>89</Value>  <Period><StartTime>2023-09-01T00:00:01+00:00</StartTime>  <EndTime>2023-09-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>98</Value>  <Period><StartTime>2023-10-01T00:00:01+00:00</StartTime>  <EndTime>2023-10-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>102</Value>  <Period><StartTime>2023-11-01T00:00:01+00:00</StartTime>  <EndTime>2023-11-30T23:59:00+00:00</EndTime>  </Period></Metric>

Please let me know if you require any additional information.

regards, Pete

Hello Pete,

The problem is that Resource Utilization report itself doesn't allow to unequivocally confirm if that 'IBM Workload Automation' entry is a product (less probable) or just a component.
'IBM Workload Automation' name can reflect both.
Re-assigning those components would make sense only if that Resource Utilization report entry represent a product.

I'd need to get this slm tag file to import that on my own and see how it's being mapped...
So, either please open up the support ticket to us (preferable mainly due to security concerns) or attach here that slm tag for investigation...

Hello again Oktawian,

I have rebuilt my BigFix/ILMT test setup and reinstalled the BigFix agents to start from a completely blank sheet. IBM Workload Scheduler (IWS) is running in containers under docker (2 x DB2 containers, 1 x IWS server, 1 x DWC web console, 1 x AIDA) on clynelish-dca.

After running the scan the results are 

This shows that the scan has found swidtags for the various IWS components but none of them match the Product Name of IBM Workload Automation as shown by the Resource Utilization.

So is it simply a question of selecting all of these IWS components and assigning them to the IBM Workload Automation 10_MONTHLY_JOBS from the software catalog?

Note that one instance of WebSphere Liberty is bundled with IWS server and another with the DWC (web console)

Thanks in advance for your help.

regards, Pete

Hello Oktawian,

Thanks for your explanation - I was concentrating on the slmtag files. The MustGather data contains an empty isotagsearch_xxx_isotag.zip file. I think this is because the slmtag generated from the IBM supplied query is located on a system that does not have any IWS software installed so there won't be a swidtag found on that system. This wasn't clear in the IWS documentation about where the slmtag file should be stored - only that it needed access to the IWS database.

I will move the slmtag file to a system that has IWS software installed (and will have an swidtag file present) and run the tests again. I'll update you with the results when I have them.

thanks for your help.

regards, Pete

Hello Pete,

It seems that you've misunderstood my latest update.
Your issue is not slmtag related...
The problem is a missing ISO tag (represented by a file with .swidtag extension), like following :
com.ibm_IBM_Workload_Automation_Agent-xxx.swidtag
ibm.com_IBM_Workload_Automation-xxx.swidtag
ibm.com_IBM_Workload_Scheduler_Agent_xxx.swidtag

A blind guess is that none of those ISO tags has ever been discovered by software scan.

As I wrote before,
'Mustgather' package (sha1 folder) should include some isotagsearch_xxx_isotag.zip file.
The question is which components has been discovered...

At last, you are welcome to open up the support ticket to give us a chance to look into Mustgather and verify additional logs & traces.

Hello again ;-)

You are correct that I am using BigFix and although the Initiate Software Scan fixlet was already active I have stopped everything and started again from scratch.

After running the Initiate Software Scan and waiting for it to complete I downloaded the MustGather data and within the zip file I have located the slmtagsearch_xxx_slmtag.zip file under the sha1_files folder. The contents of the slmtag*.zip is 2 files - a file named "1" that contains the content of the slmtag file for IWS Workload Automation (10_MONTHLY_JOBS) in XML format and a file named "list.txt" which contains the full path to the slmtag file itself (original location).

I then ran the import manually in ILMT and that appears to have worked successfully - the messages relating the the slmtag file import are

2023-11-20 14:43:17 (+0:00:00.000) INFO: Running LMT ETL SlmTagImport: Start
2023-11-20 14:43:18 (+0:00:00.234) WARN:  (ImportSlmTags-Thread:0) Some resource utilization metric values for ResourceUtilizationItem [persistentId=3303c35cbc08435080502d621d5cdbff, name=IBM Workload Automation, instanceId=/opt/IBM/TWA, publisher=null, version=null, type=10_MONTHLY_JOBS, subType=null] on computer 1 are from the future (after Mon Nov 20 14:43:18 UTC 2023). Discarding them and continue.
2023-11-20 14:43:19 (+0:00:00.845) INFO:  (ImportThread) com.ibm.license.mgmt.etl.core.actions.SlmTagImportStep::printStatistics::STATISTICS: Number of Slm import threads = 1, Number of computers = 1, Number of processed computers = 1, Number of processed good Slm archives = 1, Number of processed broken Slm archives = 0, Number of processed good Slm files = 1, Number of skipped (no valid metrics) Slm files = 0, Number of processed broken Slm files = 0, Number of updated first measured times = 0, Number of updated last measured times = 0, Number of updated rollups = 1
2023-11-20 14:43:19 (+0:00:00.014) INFO: Running LMT ETL SlmTagImport: Success

The future date is because of the end of this month being set - these are usually discarded until the first of the next month.

I'm not sure what else to check, but if you need more information please let me know.

regards, Pete

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.

Hello Pete,

Correct,
ISO tag files are the files with .swidtag extension...
(you can find a statement in one of my previous updates: The problem is a missing ISO tag (represented by a file with .swidtag extension)

'ibm.com_IBM_Workload_Automation-x.x.x.swidtag' is the dedicated ISO tag for 'IBM Workload Automation'

Hello Oktawian,

Thanks for the update. 

I have just scanned the various IWS software installation images looking for "tag" files and the only ones present in any of the installation images are swidtag files. Are these the same as the ISO tag files you are referring to?

I can't find any swidtag files that contain the PersistentID you refer to above - all of them specify a different value

Would it be possible to explain the difference between the different tag files i.e. isotag, swidtag and slmtag? 

regards, Pete

Hello Pete,

I've checked that slm tag file and definitely that 'IBM Workload Automation' entry is being discovered as a component (as vast majority of the slm tag discoveries).

So, we are back at square one...
What you need is a corresponding ISO tag (with PersistentId/GUID: 3303c35cbc08435080502d621d5cdbff) which should be discovered during software scan.
Than you will see dedicated entry on Software Classification panel...

You would have to ask their product support team why such ISO tag is not being placed at the location where IWS software is being installed.

Hello Oktawian,

Thank you again for your help with this. The slmtag file produced by the IBM supplied query only contains a set of numbers representing the "peak" of successfully executed jobs per month over the previous 12 month period. As my test IWS system doesn't really have that level of information, I have used a copy from a real production IWS system and "fabricated" the numbers for my testing requirements so I am happy to post the content here as there isn't any sensitive information contained therein. The contents are included below.

 <SchemaVersion>2.1.1</SchemaVersion>  <SoftwareIdentity>  <Name>IBM Workload Automation</Name>  <PersistentId>3303c35cbc08435080502d621d5cdbff</PersistentId>  <InstanceId>/opt/IBM/TWA</InstanceId>  </SoftwareIdentity>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>90</Value>  <Period><StartTime>2022-10-01T00:00:01+00:00</StartTime>  <EndTime>2022-10-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>91</Value>  <Period><StartTime>2022-11-01T00:00:01+00:00</StartTime>  <EndTime>2022-11-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>89</Value>  <Period><StartTime>2022-12-01T00:00:01+00:00</StartTime>  <EndTime>2022-12-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>93</Value>  <Period><StartTime>2023-01-01T00:00:01+00:00</StartTime>  <EndTime>2023-01-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>85</Value>  <Period><StartTime>2023-02-01T00:00:01+00:00</StartTime>  <EndTime>2023-02-28T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>97</Value>  <Period><StartTime>2023-03-01T00:00:01+00:00</StartTime>  <EndTime>2023-03-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>92</Value>  <Period><StartTime>2023-04-01T00:00:01+00:00</StartTime>  <EndTime>2023-04-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>84</Value>  <Period><StartTime>2023-05-01T00:00:01+00:00</StartTime>  <EndTime>2023-05-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>73</Value>  <Period><StartTime>2023-06-01T00:00:01+00:00</StartTime>  <EndTime>2023-06-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>106</Value>  <Period><StartTime>2023-07-01T00:00:01+00:00</StartTime>  <EndTime>2023-07-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>88</Value>  <Period><StartTime>2023-08-01T00:00:01+00:00</StartTime>  <EndTime>2023-08-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>89</Value>  <Period><StartTime>2023-09-01T00:00:01+00:00</StartTime>  <EndTime>2023-09-30T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>98</Value>  <Period><StartTime>2023-10-01T00:00:01+00:00</StartTime>  <EndTime>2023-10-31T23:59:00+00:00</EndTime>  </Period></Metric>
 <Metric logTime="2023-11-20T13:47:38+00:00">  <Type>10_MONTHLY_JOBS</Type>  <Value>102</Value>  <Period><StartTime>2023-11-01T00:00:01+00:00</StartTime>  <EndTime>2023-11-30T23:59:00+00:00</EndTime>  </Period></Metric>

Please let me know if you require any additional information.

regards, Pete

Hello Pete,

The problem is that Resource Utilization report itself doesn't allow to unequivocally confirm if that 'IBM Workload Automation' entry is a product (less probable) or just a component.
'IBM Workload Automation' name can reflect both.
Re-assigning those components would make sense only if that Resource Utilization report entry represent a product.

I'd need to get this slm tag file to import that on my own and see how it's being mapped...
So, either please open up the support ticket to us (preferable mainly due to security concerns) or attach here that slm tag for investigation...

Hello again Oktawian,

I have rebuilt my BigFix/ILMT test setup and reinstalled the BigFix agents to start from a completely blank sheet. IBM Workload Scheduler (IWS) is running in containers under docker (2 x DB2 containers, 1 x IWS server, 1 x DWC web console, 1 x AIDA) on clynelish-dca.

After running the scan the results are 

This shows that the scan has found swidtags for the various IWS components but none of them match the Product Name of IBM Workload Automation as shown by the Resource Utilization.

So is it simply a question of selecting all of these IWS components and assigning them to the IBM Workload Automation 10_MONTHLY_JOBS from the software catalog?

Note that one instance of WebSphere Liberty is bundled with IWS server and another with the DWC (web console)

Thanks in advance for your help.

regards, Pete

Hello Oktawian,

Thanks for your explanation - I was concentrating on the slmtag files. The MustGather data contains an empty isotagsearch_xxx_isotag.zip file. I think this is because the slmtag generated from the IBM supplied query is located on a system that does not have any IWS software installed so there won't be a swidtag found on that system. This wasn't clear in the IWS documentation about where the slmtag file should be stored - only that it needed access to the IWS database.

I will move the slmtag file to a system that has IWS software installed (and will have an swidtag file present) and run the tests again. I'll update you with the results when I have them.

thanks for your help.

regards, Pete

Hello Pete,

It seems that you've misunderstood my latest update.
Your issue is not slmtag related...
The problem is a missing ISO tag (represented by a file with .swidtag extension), like following :
com.ibm_IBM_Workload_Automation_Agent-xxx.swidtag
ibm.com_IBM_Workload_Automation-xxx.swidtag
ibm.com_IBM_Workload_Scheduler_Agent_xxx.swidtag

A blind guess is that none of those ISO tags has ever been discovered by software scan.

As I wrote before,
'Mustgather' package (sha1 folder) should include some isotagsearch_xxx_isotag.zip file.
The question is which components has been discovered...

At last, you are welcome to open up the support ticket to give us a chance to look into Mustgather and verify additional logs & traces.

Hello again ;-)

You are correct that I am using BigFix and although the Initiate Software Scan fixlet was already active I have stopped everything and started again from scratch.

After running the Initiate Software Scan and waiting for it to complete I downloaded the MustGather data and within the zip file I have located the slmtagsearch_xxx_slmtag.zip file under the sha1_files folder. The contents of the slmtag*.zip is 2 files - a file named "1" that contains the content of the slmtag file for IWS Workload Automation (10_MONTHLY_JOBS) in XML format and a file named "list.txt" which contains the full path to the slmtag file itself (original location).

I then ran the import manually in ILMT and that appears to have worked successfully - the messages relating the the slmtag file import are

2023-11-20 14:43:17 (+0:00:00.000) INFO: Running LMT ETL SlmTagImport: Start
2023-11-20 14:43:18 (+0:00:00.234) WARN:  (ImportSlmTags-Thread:0) Some resource utilization metric values for ResourceUtilizationItem [persistentId=3303c35cbc08435080502d621d5cdbff, name=IBM Workload Automation, instanceId=/opt/IBM/TWA, publisher=null, version=null, type=10_MONTHLY_JOBS, subType=null] on computer 1 are from the future (after Mon Nov 20 14:43:18 UTC 2023). Discarding them and continue.
2023-11-20 14:43:19 (+0:00:00.845) INFO:  (ImportThread) com.ibm.license.mgmt.etl.core.actions.SlmTagImportStep::printStatistics::STATISTICS: Number of Slm import threads = 1, Number of computers = 1, Number of processed computers = 1, Number of processed good Slm archives = 1, Number of processed broken Slm archives = 0, Number of processed good Slm files = 1, Number of skipped (no valid metrics) Slm files = 0, Number of processed broken Slm files = 0, Number of updated first measured times = 0, Number of updated last measured times = 0, Number of updated rollups = 1
2023-11-20 14:43:19 (+0:00:00.014) INFO: Running LMT ETL SlmTagImport: Success

The future date is because of the end of this month being set - these are usually discarded until the first of the next month.

I'm not sure what else to check, but if you need more information please let me know.

regards, Pete

Hello again,

Software Components / Products & Metrics reports display information about software components existing in ILMT catalog (definitions of all IBM products) NOT what has been discovered by your software scan.
If IBM Workload Automation is not listed in the Software Classification panel it means that either a corresponding ISO tag has never been discovered during software scan or some issues with import process.

From the context I understand that you are using BigFix actions to run software scan, so at first please verify the 'Initiate Software Scan' action output:
https://www.ibm.com/docs/en/license-metric-tool?topic=configuration-step-3-initiating-software-scans

The complete software scan output should be accessible through the so called 'Mustgather' package :
https://www.ibm.com/docs/en/license-metric-tool?topic=computers-collecting-logs-troubleshooting-purposes
Look inside isotagsearch_xxx_isotag.zip file...you should see a dedicated ISO tag file for IBM Workload Automation.

TEN_MONTHLY_JOBS / 10_MONTHLY_JOBS both means the same thing...just synonyms.

Hello Oktawian,

Thanks for the reply. I have been looking into this a bit more and it appears that IBM Workload Automation is not listed in the Software Classification panel - the results below are filtered on entries containing "Workload" in the Component Name field

It does appear in Software Components

and also in Products & Metrics

According to the link here https://www.ibm.com/support/pages/node/1281988 IWS is listed as a product that delivers SLM tag files and the CSV file contains the following entries

I noticed that the SLMtag file specifies <Type>10_MONTHLY_JOBS</Type> whereas the ILMT documentation here https://www.ibm.com/docs/en/license-metric-tool?topic=v2-metric-ids-code-names specifies TEN_MONTHLY_JOBS as the Metric code name - could that have something to do with this issue?

Thanks for your help with this.

regards, Pete

------------------------------
Pete Meechan
Principal Consultant
Orb Data Limited

Original Message:
Sent: Fri November 17, 2023 10:05 AM
From: Oktawian Powązka
Subject: perJob licensing for IBM Workload Scheduler/IBM Workload Automation

IWS/IWA can be licensed in one of 3 ways

1. perServer (or PVU) licensing based upon processor cores (as is common with a lot of other IBM software)
2. perJob licensing based upon the peak number of unique successfully executed job per month over the preceding 12-month period licensed in packs of 10_MONTHLY_JOBS
3. Mixed-model based upon a mixture of 1&2 where each IWS agent is configured for either perServer or perJob licensing

IWS perJob licensing is documented here Per Job license model

 Essentially this involves executing an IBM supplied SQL query against the TWS database that calculates the number of unique successfully executed jobs per month over the preceding 12-months outputting an XML (slmtag) file with the results. The slmtag file is then "collected" at some future point by the BigFix software scan and (eventually) imported into ILMT.

The imported data is viewable using the Resource Utilization report as shown in the sample below.