FW: IP printing from VM

[Les Geer (607-429-3580)]

>No, I haven't looked at grouping printers yet.=20
>
>I tried to specify a printer name and host IP address as the target, and
>got the same error -
>
>lpr profile exec a (asynchronous printer qeeple22
>

You need to either use the RSCS parameter, or define a GROUP LPR route
statement.
Help for the RSCS parameter:

RSCS linkid,nodeid
RSCS [EMAIL PROTECTED]
RSCS linkid AT nodeid
Identifies the RSCS link that provides a connection to a target print
daemon or device, where:

  o linkid is the one- to eight-character link identifier of the RSCS link
that provides the connection to the chosen print daemon or device.

  o nodeid is the one- to eight-character node name of the remote VM
system that provides the connection to a target chosen print daemon or
device.

When specific link and node values are not defined, "LPR" is used as the
default link identifier (linkid) for non-PostScript files, while "LPRP" is
used for PostScript files; the local node (as returned by the CMS IDENTIFY
command) is used for nodeid.


Best Regards,
Les Geer
IBM z/VM and Linux Development

Re: FW: IP printing from VM

[Marcy Cortes]

Ian, 

When I get a printer that doesn't work, I like the LPR command (direct
to the printer from your cms session) with the Trace option to find out
if the printer actually works and prints before I add it to RSCS.
Sometimes we have firewall holes that need to be punched or something
else is up with it.

This will show you that you can actually get there and that the printer
talks back to you.

LPR PROFILE EXEC A (HOST 10.1.11.111 trace


Then you can proceed with adding the printer to RSCS and setting up
something for the users to use (spool prt , tag device, maybe wrapped in
a nice exec ).


Marcy  
"This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."

FW: IP printing from VM

[Jones, Ian H]

 
> You still need to tell RSCS what link to process the file on. The LPR
exec uses
> link name LPR by default.  Per chance, did you group LPR1, LPR2, 
> etc together as ndoe LPR?

No, I haven't looked at grouping printers yet. 

I tried to specify a printer name and host IP address as the target, and
got the same error -

lpr profile exec a (asynchronous printer qeeple22

PRT FILE 0094 SENT TO   RSCS RDR AS  0037 RECS 0050 CPY  001 A
NOHOLD NOKEEP
RDR FILE 0095 SENT FROM RSCS RDR WAS 0037 RECS 0050 CPY  001 A
NOHOLD NOKEEP
 DMTAXM103E File 0037 (0037) rejected -- invalid destination address

Ready; T=0.04/0.04 13:10:41


lpr profile exec a (asynchronous host 10.120.72.245

PRT FILE 0096 SENT TO   RSCS RDR AS  0038 RECS 0050 CPY  001 A
NOHOLD NOKEEP
RDR FILE 0097 SENT FROM RSCS RDR WAS 0038 RECS 0050 CPY  001 A
NOHOLD NOKEEP
 DMTAXM103E File 0038 (0038) rejected -- invalid destination address

Ready; T=0.04/0.04 13:11:16


tag query file 95

LPR

Ready; T=0.01/0.01 13:12:54


tag query file 97

LPR

Ready; T=0.01/0.01 13:12:59


If my mistake is obvious then please point it out, but I think I can use
tag/spool/print to send output anyway.
 
 

Best regards
Ian Jones

Re: IP printing from VM

[Les Geer (607-429-3580)]

>OK, I'll bite.  I was hoping someone else would ask.
>
>How do you code a continuation on a TAG stmt and is it only for the RSCS
>use of TAG.  I looked in RSCS HELP as well as CP HELP and see no mention
>of continuation.
>

Statements in the RSCS config can be continued on multiple lines.
The default continuation character is #.
However, TAG is not a configuration file statement.

By the way, the other threads in this append chain.   You still need
to tell RSCS what link to process the file on.   The LPR exec uses
link name LPR by default.  Per chance, did you group LPR1, LPR2, etc
together as ndoe LPR?
Finally. RSCS supplies a similar exec called PPS that you may want to
try out.  HELP PPS or PPS ? will provide additional details.

Best Regards,
Les Geer
IBM z/VM and Linux Development

Re: IP printing from VM

[Jim Bohnsack]

OK, I'll bite.  I was hoping someone else would ask.

How do you code a continuation on a TAG stmt and is it only for the RSCS 
use of TAG.  I looked in RSCS HELP as well as CP HELP and see no mention 
of continuation.


Jim (never too old to learn) Bohnsack

Jones, Ian H wrote:


And after a lifetime of using RSCS I have been shown that there is a
continuation character for PARM statements  ;-)
=20

Regards=20
Ian Jones=20
UKOSG - Infrastructure Specialist=20
EDS=20
ITO - UK mainframe Software Services=20
4 Roundwood Avenue=20
Uxbridge, UB11 1BQ=20
 =20
Phone: +44 (0)7790 492056=20

mailto:[EMAIL PROTECTED]
http://www.mainframe.uk.eds.com  =20

This email contains information which is confidential and may be
privileged. Unless you are the intended addressee (or authorised to
receive for the addressee) you may not use, forward, copy or disclose to
anyone this email or any information contained in this email.  If you
have received this email in error, please advise the sender by reply
email immediately and delete this email.

Electronic Data Systems Ltd=20
Registered Office:, Lansdowne House, Berkeley Square, London  W1J 6ER=20
Registered in England no: 53419=20
VAT number: 432 99 5915=20

  


--
Jim Bohnsack
Cornell University
(607) 255-1760
[EMAIL PROTECTED]

Re: IP printing from VM

[David Boyes]

> Coding the TAG and SPOOL commands rather than using LPR EXEC has fixed
> the immediate problem. Thank you

And works better all around. 

> I'm not sure why the name of the link would need to be
> different to the printer name specified in the PARM statement, so I
have
> changed that.

Simple answer is that RSCS interprets the link name, and the remote LPD
interprets the printer name field. There's no connection between the two
naming spaces. If the remote end doesn't get a name it recognizes, then
printing won't happen. 

Re: IP printing from VM

[Jones, Ian H]

Coding the TAG and SPOOL commands rather than using LPR EXEC has fixed
the immediate problem. Thank you
 
I hit a socket problem -

DMTLPR083E Socket error on link XRXSTD request=Bind
DMTLPR083E return code=- 1 error number=13 (Permission denied)

but I found an answer in the archives, and I have specified SECURE=NO in
the EPARM field. I'm not sure why the name of the link would need to be
different to the printer name specified in the PARM statement, so I have
changed that. 

And after a lifetime of using RSCS I have been shown that there is a
continuation character for PARM statements  ;-)
 

Regards 
Ian Jones 
UKOSG - Infrastructure Specialist 
EDS 
ITO - UK mainframe Software Services 
4 Roundwood Avenue 
Uxbridge, UB11 1BQ 
  
Phone: +44 (0)7790 492056 

mailto:[EMAIL PROTECTED] 
http://www.mainframe.uk.eds.com   

This email contains information which is confidential and may be
privileged. Unless you are the intended addressee (or authorised to
receive for the addressee) you may not use, forward, copy or disclose to
anyone this email or any information contained in this email.  If you
have received this email in error, please advise the sender by reply
email immediately and delete this email.

Electronic Data Systems Ltd 
Registered Office:, Lansdowne House, Berkeley Square, London  W1J 6ER 
Registered in England no: 53419 
VAT number: 432 99 5915 

Re: IP printing from VM

[Fran Hensler]

Ian -
 
I've never been satisfied with the LPR command in CMS so I use these
commands:
 
cp spool print rscs
cp tag dev prt [printer name]
 
I have an EXEC that issues thes commands under the covers.
On a FILELIST screen the users types:SPRT / [printer name]
 
/Fran Hensler at Slippery Rock University of Pennsylvania USA for 45 years
 [EMAIL PROTECTED] +1.724.738.2153
"Yes, Virginia, there is a Slippery Rock"
 
 
 
On Tue, 10 Jun 2008 14:26:04 +0200 Jones, Ian H said:
>
>Guys,
>
>This is probably a stupid question, but it is getting urgent and I don't have
>any more time to play with it.
>
>We are trying to print to IP printers for the first time. This looks like it
>should have been a straight forward change; CMS users used to send output to
>type SNA3270P printers and now they want to send it to IP attached printers
>instead. There seems to be many different ways of specifying the printer name
>and IP address of the target printers and I chose what looks like the simplest.
>In the RSCS config I have coded -
>
>LINKDEFINE LPR1 TYPE LPR AST FORM *
>PARM LPR1 EXIT=LPRXONE EP='C=LPR' ITO=0 PR=QEEPLE22 US=YES HOST=10.120.72.245
>
>LINKDEFINE LPR2 TYPE LPR AST FORM *
>PARM LPR2 EXIT=LPRXONE EP='C=LPR' ITO=0 PR=QEEPLE29 US=YES HOST=10.120.73.222
>
>
>I am using the LPRXONE exit supplied in RSCSEXIT LOADLIB and the RSCSLPR CONFIG
>supplied with TCP/IP, because I don't (think I) have any additional
>requirements.. RSCS starts the printer links OK and then immediately
>deactivates
>them, presumably because I have specified ITO=0.
>
>So far, so good (?), but when I try to send a print file to them using LPR
>exec,
>RSCS rejects the file because it has an invalid destination address. I get the
>same result whether I use the printer name or the IP (host) address. LPR exec
>insists on using the default linkid (LPR) coded in the exec. I'm obviously
>missing something in the configuration of these things. Do I *need* a nicknames
>file ? I thought that these were one of the many options, rather than
>compulsory.
>
>
>Regards
>Ian Jones
>UKOSG - Infrastructure Specialist
>EDS
>ITO - UK mainframe Software Services
>4 Roundwood Avenue
>Uxbridge, UB11 1BQ
>
>Phone: +44 (0)7790 492056
>
>mailto:[EMAIL PROTECTED]
>http://www.mainframe.uk.eds.com
>
>This email contains information which is confidential and may be privileged.
>Unless you are the intended addressee (or authorised to receive for the
>addressee) you may not use, forward, copy or disclose to anyone this email or
>any information contained in this email.  If you have received this email in
>error, please advise the sender by reply email immediately and delete this
>email.
>
>Electronic Data Systems Ltd
>Registered Office:, Lansdowne House, Berkeley Square, London  W1J 6ER
>Registered in England no: 53419
>VAT number: 432 99 5915
>
>
>
>Received: from *unknown [130.184.5.241] by ZVM.SRU.EDU (IBM VM SMTP Level 3A0)
> via TCP with ESMTP ; Tue, 10 Jun 2008 08:26:40 EDT
>X-Warning: ZVM.SRU.EDU: Host *unknown claimed to be listserv.uark.edu

Re: IP printing from VM

[Mark Pace]

The most obvious question is, does RSCS have routing to these printers? Also
mine has a PRINTER= parm that I do not see on yours.
Mine
*
 LINKDEF XWC80 TYPE LPR  QUEUE FIFO FORM * AST
 PARM   XWC80 EXIT=LPRXONE #
 HOST=199.44.nnn.nn PRINTER=IP_199.44.nnn.nn #
  EPARM='S=NO SUFFIX=1B45 P=1B266C38441B287330501B266B3157'

On Tue, Jun 10, 2008 at 8:26 AM, Jones, Ian H <[EMAIL PROTECTED]> wrote:

>
> Guys,
>
> This is probably a stupid question, but it is getting urgent and I don't
> have any more time to play with it.
>
> We are trying to print to IP printers for the first time. This looks like
> it should have been a straight forward change; CMS users used to send output
> to type SNA3270P printers and now they want to send it to IP attached
> printers instead. There seems to be many different ways of specifying the
> printer name and IP address of the target printers and I chose what looks
> like the simplest. In the RSCS config I have coded -
>
> LINKDEFINE LPR1 TYPE LPR AST FORM
> *
> PARM LPR1 EXIT=LPRXONE EP='C=LPR' ITO=0 PR=QEEPLE22 US=YES HOST=
> 10.120.72.245
>
>
> LINKDEFINE LPR2 TYPE LPR AST FORM
> *
> PARM LPR2 EXIT=LPRXONE EP='C=LPR' ITO=0 PR=QEEPLE29 US=YES HOST=
> 10.120.73.222
>
> I am using the LPRXONE exit supplied in RSCSEXIT LOADLIB and the RSCSLPR
> CONFIG supplied with TCP/IP, because I don't (think I) have any additional
> requirements.. RSCS starts the printer links OK and then immediately
> deactivates them, presumably because I have specified ITO=0.
>
> So far, so good (?), but when I try to send a print file to them using LPR
> exec, RSCS rejects the file because it has an invalid destination address. I
> get the same result whether I use the printer name or the IP (host) address.
> LPR exec insists on using the default linkid (LPR) coded in the exec. I'm
> obviously missing something in the configuration of these things. Do I
> *need* a nicknames file ? I thought that these were one of the many options,
> rather than compulsory.
>
>
>
> Regards
> Ian Jones
> UKOSG - Infrastructure Specialist
> EDS
> ITO - UK mainframe Software Services
> 4 Roundwood Avenue
> Uxbridge, UB11 1BQ
>
> Phone: +44 (0)7790 492056
>
> *mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>
> *http://www.mainframe.uk.eds.com* 
>
> This email contains information which is confidential and may be
> privileged. Unless you are the intended addressee (or authorised to receive
> for the addressee) you may not use, forward, copy or disclose to anyone this
> email or any information contained in this email.  If you have received this
> email in error, please advise the sender by reply email immediately and
> delete this email.
>
> Electronic Data Systems Ltd
> Registered Office:, Lansdowne House, Berkeley Square, London  W1J 6ER
> Registered in England no: 53419
> VAT number: 432 99 5915
>
>


-- 
Mark Pace
Mainline Information Systems

IP printing from VM

[Jones, Ian H]

Guys,

This is probably a stupid question, but it is getting urgent and I don't have 
any more time to play with it.

We are trying to print to IP printers for the first time. This looks like it 
should have been a straight forward change; CMS users used to send output to 
type SNA3270P printers and now they want to send it to IP attached printers 
instead. There seems to be many different ways of specifying the printer name 
and IP address of the target printers and I chose what looks like the simplest. 
In the RSCS config I have coded -  

LINKDEFINE LPR1 TYPE LPR AST FORM * 
PARM LPR1 EXIT=LPRXONE EP='C=LPR' ITO=0 PR=QEEPLE22 US=YES HOST=10.120.72.245   

LINKDEFINE LPR2 TYPE LPR AST FORM * 
PARM LPR2 EXIT=LPRXONE EP='C=LPR' ITO=0 PR=QEEPLE29 US=YES HOST=10.120.73.222   


I am using the LPRXONE exit supplied in RSCSEXIT LOADLIB and the RSCSLPR CONFIG 
supplied with TCP/IP, because I don't (think I) have any additional 
requirements.. RSCS starts the printer links OK and then immediately 
deactivates them, presumably because I have specified ITO=0. 

So far, so good (?), but when I try to send a print file to them using LPR 
exec, RSCS rejects the file because it has an invalid destination address. I 
get the same result whether I use the printer name or the IP (host) address. 
LPR exec insists on using the default linkid (LPR) coded in the exec. I'm 
obviously missing something in the configuration of these things. Do I *need* a 
nicknames file ? I thought that these were one of the many options, rather than 
compulsory.
 

Regards
Ian Jones
UKOSG - Infrastructure Specialist
EDS
ITO - UK mainframe Software Services
4 Roundwood Avenue
Uxbridge, UB11 1BQ
 
Phone: +44 (0)7790 492056

mailto:[EMAIL PROTECTED]
http://www.mainframe.uk.eds.com

This email contains information which is confidential and may be privileged. 
Unless you are the intended addressee (or authorised to receive for the 
addressee) you may not use, forward, copy or disclose to anyone this email or 
any information contained in this email.  If you have received this email in 
error, please advise the sender by reply email immediately and delete this 
email.

Electronic Data Systems Ltd
Registered Office:, Lansdowne House, Berkeley Square, London  W1J 6ER 
Registered in England no: 53419
VAT number: 432 99 5915