IBM Support

IV62967: DOC APAR: OMNIBUS RESYNC PROPERTIES GATE.RESYNC.MASTER AND GATE.RESYNC.PREFERRED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • In Configuring resynchronization for bidirectional ObjectServer
    Gatewas
    http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_7.4.0/com.i
    bm.netcool_OMNIbus.doc_7.4.0/omnibus/gateways/objectservergw/wip
    /task/objsrvgw_bi_config_resynch.html
    
    under Gate.Resync.Master it states
    "Note: If you omit this property, the gateway always treats the
    ObjectServer that has been running the longest as the master."
    
    Also under Gate.Resync.Preferred it states:
    "Use this property to specify which ObjectServer the gateway
    should treat as the master during resynchronization if the
    Gate.Resynch.Master has been omitted and both ObjectServers
    have been running for the same length of time."
    
    This is incorrect, the resync direction is now based on
    ActingPrimary.
    
    Update properties to reflect how the resync direction is
    determined from technote
    http://www-01.ibm.com/support/docview.wss?uid=swg21663459
    
    The bi-directional ObjectServer gateway determines the source
    and destination ObjectServers by performing the following steps:
    
    1) Check the Gate.Resync.Master property in gateway properties
    file. Use the ObjectServer as source if defined.
    
    2) If Gate.Resync.Master is not set, check that one of the
    servers is defined with the BackupObjectServer set to TRUE. If
    neither server is defined as the backup, skip to step 4.
    
    3) If Gate.Resync.Master is not set and a backup server is
    defined, check the ActingPrimary property for the backup
    ObjectServer. Use the backup ObjectServer if ActingPrimary
    property is TRUE.
    
    4) If no backup server is defined, or the backup ObjectServer
    ActingPrimary property is FALSE, check each ObjectServer
    uptime. Use the ObjectServer that has been up the longest as
    the source.
    
    5) If the ObjectServers uptimes are the same, check
    Gate.Resync.Preferred property in gateway properties file. Use
    the ObjectServer as source if defined.
    
    6) If Gate.Resync.Preferred is not set, use the ObjectServer
    defined as ObjectServerA in the gateway properties file.
    

Local fix

  • NA, Doc APAR
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who are configuring resynchronization properties of    *
    * bidirectional ObjectServer Gateways in V7.4 and later.       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The documentation at the link below incorrectly describes    *
    * how the ObjectServer gateway determines which instance of    *
    * the gateway is the master.                                   *
    *                                                              *
    * http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/c *
    * om.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/gateways/objectserv *
    * ergw/wip/task/objsrvgw_bi_config_resynch.html                *
    *                                                              *
    * The description of the Gate.Resync.Master property states,   *
    * "Note: If you omit this property, the gateway always treats  *
    * the                                                          *
    * ObjectServer that has been running the longest as the        *
    * master.                                                      *
    *                                                              *
    * The description of the Gate.Resync.Preferred states,         *
    * "Use this property to specify which ObjectServer the gateway *
    * should treat as the master during resynchronization if the   *
    * Gate.Resynch.Master has been omitted and both ObjectServers  *
    * have been running for the same length of time."              *
    *                                                              *
    * These descriptions are incorrect.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * The correct description of the workings of the gateway is    *
    * described here:                                              *
    * http://www-01.ibm.com/support/docview.wss?uid=swg21663459    *
    ****************************************************************
    

Problem conclusion

  • Refer to the above technote for the correct description. The
    following topic will be updated with the correct description of
    the workings of the gateway to determine the master. This
    information will be posted here:
    
    http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.i
    bm.netcool_OMNIbus.doc_8.1.0/omnibus/gateways/objectservergw/wip
    /task/objsrvgw_bi_config_resynch.html
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV62967

  • Reported component name

    NETCOOL/OMNIBUS

  • Reported component ID

    5724O4800

  • Reported release

    740

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-25

  • Closed date

    2014-08-01

  • Last modified date

    2014-08-01

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSHTQ","label":"Tivoli Netcool\/OMNIbus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"740","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 July 2021