Hi There,

We are running TADz V8.2 and have a vendor product identified within the GKB, for which all but one of the modules are identified in the prowser reports - successfully reporting on Vendor, Product, Release. However, one of the modules is listed as 'Not Identified/Unknown' , and yet we do know this module is also associated with the product.  Is it documented anywhere as to the logic TADz uses to assign a module that it finds to vendor/product, version etc ie in terms of the criteria it uses?  I've looked in the Adnin Guide and Reference and can see generically how modules are assigned , and the tables where the info is held, but not the logic. 

Thanks and regards,

Martin

Hi Martin,

There could be a number of reasons why modules are not identified:

1. The module/s could be exits which we do not add to the GKB
2. They could be license modules that are unique to each site
3. They could be modules for a maint level that we have not added to the GKB

The above are just some of the reasons. The matching process is to look at each module and then find the best fit in the GKB and create what we call scorecards. For a given product there could be many scorecards since the module could belong to multiple versions of a product or even be in more than one product. The scorecards are then checked and the best match is then taken and the product identified or not identified. This is a simple explanation. There are other factors taken into account that are proprietary. If you could tell me which product and which module is not being identified I could give you a better explanation.

Regards

Jim K 

Hi There,

We are running TADz V8.2 and have a vendor product identified within the GKB, for which all but one of the modules are identified in the prowser reports - successfully reporting on Vendor, Product, Release. However, one of the modules is listed as 'Not Identified/Unknown' , and yet we do know this module is also associated with the product.  Is it documented anywhere as to the logic TADz uses to assign a module that it finds to vendor/product, version etc ie in terms of the criteria it uses?  I've looked in the Adnin Guide and Reference and can see generically how modules are assigned , and the tables where the info is held, but not the logic. 

Thanks and regards,

Martin

Hi Jim,

Many thanks for your response.

In this case it appears to be 'user error'  - the LKB entry was missing for the 'unidentified' module. This has now been added in. When will TADz next use the LKB entry to identify the module - at the time the zOS inquisitor data is next imported ?

Thanks and regards,

Martin

Hi Martin,

There could be a number of reasons why modules are not identified:

1. The module/s could be exits which we do not add to the GKB
2. They could be license modules that are unique to each site
3. They could be modules for a maint level that we have not added to the GKB

The above are just some of the reasons. The matching process is to look at each module and then find the best fit in the GKB and create what we call scorecards. For a given product there could be many scorecards since the module could belong to multiple versions of a product or even be in more than one product. The scorecards are then checked and the best match is then taken and the product identified or not identified. This is a simple explanation. There are other factors taken into account that are proprietary. If you could tell me which product and which module is not being identified I could give you a better explanation.

Regards

Jim K 

Hi There,

We are running TADz V8.2 and have a vendor product identified within the GKB, for which all but one of the modules are identified in the prowser reports - successfully reporting on Vendor, Product, Release. However, one of the modules is listed as 'Not Identified/Unknown' , and yet we do know this module is also associated with the product.  Is it documented anywhere as to the logic TADz uses to assign a module that it finds to vendor/product, version etc ie in terms of the criteria it uses?  I've looked in the Adnin Guide and Reference and can see generically how modules are assigned , and the tables where the info is held, but not the logic. 

Thanks and regards,

Martin

Hi Martin,

Yes the next time you run IQIMPORT the updated LKB entry will identify the module. Just make sure you use FULLREMATCH=Y.

Regards

Jim K.

Hi Jim,

Many thanks for your response.

In this case it appears to be 'user error'  - the LKB entry was missing for the 'unidentified' module. This has now been added in. When will TADz next use the LKB entry to identify the module - at the time the zOS inquisitor data is next imported ?

Thanks and regards,

Martin

Hi Martin,

There could be a number of reasons why modules are not identified:

1. The module/s could be exits which we do not add to the GKB
2. They could be license modules that are unique to each site
3. They could be modules for a maint level that we have not added to the GKB

The above are just some of the reasons. The matching process is to look at each module and then find the best fit in the GKB and create what we call scorecards. For a given product there could be many scorecards since the module could belong to multiple versions of a product or even be in more than one product. The scorecards are then checked and the best match is then taken and the product identified or not identified. This is a simple explanation. There are other factors taken into account that are proprietary. If you could tell me which product and which module is not being identified I could give you a better explanation.

Regards

Jim K 

Hi There,

We are running TADz V8.2 and have a vendor product identified within the GKB, for which all but one of the modules are identified in the prowser reports - successfully reporting on Vendor, Product, Release. However, one of the modules is listed as 'Not Identified/Unknown' , and yet we do know this module is also associated with the product.  Is it documented anywhere as to the logic TADz uses to assign a module that it finds to vendor/product, version etc ie in terms of the criteria it uses?  I've looked in the Adnin Guide and Reference and can see generically how modules are assigned , and the tables where the info is held, but not the logic. 

Thanks and regards,

Martin

Thanks Jim - following our monthly import I can see that FULLREMATCH=Y has resolved the 'unidentified' module issue. 

More generally, are there any general 'rules of thumb'  as to when the 'FULLREMATCH=Y' parm should  be specified ? Only when we have a recurrence of this type of issue perhaps?  I can see use of the parameter has significantly extended our import runtimes (as the manual suggests),  so I'm guessing we should not be using it all the time by default ? 

Thanks and regards,

Martin

Hi Martin,

Yes the next time you run IQIMPORT the updated LKB entry will identify the module. Just make sure you use FULLREMATCH=Y.

Regards

Jim K.

Hi Jim,

Many thanks for your response.

In this case it appears to be 'user error'  - the LKB entry was missing for the 'unidentified' module. This has now been added in. When will TADz next use the LKB entry to identify the module - at the time the zOS inquisitor data is next imported ?

Thanks and regards,

Martin

Hi Martin,

There could be a number of reasons why modules are not identified:

1. The module/s could be exits which we do not add to the GKB
2. They could be license modules that are unique to each site
3. They could be modules for a maint level that we have not added to the GKB

The above are just some of the reasons. The matching process is to look at each module and then find the best fit in the GKB and create what we call scorecards. For a given product there could be many scorecards since the module could belong to multiple versions of a product or even be in more than one product. The scorecards are then checked and the best match is then taken and the product identified or not identified. This is a simple explanation. There are other factors taken into account that are proprietary. If you could tell me which product and which module is not being identified I could give you a better explanation.

Regards

Jim K 

Hi There,

We are running TADz V8.2 and have a vendor product identified within the GKB, for which all but one of the modules are identified in the prowser reports - successfully reporting on Vendor, Product, Release. However, one of the modules is listed as 'Not Identified/Unknown' , and yet we do know this module is also associated with the product.  Is it documented anywhere as to the logic TADz uses to assign a module that it finds to vendor/product, version etc ie in terms of the criteria it uses?  I've looked in the Adnin Guide and Reference and can see generically how modules are assigned , and the tables where the info is held, but not the logic. 

Thanks and regards,

Martin