Re: Printer Sharing


Hi,

this confuses me a little bit right now.

Can you print using "qprt -PHP4PCLloc <some_file>" on gargon command line
?
You are talking about that you cannot print "from a text editor".
Generally speaking you must "teach" (configure) your application which
print command to be used. So to figure out, where the problem is, first
test from command line (not using rembak directly) whether you can perform
a remote print. If a "qprt" works then check whether you defined the
"print" command correctly (Are you using any kind of X11/Dt text editor
? )

Hint: You can stop your queues using "qadm -D<queuename>" to see whether
files are queued or not (lpstat -p<queuename>). qadm -U<queuename> sets a
queue "up" again.

Regards,
Uwe Auer

Uwe on the issues you raised.
On gargan #qprt -HP4PCLloc /testg.txt placed the job on the queue in gargon
but it did not get transfered to oldage for printing.
The text editor is the one out of the CDE desktop in the Application Manager
suite not the text editor vi in the Desktop Tools suite. Its properties box
gives no info as to where it comes from. When I had my network printer
HP4500 going before it gave up the ghost just used to hit file/print/ok and
it printed okay. In the file/print window there is a box to put a path.
Sometimes one of the many commands I try will put the job into the print
queue in gargan but it does not get to oldage for printing.
Know the situation with the defunct HP4500 was a little different, true
network printer versus present situation of printer attatched to another
server.

On gargon the /etc/hosts.equiv and /etc/hosts.lpd are completely empty, this
correct ? oldage has gargan burrin bmwaust the clients in its two files.

On oldage in Smit/manage print server/listall remote clients the results are
Command Window
/usr/bin/ruser -sP; if [[ $? -eq 1 ]] then
/usr/bin/dspmsg -s 18 smit.cat 145 ' There are no clients with print access
'
fi
Output Window
gargan
bmwaust
burrin

Is there any significance to the message ' There are no clients with print
access '

In gargan with all queue's cleared
#lpstat -pHP4PCLloc shows
Queue Dev Status
HP4PCLl @olda DOWN
HP4PCLl HP4PC READY
running #qprt -HP4PCLloc /testg.txt then
running
#lpstat -pHP4PCLloc shows
Queue Dev Status
HP4PCLl @olda DOWN
QUEUED job13 /testg.txt
HP4PCLl HP4PC READY

Awe hope the above answered your questions sarisfactorily.

Hunting around the web found this
Remote Printing
To send print jobs to a remote print server, TCP/IP must be used. The flow
of a print job is as follows...

a.. Job is initiated using lpr or enq
b.. The /etc/qdaemon on the local machine processes the job and passes the
data to a the backend process /usr/lpd/rembak
c.. rembak transmits the job to the remote printer via TCP/IP
d.. On the remote server lpd, by monitoring port 515, receives and
processes the job to the selected printer
Multiple jobs submitted on a single command line to either a local or
remote print queue is NOT supported.

AIX is able to use remote queues with names longer than 7 characters in
length. In order for this to work, you need to define the backend of the
remote queue as follows:

backend = /usr/lpd/rembak -P <QueueName> -S <ServerName> -N

a.. The -P will work with queue names longer than 7 characters.
b.. The -N is needed to inhibit sending AIX-specific control information
to a non-AIX remote host
a.. /usr/lib/lpd/aixshort indicates the remote server is another AIX
machine.
b.. /usr/lib/lpd/aixlong indicates the remote server is another AIX
machine. (For long-form output)
c.. /usr/lib/lpd/bsdshort indicates the remote server is BSD4.3 or Linux
lpq printer queue
d.. /usr/lib/lpd/bsdlong indicates the remote server is BSD4.3 or Linux
lpq printer queue (For long-form output)
gargan's print queue is called HP4PCLloc, a total of 9 characters which
exceeds the 7 character limit suggested in the above article. This article
was from http://www.ahinc.com/aix/printer.htm .
Do you think it applies to my situation ? If so, would the command be run on
gargan or oldage or both ?
Was going to cancel all I had done from your original instructions and
refeed every thing in again trying a shorter queue
name for gargan but was not sure how to undo everything in oldage.

Regards
Basil


.

Relevant Pages

  • Re: How to pickup a message from a MSMQ queue from another box?
    ... MSMQt doesn't pickup from remote queues. ... How to pickup a message from a MSMQ queue from another box? ...
    (microsoft.public.biztalk.general)
  • RE: Receive Fucntions
    ... BizTalk MSMQ Receive Functions cannot monitor MSMQ queues on remote ... You will need to write an application on the MSMQ server that will write ... in the local outgoing queue and it is then transferred to the remote queue. ...
    (microsoft.public.biztalk.server)
  • Re: sendmail default queue settings
    ... them in from memory or whatever it is you're doing, sendmail won't log ... this is the remote responding with a "temporary failure" ... sendmail can only queue the message and try ... stat=Deferred: Connection timed ...
    (comp.mail.sendmail)
  • Re: RMTOUTQ question
    ... We use several zebras, and setting them up has been simple. ... Remote outqs use LPD, which routes print jobs by IP address, and named ... RAW rmtprtq needs to go through port 9100 for their bar code language ... RAW print queue. ...
    (comp.sys.ibm.as400.misc)
  • Re: RMTOUTQ question
    ... We use several zebras, and setting them up has been simple. ... Remote outqs use LPD, which routes print jobs by IP address, and named ... RAW rmtprtq needs to go through port 9100 for their bar code language ... RAW print queue. ...
    (comp.sys.ibm.as400.misc)