Printing from S/36 or AS/36 Fails when Using Host Print Server (194935)


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 Q194935

SYMPTOMS

The Host Print Server introduced with SNA Server 3.0 is unable to successfully print data from System/36 (S/36) or Advanced System/36 (AS/36) systems. If an Advanced Program-to-Program Communications (APPC) print session is defined for use with an S/36 or AS/36 system, the APPC print session will usually stay in an Inactive or Pending state in SNA Server Manager when it attempts to activate.

CAUSE

The Host Print Server was not originally designed to differentiate between AS/400 and S/36 (or AS/36) printing. Therefore, it does not send the correct Program Initialization Parameter (PIP) data to S/36 or AS/36 systems to allow for successful initialization of a print device on these systems.

SNA Server 3.0 Service Pack 2 added an update that allowed the System Type for APPC print sessions to be specified as either AS/400 or System/36. This option was exposed under the APPC tab for an APPC print session in SNA Server Manager. When this option is set to System/36, S/36- and AS/36- specific PIP data is set to the remote system.

In addition to this change, additional testing revealed that additional modifications were needed to allow for additional S/36- and AS/36-specific PIP data, and to allow the print sessions to be properly de-allocated and closed.

RESOLUTION

To resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack


STATUS

Microsoft has confirmed that this is a problem in SNA Server versions 3.0 and 4.0. This problem was first corrected in SNA Server version 4.0 Service Pack 3.

MORE INFORMATION

After applying the update, the APPC print session needs to be configured with the System Type set to System/36 in SNA Server Manager under the APPC tab of the Print Session Properties dialog box. This causes the Host Print Server to send the correct PIP data to the S/36 or AS/36 system to initiate the print session. In addition, the AS/400 Device Name parameter under the APPC tab of the Print Session Properties dialog box must be set to a two- digit value that specifies the Target-ID of the S/36 or AS/36 system.

Modification Type:MinorLast Reviewed:7/13/2004
Keywords:kbbug kbfix kbsna400sp3fix KB194935
©2004 Microsoft Corporation. All rights reserved.