How are OPSUSS servers terminated if OSSDORM is exceeded?
Article ID: 245683
Updated On:
Products
Issue/Introduction
We discovered this IBM APAR (OA63395) that was sending SIGHUP to unrelated PIDs. The scenario:
1) system in the plex hangs and SFM varies it out of the sysplex
2) During hang, all other systems have multiple OPMUSS tasks terminate due to USSDORM (set to 60)
3) Messages on another system log stating that OPMUSS6 killed PIDs to a production MQ CHIN task.
We just would really like to know how you terminate the OPMUSS tasks when USSDORM is exceeded to see if this corroborates the OA63395 APAR issue or not.
Environment
Release : 14.0
Component : OPS/MVS
Resolution
The following two links explain the OPS/MVS OSF Server behavior but are the same for all the various OPS Servers. The "OSFDORM and all the other server types (ie, USSDORM) should act the same way."
Feedback
