PI31317: In RDz, com.ibm.ftt.resources.core.physicalResource.refresh() sometimes does not work for offline volumes

APAR status

• Closed as program error.

Error description

• In Rational Developer for System z (RDz),
  com.ibm.ftt.resources.zos.zosphysical.ZOSDataSet.isOfflineVolume
  () does not display the correct results when offline volumes are
   brought back online from outside RDz (e.g. using CA_DISK) and
  the workspace is active or when volumes are taken offline
  outside RDz while the workspace is active. Calling
  com.ibm.ftt.resources.core.physical.IPhysicalResource.refresh()
  should resolve the issue but this does not always work.
  

Local fix

• Disconnect and reconnect to the host system
  

Problem summary

• The RDz Remote Resource API ZOSDataSet.isOfflineVolume() does
  not display the correct results when offline volumes are brought
  back online from outside RDz (e.g. using CA_DISK) and the
  workspace is active or when volumes are taken offline outside
  RDz while the workspace is active.  Calling
  IPhysicalResource.refresh() should resolve the issue but this
  does not always work.
  

Problem conclusion

• Getting this to work correctly involved changes in multiple
  areas:
  
  1) Various isOfflineVolume() methods have been updated to go ask
  for the state rather than relying on cached values.
  2) Various refresh() methods now force a trip to the file
  system.
  3) Those refresh() methods also now publish their activity so
  that subscribers such as UI's can update themselves.
  4) We now tolerate logical members with no corresponding
  physical resource when the PDS is offline just like we do for
  migrated datasets.
  5) The Remote Systems view file adapter now checks for offline
  state in getImageDescriptor().
  
  The problem listed in this APAR has been resolved with
  IBM Rational Developer for System z V8.5.1.6 Fix Pack which
  is available from the Recommended Fixes support download page:
  http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
  

Temporary fix

Comments

APAR Information

• 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

  RATL DEV FOR SY

• Fixed component ID

  5724T0700

Applicable component levels