Windows Server

Raymond White · Guest

When I view my 3270 sessions in the viewer all the
sessions look correct except the print sessions. They are
showing up as LU1 and not LU3 print sessions. We have the
BARR/RJE software running and we also have LU6.2,TN3270,
and LU2 displays. All seem correct except the print
sessions.

Imelda Irby [MSFT] · Guest

Hi Raymond,

I have done research on your issue here, but I am not quite sure what viwer
you are refering to in HIS, can you please explain?

Thank you,

Imelda Irby, MCSE
Microsoft® HIS 2000/SNA Server Support Team

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS" with no
warranties, and confers no rights.

Neil Pike · Guest

Raymond - I assume this is purely cosmetic and doesn't affect anything
operationally?

Neil Pike MVP/MCSE. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise)

Guest · Posted: Fri Sep 10, 2004 5:20 am Post subject: RE: LU3 Printing

In the SNA manager under tools is a APPC-3270 session
viewer. My print sessions show up here as LU1 sessions,
and when I make any changes to the print session in the
SNA manager that should affect LU3 printing it absolutely
makes no changes to the print. I am having a lot of
problems with my print either not being formatted
correctly or missing pieces of data.

Neil Pike · Guest

Raymond - you're probably going to need to open a case with MS PSS on this
one. They'll want a copy of your com.cfg file, plus SNAPrint traces of when a
"faulty" print goes through.

It will be much quicker to get it resolved that way rather than via the
newsgroups.

Neil Pike MVP/MCSE. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise)

Imelda Irby [MSFT] · Guest

Hello Raymond,

I am going to focus on this piece of information in your response and send
you a write up, to get your SNA environment stable, after doing this
sometimes all problems dissapear, but if not then you can take traces and
open a case with us.

" I am having a lot of problems with my print either not being formatted
correctly or missing pieces of data."

Below is the action plan:

*****
There are several components required for a stable printing environment
within HIS
2000 and SNA 4 SP4. Any one of these components can cause a variety of
printing
issues. Some of these issues are hanging print services, print sessions
stuck in
spooling,and grabbled formatting.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<>
Resolution

To build a stable host printing environment there are three areas that must
be
addressed:

1. Printers need to be defined locally using either TCP or LPR locally
defined
ports.
2. Print Drivers should be Microsoft certified drivers.
3. Unused drivers must be removed.

Locally Defined Printers:
Undefined printers
The term “Undefined Printer” refers to a feature that allows the output
from an SNA
Print Service session to be directed to a printer that has not been defined
in
Windows NT Server. This is configured by typing the UNC path of the shared
network
printer into the printer field of the SNA Server printer session
properties, or by
selecting a printer using the “Network” button from the Print Setup dialog
in the
SNA printer session properties.

An SNA Print Service session configured to use an undefined printer uses an
OpenPrinter call to initiate a print job with Windows NT Server. Windows
NT Server
then creates a temporary connection to the Remote Print Server to allow the
SNA
print session to be activated. For this job, the spooler service will copy
the
driver files onto the local system using RPC requests, and it will use the
Remote
Print Provider (win32spl.dll). The spooler creates a cache containing the
driver
version information, and updates the registry with the cached information.
At the
end of connection, when ClosePrinter is called, the driver files stay on
the system
but the cached information is deleted from the registry.

When the next print job is received from the host, another OpenPrinter call
is made
to activate the SNA print session. The spooler detects the existence of
the
printer driver, however the information in the cache has been removed. The
spooler
service contacts the remote print provider to compare the printer driver
files, and
all of the cached information is copied again in the registry. The process
of
comparing driver files creates a large amount of SMB and RPC traffic on the
network, and can be avoided by creating a permanent connection to the
Remote Print
Server.

Resolution: To define the printers locally using either TCP or LPR printing.

Third Print Drivers:
Some third-party print drivers expect a DEVMODE structure to be a certain
size.
Specifically, such drivers expect dmDriverExtra to be set properly. They do
not do
any error checking. The SNA Print Service was not setting this field and
would
create a structure smaller than the
print driver is expecting. Because the third-party driver would not check
the size
of the structure that was was passed to it, it writes beyond the size of
the
structure, which causes numerous problems, up to and including
blue-screens. A QFE
fix was generated for this problem, but does not necessary resolve all
problems
with 3rd party print drivers that are uncertified. NOTE: This is most
apparent in
print drivers from Hewlett Packard.

Resolution: Change these to the coordinating Microsoft drivers.

Unused Drivers:
Because of similar calls within the driver code these will cause mismatches
resulting in printing issues.

Resolution: Uninstall all unused drivers.

The steps to uninstall the unused drivers that I have outlined below:

Start button
Settings
Printers
File
Server Properties
Drivers Tab
There you can delete the unused drivers.

Thank you,

Imelda Irby, MCSE
Microsoft® HIS 2000/SNA Server Support Team

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS" with no
warranties, and confers no rights.

Guest · Posted: Wed Oct 06, 2004 9:40 pm Post subject: RE: LU3 Printing

Imelda,
Thanks for your reply,it was extremely informative
and helpfull. We are running the BARR RJE Print and File
software on the same server as the HIS. The BARR product
uses it's own print drivers, could these drivers possibly
be causing a problem with my SNA print? Just a thought.

Thanks,

Raymond

Imelda Irby [MSFT] · Guest

That is posssible, I don't know much about that product, but in this case
those are not MS certified drivers, so its a good chance that it causing a
problem with SNA printing. One of the events that you can look for in the
event viewer is the one below. Also, just so you know we have HIS SP1
printing hotfixes, if you have not applied hot fixes to HIS yet, it might
help.
Event Type: Warning
Event Source: SNA Virtual Print Driver
Event Category: None
Event ID: 25
Date: 7/10/2002
Time: 12:54:04 PM
User: N/A
Computer: SNAGW10

Thank you,

Imelda Irby, MCSE
Microsoft® HIS 2000/SNA Server Support Team

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS" with no
warranties, and confers no rights.

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1