Re: Display device error

["Jim Franz" <franz400@xxxxxxxxxxxx>]

Dave - please describe your network setup.
Have seen this msg often when 400 times out a connection because "somehow"
the
pc/Client Access failed to respond in time.
Is this all local area network? Are there good powered switches in the lan
or "cheap" hubs? Is there periods of large amount of traffic on lan?
If wide area network, is there a sufficient pipe to handle all traffic? Are
the routers sufficient (with enough memory) to handle (remember the network
only as fast as slowest link.
Is this totally TCP/IP or is SNA traffic mixed on the local or wide network?
Is this 10 or 100m ethernet? Do your network people have traffic analyzer to
determine if massive retries going on? Or lots of traffic they are unaware
of?
Don't settle for the usual "Windows is running fine-it must be the 400"
answer.
jim
----- Original Message -----
From: "Dave Snyder" <dsnyder@xxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, February 27, 2003 3:36 PM
Subject: Re: Display device error


> This problem is very random - not happening to the same users all the
time. Most are actively working at their workstations.
> Dave
>
> >>> "Paul Nelson" <pnelson@xxxxxxxxxx> 2/27/03 3:21:15 PM >>>
> Is the user actively pounding away, or are they letting the device sit for
a
> period of time when they notice the disconnect? Does this happen to all
the
> users, or just a few? Have the wiring checked for a source of electrical
> noise and for solid continuity. Sometimes a new source of interference is
> placed too close too your network wiring, be it a welder or a paper
> shredder.
>
> Once you understand what the users are doing, and when you know that your
> network is good, check your TCP/IP time out values.
>
> Paul Nelson
> Arbor Solutions, Inc.
> 708-670-6978 Cell
> 708-923-7354 Home
> pnelson@xxxxxxxxxx
>
> ----- Original Message -----
> From: "Dave Snyder" <dsnyder@xxxxxxxxxx>
> To: <midrange-l@xxxxxxxxxxxx>
> Sent: Thursday, February 27, 2003 1:48 PM
> Subject: Display device error
>
>
> What type of things would cause this error? It is happening to us more and
> more. The symptoms are that the user is working and the session just kicks
> out. Any special parameters that I should look at?
> Dave
>
>  Message ID . . . . . . :   CPF5140       Severity . . . . . . . :   70
>  Message type . . . . . :   Information
>  Date sent  . . . . . . :   02/27/03      Time sent  . . . . . . :
> 13:28:09
>
>  Message . . . . :   Session stopped by a request from device QPADEV002Z.
>  Cause . . . . . :   The request shutdown was caused by either the user
> turning
>    the power off, by a device error, or the ASCII controller inactivity
> timer
>    expired.
>  Recovery  . . . :   Close the files and vary the device off (VRYCFG
> command).
>    If the problem occurs again, enter the ANZPRB command to run problem
>    analysis.
>
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>