PM70239: In RDz 8.0.3.1, Last modified date is incorrect for sequential files on USS

APAR status

• Closed as program error.

Error description

• Headline:
  In RDz 8.0.3.1, Last modified date is incorrect for sequential
  files on USS
  
  APAR Error Description:
  Abstract: In Rational Developer for System z (RDz) version
  8.0.3.1, the last modified date is incorrect for sequential
  files on USS.
  Problem: 1. On the Remote System Explorer (RSE), copy and paste
  a sequential file from MVS to USS.
  2. On the RSE, select the file in USS: The Properties view does
  not show the current modified date but 1/1/1970.
  3. On the RSE, right-click on the file on USS and select menu
  Properties and item Info: current modified date is also 1/1/1970
  4. Modify and save the USS file in LPEX for example: the last
  modified date doesn't get updated and is still displayed as
  1/1/1970.
  
  Local fix:
  If the file is modified outside RDz (using vi or oedit for
  example) then the last modified date appears correctly in RDz
  client.
  

Local fix

Problem summary

• When a data set was copied to the USS without ISPF statistics,
  the timestamp of copied file was 0 but 0 timestamp was handled
  as an invalid cache state.
  

Problem conclusion

• The RDz client was fixed to set the copied time to the copied
  file if the data set has no ISPF statistics.
  
  The problem listed in this APAR has been resolved with
  IBM Rational Developer for System z V8.0.3.4 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

• R803 PSY

     UP