Absolute Vertical Move Command Handled Incorrectly If PDT Used (195402)
The information in this article applies to:
- Microsoft SNA Server 3.0
- Microsoft SNA Server 3.0 SP1
- Microsoft SNA Server 3.0 SP2
- Microsoft SNA Server 3.0 SP3
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
This article was previously published under Q195402 SYMPTOMS
AS/400 print jobs that contain the Absolute Vertical Move SCS Command will
print with incorrect formatting if the AS/400 print session is configured
to use a Printer Definition Table (PDT) file. The incorrect formatting will
appear as data printing farther down the page then it is supposed to print.
As an example, a print job that contains an Absolute Vertical Move command
at the end of line 12 that specifies printing should continue on line 24
will generate printed output that has the next data printed on line 36
instead of on line 24.
This does not occur if the AS/400 print session is not configured to use a
PDT in SNA Server Manager.
CAUSE
The virtual print driver used by SNA Server's host print service does not
keep track of the print job's current line number when a PDT is used for a
print session. Consequently, the 5250 print provider always uses a current
line number of 1 when calculating the number of lines to move down the page
when processing an Absolute Vertical Move command. This results in extra
carriage returns being sent to the printer, which moves the print data too
far down the page.
The current line number is tracked when a PDT is not used, which is why
this problem does not occur when a PDT is not used for the AS/400 print
session.
RESOLUTIONSNA Server 3.0To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack
SNA Server 4.0
This problem was corrected in the latest SNA Server version 4.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):
STATUS
Microsoft has confirmed this to be a problem in SNA Server versions 3.0,
3.0 Service Pack 1, 3.0 Service Pack 2, 3.0 Service Pack 3, 4.0, and 4.0
Service Pack 1. This problem was first corrected in SNA Server 3.0 Service Pack 4.
| Modification Type: | Minor | Last Reviewed: | 3/21/2005 |
|---|
| Keywords: | kbbug kbfix KB195402 |
|---|
|