Printer Qeues

[nipun_2]

Hi,
we have vms 7.3-1 and a 3 node common environment cluster running on ethernet lan.

We have a generic printer qeue HPLJET_PS setup. Now often some applications start the print qeues. Sometimes the qeues go into pending stage and after certain point and time when I do
$ Show entry

It shows me a list of entries (including printing jobs). Out of these the print jobs simply don't print (or get executed).

The only thing that we do right now is do
del /en=(number) and manually delete each entry. If that still doesn't work then we reboot the entire system.

And again the whole process starts from entry =1 and now if we send anything to the printer it prints.

Is there a better way to stop printer queues an d restart them

I tried

$stop /que /reset HPLJET_PS
$init /que /start /generic=HPLJET_PS

however it just showed all the previous entries as "stopped" and the new entries I started after the initialization were simply pending.

Please let me know what would be the right way to restart the printer qeues.

Note: Our print jobs often consists of Images and our printer is a Laser jet HP 4000
Thanks in Advance.

[Volker Halle]

Nipun,

printers are driven by print-symbionts, which operate device execution queues. A generic queue is a higher-level structure, which accepts print-jobs and distributes them to execution queues.

You can stop an execution queue with STOP/QUE/RESET HPLJET_PS

And you can start it again with START/QUE HPLJET_PS


$init /que /start /generic=HPLJET_PS


This command is missing the target queue name parameter, that you want to start. The /GENERIC=HPLJET_PS qualifier specifies, that print-jobs submitted to this 'generic' queue (who's name you did not specify as a parameter) are to be sent to the execution queue HPLJET_PS.

If a print-job does not get printed, use SHOW ENT/FULL or SHOW QUE/ALL/FULL HPLJET_PS to find out the reason why.

Volker.

[Terry Yeomans · Accepted solution]

If you need to get rid of quite a few entries, then:
STOP /RESET /QUEUE queue_name
DELETE /QUEUE queue_name
Then @ the startup com file that creates your queue. Hope this helps. Terry.

[Mobeen_1]

Nipun,
There certainly is no need for rebooting the system every time you have an issue with the print queues. Can you please provide the following

$show queue/full HPLJET_PS
$show entry/full (this should give some reason for not printing)

regards
Mobeen

[nipun_2]

Hello Thanks for the replies.

I had a print problem again although this might might be because of a different nature

We have evaluation application which first uses

via generic que (sys$fast) assings to the execution queues (in order) SC4238_Fast,Salsa_Fast

These two exection queues goes to two different nodes and

I just changed the order of execution que so that Execut que is Salsa_Fast followed by SC4238_Fast.

To do that I did the following

stop /reset SYS$Fast
INIT /QUE /START /GENERIC =(SALSA_FAST,SC4238_FAST)
INIT /QUE /START /BATCH SALS_FAST

I did
Sh que /full /generic
sh en /full hpljet_ps
sh que /full hpljet_ps

I am attaching the files

[Lawrence Czlapinski]

Nipun:
It should be:
$INIT /QUE /START /GENERIC =(SALSA_FAST,SC4238_FAST) SYS$FAST
Lawrence

[nipun_2]

Hi Lawrence,
Thanks for the reply. I believe it did ask me for the generic que name and I gave
SYS$Fast so effectively same as
int..../generic = ... SYS$FAST





And I think it did work fine (at least the evaluations) but print outs
were the problem
Nipun

[Jan van den Ende]

Nipun,

I am just guessing now, but, are ALL your disks mounted on ALL your nodes? If yes, forget this. If NO, then consider: how could a queue process a file it cannot reach?

Proost.

Have one on me.

jpe

[nipun_2]

Thanks for the reply Jan,
But yeah all the disks are mounted

Nipun

[Jan van den Ende]

Nipun,

can you describe your 'issues' a bit more, please?

-- your print command, and then
-- sh que/all/ful
-- any messages?

Proost.

Have one on me.

jpe