PM74759: XSCMD ROUTETABLE COMMAND DOES NOT SORT PARTITIONS IN OUTPUT

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

  • The predecessor to xscmd, xsadmin, prints out the results of a
    similar command with sorted partition IDs, such as the
    following:
    
    Here is xsadmin output:
    Shard Type Partition State     Host                      Zone
    Primary    0         reachable myhost.mycom.com   DefaultZone
    Primary    1         reachable myhost.mycom.com   DefaultZone
    Primary    2         reachable myhost.mycom.com   DefaultZone
    Primary    3         reachable myhost.mycom.com   DefaultZone
    ...
    
    However, in xscmd, the output is not sorted by partition ID:
    Shard Type Partition State     Host                      Zone
    Primary    10        reachable myhost.mycom.com   DefaultZone
    Primary    12        reachable myhost.mycom.com   DefaultZone
    Primary    14        reachable myhost.mycom.com   DefaultZone
    Primary    16        reachable myhost.mycom.com   DefaultZone
    
    If customer scripts make an assumption that the partition
    information will be sorted by ID, then they moving break upon
    moving to v8.5 or higher.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of the IBM WebSphere eXtreme      *
    *                  Scale xscmd command-line interface, v8.5    *
    *                  or higher                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Thexscmd -c routetable command does     *
    *                      not                                     *
    *                      sort                                    *
    *                      by                                      *
    *                      Parttion ID.                            *
    ****************************************************************
    * RECOMMENDATION:  Install fixpack containing this APAR, or    *
    *                  request an iFix containing this APAR.       *
    ****************************************************************
    If you wrote scripts based on the xsadmin
    output to check the health of the routes with the routetable
    command, you might notice that in Version 8.5, the partition ID
    sorting
    no
    longer exists.
    The change in behavior is due to the deprecation of the
    RouteTableValidation ObjectGrid API from Version 7.1.1 in
    favor of an updated API in Version 8.5 and later.
    

Problem conclusion

  • The xscmd tool was updated to tolerate the API change.  The
    xscmd -c routetable command was updated to sort by partition ID.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM74759

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-10

  • Closed date

    2012-10-10

  • Last modified date

    2012-10-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

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

  • R850 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere eXtreme Scale

Software version:

850

Reference #:

PM74759

Modified date:

2012-10-10

Translate my page

Machine Translation

Content navigation