5250 Printing Causes High CPU Utilization (172484)
The information in this article applies to:
- Microsoft SNA Server 3.0
- Microsoft SNA Server 3.0 SP1
This article was previously published under Q172484 SYMPTOMS
An SNA Server system using the print server service for 5250 printing may
occasionally show very high CPU utilization, even though there are no print
jobs currently printing. In addition, the AS/400 that SNA Server is
connected to may also show an increase in its CPU utilization at the same
time.
You may notice that there are print jobs on the AS/400 print writers
waiting to be printed when this problem occurs.
An SNA Server Data Link Control (DLC) message traces shows repeated LUSTAT
messages being sent between the SNA Server computer and the AS/400 in rapid
succession while the problem is going on.
CAUSE
When a print request is received from a host, the print server issues a
StartDoc() call to initialize the connection to the printer that the print
session is configured to use. The CPU utilization problem occurs when the
StartDoc() call returns an error that the 5250 print provider does not
correctly handle. The print server fails to send an error message to the
AS/400 when the StartDoc() call fails and does not respond to the AS/400
print request at all. The result is that the print server and the AS/400
establish a loop by sending LUSTAT messages back and forth. The frequency
of these messages causes the CPU utilization on both systems to increase.
If the StartDoc() call is successful, the AS/400 print job is printed
normally.
STATUS
Microsoft has confirmed this to be a problem in SNA Server versions 3.0 and
3.0 Service Pack 1 (SP1). This problem was corrected in the latest SNA
Server version 3.0 U.S. Service Pack. For information on obtaining this
Service Pack, query on the following word in the Microsoft Knowledge Base
(without the spaces):
Modification Type: | Minor | Last Reviewed: | 7/14/2004 |
---|
Keywords: | kbbug kbfix kbnetwork KB172484 |
---|
|