PM13161: RDz: LPEX editor 'Dirty' value gets reset prematurely

APAR status

• Closed as program error.

Error description

• Error description:
  Product Version: RDz V7.5.1, RDz V7.6.0
  Upon the save command, the LPEX editor resets the dirty '*'
  value regardless of the outcome of the save.
  
  For example; if the dataset resources are less than that of the
  file attempting to be saved RDz will fail with E37-4 error
  message and the editor '*' value will be reset even though
  the remote save failed. This happens because RDz will cache it
  locally and LPEX will count that as a successful save.
  
  Local fix:
  Allow enough resources to save members to a dataset.
  

Local fix

Problem summary

• Users affected:
  Users of LPEX with the remote MVS subsystem
  
  Problem description:
  The LPEX dirty flag is cleared when the file is saved to the
  local cache.  However if the cache synchronization fails, the
  dirty flag incorrectly remains cleared.
  

Problem conclusion

• The LPEX dirty flag is set if the synchronization to the remove
  MVS host fails.
  
  
  The problem listed in this APAR has been resolved with
  IBM Rational Developer for System z V7.6.2.1 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

• R762 PSY

     UP