IBM Support

IT32641: "GENERATE DEDUPSTATS" WITH WILDCARD FOR NODENAME(S) CAN REPORT NODE NAMES WITH ZERO DATA IN THE CHOSEN STORAGE POOL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When running "generate dedupstats" with a wildcard for nodename,
    it can be seen in the outputs in activity log that node names,
    with no data in that
    storage pool, are reported against.
    
    For example, run 'generate dedupstats' against a
    directory-container storage pool called containerpool01 with
    wildcard for nodenames,
    and node name NODE01 has no data in this directory-container
    storage pool, then the following can be seen in activity log.
    
    GENERATE  DEDUPSTATS containerpool01 *
    
    ANR0984I Process 282 for GENERATE DEDUPSTATS started in
    the BACKGROUND
    
    ANR0896I Generated 4 statistics reports about data
    deduplication for node NODE01 in  pool CONTAINERPOOL01.
    
    query process will also show NODE01 being processed by 'generate
    dedupstats'.
    
    The node being incorrectly processed does not affect the results
    of 'generate dedupstats' command
    and 'query dedupstats' will report for nodes only with data in
    the directory-container storage pool.
    
    Ignore the messages for node name(s) with no data in the
    associated storage pool
    
    
    IBM Spectrum Protect versions affected:
    IBM Spectrum Protect Server 7.1.3 and higher,and 8.1 and higher
    on all supported platforms
    
    Initial Impact: Low
    
    
    
    Additional Keywords: TSM "Spectrum Protect" TS003550869    gen
    dedupstats generate node nodename wildcard
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Spectrum Protect server users.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See error description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in level 8.1.10. Note that this is     *
    * subject to change at the discretion of IBM.                  *
    ****************************************************************
    

Problem conclusion

  • This problem was fixed.
    Affected platforms for reported release:  AIX, Linux, and
    Windows.
    Platforms fixed:  AIX, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT32641

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    81L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-24

  • Closed date

    2020-05-01

  • Last modified date

    2020-05-01

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

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

Fix information

  • Fixed component name

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP

  • R81A PSY

       UP

  • R81L PSY

       UP

  • R81W PSY

       UP

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"81L"}]

Document Information

Modified date:
26 August 2021