PI09352: Rational Developer for System z V126.96.36.199 - PushToClient export action not working for zossys.xml
Fixes are available
Closed as program error.
In Rational Developer for System z (RDz) V188.8.131.52, PushToClient export action fails to properly upload z/OS mapping file, zossys.xml, to the host. Upon exporting the zossys.xml file from client to the host and inspecting the date of the file, the user notices that the file still has the original (as-shipped) default date 1970/01/01. How to Reproduce: 1 On the RDz client, edit the z/OS Mapping for one of your host systems 2 Before exporting the file, delete the existing zossys.xml file on the host 3 Perform steps to export configuration files (File ? Export ? Rational Developer for System z ? Configuration Files) 4 After exporting (uploading) the configuration files and listing the file, zossys.xml still has the old default date Local fix: Manually update the file on the host
If there is no mapping file in the client (i.e. local change) sub-folder for generic mappings, then changes are never saved to the client sub-folder and are therefore never exported since the local change (client) sub-folder has no changes.
The code has been modified to always save mapping changes to the client sub-folder rather than first checking to see if a file exists in the client sub-folder. The problem listed in this APAR has been resolved with IBM Rational Developer for System z V184.108.40.206 Fix Pack which is available from the Recommended Fixes support download page: http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
Reported component name
RATL DEV FOR SY
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
RATL DEV FOR SY
Fixed component ID
Applicable component levels