| Author |
Message |
Stan Fry
Guest
|
 Posted:
Fri Oct 07, 2005 8:51 pm Post subject:
SNA LU sessions printing weird char. |
|
|
I have an instance where some (not all) mainframe print jobs are printing
boxes where spaces should be in some reports. They are using a std Microsoft
Laser Jet 4 driver from Windows 2000. HIS 2000 SP2 is installed and all the
OS patches. I have tried more specific printer drivers and postscript with
no luck. If I switch the driver to generic text I then see dots (.) where
the boxes were. I think its some kind of ASCII control char sequence were
receiving from the host that's not interputed correctly Are there any
documents to assist in trouble shooting, a patch or article? I have
exhausted my resources. Could HIS 2000 SP2 have introduced something? |
|
| Back to top |
|
 |
Neil Pike
Guest
|
| Posted:
Sat Oct 08, 2005 8:50 pm Post subject:
Re: SNA LU sessions printing weird char. |
|
|
Stan - the fact that the generic text driver prints dots makes me think that
they aren't actually spaces on the mainframe. More likely they are binary
zeroes or some other special character.
Best bet would be to look at the files on the mainframe before they're printed
- use ispf browse hex mode or file-aid or similar.
| Quote: | I have an instance where some (not all) mainframe print jobs are printing
boxes where spaces should be in some reports. They are using a std Microsoft
Laser Jet 4 driver from Windows 2000. HIS 2000 SP2 is installed and all the
OS patches. I have tried more specific printer drivers and postscript with
no luck. If I switch the driver to generic text I then see dots (.) where
the boxes were. I think its some kind of ASCII control char sequence were
receiving from the host that's not interputed correctly Are there any
documents to assist in trouble shooting, a patch or article? I have
exhausted my resources. Could HIS 2000 SP2 have introduced something?
|
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP |
|
| Back to top |
|
|
Charles Ezzell (MSFT)
Guest
|
| Posted:
Mon Oct 10, 2005 4:51 pm Post subject:
Re: SNA LU sessions printing weird char. |
|
|
What Neil said <G>
A trace of the datastream would tell us what is being sent. But, without
that I'm guessing here <G>
Is this an LU1 print job? On your snaprint service properties dialog, there
is the following option, which in unchecked by default.
Click Ignore Characters 3F and Under to cause the print service to ignore
Hexadecimal characters 3F and below. In LU 1 data streams, this option
causes hexadecimal characters below 40 to be replaced by spaces.
Note that by checking this, it could potentially break other print jobs that
"need" those characters. Turning this on affects ALL print sessions (it is
global).
--
HTH,
Charles Ezzell
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.0000633b.0c7b4da9@compuserve.com...
| Quote: | Stan - the fact that the generic text driver prints dots makes me think
that
they aren't actually spaces on the mainframe. More likely they are binary
zeroes or some other special character.
Best bet would be to look at the files on the mainframe before they're
printed
- use ispf browse hex mode or file-aid or similar.
I have an instance where some (not all) mainframe print jobs are
printing
boxes where spaces should be in some reports. They are using a std
Microsoft
Laser Jet 4 driver from Windows 2000. HIS 2000 SP2 is installed and all
the
OS patches. I have tried more specific printer drivers and postscript
with
no luck. If I switch the driver to generic text I then see dots (.)
where
the boxes were. I think its some kind of ASCII control char sequence were
receiving from the host that's not interputed correctly Are there any
documents to assist in trouble shooting, a patch or article? I have
exhausted my resources. Could HIS 2000 SP2 have introduced something?
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
|
|
|
| Back to top |
|
|
Neil Pike
Guest
|
| Posted:
Wed Oct 26, 2005 4:51 pm Post subject:
Re: SNA LU sessions printing weird char. |
|
|
Stan - there were certainly a whole bunch of print fixes between SP1 and SP2.
I was running post-SP1 hotfixes for a long time until SP2 came out (migrated it
all to HIS 2004 now).
Search the Kb (or Technet) with the keywords
kbfix kbHostIntegServ2000SP1 print
to get a list of public fixes.
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP |
|
| Back to top |
|
|
Stan Fry
Guest
|
| Posted:
Wed Oct 26, 2005 4:51 pm Post subject:
Re: SNA LU sessions printing weird char. |
|
|
Charles,
Did anything change between HIS 2000 SP1 and SP2 that pertains to this
print function? Why I ask is, it all worked before and the only recent
change was to SP2. Either this broke this functionality or the host
application changed. At this account it is not likely.
Stan
"Charles Ezzell (MSFT)" <charliee@online.microsoft.com> wrote in message
news:%23PZ$91ZzFHA.2072@TK2MSFTNGP14.phx.gbl...
| Quote: | What Neil said <G
A trace of the datastream would tell us what is being sent. But, without
that I'm guessing here <G
Is this an LU1 print job? On your snaprint service properties dialog,
there is the following option, which in unchecked by default.
Click Ignore Characters 3F and Under to cause the print service to ignore
Hexadecimal characters 3F and below. In LU 1 data streams, this option
causes hexadecimal characters below 40 to be replaced by spaces.
Note that by checking this, it could potentially break other print jobs
that "need" those characters. Turning this on affects ALL print sessions
(it is global).
--
HTH,
Charles Ezzell
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.0000633b.0c7b4da9@compuserve.com...
Stan - the fact that the generic text driver prints dots makes me think
that
they aren't actually spaces on the mainframe. More likely they are
binary
zeroes or some other special character.
Best bet would be to look at the files on the mainframe before they're
printed
- use ispf browse hex mode or file-aid or similar.
I have an instance where some (not all) mainframe print jobs are
printing
boxes where spaces should be in some reports. They are using a std
Microsoft
Laser Jet 4 driver from Windows 2000. HIS 2000 SP2 is installed and all
the
OS patches. I have tried more specific printer drivers and postscript
with
no luck. If I switch the driver to generic text I then see dots (.)
where
the boxes were. I think its some kind of ASCII control char sequence
were
receiving from the host that's not interputed correctly Are there any
documents to assist in trouble shooting, a patch or article? I have
exhausted my resources. Could HIS 2000 SP2 have introduced something?
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
|
|
|
| Back to top |
|
|
Charles Ezzell (MSFT)
Guest
|
| Posted:
Wed Oct 26, 2005 8:51 pm Post subject:
Re: SNA LU sessions printing weird char. |
|
|
Nothing I can think of at this moment would have changed to affect printing
in this area, and I see most (95%) of the print fixes we release. If you
could open a case, it should be simple to repro the problem on our end. We
would need nodemsg tracing (including bind) to create a script for the data
stream, the com.cfg file (for print session configuration), snaprint
internal traces, and a report run (the engineer would supply the tool) that
would give us the configuration of your system, right down to the print
drivers in use. Actually, if you did the traces, the report tool would grab
the trace files and com.cfg file automatically.
--
HTH,
Charles Ezzell
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Stan Fry" <stanleyfry@hotmail.com> wrote in message
news:eFMvEOj2FHA.2364@TK2MSFTNGP12.phx.gbl...
| Quote: | Charles,
Did anything change between HIS 2000 SP1 and SP2 that pertains to this
print function? Why I ask is, it all worked before and the only recent
change was to SP2. Either this broke this functionality or the host
application changed. At this account it is not likely.
Stan
"Charles Ezzell (MSFT)" <charliee@online.microsoft.com> wrote in message
news:%23PZ$91ZzFHA.2072@TK2MSFTNGP14.phx.gbl...
What Neil said <G
A trace of the datastream would tell us what is being sent. But, without
that I'm guessing here <G
Is this an LU1 print job? On your snaprint service properties dialog,
there is the following option, which in unchecked by default.
Click Ignore Characters 3F and Under to cause the print service to ignore
Hexadecimal characters 3F and below. In LU 1 data streams, this option
causes hexadecimal characters below 40 to be replaced by spaces.
Note that by checking this, it could potentially break other print jobs
that "need" those characters. Turning this on affects ALL print sessions
(it is global).
--
HTH,
Charles Ezzell
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.0000633b.0c7b4da9@compuserve.com...
Stan - the fact that the generic text driver prints dots makes me think
that
they aren't actually spaces on the mainframe. More likely they are
binary
zeroes or some other special character.
Best bet would be to look at the files on the mainframe before they're
printed
- use ispf browse hex mode or file-aid or similar.
I have an instance where some (not all) mainframe print jobs are
printing
boxes where spaces should be in some reports. They are using a std
Microsoft
Laser Jet 4 driver from Windows 2000. HIS 2000 SP2 is installed and all
the
OS patches. I have tried more specific printer drivers and postscript
with
no luck. If I switch the driver to generic text I then see dots (.)
where
the boxes were. I think its some kind of ASCII control char sequence
were
receiving from the host that's not interputed correctly Are there any
documents to assist in trouble shooting, a patch or article? I have
exhausted my resources. Could HIS 2000 SP2 have introduced something?
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in