IBM Support

IV30424: DOCUMENTATION MISSING ON SERIAL NUMBER SANITY CHECKS PROPERTY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • The following new property was added initially in TADDM 7.2.1
FP2:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks

At that time, the default value for this setting was:
^(?!.*null).*$,\\d+

And, as this shows, the separator between the sanity checks was
a comma.

So, if a new check was added, the user would need to set the
property to include the default value and the append their
check(s) with a comma like:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks=^(?!.*null).*$,\\d+,userAddedCheck1,userAddedCheck2,...

However, in TADDM Fixpack 3, the default sanity checks list was
updated to be:

^(?!null);^(?!not );^(?!n/a);^(?!permission);^(?!to be
);^(?!undef);^[ -:\\.\\w]{4,80}$

And, as shown in this list, the separator was changed from a
comma to a semi-colon.

So, anyone with the property set using the initial
FP2 syntax will find that their serial numbers are failing the
sanity checks unexpectedly now as the expression list is no
longer split on the commas.  As a result they will see that
serial numbers are not set and they may also see a warning
message in their sensor logs indicating that the discovered
serial number is invalid.

The Fixpack 3 README should have included the above information
and included steps to update this property with the new default
setting and with the new semicolon separator.  Additionally, the
updated 7.2.1 FP3 documentation should have also included this
new property and descibed it's usage.  Finally, the default
sanity check regular expressions needs to be externalized
somewhere perhaps listed (and updated when changed) in the
collation.properties file.  Users need to know this so they can
successfully keep all the default checks and simply add their
own.

Finally, the READMEs show that the sanity checks string of
regular expressions should be quoted when added into
collation.properties.  For example:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks="^(?!.*null).*$,\\d+"

This causes incorrect results as the quotation marks are then
processed as part of the regular expressions.  No quotations
should be used unless they are intended to be included in the
regex.  So, for 7.2.1 Fixpack 2, the default sanity checks would
be specified as:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks=^(?!.*null).*$,\\d+

The following new property was added initially in TADDM 7.2.1
FP2:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks

At that time, the default value for this setting was:
^(?!.*null).*$,\\d+

And, as this shows, the separator between the sanity checks was
a comma.

So, if a new check was added, the user would need to set the
property to include the default value and the append their
check(s) with a comma like:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks=^(?!.*null).*$,\\d+,userAddedCheck1,userAddedCheck2,...

However, in TADDM Fixpack 3, the default sanity checks list was
updated to be:

^(?!null);^(?!not );^(?!n/a);^(?!permission);^(?!to be
);^(?!undef);^[ -:\\.\\w]{4,80}$

And, as shown in this list, the separator was changed from a
comma to a semi-colon.

So, anyone with the property set using the initial
FP2 syntax will find that their serial numbers are failing the
sanity checks unexpectedly now as the expression list is no
longer split on the commas.  As a result they will see that
serial numbers are not set and they may also see a warning
message in their sensor logs indicating that the discovered
serial number is invalid.

The Fixpack 3 README should have included the above information
and included steps to update this property with the new default
setting and with the new semicolon separator.  Additionally, the
updated 7.2.1 FP3 documentation should have also included this
new property and descibed it's usage.  Finally, the default
sanity check regular expressions needs to be externalized
somewhere perhaps listed (and updated when changed) in the
collation.properties file.  Users need to know this so they can
successfully keep all the default checks and simply add their
own.

Finally, the READMEs show that the sanity checks string of
regular expressions should be quoted when added into
collation.properties.  For example:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks="^(?!.*null).*$,\\d+"

This causes incorrect results as the quotation marks are then
processed as part of the regular expressions.  No quotations
should be used unless they are intended to be included in the
regex.  So, for 7.2.1 Fixpack 2, the default sanity checks would
be specified as:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks=^(?!.*null).*$,\\d+

And, any additional expressions desired would be appended to
this using a comma separator.


In 7.2.1 Fixpack 3, the default sanity checks would be specified
as:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks=^(?!null);^(?!not );^(?!n/a);^(?!permission);^(?!to be
);^(?!undef);^[ -:\\.\\w]{4,80}$


And, any additional expressions desired would be appended to
this using a semicolon separator.

Local fix

  • Use the appropriate default values and separator for the fixpack
version installed.

Problem summary

  • The following new property was added initially in TADDM 7.2.1
FP2:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks

At that time, the default value for this setting was:
^(?!.*null).*$,\\d+

And, as this shows, the separator between the sanity checks was
a comma.

So, if a new check was added, the user would need to set the
property to include the default value and the append their
check(s) with a comma like:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks=^(?!.*null).*$,\\d+,userAddedCheck1,userAddedCheck2,...

However, in TADDM Fixpack 3, the default sanity checks list was
updated to be:

^(?!null);^(?!not );^(?!n/a);^(?!permission);^(?!to be
);^(?!undef);^[ -:\\.\\w]{4,80}$

And, as shown in this list, the separator was changed from a
comma to a semi-colon.

So, anyone with the property set using the initial
FP2 syntax will find that their serial numbers are failing the
sanity checks unexpectedly now as the expression list is no
longer split on the commas.  As a result they will see that
serial numbers are not set and they may also see a warning
message in their sensor logs indicating that the discovered
serial number is invalid.

The Fixpack 3 README should have included the above information
and included steps to update this property with the new default
setting and with the new semicolon separator.  Additionally, the
updated 7.2.1 FP3 documentation should have also included this
new property and descibed it's usage.  Finally, the default
sanity check regular expressions needs to be externalized
somewhere perhaps listed (and updated when changed) in the
collation.properties file.  Users need to know this so they can
successfully keep all the default checks and simply add their
own.

Finally, the READMEs show that the sanity checks string of
regular expressions should be quoted when added into
collation.properties.  For example:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks="^(?!.*null).*$,\\d+"

This causes incorrect results as the quotation marks are then
processed as part of the regular expressions.  No quotations
should be used unless they are intended to be included in the
regex.  So, for 7.2.1 Fixpack 2, the default sanity checks would
be specified as:

com.collation.discover.agent.sys.ComputerSystem.serialNumberSani
tyChecks=^(?!.*null).*$,\\d+



i












i
.




















e












i





d


i





i












i
.




















e












i





d


i






d


i

Problem conclusion

  • The following changes will be made in the next release of the
publications:

Topic: Sensors > Sensor reference > Configure
collation.properites

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IV30424
    • 

  • Reported component name
    APP DEPENDENCY
    • 

  • Reported component ID
    5724N5500
    • 

  • Reported release
    721
    • 

  • Status
    CLOSED  DOC
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2012-10-17
    • 

  • Closed date
    2012-11-30
    • 

  • Last modified date
    2012-11-30
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Fix information


    



Applicable component levels


    








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"721","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            30 November 2012
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback