|
midrange.com
After painfully RTFM, I have a slightly less muddled picture of
this. I have actually set up a pass-thru printer, which requires a
named outq on the remote system.
I've ended up with a workable solution, but it would have been much
better if CRTOUTQ RMTPRTQ(*USER) was supported. I can't see why
it's not. LPR (which sends one splf to a remote system) checks for
USERID on the remote as400 and directs output to the OUTQ specified
in the USRPRF. For whatever reason, printer pass-thru won't work
that way even though it uses LPR.
oh well! sorry if I was just wasting bandwidth today...
Eric DeLong
______________________________ Reply Separator _________________________________
Subject: RE: Re[2]: Config help - remote printer
Author: <MIDRANGE-L@midrange.com > at INET_WACO
Date: 10/22/98 1:09 PM
Eric.
I don't have any direct experience in setting up remote outqs for
AS/400
to AS/400 communications but I found the following. There is more
information in the OS/400 Printer Device Programming Manual. HTH.
2.3.5.1 Source System Activity - Creating the Remote Output Queue
The result of using this example would be spooled output files sent to
output queue OUTQRMT on the target system
(SYSNMDLC).
Type CRTOUTQ and prompt (F4). The following screen appears. Type in the
values shown and press the Enter key. The
remote output queue RMTOUTQ is created. The other parameter values are
needed to ensure connection and delivery to the
designated system.
+-----------------------------------------------------------------------
-----------+
|
|
| Create Output Queue (CRTOUTQ)
|
|
|
| Type choices, press Enter.
|
|
|
| Output queue . . . . . . . . . . RMTOUTQ Name
|
| Library . . . . . . . . . . . MYLIB Name, *CURLIB
|
| Maximum spooled file size:
|
| Number of pages . . . . . . . *NONE Number, *NONE
|
| Starting time . . . . . . . . Time
|
| Ending time . . . . . . . . . Time
|
| + for more values
|
| Order of files on queue . . . . *FIFO *FIFO, *JOBNBR
|
| Remote system . . . . . . . . . SYSNMDLC
|
| Remote printer queue . . . . . OUTQRMT
|
| Queue for writer messages . . . QSYSOPR Name, QSYSOPR
|
| Library . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB
|
| Connection type . . . . . . . . *SNA *SNA, *IP
|
| Destination type . . . . . . . . *OS400 *OS400, *OS400V2, *PSF2...
|
| Text 'description' . . . . . . . AS/400 V3R1 to AS/400 V3R1
|
|
|
|
|
|
Bottom |
| F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
|
| F13=How to use this display F24=More keys
|
|
|
|
|
+-----------------------------------------------------------------------
-----------+
To begin sending spooled output files from the RMTOUTQ remote output queue,
run the Start Remote Writer (STRRMTWTR)
command. Type STRRMTWTR and prompt (F4).
The following screen appears. Type in the values for the parameters
displayed and press the Enter key. Spooled output files
are then sent to the OUTQRMT on the target system (SYSNMDLC).
+-----------------------------------------------------------------------
-----------+
|
|
| Start Remote Writer (STRRMTWTR)
|
|
|
| Type choices, press Enter.
|
|
|
| Output queue . . . . . . . . . . RMTOUTQ Name, *ALL
|
| Library . . . . . . . . . . . stumpf Name, *LIBL, *CURLIB
|
| Queue for writer messages . . . *OUTQ Name, *OUTQ, *REQUESTER
|
| Library . . . . . . . . . . . Name, *LIBL, *CURLIB
|
| Form type options:
|
| Form type . . . . . . . . . . *ALL Form type, *ALL, *STD,
*FORMS |
| Message option . . . . . . . . *NOMSG *NOMSG, *INQMSG, *MSG...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bottom |
| F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
|
| F13=How to use this display F24=More keys
|
|
|
|
|
+-----------------------------------------------------------------------
-----------+
Eric Kempter
CommAir Mechanical Services, Inc.
-----Original Message-----
From: Eric DeLong [SMTP:eric.delong@pmsi-services.com]
Sent: Thursday, October 22, 1998 8:21 AM
To: MIDRANGE-L@midrange.com
Subject: Re[2]: Config help - remote printer
The printer is actually attached to 5394 as remote printer from
Dallas. I need an outq locally(waco) to communicate to the AS400 in
Dallas, which drives the printer in wherever(chicago?).
Since I have to use TCP/IP to talk to Dallas (going over frame
relay), I'm not sure how to pass spooled output from waco to
dallas, targeting the remote printer. LPD? (What I know about TCPIP
amounts to the proverbial "hill o' beans")
Preferably, I'd just like to create splf in waco, outq redirects to
dallas, then prints at remote site. Am I hopelessly lost here?
8(
Eric DeLong
______________________________ Reply Separator
_________________________________
Subject: RE: Config help - remote printer
Author: <MIDRANGE-L@midrange.com > at INET_WACO
Date: 10/21/98 4:53 PM
Specify the IP address of the interface to your printer (Jet Direct???) in
the configuration of your remote outq. Anything that goes in that queue
goes to that printer. Does that help or I have missed the jist of this
message entirely?
Eric Kempter
CommAir Mechanical Services, Inc.
-----Original Message-----
From: Eric DeLong [SMTP:eric.delong@pmsi-services.com]
Sent: Wednesday, October 21, 1998 3:13 PM
To: midrange-l@midrange.com
Subject: Config help - remote printer
OK folks, I'm feeling pretty dumb right now..... We're setting up access to
our
production system to a remote office. Heres the layout:
DSP/PRT(5394somewhere) <-(SNA)-> AS400(dallas) <-(TCP/IP via FR)->
AS400(waco)
As I understand it, we'll create a rmt outq in Waco, same name outq in
Dallas
that drives a remote printer at wherever. Is that right? Somehow, I've
developed
a mental block on the whole TCPIP printer thing. Anything I need to know?
We'll be using telnet to pasthru from Dallas to Waco for interactive
access.
Eric DeLong
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
