System Service sys$qiow

[Richard Whalen]

A hang on a write to a TCP/IP network channel means that that the negotiated window size between the two systems involve has been consumed and that the allow amount of additional system buffer space on the local system has also been consumes.

So the task is to figure out why the process on the remote system isn't reading the data.

[Guenther Froehlin]

I am with John G. This is a write to a mailbox passing the devive name of an IP socket.

ajaydec, what's the product involved here?
You have to find the code for the reader of this mailbox. While the process hangs find out the mailbox name:

$ ANALYZE/SYSTEM
SDA> SHOW SUMMARY/IMAGE ! find the hung process
SDA> SHOW PROCESS/INDEX=of-hung_process/CHANNEL
...look for MBAnnn device marked "Busy".
Next:
SDA> SET OUT log.txt
SDA> SHOW PROCESS/CHANNEL ALL
SDA> EXIT
$ SEARCH log.txt "index:",MBAnnn ! from above

This may give you a hint to other processes using this mailbox. You may find the reader process and the image it is running.

/Guenther

[#3]

regards,
ajaydec