RE: Client Access Sessions taking forever to bring up Signon Screen

[Joe Giusto <JGiusto@xxxxxxxxxxxx>]

Yes, it is TCP/IP.






-----Original Message-----
From:   Terry.Rhoades@blum.com [SMTP:Terry.Rhoades@blum.com]
Sent:   Tuesday, January 09, 2001 10:18 AM
To:     MIDRANGE-L@midrange.com
Subject:        Re: Client Access Sessions taking forever to bring up Signon
Screen


What photocol is being used by Client Access?   TCP/IP?




 
We are experiencing a very long delay when starting Client Access sessions.
Sometimes it is taking 5 - 10 minutes to get to the signon screen.  This
usually occurs when there is an interactive job that is taking a large
amount of resources.  I have noticed that the job QTVDEVICE is running at
Priority 50.
My thought was to  change this priority to 20 or below so that users will
stop complaining about the delay for the signon screen.

The question is, where is the best place to do this?  I was thinking about
changing the Class description, but have been unable to determine which one
is being used, and I also do not what other jobs to use this priority (which
would bring the system to it knees if there are other tasks that share this
class/routing entry).

Thank you very much for any suggestions that you can offer.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---