Saw the other post to this (from Dwight?) and he had some good things to
check. But I wanted to add my $.02.....
I just got done talking to IBM about something that was different, but the
symptoms are similar. My situation was an Admin command with lots of data
being pumped back to the client. I happened to notice when looking from
another admin session that the first session was in an idle wait on the
server, and yet the results had not been delivered on my screen. In some
cases the session would time out on the server, although I did not get the
messages. Sometimes the resluts were never received - or I'd get impatient
and blow away the session ;-(
The answer was that the server was actually done with all of the information
from the query, and had pumped it back to the Admin client. The admin session
was trying to sort it, etc. to get it in the correct order and format before
it could present it. PC sorts not being very efficient, there was often quite
a delay.
So how does this apply to you? **Perhaps** the server has done all it can do
for the moment, and is waiting for a response from the client. If the client
is too busy to respond within the timeout interval, or ADSM has a lot of data
to sift through (such as a huge directory tree??) , then it would be curtains
for your session.....
Just a thought.....
Jerry Lawson
jlawson AT thehartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Idletimeout for no reason
02-25-97 09:16 PM
I am wondering if anyone else has seen this behaviour. On a small
number of clients, we are seeing message ANS4017E on the client caused
by the IDLETIMEOUT (20 minutes) being reached on the server (MVS level
10) during backup and, in two cases, on a restore operation. One AIX
client is failing backup consistently every night. This client is not
doing anything else at the time, and does not have an excessive number
of directories or excessively large directories.
One OS/2 client is failing the same way although after the third retry,
the backup succeeds.
A NetWare server trying to restore a directory tree containing about
200M of files runs for several minutes, creates the directory structure,
and restores several files before apparently stopping in the middle of
restoring a file. Q SESS shows wait time just building up until the
IDLETIMEOUT hits. No tape mounts or messages outstanding.
Any suggestions on what to look for here would be greatly appreciated.
Thanks
Sam Sheppard
San Diego Data Processing Corp.
shs AT sddpc.sannet DOT gov
|
