IBM Support

IT00639: ALERT MESSAGES FOR SPOKE SERVER DISPLAY CORRUPTED CHARACTERS IN OPERATIONS CENTER WHEN NON ENGLISH LANGUAGE USED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Error Description:
    The hub and spoke servers are running in the same language but
    alerts from spoke servers have corrupted characters.  The reason
    is because the spoke servers are not correctly handling the code
    page of alert message text string when sending it to the hub
    server. This results in the spoke's alert messages to display
    with corrupted characters on the Hub server and on the Operation
    Center.
    
    
    Versions Affected: Tivoli Storage Manager Server version 7.1 on
    spoke server
    
    Customer/L2 Diagnostics:
    This APAR can happen when the Spoke and Hub server are running
    in the same language other than English.
    From the Operations Center, the alert messages for hub server
    are correctly displayed.
    However alert messages for spoke servers display corrupted
    characters. Please check if the language setting for both hub
    and spoke server are the same. If yes, please do the following
    to confirm if you are running into this APAR:
    1.  On the Spoke's server console issue QUERY  ALERTSTATUS.
    Does the alert look OK without bad characters?
    2.  On the Hub's server console issue  QUERY ALERTSTATUS
    SOURCE=Spoke Server Name.  Does the alert from spoke server look
    OK without bad characters?
    3.  From the OC command line, issue the following to the Hub,
    QUERY ALERTSTATUS SOURCE= Spoke Server Name, does the alert text
    look OK without bad characters? If the alert  message from test
    1 is good but has bad characters from test 2 and 3, you are very
    likely running into this APAR.
    

Local fix

  • Use the Operation Center command line interface to run a QUERY
    ALERTSTATUS which will display the message with the correct
    characters.
    

Problem summary

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

Problem conclusion

  • This problem was fixed.
    Affected platforms:  AIX, HP-UX, Solaris, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT00639

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-27

  • Closed date

    2014-05-19

  • Last modified date

    2014-05-19

  • 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

  • R63A PSY

       UP

  • R63H PSY

       UP

  • R63L PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 71W

Reference #: IT00639

Modified date: 19 May 2014