PI99115: IDZ CLIENT FREEZES WHEN TRYING TO EXPAND A Z/OS PROJECT

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 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