APAR status
Closed as program error.
Error description
Expanding z/OS project in IBM Developer for z Systems 14.0.0.5 triggers a connection and asks for logon details to be provided, after that IDz freezes and customer had to restart the application. The "lock" being waited on is not a user lock, like we do for edited MVS members, but rather a java "monitor" lock for thread synchronization.
Local fix
There is no known workaround at this time.
Problem summary
Expanding z/OS project in IBM Developer for z Systems 14.0.0.5 triggers a connection and asks for logon details to be provided, after that IDz freezes and customer had to restart the application. The "lock" being waited on is not a user lock, like we do for edited MVS members, but rather a java "monitor" lock for thread synchronization.
Problem conclusion
A combination of having out-of-synch secure storage and initializing the MVS subsystem via the main thread leads to a deadlock scenario.
Temporary fix
Comments
APAR Information
APAR number
PI99115
Reported component name
DEV FOR Z SYS
Reported component ID
5724T0700
Reported release
E00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-06-13
Closed date
2018-07-27
Last modified date
2018-07-27
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
DEV FOR Z SYS
Fixed component ID
5724T0700
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSJK49","label":"IBM Developer for z Systems"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"E00","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
27 October 2020