IBM Support

PI08299: Incorrectly using xscmd -c establishLink can result in a sucessful link, but failed replication.

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

  • When the xscmd -c establishLink command uses a local catalog
endpoint as one of the endpoints for the remote domain, the
result may incorrectly be a successful link. At some future
time, the bad endpoint may be used in replication, resulting in
many CWOBJ4924I messages that show the local domain and the
remote domain having the same domain name, and replication will
not complete from that point forward.

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:  WebSphere eXtreme Scale users of multi-     *
*                  master                                      *
*                  replication (MMR).                          *
****************************************************************
* PROBLEM DESCRIPTION: If incorrect endpoints are used with    *
*                      the                                     *
*                      xscmd -c establishLink command, a bad   *
*                      link might be established.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When ‚  the ‚  xscmd ‚  -
c ‚  establishLink ‚  command ‚  uses ‚  a ‚  local ‚  catalog
server ‚  endpoint, ‚  the link might complete
incorrectly. ‚  At ‚  some ‚  future ‚  time, ‚  the ‚  bad ‚  e
might ‚  be ‚  used ‚  in ‚  replication, ‚  resulting ‚  in ‚  
4I ‚  
messages ‚  that
show ‚  the ‚  local ‚  domain ‚  and ‚  the ‚  remote ‚  domain
the ‚  same ‚  domain ‚  name. Replication ‚  does
not ‚  complete ‚  from ‚  that ‚  point ‚  forward.

    



Problem conclusion


    

  • The xscmd -c establishLink command now correctly fails with the

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PI08299
    • 

  • 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
    2013-12-17
    • 

  • Closed date
    2013-12-17
    • 

  • Last modified date
    2013-12-17
    • 





    

  • 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
    • 

  • R860  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            17 December 2013
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback