********************************************************************* These hotfixed modules are Build 439 of the SNA Server Print Service. ********************************************************************* This fix includes: - all SNA Server 3.0 Service Pack 1 fixes - all post-Service Pack 1 fixes through 439. For a list of SNA Server Service Pack 1 fixes, see sna30sp1.hlp included with the Service Pack 1. To apply the newest SNA Server Print Service, perform the following: 1. Stop SNAPrint Service through SNA Server Manager or through Control Panel, Services applet. 2. Stop SNA Server Manager. 3. Rename the following files in the \system directory: hplj2.pdf msg5250.dll pdfcomp.exe ppd3270.dll ppd5250.dll snanls.dll snaprint.exe snaxlt.dll winvprt.dll prmngext.dll snacfg.dll snacfg.exe 4. Extract using: C:\temp> print439 -d. This will extract the subdirectories as well. The subdirectories DLL and EXE are the symbol files for the actual binaries. These should be copied over to the corresponding \symbols\\ directory. 5. Copy the following files to the \system directory: hplj2.pdf msg5250.dll pdfcomp.exe ppd3270.dll ppd5250.dll snanls.dll snaprint.exe snaxlt.dll winvprt.dll prmngext.dll snacfg.dll snacfg.exe 6. Restart SNAPrint and SNA Server Manager. Article Titles: =============== Some SNA Print Service Jobs Print Using Condensed Font. (**This was actually included in print437.exe**) Last Byte of Transparent Section Interpreted Incorrectly. SNA Server Print Service Doesn’t Support Print Position > 132. Buffer Pool Error 685 Printing Two Large Jobs Simultaneously Zero Length RU Causes Job Causes Subsequent Jobs to Hang. SNA APPC Print Server Sessions Inactive with System 36 Host Request Definite Response Should Signal When Job Sent To Printer. Article Details: ================ ***************************************************************************** Some SNA Print Service Jobs Print Using Condensed Font. -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server version 3.0 and 3.0 sp1. -------------------------------------------------------------------------- SYMPTOMS ======== Some SNA Server Print Service jobs print using condensed font when they should not. RESOLUTION ========== A fix has been made to correct this problem. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server 3.0 and 3.0 sp1. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. ***************************************************************************** Last Byte of Transparent Section Interpreted Incorrectly. -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server version 3.0 SP1 -------------------------------------------------------------------------- SYMPTOMS ======== The last byte in a transparent section gets interpreted as being outside the transparent section when the transparent section is immediately preceded by a control character (IE - “0D”). For instance, the following sequence has ‘0D’ (carriage return) followed by a transparent section starting with ‘35’. In this case, the 1B (Esc character) would be inappropriately dropped and therefore the remaining bytes would be sent to the printer without the leading Esc character. This would cause the remaining bytes to be printed when they were actually intended to be part of the escape sequence. 0D35011B 5081F2F2 D9 CAUSE ===== When there is a control character immediately preceding transparent sections, there was a bug in the code which caused the print server to believe the transparent section to be one byte shorter than it really was. RESOLUTION ========== A change was made to check whether a transparent byte has actually been sent to the printer before decrementing the number of transparent bytes left to be processed. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 3.0 SP1. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. ***************************************************************************** SNA Server Print Service Doesn’t Support Print Position > 132. -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server version 3.0 SP1 -------------------------------------------------------------------------- SYMPTOMS ======== Print Server inserts a NL (new line) character after print position 132 even if the default page width is set to a value greater than 132. The Spec. at page 2-22 says: The NL order is executed only when encountered during an unformatted printout; this is, a printout that does not have a line-length format specified. When an NL order is encountered in the buffer, the priner performs an NL function. If no NL order is encountered before the printer reaches the end of a line (as determined by the maximum print position), the printer automatically performs an NL function and continues printing. If an NL order is encountered at one character position past the maximum print position, the 3230,3268,3284,3286,3287 and 3288 printer will perform two NL functions; the 3262 and 3289 printers will perform one NL function. RESOLUTION ========== Previously, LU3 printing had a maximum line length of 132 characters. This is an enhancement to allow users to specify the line width using the SNA Server Manager. Note: The maximum MPP (maximum print position) we support in the code is 255 characters, but users may specify any value in the SNA Server Manager. This change also includes code to set the MPP to 255 if the user specifies a value greater than this. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 3.0 SP1. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. ***************************************************************************** Buffer Pool Error 685 Printing Two Large Jobs Simultaneously -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server for Windows NT, versions 3.0 SP1 -------------------------------------------------------------------------- SYMPTOMS ======== While attempting to process two large print jobs (approx. 700 pages) the SNA 3270 Emulator logs an event 685, indicating a failure to extend a buffer pool. When this failure occurs the affected component is terminated, resulting in the failure of both print jobs. CAUSE ===== The Print Server will occasionally produce an extra credit message. Normally this would not cause a problem; the Print Server would just cope with the extra message it got sent. However, in the case of a very large job, the print server never had time to catch up with the extra messages. The input queue just got longer and longer until the buffer limit was reached (3000 outstanding messages). RESOLUTION ========== The fix was to defer sending credit messages until we are certain that we will process the message immediately, and not put it back on the queue. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 3.0 SP1. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. ***************************************************************************** Zero Length RU Causes Job Causes Subsequent Jobs to Hang. -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server version 3.0 SP1 -------------------------------------------------------------------------- SYMPTOMS ======== If a zero length RU is encountered and Job Monitoring is enabled, any subsequent jobs sent to SNA Server Print Service will hang. DLC DAF:E9 OAF:01 ODAI:off Normal DLC BID RQD DFC FI BC EC DR1 PI DLC DLC ---- Header at address 010342E0, 1 elements ---- DLC 01020005 6C002C00 E9010005 01001C01 <....l.,.Z.......> DLC DLC ---- Element at address 0152CFF0, start 10, end 13 ---- DLC 4B8100C8 FMI ------------------------------------------------------------ FMI 01027102->10120600 FMIST CTRL BID REQ FMI ACK required Msg key:6 FMHI BCI ECI RBI FMI FMI ---- Header at address 010342E0, 0 elements ---- FMI 02011401 E0012C00 E9010006 01001C01 <......,.Z.......> FMI ------------------------------------------------------------ FMI 10120600->01027102 FMIST CTRL BID ACK FMI Msg key:4 COMMIT EBI CDI SDI FMI FMI ---- Header at address 01034418, 0 elements ---- FMI 02021405 17001500 00000004 01005E02 <..............^.> DLC ------------------------------------------------------------ DLC 01020101->04160080 DLC DATA DLC DAF:01 OAF:E9 ODAI:off Normal DLC BID +RSP DFC FI BC EC DR1 PI DLC DLC ---- Header at address 010342E0, 1 elements ---- DLC 02011401 E0002C00 01E90005 01001C01 <......,..Z......> DLC DLC ---- Element at address 0152B7FC, start 10, end 13 ---- DLC CB8100C8 <.a.H > Zero Length RU: DLC ------------------------------------------------------------ DLC 04160080->01020101 DLC DATA DLC DAF:E9 OAF:01 ODAI:off Normal DLC RQE FMD BC EC DR1 PI BB EB DLC DLC ---- Header at address 010342E0, 1 elements ---- DLC 00020011 6A002C00 E9010006 01001C01 <....j.,.Z.......> DLC DLC ---- Element at address 0152B7FC, start 10, end 12 ---- DLC 0391C0 <.j. > DLC ------------------------------------------------------------ DLC 01020101->04160080 DLCST RSRC DLC Credit:4 DLC DLC ---- Header at address 01034418, 0 elements ---- DLC 04020004 17001500 00000004 01005E02 <..............^.> DLC ------------------------------------------------------------ DLC 01020101->04160080 DLC DATA DLC DAF:01 OAF:E9 ODAI:off Normal DLC +RSP FMD BC EC PI DLC DLC ---- Header at address 01034210, 1 elements ---- DLC 04020000 00002C00 01E90000 01002801 <......,..Z....(.> DLC DLC ---- Element at address 0152CFF0, start 10, end 12 ---- DLC 830100 FMI -------------------------------------------------------------- FMI 01027102->10120600 FMI DATA FMI NO ACK reqd Key:7 Seq:6 BCI ECI BBI EBI CEI FMI BBIUI EBIUI FMI FMI ---- Header at address 010342E0, 1 elements ---- FMI 00020007 6C0E2C00 E9010006 01001C01 <....l.,.Z.......> FMI -------------------------------------------------------------- FMI 01027102->10120600 FMIST SESS FMI Code:BETB FMI FMI ---- Header at address 01034620, 0 elements ---- FMI 05020007 00002C00 E9010002 01001C01 <......,.Z.......> FMI -------------------------------------------------------------- FMI 10120600->01027102 FMIST RSRC FMI Credit:1 FMI FMI ---- Header at address 01034620, 0 elements ---- FMI 04010001 E0012C00 E9010006 01005E02 <......,.Z.....^.> FMI -------------------------------------------------------------- FMI 10120600->01027102 FMIST ACK FMI Msg key:7 Replies:5376 Sequence:6 FMI FMI ---- Header at address 01034620, 0 elements ---- FMI 01020007 17001500 00000006 01005E02 <..............^.> DLC -------------------------------------------------------------- DLC 04160080->01020101 DLCST RSRC DLC Credit:4 DLC DLC ---- Header at address 01034418, 0 elements ---- DLC 04020004 00002C00 01E90000 01001C01 <......,..Z......> A request to start a new job is submitted from the host: DLC -------------------------------------------------------------- DLC 04160080->01020101 DLC DATA DLC DAF:E9 OAF:01 ODAI:off Normal DLC BID RQD DFC FI BC EC DR1 PI DLC DLC ---- Header at address 01034418, 1 elements ---- DLC 01B0B006 00002C00 E9010007 01001C01 <......,.Z.......> DLC DLC ---- Element at address 0152CFF0, start 10, end 13 ---- DLC 4B8100C8 This request is then passed over FMI to the SNA Server Print Service: FMI -------------------------------------------------------------- FMI 01027102->10120600 FMIST CTRL BID REQ FMI ACK required Msg key:8 FMHI BCI ECI RBI FMI FMI ---- Header at address 01034418, 0 elements ---- FMI 02011401 E0012C00 E9010008 01001C01 <......,.Z.......> There is no response from the SNA Server Print Service. CAUSE ===== If Job Monitoring is turned on for a session, jobs are not fully closed down until the printer has notified SNA Server Print Service that the job has finished printing. Unfortunately, a zero length job never starts printing so it never finishes and the job is never properly closed. RESOLUTION ========== A fix was made so that the SNA Server Print Service will generate a message that the zero length RU was printed successfully thus giving it permission to close the session down. This will allow any subsequent jobs to then be printed. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 3.0 SP1. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. ***************************************************************************** SNA APPC Print Server Sessions Inactive with System 36 Host -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server for Windows NT, version 3.0, 3.0 SP1 -------------------------------------------------------------------------- SYMPTOMS ======== APPC Print sessions defined on an SNA 3.0 Server stay in an "Inactive" status and will not go to "Available" 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 we are emulating an AS/400. To communicate with either a S/36 or an AS/36 Host, SNA Server must send 0x0500. STATUS ====== Microsoft has confirmed this to be a problem in SNA version 3.0 and 3.0 SP1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. ***************************************************************************** Request Definite Response Should Signal When Job Sent To Printer. -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server version 3.0 SP1 -------------------------------------------------------------------------- SYMPTOMS ======== If the Monitor Job, Request Definite Response option is checked in a printer session’s property page, the definite response message is sent to the host when the print job has handed it to the Windows NT spooler. Instead, it should perform this when Windows NT has been notified by the physical printer that the job has completed. RESOLUTION ========== The fix is to send definite response when Windows NT has been notified by the physical printer that the job has completed. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 3.0 SP1. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.