We believe it is on the network side, not the AS/400, but have not been able to determine this.
Could you give us some suggestions to help locate where the problem is?
The main thing I was looking for was the best way to start diagnosing these types of problems. The clocks connect to the AS/400. It will connect to a remote site, and it seems to drop more often around the end of the work day.
As a side note, at 5:30 p.m. I noticed a few TCP/IP connections going to close-wait status, some ending, and more being generated with an average of about 6. When I received notice that connections were being lost, I checked netstat for close-wait connections. There were over 40 and all of them were from Management Central –- monitors on the systems. With this number of close-wait connections, TCP/IP will drop connections as we saw with the WebSphere problem connections, which were doing the same thing. I have opened a PMR with IBM, and in the meantime I have shut down Management Central until we determine if this was the cause or not.
Thanks you for your help.
It may be due to some station trying to connect many times. In order to further investigate it, I would consider setting up an IP journal, which is part of journal filter. This is a little heavy on the machine, but it will log all the required events.
Dig Deeper on Debugging
Related Q&A from Shahar Mor
Use work station customize object or printer type in iSeries Access to print the output of an RPG file from the AS/400 to an HP printer. Continue Reading
On the AS/400 library, source files are multi-member. View source files using GET QCLSRC.membername or MGET QRPGSRC.* Continue Reading
Connecting the iSeries in AS/400, issue STRHOSTSVR *ALL. Make sure the as-signon port is in listen state and check the firewall settings. Continue Reading