Re: got a good one - semaphores

We have all the desired debugs in place: threads ids, semdebug, console 
log, etc.

IBM does not believe it is semaphore or orphan memory related.  It would 
be nice to clean them up but semaphore cleanup would required all the 
other DPARs to take an outage.

The idea is that we are not hanging rather than resource contention on the 
address book.  There is a possibility that our AdminP mail moves may be 
part of the issue for address book contention.

We are planning our outage so that we can get a complete semdebug.txt. 
Apparently all the data is in temp files and written during a crash or 
shutdown.  This way they have more info to parse through and compare.

Again, the semaphore shows the holder as the server job.  The call stack 
for the holding thread never looks the same.


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------