Over a 1.5 hour period (90 monitor intervals) when lots of people were complaining, In ESATCP1 The only window showing consistently flagged values. Segments transmitted/InErr from .1-79.3 with a positive value reported every interval; Closes per minute/Resets with 16 non-zero intervals ranging from 1 (6 int) to 369. ESATCP2 Not a single highlighted value. ESATCP3 One interval had a bad Dest count of 688 ESAXACT a few (< 10) intervals had flagged entries under Pct non-dormant/PAG - the numbers were between 1.2 and 2.5
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[email protected]] On Behalf Of Barton Robinson > Sent: Tuesday, August 25, 2009 1:31 PM > To: [email protected] > Subject: Re: TCP/IP Hangs? > > look at the ESAXACT screen/report and make sure tcpip is not > waiting for anything. If very storage constrained, could see that. > Look at ESATCP1/2/4 for errors that show up in the network. > > Schuh, Richard wrote: > > We notice fairly frequent occurrences of a momentary hang > condition. > > We see the x-clock in the lower left corner of the terminal > emulator > > screen. These can last any where from a couple to 30 or > more seconds. > > I have been unsuccessful tying this to any messages in the TCPIP > > console log. How do I find out what is happening, whether it is a > > TCP/IP problem or one elsewhere in the network? > > > > > > * Surely there are numbers in the monitor data that > will help, but > > which ones? I am at a loss. > > * Are there any traces that I should run? Seems > doubtful - how do > > you trace a non-event? > > > > > > Regards, > > Richard Schuh > > > > > > >
