The ISV SCRT Report lists a Broadcom product not in use in the LPAR
Article ID: 271153
Updated On:
Products
Issue/Introduction
After creating an ISV SCRT Report for the first time, there was a Broadcom product that was not installed or used in the LPAR.
The Broadcom product appeared in the LPAR product environment only, what was impossible due to the general approach for the software install, testing and promotion in this LPAR..
Monthly usage of this Broadcom product according to the ISV SCRT Report was minimal, but the Broadcom product was not used in the LPAR.
Environment
Release : 15.0
Resolution
In this situation you have to issue the TSO CAIRIMU PROD in the LPAR and check for the following message:
+CAS9087I PROD (XX) VIOLS|WARNS/STAT(002/Y) WARNSTART(***
+CAS9088I EXPIRY1(******<NA>******) EXPIRY2(******<NA>**
+CAS9101I 1STVIOL(mm/dd/yyyy@hh:mm) LASTVIOL(mm/dd/yyyy@hh:mm)
The XX is the LPM Key for the Broadcom product.
This means on mm/dd/yyyy@hh:mm, an end user attempted to run the Broadcom product with LPM Key XX, there was not any LMP Key installed for the Broadcom product so there was the violation. However at the time of the LMP Key check a SMF record was created in the SMF data sets, this was the SMF record that was reported by the IBM SCRT program.
Unless you know the end user that attempted to work with the Broadcom product this is difficult to research. If you have a repetitive situation a SLIP trap can be set over the CAS9 error message and create a SVC Dump to know how the Broadcom product that was invoked, you have to contact Broadcom Technical Support to set up the right SLIP trap.
Feedback
