IBM Support

IJ37679: MMBACKUP IS MISSING THE -SERVER OPTION IN ONE OF THE DSMC QUERY CALLS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • mmbackup uses Spectrum Protect
    BA client command 'dsmc' to
    communicate with the Spectrum Protect Server.
    If the -server option is not given to dsmc,
    dsmc gets a default server name from
    the Protect client configuration.
    If --tsm-servers <servername> to mmbackup is different
    from the default server name and the default server
    is not functional, mmbackup could show unexpected
    behavior because mmbackup does not provide the
    -server option in one of the dsmc query calls.
    

Local fix

  • Make sure the --tsm-servers <server> is the
    same as the default servername in dsm.opt
    

Problem summary

  • mmbackup uses Spectrum Protect
    BA client command 'dsmc' to
    communicate with the Spectrum Protect Server.
    If the -server option is not given to dsmc,
    dsmc gets a default server name from
    the Protect client configuration.
    If --tsm-servers <servername> to mmbackup is different
    from the default server name and the default server
    is not functional, mmbackup could show unexpected
    behavior because mmbackup does not provide the
    -server option in one of the dsmc query calls.
    

Problem conclusion

  • This problem is fixed in 5.1.2  PTF 3
    To see all Spectrum Scale APARs and
    their respective fix solutions refer to page
    https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale_
    apars.html
    
    Benefits of the solution:
    mmbackup will get consistent information
    from the Spectrum Protect server.
    
    Work around:
    Make sure the --tsm-servers <server> is the
    same as the default servername in dsm.opt
    
    Problem trigger:
    Run mmbackup when --tsm-servers <server> is not
    the same as the default servername in dsm.opt
    and default server is not functional.
    
    Symptom:
    Component Level Outage
    
    Platforms affected:
    All
    
    Functional Area affected:
    mmbackup
    
    Customer Impact:
    High Importance
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ37679

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    512

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-02-10

  • Closed date

    2022-02-10

  • Last modified date

    2022-02-10

  • 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

    SPEC SCALE STD

  • Fixed component ID

    5737F33AP

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"512","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
10 February 2022