PI71481: RATIONAL DEVELOPER FOR SYSTEM Z (RDZ) ZOS SYSTEM MAPPINGS IN PUSH TO CLIENT REQUIRES A RESTART OF THE CLIENT
Fixes are available
Rational Developer for System z Fix Pack 3 (18.104.22.168) for 9.5.1.
Rational Developer for System z Fix Pack 4 (22.214.171.124) for 9.5.1.
Rational Developer for System z Fix Pack 5 (126.96.36.199) for 9.5.1.
Rational Developer for System z Fix Pack 5 (188.8.131.52) for 9.5.1.
Rational Developer for z Systems Fix Pack 7 (184.108.40.206) for 9.5.1.
Rational Developer for z Systems Fix Pack 8 (220.127.116.11) for 9.5.1.
Rational Developer for z Systems Fix Pack 9 (18.104.22.168) for 9.5.1.
Closed as program error.
Rational Developer for System z - RDz v9.5.1 IBM Developer for z Systems - IDz v14.0 When zOS system mappings are pushed down to clients the RDz client must be restarted in order to utilized. Once the zOS systems mappings are downloaded via the push to client (PC) and the client has been restarted then the mappings work from that point on.
Restart client after mappings are pushed down from host to client
When a user uses push-to-client to update file system mappings, the mappings and the view are not updated until the product is restarted.
The mapping properties are being stored in a variable so that excessive reloads don't effect performance. The code that checks the variable was not accounting for the case where the file system mappings may be updated via push-to-client. The problem listed in this APAR has been resolved with IBM Rational Developer for z Systems V22.214.171.124 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
DEV FOR Z SYS
Reported component ID
NoSpecatt / Xsystem
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
DEV FOR Z SYS
Fixed component ID
Applicable component levels