IBM Support

IT01620: TPC-R GUI SHOWS WRONG DATA EXPOSURE VALUE FOR SVC

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • SVCDataExposure doesn't override Progress.equals(), and also
    doesn't pass in unique fields to it's
    super class (which does implement equals).  As a result, when
    the data exposure changes, the old
    SVCDataExposure  object and the new SVCDataExposure  object
    compare as equivalent.  Thus, the GUI
    doesn't get the event that the DataExposure changed, and keeps
    showing the old value.
    This evident in the logs. Particularly, dataExpTime does not
    change in gui xml trace. In the example
    below, notice: dataExpTime="00:19:31":
    """"""""""""""""""""""""""""""
    2014-05-02 11:28:02.103-0500 Default Executor-thread-6495
    XMLOutputLogger
    AbstractRequestHandler.getPage Requested Page: SessionDetails
    <?xml version="1.0" encoding="UTF-8"?>
    <page name = "Response" version = "1.00">
     <data>
      <time>May 2, 2014 11:28:02 AM</time>
      <session name="<session name>" status="Normal" type="GM"
    specificType="Global Mirror
    Failover/Failback w/ Change Volumes" state="Prepared"
    recoverable="true" copySets="103"
    description="<description>" appRole="H1" isAddCSAllowed="true"
    hasDisconnectedBoxes="false"
    transitioning="false" supportedHW="SVC-" zosAssociation=""
    candidates="" >
    <participating >  <sequence role="H1-H2" errorCount="0"
    recoverable="103"
    copying="103" progress="n/a" direction="true" failedOver="false"
    copyType="GM" timestamp="n/a"
    defined="0" preparing="0" prepared="103" suspended="0"
    target_avail="0" ><progress
    type="dataExposureSVC" dataExpTime="00:19:31" interval="30"
    ></progress></sequence>
    ...
    2014-05-02 11:34:04.921-0500 Default Executor-thread-6495
    XMLOutputLogger
    AbstractRequestHandler.getPage Requested Page: SessionDetails
    <?xml version="1.0" encoding="UTF-8"?>
    <page name = "Response" version = "1.00">
     <data>
      <time>May 2, 2014 11:34:04 AM</time>
      <session name="<session name>" status="Normal" type="GM"
    specificType="Global Mirror
    Failover/Failback w/ Change Volumes" state="Prepared"
    recoverable="true" copySets="103"
    description="<description>" appRole="H1" isAddCSAllowed="true"
    hasDisconnectedBoxes="false"
    transitioning="false" supportedHW="SVC-" zosAssociation=""
    candidates="" >
    <participating >  <sequence role="H1-H2" errorCount="0"
    recoverable="103"
    copying="103" progress="n/a" direction="true" failedOver="false"
    copyType="GM" timestamp="n/a"
    defined="0" preparing="0" prepared="103" suspended="0"
    target_avail="0" ><progress
    type="dataExposureSVC" dataExpTime="00:19:31" interval="30"
    ></progress></sequence>
    """"""""""""""""""""""""""""""
    However, DataExposure does change in csmTrace logs:
    """"""""""""""""""""""""""""""
    014-05-02 11:34:23.625-0500 CSMCOM-3DC9 RepMgr D < SessionMgr
    getSequenceSpecifics Exit, return
    value =  Sequence Name = H1-H2
      Session Name = <session name>
      SequenceSpecifics.toString <no op> Type = Intercluster
     Src Cluster = SVC:CLUSTER:<name>
     Tgt Cluster = SVC:CLUSTER:<name>
     Type = Intercluster
     QueryInterval = 30
     DataExposure = 1555000
     Src Cluster = SVC:CLUSTER:<name>
     Tgt Cluster = SVC:CLUSTER:<name>
    ...
    2014-05-02 11:34:25.794-0500 CSMEVT-CB25 RepMgr D < SessionMgr
    getSequenceSpecifics Exit, return
    value =  Sequence Name = H1-H2
      Session Name = <session name>
      SequenceSpecifics.toString <no op> Type = Intercluster
     Src Cluster = SVC:CLUSTER:<name>
     Tgt Cluster = SVC:CLUSTER:<name>
     Type = Intercluster
     QueryInterval = 30
     DataExposure = 1557000
     Src Cluster = SVC:CLUSTER:<name>
     Tgt Cluster = SVC:CLUSTER:<name>
    """"""""""""""""""""""""""""""
    

Local fix

  • upgrade to latest FP.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * TPC for Replication 5.2.0 and 5.2.1 users                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fix maintenance when available.                        *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is targeted for the following maintenance
    package:
    
    | refresh pack | 5.2-TIV-TPC-RP0002 - target June 2014
    
    http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
    
    The target dates for future refresh packs or fix packs do not
    represent a formal commitment by IBM. The dates are subject to
    change without notice.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT01620

  • Reported component name

    TPC

  • Reported component ID

    5608TPC00

  • Reported release

    520

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-07

  • Closed date

    2014-05-16

  • Last modified date

    2014-05-16

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

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

Modules/Macros

  • REP
    

Fix information

  • Fixed component name

    TPC

  • Fixed component ID

    5608TPC00

Applicable component levels

  • R520 PSY

       UP

  • R521 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS5R93","label":"IBM Spectrum Control"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"520","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
23 March 2022