APPC Print Sessions Inactive w/ System 36 or AS/36 Host

The information in this article applies to:

• Microsoft SNA Server, versions 3.0 and 3.0 Service Pack 1 (SP1)

SYMPTOMS

APPC print sessions defined on an SNA 3.0 Server stay in an inactive status and do not change to available status if the host is either a System/36 or an AS/36.

CAUSE

The PIP data sent in an APPC print session Attach contains a 2-byte field called "Reported System ID," which specifies which type of source system the SNA Print Server is trying to emulate. By default, SNA Server sends 0x0510 to indicate that an AS/400 is being emulated. To communicate with either an S/36 or an AS/36 Host, SNA Server must send 0x0500.

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):

   S E R V P A C K

Keywords          : snaprintservice kbfix3.00.sp2 kbnetwork
Version           : 3.0
Platform          : winnt