Hello Les,
I have removed the PORT-9100 and indeed now I get the output on the print
er.
Also I tried this with both LPRXPSE and LPRXONE and both gave me output.
The
first in postscript and the second in plain text. The actual output doesn
't
differ all that much but the separation page is differ
Hello David,
>1) remove the PORT=9100. Port 9100 is the HP socket printing protocol,
not
LPR/LPD. The two are not interoperable, and RSCS doesn't know squat about
the HP protocol (it'd sure be nice if RSCS got IPP support -- hint, hint)
I tried without PORT (therefore with the default 515) an
> >Hello Les,
> >
> >I was looking through the handover from Dick. I have tried the EOT=N
> but no
> >luck either.
> >
> >The parms now look like:
> >PARM P002NT EXIT=LPRXPSE EPARM='EH=N EOT=N C=LPRP' HOST=161.9=0.24.70
> #
> >PORT=9100 PRINT=P002NT SECURE=NO TI
> >
> > #
> >
I notice you are trying to connect to port 9100 instead of 515 at the
printer (or print server). Is there an LPR deamon running at this
port. Try changing the definition to 515 and see if the problem
still persists.
The trace I am referring to is an RSCS link trace rather than a
TCP/IP trace
B
Hello Les,
I was looking through the handover from Dick. I have tried the EOT=N bu
t no
luck either.
The parms now look like:
PARM P002NT EXIT=LPRXPSE EPARM='EH=N EOT=N C=LPRP' HOST=161.9
0.24.70 #
PORT=9100 PRINT=P002NT SECURE=NO TI=20
#
HOSTN=europe.
>Hello Les,
>It did not work.
>Perhaps I miss something in the TCPIP environment.
>May be you have an example what parameters I need for the TCPIP.
Next try adding EPARM 'EOT=No'
This will cause the exit to stop sending an end of transmission character
after the separator page and data file.
If th
Hello Lawrence,
I gave it a try but it still does not work.
Maybe I miss something in the TCPIP environment.
Besides the port definition, do I need other TCPIP definitions?.
With regards, Dick
Hello Les,
It did not work.
Perhaps I miss something in the TCPIP environment.
May be you have an example what parameters I need for the TCPIP.
With regards, Dick
Hello Lawrence.
Thanks for your advise.
I will try it all today.
Regards, Dick
Hello Les,
I only print plain text like CMS members.
I will try your advise right away.
With regards, Dick
Mr Vandersluiszen,
Here's an RSCS definition I'm using right now to print PostScript files t
o
an IBM InfoPrint 2090E over TCP/IP:
LINKDEFINE US177 TYPE LPR QUEUE FIFO FORM * AST
PARM US177 EXIT=LPRXONE TCPID=TCPIP163 #
HOST=2xx.1x.2xx.177 EPARM='C=LPR S=N FF=N' PRINTER=
US177
Try adding EH=N to the link EPARM. This will stop the error handler from
being sent to the printer. Perhaps this is causing problems within the
printer.
Are you trying to print plain text or a postscript file?
Best Regards,
Les Geer
IBM z/VM and Linux Development
>We have a department printer
Hello,
We have a department printer to which I want to print CMS members.
The LPR TCPIP commands like LPRSET, LPR, LPQ and LPRM works fine.
It is also possible to use RSCS as a printserver but the combination of
RSCS printing over TCP/IP is not a lucky one till now.
When I send a print the define
13 matches
Mail list logo
