IC94177: SERVER WITH VIRTUAL VOLUME ROLE IS NOT VISIBLE ON OPERATIONS CENTER

IBM Tivoli Storage Manager V6.3 Fix Pack 5 (6.3.5.000) Server Downloads

APAR status

• Closed as program error.

Error description

• A Tivoli Storage Manager server that is used as a target
  for virtual volumes will not be visible in the Operations
    Center, even after configuring it as a spoke server.
  Tivoli Storage Manager Versions Affected:
    6.3.4
  Customer/L2 Diagnostics (If Applicable)
    To verify that the server is used as a target for virtual
    volumes, use the QUERY SERVER command as such:
  
      query server <spoke_server_name> format=detailed
  
    Verify in the output that the server role reports as
    "Virtual Volumes" in the "Role(s)" field.
  Initial Impact:
    Medium
  Additional Keywords:
    Ops Center Hub Spoke
  

Local fix

• Delete the spokes server definition on the hub and
    redefine it (using the SERVERPASSWORD parameter).  This
    will reset the server Roles. This server definition can
    then be used for monitoring via the Operations Center.
  
    Next, define a new virtual volume server definition (using
    the PASSWORD parameter) for the same server but with a
    different name. Update the existing DEVTYPE=SERVER device
    class to reference this new server definition.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM Tivoli Storage Manager      *
  *                 Server users of Operation Center.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: See Error Description.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.  This     *
  *                 problem is currently projected to be fixed   *
  *                 in server level 6.3.4.200 and 6.3.5.  Note   *
  *                 that this is subject to change at the        *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• The problem was fixed.
  Affected Platforms: AIX, HP-UX, Solaris, Linux, Windows.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• ADMS2SC
  

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP