|
<P>Dave....what version of Client Access are you running? OS400 level? We are experiencing the same problem....many users just dropping and I know they are not closing with an X or anything like power problem. It seems since we put up the last CAE level (don't know exact number as I am home). </P><P>Gail Crane<BR>Johanson Manufacturing Corp.<BR>phone 973-334-2676<BR>gcrane@xxxxxxxxxxxxxxx</P><P> <BR><FONT SIZE=2><B>"Dave Snyder" <dsnyder@xxxxxxxxxx></B></FONT><BR><FONT SIZE=2>Sent by: midrange-l-bounces@xxxxxxxxxxxx</FONT><BR><FONT SIZE=2>02/27/2003 03:36 PM</FONT><BR><FONT SIZE=2>Please respond to Midrange Systems Technical Discussion</FONT><BR><BR> <FONT SIZE=2>To:</FONT> <FONT SIZE=2>midrange-l@xxxxxxxxxxxx</FONT><BR> <FONT SIZE=2>cc:</FONT> <BR> <FONT SIZE=2>bcc:</FONT> <BR> <FONT SIZE=2>Subject:</FONT> <FONT SIZE=2>Re: Display device error</FONT><BR> <BR><BR></P><P><FONT FACE="Monospace,Courier">This problem is very random - not happening to the same users all the time. Most are actively working at their workstations.<BR>Dave<BR></FONT><BR><FONT FACE="Monospace,Courier">>>> "Paul Nelson" <pnelson@xxxxxxxxxx> 2/27/03 3:21:15 PM >>><BR>Is the user actively pounding away, or are they letting the device sit for a<BR>period of time when they notice the disconnect? Does this happen to all the<BR>users, or just a few? Have the wiring checked for a source of electrical<BR>noise and for solid continuity. Sometimes a new source of interference is<BR>placed too close too your network wiring, be it a welder or a paper<BR>shredder.<BR></FONT><BR><FONT FACE="Monospace,Courier">Once you understand what the users are doing, and when you know that your<BR>network is good, check your TCP/IP time out values.<BR></FONT><BR><FONT FACE="Monospace,Courier">Paul Nelson<BR>Arbor Solutions, Inc.<BR>708-670-6978 Cell<BR>708-923-7354 Home<BR>pnelson@xxxxxxxxxx<BR></FONT><BR><FONT FACE="Monospace,Courier">----- Original Message -----<BR>From: "Dave Snyder" <dsnyder@xxxxxxxxxx><BR>To: <midrange-l@xxxxxxxxxxxx><BR>Sent: Thursday, February 27, 2003 1:48 PM<BR>Subject: Display device error<BR></FONT><BR><BR><FONT FACE="Monospace,Courier">What type of things would cause this error? It is happening to us more and<BR>more. The symptoms are that the user is working and the session just kicks<BR>out. Any special parameters that I should look at?<BR>Dave<BR></FONT><BR><FONT FACE="Monospace,Courier">Message ID . . . . . . : CPF5140 Severity . . . . . . . : 70<BR>Message type . . . . . : Information<BR>Date sent . . . . . . : 02/27/03 Time sent . . . . . . :</FONT><BR><FONT FACE="Monospace,Courier">13:28:09<BR></FONT><BR><FONT FACE="Monospace,Courier">Message . . . . : Session stopped by a request from device QPADEV002Z.<BR>Cause . . . . . : The request shutdown was caused by either the user</FONT><BR><FONT FACE="Monospace,Courier">turning<BR>the power off, by a device error, or the ASCII controller inactivity</FONT><BR><FONT FACE="Monospace,Courier">timer<BR>expired.</FONT><BR><FONT FACE="Monospace,Courier">Recovery . . . : Close the files and vary the device off (VRYCFG<BR>command).</FONT></P><UL><FONT FACE="Monospace,Courier">If the problem occurs again, enter the ANZPRB command to run problem<BR>analysis.</FONT><BR><BR><BR><BR><BR></UL><P><FONT FACE="Monospace,Courier">_______________________________________________<BR>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list<BR>To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>To subscribe, unsubscribe, or change list options,<BR>visit: <A HREF=http://lists.midrange.com/mailman/listinfo/midrange-l>http://lists.midrange.com/mailman/listinfo/midrange-l</A><BR>or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>Before posting, please take a moment to review the archives<BR>at <A HREF=http://archive.midrange.com/midrange-l>http://archive.midrange.com/midrange-l</A>.<BR></FONT><BR><FONT FACE="Monospace,Courier">_______________________________________________<BR>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list<BR>To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>To subscribe, unsubscribe, or change list options,<BR>visit: <A HREF=http://lists.midrange.com/mailman/listinfo/midrange-l>http://lists.midrange.com/mailman/listinfo/midrange-l</A><BR>or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>Before posting, please take a moment to review the archives<BR>at <A HREF=http://archive.midrange.com/midrange-l>http://archive.midrange.com/midrange-l</A>.<BR></FONT><BR><BR><BR><FONT FACE="Monospace,Courier">_______________________________________________<BR>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list<BR>To post a message email: MIDRANGE-L@xxxxxxxxxxxx<BR>To subscribe, unsubscribe, or change list options,<BR>visit: <A HREF=http://lists.midrange.com/mailman/listinfo/midrange-l>http://lists.midrange.com/mailman/listinfo/midrange-l</A><BR>or email: MIDRANGE-L-request@xxxxxxxxxxxx<BR>Before posting, please take a moment to review the archives<BR>at <A HREF=http://archive.midrange.com/midrange-l>http://archive.midrange.com/midrange-l</A>.</FONT></P>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.